OASIS Virtual I/O Device (VIRTIO) TC

Chet, Paul, Attached please find packaged csd01 and csprd01. PDF, HTML and extra files (tex source and listings) are included. The source in pushed on SVN. I hope I've addressed all the issues you have pointed out. If possible, please review and respond on this Monday so we have time to fix remaining issues before our call this Tuesday: we would like to vote on both CSD and CSPRD and starting the public review period. Thanks! -- MST

"Michael S. Tsirkin" <mst@redhat.com> writes: > Chet, Paul, > Attached please find packaged csd01 and csprd01. > PDF, HTML and extra files (tex source and listings) are included. > The source in pushed on SVN. > I hope I've addressed all the issues you have pointed out. > > If possible, please review and respond on this Monday so we have > time to fix remaining issues before our call this Tuesday: > we would like to vote on both CSD and CSPRD and starting > the public review period. > > Thanks! You're missing the attachment? Cheers, Rusty.

On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: > Chet, Paul, > Attached please find packaged csd01 and csprd01. > PDF, HTML and extra files (tex source and listings) are included. > The source in pushed on SVN. > I hope I've addressed all the issues you have pointed out. > > If possible, please review and respond on this Monday so we have > time to fix remaining issues before our call this Tuesday: > we would like to vote on both CSD and CSPRD and starting > the public review period. > > Thanks! Here are the attachments. > -- > MST Attachment: virtio-v1.0-csd01.zip Description: Zip archive Attachment: virtio-v1.0-csprd01.zip Description: Zip archive

"Michael S. Tsirkin" <mst@redhat.com> writes: > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: >> Chet, Paul, >> Attached please find packaged csd01 and csprd01. >> PDF, HTML and extra files (tex source and listings) are included. >> The source in pushed on SVN. >> I hope I've addressed all the issues you have pointed out. >> >> If possible, please review and respond on this Monday so we have >> time to fix remaining issues before our call this Tuesday: >> we would like to vote on both CSD and CSPRD and starting >> the public review period. >> >> Thanks! > > > Here are the attachments. Updated with a little more polish, as discussed on mailing lists. We'd still do well to tighten the language in the bus-specific and device-specific sections, but this is sufficient for draft 1 I feel. Cheers, Rusty. Attachment: virtio-v1.0-csd01.zip Description: Zip archive Attachment: virtio-v1.0-csprd01.zip Description: Zip archive

On Mon, Dec 02, 2013 at 11:25:02PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst@redhat.com> writes: > > > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: > >> Chet, Paul, > >> Attached please find packaged csd01 and csprd01. > >> PDF, HTML and extra files (tex source and listings) are included. > >> The source in pushed on SVN. > >> I hope I've addressed all the issues you have pointed out. > >> > >> If possible, please review and respond on this Monday so we have > >> time to fix remaining issues before our call this Tuesday: > >> we would like to vote on both CSD and CSPRD and starting > >> the public review period. > >> > >> Thanks! > > > > > > Here are the attachments. > > Updated with a little more polish, as discussed on mailing lists. I don't see it pushed on svn, I think you forgot. I'll extract and commit. > We'd still do well to tighten the language in the bus-specific and > device-specific sections, but this is sufficient for draft 1 I feel. > > Cheers, > Rusty. >

Hi Rusty,  I will review it today.  /chet On Mon, Dec 2, 2013 at 7:55 AM, Rusty Russell < rusty@au1.ibm.com > wrote: "Michael S. Tsirkin" < mst@redhat.com > writes: > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: >> Chet, Paul, >> Attached please find packaged csd01 and csprd01. >> PDF, HTML and extra files (tex source and listings) are included. >> The source in pushed on SVN. >> I hope I've addressed all the issues you have pointed out. >> >> If possible, please review and respond on this Monday so we have >> time to fix remaining issues before our call this Tuesday: >> we would like to vote on both CSD and CSPRD and starting >> the public review period. >> >> Thanks! > > > Here are the attachments. Updated with a little more polish, as discussed on mailing lists. We'd still do well to tighten the language in the bus-specific and device-specific sections, but this is sufficient for draft 1 I feel. Cheers, Rusty. -- /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  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Michael, Rusty, Cornelia, Pawel -  Thanks for putting this together so that we could give you feedback. Overall it looks excellent and these are mainly minor changes. The first ones in the content should be made before you approve the working draft. Then the second and third sections spell out updates to make to create the Committee Specification Draft and the Committee Specification Public Review Draft versions of the spec.  1) In the content itself:    -- In Appendix A. Acknowledgements, add the TC members. The section must be populated before the TC approves the WD.    -- If you have no Non-Normative References then remove the empty section 1.3.    -- Any place in the content that you link to urls on docs.oasis-open.org/. .. you will need to update them with the same changes as specified below. So, for example, section 7 virtio_ring.h includes a link to http://docs.oasis-open.org/virtio/virtio/1.0/wd01/listings/virtio_ring.h . You will want to change that to http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/listings/virtio_ring.h . for the Committee Spec Draft copy and http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/listings/virtio_ring.h . for the Committee Spec Draft / Public Review Draft version.    -- We recommend numbering footnotes sequentially from start to finish to avoid problems with the HTML footnotes.       Also, we note that in the HTML version supplied, there were not foot notes, even though they appear in the PDF version.    -- In the HTML document, the cover page links should be the same as the PDF. The current review draft has different Specification URIs on the cover page than does the PDF -- and the PDF ones are in the correct form.    -- If possible, in the PDF, align the left margins. That is, align "This version:" etc. with "Specification URIs". Not aligned now.    -- In the HTML, the rule (horizontal line) is not present above the Appendix section titles. Please add that.  2) After the TC votes to approve the WD as a CSD:    -- Change "Working Draft" to "Committee Specification Draft 01"    -- Change the date "05 Nov 2013" to the date the TC voted to approve and spell out the full month. E.g. "03 December 2013"    -- In the URIs change "wd01" to "csd01". Also, change "/1.0/" to "/v1.0/". Don't miss changing it in the link as well as in the visible text. So, for example, " http://docs.oasis-open.org/virtio/virtio/1.0/wd01/virtio-v1.0-wd01.pdf (Authoritative)" gets changed to " http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf (Authoritative)".    -- Also make these URI updates to the links under "Additional artifacts" and "Citation format".    -- Under "Additional artifacts", change the word "which" to "that".    -- In the footer, also change the date from "05 Nov" to the approval date with the month fully spelled out.    -- Under "Status", the first sentence should change from "… or approved by the members of OASIS…" to "… or approved by the Virtual I/O Device (VIRTIO) TC…"    -- Under "Citation format", the date should change to the approval date, e.g. "03 December 2013." "OASIS Standard" should change to "OASIS Committee Specification Draft 01." and the link should be changed from "wd01" to "csd01."  3) To create the public review version from the  CSD:    -- Add a "/" after "Committee Specification Draft 01" then a soft return and then, aligned under "Committee Spec…" put "Public Review Draft 01". For an example, see http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/pkcs11-curr-v2.40-csprd01.html   -- If the TC approves the public review at a different meeting than the approval of the Committee Specification, then change the approval date to that date.    -- In all the URIs, change "csd01" to "csprd01".    -- On the footer on the PDF, change the "csd01" in the filename to "csprd01"    -- In the Citation format, change "Committee Specification Draft 01" to "Committee Specification Draft 01 / Public Review Draft 01".  I think that covers it. Let me know if you have any questions on any of this.  /chet   On Mon, Dec 2, 2013 at 7:55 AM, Rusty Russell < rusty@au1.ibm.com > wrote: "Michael S. Tsirkin" < mst@redhat.com > writes: > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: >> Chet, Paul, >> Attached please find packaged csd01 and csprd01. >> PDF, HTML and extra files (tex source and listings) are included. >> The source in pushed on SVN. >> I hope I've addressed all the issues you have pointed out. >> >> If possible, please review and respond on this Monday so we have >> time to fix remaining issues before our call this Tuesday: >> we would like to vote on both CSD and CSPRD and starting >> the public review period. >> >> Thanks! > > > Here are the attachments. Updated with a little more polish, as discussed on mailing lists. We'd still do well to tighten the language in the bus-specific and device-specific sections, but this is sufficient for draft 1 I feel. Cheers, Rusty. -- /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  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

On Mon, Dec 02, 2013 at 12:08:48PM -0500, Chet Ensign wrote: > Michael, Rusty, Cornelia, Pawel -  > > Thanks for putting this together so that we could give you feedback. Overall it > looks excellent and these are mainly minor changes. The first ones in the > content should be made before you approve the working draft. Then the second > and third sections spell out updates to make to create the Committee > Specification Draft and the Committee Specification Public Review Draft > versions of the spec.  > > 1) In the content itself:  > >   -- In Appendix A. Acknowledgements, add the TC members. The section must be > populated before the TC approves the WD.  > >   -- If you have no Non-Normative References then remove the empty section > 1.3.  > >   -- Any place in the content that you link to urls on docs.oasis-open.org/... > you will need to update them with the same changes as specified below. So, for > example, section 7 virtio_ring.h includes a link to http://docs.oasis-open.org/ > virtio/virtio/1.0/wd01/listings/virtio_ring.h. You will want to change that to > http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/listings/virtio_ring.h . for > the Committee Spec Draft copy and http://docs.oasis-open.org/virtio/virtio/v1.0 > /csprd01/listings/virtio_ring.h. for the Committee Spec Draft / Public Review > Draft version.  > >   -- We recommend numbering footnotes sequentially from start to finish to > avoid problems with the HTML footnotes.  > >      Also, we note that in the HTML version supplied, there were not foot > notes, even though they appear in the PDF version.  > >   -- In the HTML document, the cover page links should be the same as the PDF. > The current review draft has different Specification URIs on the cover page > than does the PDF -- and the PDF ones are in the correct form.  > >   -- If possible, in the PDF, align the left margins. That is, align "This > version:" etc. with "Specification URIs". Not aligned now.  > >   -- In the HTML, the rule (horizontal line) is not present above the Appendix > section titles. Please add that.  > > 2) After the TC votes to approve the WD as a CSD:  > >   -- Change "Working Draft" to "Committee Specification Draft 01"  > >   -- Change the date "05 Nov 2013" to the date the TC voted to approve and > spell out the full month. E.g. "03 December 2013"  > >   -- In the URIs change "wd01" to "csd01". Also, change "/1.0/" to "/v1.0/". > Don't miss changing it in the link as well as in the visible text. So, for > example, " http://docs.oasis-open.org/virtio/virtio/1.0/wd01/ > virtio-v1.0-wd01.pdf (Authoritative)" gets changed to "http:// > docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf > (Authoritative)".  > >   -- Also make these URI updates to the links under "Additional artifacts" and > "Citation format".  > >   -- Under "Additional artifacts", change the word "which" to "that".  > >   -- In the footer, also change the date from "05 Nov" to the approval date > with the month fully spelled out.  > >   -- Under "Status", the first sentence should change from "… or approved by > the members of OASIS…" to "… or approved by the Virtual I/O Device (VIRTIO) > TC…"  > >   -- Under "Citation format", the date should change to the approval date, e.g. > "03 December 2013." "OASIS Standard" should change to "OASIS Committee > Specification Draft 01." Hmm is this OASIS Committee Specification Draft or "Committee Specification Draft"? > and the link should be changed from "wd01" to > "csd01."  > > 3) To create the public review version from the  CSD:  > > >   -- Add a "/" after "Committee Specification Draft 01" then a soft return and > then, aligned under "Committee Spec…" put "Public Review Draft 01". For an > example, see http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/ > pkcs11-curr-v2.40-csprd01.html > >   -- If the TC approves the public review at a different meeting than the > approval of the Committee Specification, then change the approval date to that > date.  > >   -- In all the URIs, change "csd01" to "csprd01".  > >   -- On the footer on the PDF, change the "csd01" in the filename to "csprd01"  > >   -- In the Citation format, change "Committee Specification Draft 01" to > "Committee Specification Draft 01 / Public Review Draft 01".  > > > I think that covers it. Let me know if you have any questions on any of this.  > > /chet > > >   > > > > On Mon, Dec 2, 2013 at 7:55 AM, Rusty Russell <rusty@au1.ibm.com> wrote: > > "Michael S. Tsirkin" <mst@redhat.com> writes: > > > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: > >> Chet, Paul, > >> Attached please find packaged csd01 and csprd01. > >> PDF, HTML and extra files (tex source and listings) are included. > >> The source in pushed on SVN. > >> I hope I've addressed all the issues you have pointed out. > >> > >> If possible, please review and respond on this Monday so we have > >> time to fix remaining issues before our call this Tuesday: > >> we would like to vote on both CSD and CSPRD and starting > >> the public review period. > >> > >> Thanks! > > > > > > Here are the attachments. > > Updated with a little more polish, as discussed on mailing lists. > > We'd still do well to tighten the language in the bus-specific and > device-specific sections, but this is sufficient for draft 1 I feel. > > Cheers, > Rusty. > > > > > > -- > > /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  > > Check your work using the Support Request Submission Checklist at http:// > www.oasis-open.org/committees/download.php/47248/ > tc-admin-submission-checklist.html  > > TC Administration information and support is available at http:// > www.oasis-open.org/resources/tcadmin > > Follow OASIS on: > LinkedIn:     http://linkd.in/OASISopen > Twitter:         http://twitter.com/OASISopen > Facebook:   http://facebook.com/oasis.open

Hi Michael and all, There are two answers, depending on exactly where it is: 1) When the "stage name" (e.g., "Committee Specification Draft 01") appears as the subtitle (i.e., at the top, on the line immediately following "Version x.y" which concludes the main title) it does NOT include the word "OASIS". (we already have the OASIS logo there) 2) In the "Citation format:" section of the front page material, the word "OASIS" (without a separating period) is placed before the "stage name".  In any case, please refer to the examples provided in the ZIP file I sent to the TC mailing list on 25 November ( https://lists.oasis-open.org/archives/virtio/201311/msg00116.html ) for the expected formats. Best regards, Paul On Mon, Dec 2, 2013 at 2:54 PM, Michael S. Tsirkin < mst@redhat.com > wrote: On Mon, Dec 02, 2013 at 12:08:48PM -0500, Chet Ensign wrote: > Michael, Rusty, Cornelia, Pawel -  > > Thanks for putting this together so that we could give you feedback. Overall it > looks excellent and these are mainly minor changes. The first ones in the > content should be made before you approve the working draft. Then the second > and third sections spell out updates to make to create the Committee > Specification Draft and the Committee Specification Public Review Draft > versions of the spec.  > > 1) In the content itself:  > >   -- In Appendix A. Acknowledgements, add the TC members. The section must be > populated before the TC approves the WD.  > >   -- If you have no Non-Normative References then remove the empty section > 1.3.  > >   -- Any place in the content that you link to urls on docs.oasis-open.org/. .. > you will need to update them with the same changes as specified below. So, for > example, section 7 virtio_ring.h includes a link to http://docs.oasis-open.org/ > virtio/virtio/1.0/wd01/listings/virtio_ring.h. You will want to change that to > http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/listings/virtio_ring.h . for > the Committee Spec Draft copy and http://docs.oasis-open.org/virtio/virtio/v1.0 > /csprd01/listings/virtio_ring.h. for the Committee Spec Draft / Public Review > Draft version.  > >   -- We recommend numbering footnotes sequentially from start to finish to > avoid problems with the HTML footnotes.  > >      Also, we note that in the HTML version supplied, there were not foot > notes, even though they appear in the PDF version.  > >   -- In the HTML document, the cover page links should be the same as the PDF. > The current review draft has different Specification URIs on the cover page > than does the PDF -- and the PDF ones are in the correct form.  > >   -- If possible, in the PDF, align the left margins. That is, align "This > version:" etc. with "Specification URIs". Not aligned now.  > >   -- In the HTML, the rule (horizontal line) is not present above the Appendix > section titles. Please add that.  > > 2) After the TC votes to approve the WD as a CSD:  > >   -- Change "Working Draft" to "Committee Specification Draft 01"  > >   -- Change the date "05 Nov 2013" to the date the TC voted to approve and > spell out the full month. E.g. "03 December 2013"  > >   -- In the URIs change "wd01" to "csd01". Also, change "/1.0/" to "/v1.0/". > Don't miss changing it in the link as well as in the visible text. So, for > example, " http://docs.oasis-open.org/virtio/virtio/1.0/wd01/ > virtio-v1.0-wd01.pdf (Authoritative)" gets changed to "http:// > docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf > (Authoritative)".  > >   -- Also make these URI updates to the links under "Additional artifacts" and > "Citation format".  > >   -- Under "Additional artifacts", change the word "which" to "that".  > >   -- In the footer, also change the date from "05 Nov" to the approval date > with the month fully spelled out.  > >   -- Under "Status", the first sentence should change from "… or approved by > the members of OASIS…" to "… or approved by the Virtual I/O Device (VIRTIO) > TC…"  > >   -- Under "Citation format", the date should change to the approval date, e.g. > "03 December 2013." "OASIS Standard" should change to "OASIS Committee > Specification Draft 01." Hmm is this OASIS Committee Specification Draft or "Committee Specification Draft"? > and the link should be changed from "wd01" to > "csd01."  > > 3) To create the public review version from the  CSD:  > > >   -- Add a "/" after "Committee Specification Draft 01" then a soft return and > then, aligned under "Committee Spec…" put "Public Review Draft 01". For an > example, see http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/ > pkcs11-curr-v2.40-csprd01.html > >   -- If the TC approves the public review at a different meeting than the > approval of the Committee Specification, then change the approval date to that > date.  > >   -- In all the URIs, change "csd01" to "csprd01".  > >   -- On the footer on the PDF, change the "csd01" in the filename to "csprd01"  > >   -- In the Citation format, change "Committee Specification Draft 01" to > "Committee Specification Draft 01 / Public Review Draft 01".  > > > I think that covers it. Let me know if you have any questions on any of this.  > > /chet > > >   > > > > On Mon, Dec 2, 2013 at 7:55 AM, Rusty Russell < rusty@au1.ibm.com > wrote: > >     "Michael S. Tsirkin" < mst@redhat.com > writes: > >     > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: >     >> Chet, Paul, >     >> Attached please find packaged csd01 and csprd01. >     >> PDF, HTML and extra files (tex source and listings) are included. >     >> The source in pushed on SVN. >     >> I hope I've addressed all the issues you have pointed out. >     >> >     >> If possible, please review and respond on this Monday so we have >     >> time to fix remaining issues before our call this Tuesday: >     >> we would like to vote on both CSD and CSPRD and starting >     >> the public review period. >     >> >     >> Thanks! >     > >     > >     > Here are the attachments. > >     Updated with a little more polish, as discussed on mailing lists. > >     We'd still do well to tighten the language in the bus-specific and >     device-specific sections, but this is sufficient for draft 1 I feel. > >     Cheers, >     Rusty. > > > > > > -- > > /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  > > Check your work using the Support Request Submission Checklist at http:// > www.oasis-open.org/committees/download.php/47248/ > tc-admin-submission-checklist.html  > > TC Administration information and support is available at http:// > www.oasis-open.org/resources/tcadmin > > Follow OASIS on: > LinkedIn:     http://linkd.in/OASISopen > Twitter:         http://twitter.com/OASISopen > Facebook:   http://facebook.com/oasis.open -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

On Mon, Dec 02, 2013 at 12:08:48PM -0500, Chet Ensign wrote: > Michael, Rusty, Cornelia, Pawel -  > > Thanks for putting this together so that we could give you feedback. Overall it > looks excellent and these are mainly minor changes. The first ones in the > content should be made before you approve the working draft. Then the second > and third sections spell out updates to make to create the Committee > Specification Draft and the Committee Specification Public Review Draft > versions of the spec.  > > 1) In the content itself:  > >   -- In Appendix A. Acknowledgements, add the TC members. The section must be > populated before the TC approves the WD.  > >   -- If you have no Non-Normative References then remove the empty section > 1.3.  > >   -- Any place in the content that you link to urls on docs.oasis-open.org/... > you will need to update them with the same changes as specified below. So, for > example, section 7 virtio_ring.h includes a link to http://docs.oasis-open.org/ > virtio/virtio/1.0/wd01/listings/virtio_ring.h. You will want to change that to > http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/listings/virtio_ring.h . for > the Committee Spec Draft copy and http://docs.oasis-open.org/virtio/virtio/v1.0 > /csprd01/listings/virtio_ring.h. for the Committee Spec Draft / Public Review > Draft version.  > >   -- We recommend numbering footnotes sequentially from start to finish to > avoid problems with the HTML footnotes.  > >      Also, we note that in the HTML version supplied, there were not foot > notes, even though they appear in the PDF version.  > >   -- In the HTML document, the cover page links should be the same as the PDF. > The current review draft has different Specification URIs on the cover page > than does the PDF -- and the PDF ones are in the correct form.  Fixed. >   -- If possible, in the PDF, align the left margins. That is, align "This > version:" etc. with "Specification URIs". Not aligned now.  > >   -- In the HTML, the rule (horizontal line) is not present above the Appendix > section titles. Please add that.  > > 2) After the TC votes to approve the WD as a CSD:  > >   -- Change "Working Draft" to "Committee Specification Draft 01"  > >   -- Change the date "05 Nov 2013" to the date the TC voted to approve and > spell out the full month. E.g. "03 December 2013"  > >   -- In the URIs change "wd01" to "csd01". Also, change "/1.0/" to "/v1.0/". Fixed this second issue. > Don't miss changing it in the link as well as in the visible text. So, for > example, " http://docs.oasis-open.org/virtio/virtio/1.0/wd01/ > virtio-v1.0-wd01.pdf (Authoritative)" gets changed to "http:// > docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf > (Authoritative)".  > >   -- Also make these URI updates to the links under "Additional artifacts" and > "Citation format".  > >   -- Under "Additional artifacts", change the word "which" to "that".  > >   -- In the footer, also change the date from "05 Nov" to the approval date > with the month fully spelled out.  > >   -- Under "Status", the first sentence should change from "… or approved by > the members of OASIS…" to "… or approved by the Virtual I/O Device (VIRTIO) > TC…"  > >   -- Under "Citation format", the date should change to the approval date, e.g. > "03 December 2013." "OASIS Standard" should change to "OASIS Committee > Specification Draft 01." and the link should be changed from "wd01" to > "csd01."  > > 3) To create the public review version from the  CSD:  > > >   -- Add a "/" after "Committee Specification Draft 01" then a soft return and > then, aligned under "Committee Spec…" put "Public Review Draft 01". For an > example, see http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/ > pkcs11-curr-v2.40-csprd01.html > >   -- If the TC approves the public review at a different meeting than the > approval of the Committee Specification, then change the approval date to that > date.  > >   -- In all the URIs, change "csd01" to "csprd01".  > >   -- On the footer on the PDF, change the "csd01" in the filename to "csprd01"  > >   -- In the Citation format, change "Committee Specification Draft 01" to > "Committee Specification Draft 01 / Public Review Draft 01".  > > > I think that covers it. Let me know if you have any questions on any of this.  > > /chet > > >   > > > > On Mon, Dec 2, 2013 at 7:55 AM, Rusty Russell <rusty@au1.ibm.com> wrote: > > "Michael S. Tsirkin" <mst@redhat.com> writes: > > > On Sun, Dec 01, 2013 at 11:54:30PM +0200, Michael S. Tsirkin wrote: > >> Chet, Paul, > >> Attached please find packaged csd01 and csprd01. > >> PDF, HTML and extra files (tex source and listings) are included. > >> The source in pushed on SVN. > >> I hope I've addressed all the issues you have pointed out. > >> > >> If possible, please review and respond on this Monday so we have > >> time to fix remaining issues before our call this Tuesday: > >> we would like to vote on both CSD and CSPRD and starting > >> the public review period. > >> > >> Thanks! > > > > > > Here are the attachments. > > Updated with a little more polish, as discussed on mailing lists. > > We'd still do well to tighten the language in the bus-specific and > device-specific sections, but this is sufficient for draft 1 I feel. > > Cheers, > Rusty. > > > > > > -- > > /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  > > Check your work using the Support Request Submission Checklist at http:// > www.oasis-open.org/committees/download.php/47248/ > tc-admin-submission-checklist.html  > > TC Administration information and support is available at http:// > www.oasis-open.org/resources/tcadmin > > Follow OASIS on: > LinkedIn:     http://linkd.in/OASISopen > Twitter:         http://twitter.com/OASISopen > Facebook:   http://facebook.com/oasis.open

Chet Ensign <chet.ensign@oasis-open.org> writes: > Michael, Rusty, Cornelia, Pawel - > > Thanks for putting this together so that we could give you feedback. > Overall it looks excellent and these are mainly minor changes. The first > ones in the content should be made before you approve the working draft. > Then the second and third sections spell out updates to make to create the > Committee Specification Draft and the Committee Specification Public Review > Draft versions of the spec. > > 1) In the content itself: > > -- In Appendix A. Acknowledgements, add the TC members. The section must > be populated before the TC approves the WD. Done, thanks. > -- If you have no Non-Normative References then remove the empty section > 1.3. Done, thanks. > -- Any place in the content that you link to urls on docs.oasis-open.org/... > you will need to update them with the same changes as specified below. So, > for example, section 7 virtio_ring.h includes a link to > http://docs.oasis-open.org/virtio/virtio/1.0/wd01/listings/virtio_ring.h . > You will want to change that to > http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/listings/virtio_ring.h . > for the Committee Spec Draft copy and > http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/listings/virtio_ring.h . > for the Committee Spec Draft / Public Review Draft version. OK, did that in shell. > -- We recommend numbering footnotes sequentially from start to finish to > avoid problems with the HTML footnotes. Done. > > Also, we note that in the HTML version supplied, there were not foot > notes, even though they appear in the PDF version. They're in separate files, which mistakenly weren't included in the zip. Fixed. > -- In the HTML document, the cover page links should be the same as the > PDF. The current review draft has different Specification URIs on the cover > page than does the PDF -- and the PDF ones are in the correct form. This seems to be fixed by the URL fix above. > -- If possible, in the PDF, align the left margins. That is, align "This > version:" etc. with "Specification URIs". Not aligned now. Hmm, OK for some reason that was indented 0.4 inches: changing that to 0 seems to have worked. > -- In the HTML, the rule (horizontal line) is not present above the > Appendix section titles. Please add that. Hmm, that I can't figure out. I'll leave it to MST :) > 2) After the TC votes to approve the WD as a CSD: > > -- Change "Working Draft" to "Committee Specification Draft 01" > > -- Change the date "05 Nov 2013" to the date the TC voted to approve and > spell out the full month. E.g. "03 December 2013" OK, that I've done already. > -- In the URIs change "wd01" to "csd01". Also, change "/1.0/" to > "/v1.0/". Don't miss changing it in the link as well as in the visible > text. So, for example, " > http://docs.oasis-open.org/virtio/virtio/1.0/wd01/virtio-v1.0-wd01.pdf (Authoritative)" > gets changed to " > http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf (Authoritative)". OK, fixed the 1.0 to v1.0 in both versions. > -- Also make these URI updates to the links under "Additional artifacts" > and "Citation format". The first one is done, the latter was malformed. Fixed. > -- Under "Additional artifacts", change the word "which" to "that". Thanks, done. > -- In the footer, also change the date from "05 Nov" to the approval date > with the month fully spelled out. Done. > -- Under "Status", the first sentence should change from "… or approved > by the members of OASIS…" to "… or approved by the Virtual I/O Device > (VIRTIO) TC…" Done. > -- Under "Citation format", the date should change to the approval date, > e.g. "03 December 2013." "OASIS Standard" should change to "OASIS Committee > Specification Draft 01." and the link should be changed from "wd01" to > "csd01." Done. > 3) To create the public review version from the CSD: > > -- Add a "/" after "Committee Specification Draft 01" then a soft return > and then, aligned under "Committee Spec…" put "Public Review Draft 01". For > an example, see > http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/pkcs11-curr-v2.40-csprd01.html > > -- If the TC approves the public review at a different meeting than the > approval of the Committee Specification, then change the approval date to > that date. > > -- In all the URIs, change "csd01" to "csprd01". > > -- On the footer on the PDF, change the "csd01" in the filename to > "csprd01" > > -- In the Citation format, change "Committee Specification Draft 01" to > "Committee Specification Draft 01 / Public Review Draft 01". OK, these should all be correct now. Thanks, Rusty.

On Tue, Dec 03, 2013 at 06:18:54PM +1030, Rusty Russell wrote: > > -- If possible, in the PDF, align the left margins. That is, align "This > > version:" etc. with "Specification URIs". Not aligned now. > > Hmm, OK for some reason that was indented 0.4 inches: changing that to 0 > seems to have worked. Did you commit this? Still seems same alignment to me. I think this won't block public review.

Don't spend too much time on the alignment problem. That's just a nice to have.  Thanks for all the other fixes - will make progression through the process very smooth!  /chet On Tue, Dec 3, 2013 at 4:00 AM, Michael S. Tsirkin < mst@redhat.com > wrote: On Tue, Dec 03, 2013 at 06:18:54PM +1030, Rusty Russell wrote: > >   -- If possible, in the PDF, align the left margins. That is, align "This > > version:" etc. with "Specification URIs". Not aligned now. > > Hmm, OK for some reason that was indented 0.4 inches: changing that to 0 > seems to have worked. Did you commit this? Still seems same alignment to me. I think this won't block public review. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- /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  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open