Line Numbers for Public Review

["Considine, Toby" <Toby.Considine@unc.edu>]

In todayâs meeting, the desirability of line numbers in PDFs for public review was discussed. There was some concerns raised on if it was even allowed.

 

The use of Line Numbers in a PDF for public review is not only allowed, but recommended.

 

See below. The OASIS editors guide is newly revised, and a notice was sent to all chairs last week.

 

Thanks, Chet! I missed it when I ran through the on-line docs.

 

See below.

 

From: Chet Ensign <chet.ensign@oasis-open.org>
Sent: Tuesday, September 11, 2018 2:24 PM
To: Considine, Toby <Toby.Considine@unc.edu>
Subject: Re: The OASIS Editor's Handbook is now available

 

Toby, thanks. Actually, that is a topic I should spell out explicitly - preparing your work for public review. 

 

The topic of line numbers is there though. Section 4.1.5 in part 4 (https://docs.google.com/document/d/10lt8f2pn_ebZTsWJiGYiWYzyo6NbjuTskvDcS2tSyPw/edit#). It starts: 

 

4.1.5 Line numbering

Ah, line numbers. So seductive; so seemingly precise.

And goes on to say that you should only use them in PDF because that is the only way you can guarantee that the numbers are the same for all viewers. 

 

I will go back to the Table of Contents and decide where to put a section on prepping your work for PR. That is a section that editors can really use. 

 

Best, 

 

/chet 

 

 

On Tue, Sep 11, 2018 at 2:09 PM, Considine, Toby <Toby.Considine@unc.edu> wrote:

Chet.

A fine and timely set of documents.

I was in one of the OpenC2 meetings today and the subject of Line Numbered PDFs came up (because I brought it up) and several editors suggested they would not want to do that because it âmight not be allowed in OASISâ

I thought no problem, I have this handy dandy new guide that just came outâ.

I cannot find in the documents comments/guidance  about preparing specifications for public reviewâ

Any comments?

tc

 

From: Chet Ensign <chet.ensign@oasis-open.org>
Sent: Wednesday, September 5, 2018 1:33 PM
To: chairs@lists.oasis-open.org
Cc: OASIS TAB <tab@lists.oasis-open.org>
Subject: The OASIS Editor's Handbook is now available

Chairs, 

The OASIS TAB announces version 1.0 of the OASIS Editor's Manual. Please share these with your spec editors. 

The Editor's Manual is published in four parts: 

Part 1: The role of editor - https://docs.google.com/document/d/1lTartcAzlqidzrCxuXFFiwdRDKRipqMnNsMS24SZdjg/edit#heading=h.bi4fdsq13pue - explains the basics of the job you undertake when you volunteer to edit a work product.  

Part 2: The Editorial Process - https://docs.google.com/document/d/1gaYTQleiGMRA1vt2sLo1YUXqlGJe-JXgukJvSSlOhRI/edit#heading=h.bi4fdsq13pue - describes the work flow for TC work products from working draft through OASIS Standard.

Part 3: Document Structure - https://docs.google.com/document/d/1yA-wt2wB4NOpgoQ81VBfuJ1WPA1GK_BuddiVP_L6BnU/edit#heading=h.psw0b8lwn5fm - covers the components of work products including required sections and considerations about whether to organize a work as a single part or a multi-part work. 

Part 4: Work Product Preparation - https://docs.google.com/document/d/10lt8f2pn_ebZTsWJiGYiWYzyo6NbjuTskvDcS2tSyPw/edit# - covers lessons learned, tips, etc for preparing documents without errors. 

The manual is prepared in four Google Docs for now. Anyone with the link can add comments and we would welcome feedback. Please feel free to comment directly to the documents. If you prefer, you can send your thoughts to tab-askthetab@lists.oasis-open.org.

If you run into any difficulties accessing or commenting on the documents, please reply directly back to me. 

Many thanks, 

The OASIS Technical Advisory Board (TAB) 

 

Chet Ensign (chair)

Trey Darley

Jacques Durand

Patrick Durusau

Stefan Hagen

Ashok Malhotra (invited expert) 

 

-- 

/chet 
----------------