I will talk with staff about that. It isn't standard practice so I want to think carefully about adding it into the stream of published links.
I see that you have it listed on the main TC page so that is one consistent place where people look.
In any case, I'll get back to you on this.
/chet
On Tue, Feb 16, 2016 at 11:22 AM, Michael S. Tsirkin <
> wrote:
On Tue, Feb 16, 2016 at 11:05:28AM -0500, Chet Ensign wrote: >
> But can something be done for existing spec until we release CS04? >
> Not now, no. We don't go back and change content once published on
> docs.oasis-open.org . That would be effectively changing history and we feel it
> is critical to our large communities of developers, implementers and users that
> once a spec is published it will not change.
Oh well. Any chance you can maintain unversioned latest links, e.g. http://docs.oasis-open.org/virtio/virtio/latest/final/virtio-latest.html
http://docs.oasis-open.org/virtio/virtio/latest/final/virtio-latest.pdf
?
> On Tue, Feb 16, 2016 at 10:32 AM, Michael S. Tsirkin <
> wrote: >
> On Tue, Feb 16, 2016 at 10:16:10AM -0500, Chet Ensign wrote: >
> Hi Michael, > > >
> Well, I can see the confusion you mention. In your case, at least the
> CS03 is >
> visible there as the Previous version. And generally speaking, we don't
> usually >
> have a situation like VIRTIO where a CS goes back into production as a
> draft >
> and winds up approved as a new CS. So this situation is uncommon. > > >
> That said, if Latest version pointed to CS03, how would anyone know that
> work >
> was continuing under a new CSD? Potential for confusion there as well. > > >
> Our procedure is to use Latest version to point to whatever the most
> current >
> stage of the evolution of the specification has reached. That way,
> someone who >
> happens to have a local copy of CS02 for example, and the spec is now a >
> Candidate OASIS Standard, will get that most current incarnation of the
> spec >
> when the ask for the Latest version. > > >
> One way to solve this though would be, under Related work, to indicate
> that > > > > "This specification updates: >
> Virtual I/O Device (VIRTIO)
Version 1.0. Edited by Rusty Russell, Michael
> S. >
> Tsirkin, Cornelia Huck, and Pawel Moll. 02 August 2015. OASIS Committee >
> Specification 03. http://docs.oasis-open.org/virtio/virtio/v1.0/cs03/
>
> virtio-v1.0-cs03.html." >
> Our next version will likely be CS04 so it won't be a problem then.
> But can something be done for existing spec until we release CS04? > > > >
> So that way it would be made clear on page 1 of the spec. That's probably
> a >
> good idea for the cases like this where a CSPRD has followed an OASIS >
> deliverable. > > >
> What do you think? > > > > /chet > >
> What I *really* think is that we would like to have a non-versioned
> latest final deliverable link:
> http://docs.oasis-open.org/virtio/virtio/latest/final/virtio-latest.html
> http://docs.oasis-open.org/virtio/virtio/latest/final/virtio-latest.pdf
>
> Then we could stop releasing new CS versions after CS04, and increment
> the version number instead. >
> As it is we are forced to release CS versions, otherwise people
> following "latest" link in the document won't find the latest spec. > > > > > > >
> On Tue, Feb 16, 2016 at 4:16 AM, Michael S. Tsirkin < >
> wrote: > > >
> Hi Chet, >
> I noticed that the latest versions: >
> http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html
>
> http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.pdf
>
> Have been replaced with the csprd05 version as well. > > >
> This seems to confuse people: they arrive >
> at the latest version link, see that it's a draft, >
> and assume that no final deliverable has been >
> created yet. > > >
> I think that virtio-1.0 should point at CS03, >
> don't you agree? > > >
> On Tue, Jan 12, 2016 at 09:49:01AM -0500, Chet Ensign wrote: > >
> In last nights announcement of the public review for Virtual I/O
> Device > > > (VIRTIO)
Version 1.0, I stated that "This public review draft makes >
> changes to > >
> Committee Specification 03. The changes are tracking in the
> red-line file >
> at > >
> http://docs.oasis-open.org/virtio/virtio/v1.0/cs03/
>
> virtio-v1.0-cs03-diff.html." > >
> The correction location for the red-line file is http:// >
> docs.oasis-open.org/
> >
> virtio/virtio/v1.0/csprd05/virtio-v1.0-csprd05-diff.html. My
> apologies to >
> all > >
> for the error. > > > > >
> Best, > > > > > > /chet > > > > >
> On Mon, Jan 11, 2016 at 8:28 PM, Chet Ensign <
> > > >
> wrote: > > > > >
> OASIS members and other interested parties, > > > > >
> The OASIS Virtual I/O Device (VIRTIO)
TC members [1] have
> produced an > >
> updated Committee Specification Draft (CSD) and submitted this > >
> specification for 15-day public review: > > > > >
> Virtual I/O Device (VIRTIO)
Version 1.0 > >
> Committee Specification Draft 05 / Public Review Draft 05 > >
> 29 October 2015 > > > > >
> Specification Overview: > > > > >
> This document describes the specifications of the "virtio"
> family of > >
> devices. These devices are found in virtual environments, yet
> by >
> design > >
> they are not all that different from physical devices, and this >
> document > >
> treats them as such. This allows the guest to use standard
> drivers >
> and > >
> discovery mechanisms. > > > > >
> The purpose of virtio and this specification is that virtual >
> environments > >
> and guests should have a straightforward, efficient, standard
> and > >
> extensible mechanism for virtual devices, rather than boutique > >
> per-environment or per-OS mechanisms. > > > > >
> Public Review Period: > > > > >
> The public review starts 12 January 2016 at 00:00 UTC and ends
> 26 >
> January > >
> 2016 at 11:59 UTC. This public review draft makes changes to >
> Committee > >
> Specification 03. The changes are tracking in the red-line file
> at >
> http:// > >
> docs.oasis-open.org/virtio/virtio/v1.0/cs03/
>
> virtio-v1.0-cs03-diff.html. > > > > >
> This is an open invitation to comment. OASIS solicits feedback
> from > >
> potential users, developers and others, whether OASIS members
> or not, >
> for > >
> the sake of improving the interoperability and quality of its >
> technical > >
> work. > > > > >
> URIs: > >
> The prose specification document and related files are
> available >
> here: > > > > >
> Editable source (Authoritative): > >
> http://docs.oasis-open.org/virtio/virtio/v1.0/csprd05/tex/
> > > > >
> HTML: > >
> http://docs.oasis-open.org/virtio/virtio/v1.0/csprd05/
> >
> virtio-v1.0-csprd05.html > > > > >
> PDF: > >
> http://docs.oasis-open.org/virtio/virtio/v1.0/csprd05/
> >
> virtio-v1.0-csprd05.pdf > > > > >
> Example Driver Listing: > >
> http://docs.oasis-open.org/virtio/virtio/v1.0/csprd05/listings/
> > > > >
> ZIP distribution files (complete): > > > > >
> For your convenience, OASIS provides a complete package of the
> prose > >
> specification and related files in a ZIP distribution file. You
> can > >
> download the ZIP file here: > > > > >
> http://docs.oasis-open.org/virtio/virtio/v1.0/csprd05/
> >
> virtio-v1.0-csprd05.zip > > > > >
> Additional information about this specification and the VIRTIO
> TC may >
> be > >
> found on the TC's public home page located at: > > > > >
> http://www.oasis-open.org/committees/virtio/
> > > > >
> Comments may be submitted to the TC by any person through the
> use of >
> the > >
> OASIS TC Comment Facility which can be accessed via the button >
> labeled > > > "Send A Comment" at the top of the TC public home page, or
> directly >
> at: > > > > >
> http://www.oasis-open.org/committees/comments/form.php ?
> wg_abbrev= >
> virtio > > > > >
> Feedback submitted by TC non-members for this work and for
> other work >
> of > >
> this TC is publicly archived and can be viewed at: > > > > >
> http://lists.oasis-open.org/archives/virtio-comment/
> > > > >
> All comments submitted to OASIS are subject to the OASIS
> Feedback >
> License, > >
> which ensures that the feedback you provide carries the same >
> obligations at > >
> least as the obligations of the TC members. In connection with
> this >
> public > >
> review of 'Virtual I/O Device (VIRTIO)
Version 1.0', we call
> your >
> attention > >
> to the OASIS IPR Policy [2] applicable especially [3] to the
> work of >
> this > >
> technical committee. All members of the TC should be familiar
> with >
> this > >
> document, which may create obligations regarding the disclosure
> and > >
> availability of a member's patent, copyright, trademark and
> license >
> rights > >
> that read on an approved OASIS specification. > > > > >
> OASIS invites any persons who know of any such claims to
> disclose >
> these if > >
> they may be essential to the implementation of the above >
> specification, so > >
> that notice of them may be posted to the notice page for this
> TC's >
> work. > > > > > >
==========
Additional references: > > > > > > [1] OASIS Virtual I/O Device (VIRTIO)
TC > >
> http://www.oasis-open.org/committees/virtio/
> > > > > > [2] http://www.oasis-open.org/policies-guidelines/ipr
> > > > > > [3] http://www.oasis-open.org/committees/virtio/ipr.php
> >
> https://www.oasis-open.org/policies-guidelines/ipr#
> licensing_req > >
> Non-Assertion Mode > > > > > > -- > > > > > > /chet > > >
----------------
> >
> Chet Ensign > >
> Director of Standards Development and TC Administration > >
> OASIS: Advancing open standards for the information society > >
> http://www.oasis-open.org
> > > > >
> Primary: +1 973-996-2298
> >
>
Mobile: +1 201-341-1393 > > > > > > > > > > > > > > > -- > > > > > > /chet > > >
----------------
> >
> Chet Ensign > >
> Director of Standards Development and TC Administration > >
> OASIS: Advancing open standards for the information society > >
> http://www.oasis-open.org
> > > > >
> Primary: +1 973-996-2298
> >
>
Mobile: +1 201-341-1393 > > > > > > > > > > -- > > > > /chet > >
----------------
>
> Chet Ensign >
> Director of Standards Development and TC Administration >
> OASIS: Advancing open standards for the information society >
> http://www.oasis-open.org
> > >
> Primary: +1 973-996-2298
>
>
Mobile: +1 201-341-1393 > > > > > -- > > /chet >
----------------
> Chet Ensign
> Director of Standards Development and TC Administration
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> Primary: +1 973-996-2298
>
Mobile: +1 201-341-1393
--
/chet
----------------
Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
