[OASIS Issue Tracker] (VIRTIO-77) Conformance clause

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://tools.oasis-open.org/issues/browse/VIRTIO-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Tsirkin updated VIRTIO-77:
----------------------------------

    Fix Version/s: virtio 1.0 csprd02
      Description: 
9 Conformance reads:

*****
An implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level requirements defined within this specification. 
*****

8(a) of the TC Process (https://www.oasis-open.org/policies-guidelines/tc-process#specQuality) defines conformance clauses as:

*****
A specification that is approved by the TC at the Committee Specification Public Review Draft, Committee Specification or OASIS Standard level must include a separate section, listing a set of numbered conformance clauses, to which any implementation of the specification must adhere in order to claim conformance to the specification (or any optional portion thereof).
*****

Reference to all the "MUST or REQUIRED" level requirements does not meet the requirements of the TC process. 

First, "requirements for conformance" are not limited to "MUST or REQUIRED." RFC2119 allows a great deal of flexibility that should not be ignored in writing normative text. By ignoring "SHOULD" for example, does the TC contemplate implementers just making it up as they go along? I thought not. 

Second, just on my cursory scan of the specification, I can see there are at least two levels of conformance, legacy verus non-legacy but I am not familiar enough with the area to map the classes of conformance.

  was:
9 Conformance reads:

*****
An implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level requirements defined within this specification. 
*****

8(a) of the TC Process (https://www.oasis-open.org/policies-guidelines/tc-process#specQuality) defines conformance clauses as:

*****
A specification that is approved by the TC at the Committee Specification Public Review Draft, Committee Specification or OASIS Standard level must include a separate section, listing a set of numbered conformance clauses, to which any implementation of the specification must adhere in order to claim conformance to the specification (or any optional portion thereof).
*****

Reference to all the "MUST or REQUIRED" level requirements does not meet the requirements of the TC process. 

First, "requirements for conformance" are not limited to "MUST or REQUIRED." RFC2119 allows a great deal of flexibility that should not be ignored in writing normative text. By ignoring "SHOULD" for example, does the TC contemplate implementers just making it up as they go along? I thought not. 

Second, just on my cursory scan of the specification, I can see there are at least two levels of conformance, legacy verus non-legacy but I am not familiar enough with the area to map the classes of conformance. 


       Resolution: Passed in minutes of 2014-02-25 meeting, committed as r262-r278 inclusive.  (was: Passed in minutes of 2014-02-25 meeting, committed as r262-r278 inclusive. )

> Conformance clause
> ------------------
>
>                 Key: VIRTIO-77
>                 URL: https://tools.oasis-open.org/issues/browse/VIRTIO-77
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Bug
>         Environment: Conformance
>            Reporter: Patrick Durusau
>            Assignee: Rusty Russell
>             Fix For: virtio 1.0 csprd02
>
>
> 9 Conformance reads:
> *****
> An implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level requirements defined within this specification. 
> *****
> 8(a) of the TC Process (https://www.oasis-open.org/policies-guidelines/tc-process#specQuality) defines conformance clauses as:
> *****
> A specification that is approved by the TC at the Committee Specification Public Review Draft, Committee Specification or OASIS Standard level must include a separate section, listing a set of numbered conformance clauses, to which any implementation of the specification must adhere in order to claim conformance to the specification (or any optional portion thereof).
> *****
> Reference to all the "MUST or REQUIRED" level requirements does not meet the requirements of the TC process. 
> First, "requirements for conformance" are not limited to "MUST or REQUIRED." RFC2119 allows a great deal of flexibility that should not be ignored in writing normative text. By ignoring "SHOULD" for example, does the TC contemplate implementers just making it up as they go along? I thought not. 
> Second, just on my cursory scan of the specification, I can see there are at least two levels of conformance, legacy verus non-legacy but I am not familiar enough with the area to map the classes of conformance.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)