Ballot Details: Defer VIRTIO-167: Confusing "non-Transitional" conformance statement (CLOSED)

Ballot Question Should the TC defer issue VIRTIO-167 to after specification version(s) "virtio 1.1 cs01"?
Ballot 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-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.

--------------------------------------
Ballot Options
VOTING CLOSED: Thursday, 21 March 2019 @ 5:30 pm EDT
Yes 1 20
No 4 80
Abstain 1
Open Date Thursday, 14 March 2019 @ 5:30 pm EDT
Close Date Thursday, 21 March 2019 @ 5:30 pm EDT
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 5
Eligible members who have voted 6 of 6 100%
Eligible members who have not voted 0 of 6 0%

Voting Summary by Option

Options with highest number of votes are bold
Option # Votes % of Total
Yes 1 20%
No 4 80%
Abstain 1

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Pasic, Halil IBM Yes 2019-03-15 13:11:00 1
* Carabas, Mihai Oracle No 2019-03-15 07:39:00
* Hajnoczi, Stefan Red Hat No 2019-03-20 16:57:00
* Huck, Cornelia Red Hat No 2019-03-14 22:18:00 1
* Kiszka, Jan Siemens AG No 2019-03-15 06:41:00
* Tsirkin, Michael S. Red Hat Abstain 2019-03-14 21:50:00 1

Voter Comments

Submitter Vote Comment
Pasic, Halil
IBM
Yes My preferred solution, as addressing all the points VIRTIO-167 properly is to big at this stage.
Huck, Cornelia
Red Hat
No I do not think we need to defer addressing this issue.
Tsirkin, Michael S.
Red Hat
Abstain If my other option does not carry the day, this is my second preference.