search

oasis-tcs / openc2-apsc-stateless-packet-filter

OASIS OpenC2 TC: A GitHub repository is to provide configuration management and to aid in the development of the first generation OpenC2 firewall profile
https://github.com/oasis-tcs/openc2-apsc-stateless-packet-filter
Other
6 stars 10 forks source link

Set and then use language for distinguishing normative from non-normative content #39

Closed jmbrule closed 5 years ago

jmbrule commented 5 years ago

This is a tab comment 1638. It states "There is no description or use of language to distinguish normative from non-normative text, including appendices. Sections 1.6, 1.7 and 1.8 for instance. But there are other notes, examples, appendices, all of which should be non-normative."

dlemire60 commented 5 years ago

I went looking at some recently announced committee specifications to see how they dealt with identifying normative / non-normative content, per the TAB comments we received on all three specifications. What I see: 1) The Universal Business Language OASIS Standard appends appropriate section headers with "(Non-normative)" 2) The OSLC Architecture Management committee specs tag non-normative sections only with This section is non-normative. immediately after the section header 3) The TOSCA committee spec embeds words about normative or non- into the intro text for each major section (1.0, 2.0), for example "Except for the examples, this section is normative and ..."

Chet Ensign indicate a preference for approach #2, which I also like. Based on the examples I've looked at, it seems to be acceptable to identify just the non-normative sections, leaving everything else as implicitly normative. I'm going to create a pull request for the HTTPS spec using this approach.

jmbrule commented 5 years ago

Attempted to resolve with pull request 53 https://github.com/oasis-tcs/openc2-apsc-stateless-packet-filter/pull/53

jmbrule commented 5 years ago

Closed per Jan 30 AP-SC meeting