OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (VIRTIO-178) Normative vs. Non-Normative text unmarked


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

Michael S. Tsirkin updated VIRTIO-178:
--------------------------------------
    Affects Version/s: virtio 1.1 cs01

> Normative vs. Non-Normative text unmarked
> -----------------------------------------
>
>                 Key: VIRTIO-178
>                 URL: https://issues.oasis-open.org/browse/VIRTIO-178
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Bug
>    Affects Versions: virtio 1.1 cs01
>         Environment: Normative
>            Reporter: Patrick Durusau
>            Priority: Major
>
> 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.
> Â



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]