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-167: Confusing "non-Transitional" conformance statement
--------------------------------------
We read in 7.4:
"A non-transitional implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level requirements defined above. "
Is that true? ALL the "MUST" in all previous sections? Probably not. Or maybe it is "below" and not "above". (always explicitly refer to requirements sets by using a sub-section number & name)
I suggest to make "transitional" just a variable (i.e. a parameter) in previous top-level conf clauses. (see TAB conformance guideline [http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html, section 5.5) |http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html)]E.g. someone claiming conformance as "PCI driver" should always clarify: "transitional PCI driver" or "non-transitional PCI driver"
--------------------------------------
The TC agrees that the issue will not be resolved for the revision
"virtio-v1.1-cs01" of the specification.
Justification:
--------------------------------------
The issue seems minor.
It seems that we should look at reworking this section going forward
so it is not clear making changes to it is justified.
Further the issue is not new and is present 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.
-------------------------------------- |
