New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change requirements tagging #314

Closed
jyutzler opened this Issue Mar 10, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@jyutzler
Contributor

jyutzler commented Mar 10, 2017

Per Scott Simmons:

Requirements: per TC guidance, requirement numbers are now persistent. GeoPackage uses a custom block type that automatically sequentially numbers requirements. These will need to have fixed numbering going forward, so any requirements deleted in 1.2 will need to be “skipped” and inserted requirements come from the end of the list of available sequential numbers. Our new Asciidoc standard template has a method to store requirements each in a separate file. However, for GeoPackage I can give you a new block definition style (based on an Example) that will allow cross-referencing and compile nicely. See below:

[[r1]]
[caption=""]
.Requirement 1
====
requirement text, blah blah blah
====

This will require some manual work but we can do it while retaining existing requirement numbers.

@jyutzler

This comment has been minimized.

Contributor

jyutzler commented Mar 17, 2017

One side-effect of this change is that requirements numbers will go back to what they were in 1.1. Before this fix, the requirements numbers in the extensions were different. New requirements numbers will be added to new sections - Attributes and the elevation extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment