|
Should the TC accept changes listed in the description to resolve issue VIRTIO-168,
for inclusion in specification version(s) "virtio 1.1 cs01", and future versions of the specification?
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 resolve the following specification issue:
VIRTIO-168: Conformance clause clarification, about the names of profiles of conformance (and their combinations)
--------------------------------------
Overall, well-formed conformance section (one of the best we TAB reviewers have seen!) The main conformance targets - drivers, devices - are well identified. The specification is clearly attributing normative requirements to either driver, or device.
Some conformance aspects could still be clarified:
* All the subsections under 7.2 or 7.3 are named "clauses" in 7.1. So their titles should be "Clause XYZ". Or else if we want to keep "CLause" to only the top-level set of requirements - then define just a couple of clauses in 7.1, e.g. "Conformance Clause for VIRTIO1.1 drivers". Then all thee following subsections should just be titled "Conformance requirements sets" e.g. "COnformance requirements for PCI drivers"), and preferably not "clause" (keeping "clause" for only the full set of requirements that a product can claim for conformance).
* In any case, it is good to associate a clear name to each conformance level/profile that can be claimed. For example, "PCI network driver" (if satisfying 7.2 + 7.2.1 + 7.2.4. Is that a meaningful combination? irt seems so according to 7.1). So that there is no ambiguity of what are the valid conformance profiles. Some parameterization of a clause can be used: Look in TAB guideline : [http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html] for "variable conformance clauses" (section 5.5). In other words: define the precise statement that someone should use when claiming a conformance profile.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio/201903/msg00027.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.1 cs01", and future versions of the
specification.
--------------------------------------
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.
--------------------------------------
|
