Re: Editorial comments on VIRTIO v1.2 csd01

Hi all,

(Using correct email for Cornelia this time - apologies!)

Thanks for addressing the list of editorial issues. Since we have already published the current documents andÂannounced the public review, we will not change them. Now that you have fixed your source files, theyÂwill be correct inÂyour repository for your future publications.

Regarding the reference toÂ[S390 Common I/O]Â, our key requirement is to avoid publishing "OASIS Standards Final Deliverables [1]" documents withÂbroken hyperlinks, particularly for a Normative reference. If the document is not available online, you can simply provide the title, publisher, date, etc., similar to a printed book, with no hyperlink.

Best regards,

Paul

[1]Âhttps://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dOASISstdsFinal

On Tue, May 10, 2022 at 10:59 AM Michael S. Tsirkin <mst@redhat.com> wrote:

On Mon, May 09, 2022 at 04:40:53PM -0400, Paul Knight wrote:
> Hi all,
>
> These comments are intended for the TC Editors, although I'm sending it to the
> TC's email list for future reference.
>
> In running a link check, I noted several issues, none significant for this
> initial public review publication:
> - broken link in Normative references:
> -- [S390 Common I/O] ESA/390 Common I/O-Device and Self-Description, IBM
> Publication SA22-7204,
> http://publibfp.dhe.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar501/CCONTENTS, and any
> future revisions
> (This link is currently broken, and I could not find any alternative source for
> this document. - please rewrite the reference to indicate document is no longer
> available at this link. You may also consider whether the solitary citation at
> 4.3.1.3 is still needed.)
> This broken link is not a blocking issue for a Committee specification Draft,
> but it will not be allowed for a Committee Specification.
>
> Minor broken links in the "Revision History" - Appendix D
> - https://lists.oasis-open.org/archives/virtio-dev/201910/msg00057.html. (bad
> link due to inclusion of the terminating period - second item dated 01 Sep 2020
> in Appendix D Revision history) - not a blocking issue
> - Âhttps://lkml.org/lkml/2020/4/21/1020) (bad link due to including the final
> right parenthesis in the hyperlink - item dated 01 Sep 2020 by Petre Eftime) -
> not a blocking issue
> - https://github.org/oasis-tcs/virtio-spec/issues/97 Â(bad link due to using
> github.org instead of github.com - first item dated 30 Mar 2021 in Appendix D
> Revision history) - not a blocking issue
>
> Appearance:
> - (HTML only) To conform to OASIS style, this should use bold font in title and
> headings from top through "Notices"
> -- I noted that in the HTML file, these headings use class="aeb10-", but this
> is not defined in the .css file.
> -- For this publication, I defined it by inserting the line below into the .css
> file (virtio-v1.2-csd01.css, at line 18), which fixed this issue:
> --- .aeb10-{font-weight: bold;}
> Please make this adjustment (or something with a similar effect) in your
> publication process for the future.
>
> Best regards,
> Paul

Hi Paul,
Just in case you think it's appropriate, I uploaded a version with these
changes as a revision for csd01.

Here it is, revision 3:
https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/69907/virtio-v1.2-wd02-as-csd01-diffs.zip

> --
> Paul Knight....Document Process Analyst
> OASIS...Setting the standard for open collaboration

virtio message