Closed jensmaurer closed 3 years ago
My guess is that ISO/CS was text-searching for the normative references and looking for a "shall" in the immediate vicinity. Given that we usually don't do "shall" for requirements on implementations, that check probably failed.
I've asked for clarification on which specific normative references they are referring to. My guess is that there are certain comments (001, 002, 012, 017) that they always provide, without really checking whether they're relevant.
@zygoloid , The edited DIS document provided for CS016 #392 has highlighting for the specific normative references they feel are not properly referenced. I've updated the text above with specifics.
Analysis of "normative references" marked in the edited DIS:
Final disposition: Accepted with modifications: References to ISO/IEC/IEEE 60559:2011 and UAX#29 have been moved to the Bibliography; the date and mention of "parts" of ISO/IEC 2382 has been removed, and the normative relevance of ISO 8601:2004 has been called out.
ISO/IEC, Directives, Part 2, 15.5.2: "Only documents referred to in the text shall be listed in Clause 2." ISO/IEC, Directives, Part 2, 15.5.3: "Only references cited in the text in such a way that some or all of their content constitutes requirements of the document shall be listed in the Normative references clause."
The normative references list is not just a list of important documents. It lists the references that are part of the requirements of the document. Please remove the concerned reference(s) to the Bibliography or cite them explicitly as a requirement (shall) in the text, as indicated in the DIS edited text.
Specifically: