Description
Please vote Yes if you agree with all of the following. If you disagree, please vote No. If you don't have an opinion, please vote Abstain. I move that: The TC agrees to defer resolving the following specification issue: VIRTIO-178: Normative vs. Non-Normative text unmarked -------------------------------------- I'm assuming that 1 Introduction, your "for example" under 1.4 Structure Specifications, and at least some of the 62 Notes: are non-normative, but have not been so marked or described. That is you can use non-normative on a section heading and/or say: All notes are non-normative. In particular I have in mind notes like: 4.1.5.1.2.1 "Note: For example, a device which does not expect to send interrupts at a high rate might only specify 2 MSI-X vectors." In terms of conformance to this specification, clearly non-normative language. As are many of the remaining 61 uses of note. -------------------------------------- The TC agrees that the issue will not be resolved for the revision "virtio-v1.1-cs01" of the specification. Justification: -------------------------------------- There does not appear any bona fide confusion: reporter had no trouble understanding that a note with "for example" is a non-normative one, while a note with a "MUST" is a normative one. The issue is also present in the same form in virtio-v1.0-cs04. -------------------------------------- -------------------------------------- Reminder: A Voting Member must be active in a TC to maintain voting rights. As the Virtio TC has adopted a standing rule to conduct business only by electronic ballot, without Meetings, a Voting Member who fails to cast a ballot in two consecutive Work Product Ballots loses his or her voting rights at the close of the second ballot missed. --------------------------------------
