-
Notifications
You must be signed in to change notification settings - Fork 4
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
publish to leaf topics only (#137) #146
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to talk with TT-NWPMD first. Topics in that team were created with the knowledge that they did not have to go down to the last leaf...
@efucile is this suitable for fast track? this is the addition of new practices (SHALL) and not just code table entries. Previously used valid topics will become invalid. |
@@ -5,4 +5,6 @@ | |||
^|A |Data SHALL NOT be published with a topic that is not defined in this specification. | |||
^|B |Data SHALL be published to at least the level of the sub-discipline topic (level 8 or beyond). | |||
^|C |Metadata SHALL be published to at least the level of the notification type (``metadata``). | |||
^|D |Topics SHALL be published to the lowest possible defined level (leaf). | |||
^|E |Topics SHALL NOT be published to intermediary levels where sublevels are defined. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rows 8 and 9 are new standard practices / provisions that will lead to previously valid topics becoming invalid. I'm not sure this is suitable for the FT process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the addition requirements do not align with requirement B
Fixes #137
I've also renamed the "Publishing guidelines" section to just "Publishing" (i.e. requirements != guidelines).