OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi Chet,   Thanks for the links.   The sample specification uses capitalized terms in the conformance clause but terms appear mostly in lower case in the rest of the document. We will use a similar style: capitalization in the conformance clause and lower case in the rest. The latest template you and Ken uploaded to Kavi says:   The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional are to be interpreted as described in [RFC 2119]. Note that for reasons of style, these words are not capitalized in this document.   We have the same wording in our current draft.   We may need to update the stylesheets, I'll take care of that.   Regards, Rodolfo -- Rodolfo M. Raya Maxprograms http://www.maxprograms.com    

Thanks Rodolfo and Chet. Onward and upward!   From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Rodolfo M. Raya Sent: Friday, June 15, 2012 1:37 PM To: Chet Ensign Cc: xliff@lists.oasis-open.org; Bryan Schnabel Subject: RE: [xliff] Uppercasing conformance keywords in OASIS specs   Hi Chet,   Thanks for the links.   The sample specification uses capitalized terms in the conformance clause but terms appear mostly in lower case in the rest of the document. We will use a similar style: capitalization in the conformance clause and lower case in the rest. The latest template you and Ken uploaded to Kavi says:   The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional are to be interpreted as described in [RFC 2119]. Note that for reasons of style, these words are not capitalized in this document.   We have the same wording in our current draft.   We may need to update the stylesheets, I'll take care of that.   Regards, Rodolfo -- Rodolfo M. Raya Maxprograms http://www.maxprograms.com    
Original Message -------- Subject: Re: [xliff] Uppercasing conformance keywords in OASIS specs From: Chet Ensign < chet.ensign@oasis-open.org > Date: Fri, June 15, 2012 5:13 pm To: "Rodolfo M. Raya" < rmraya@maxprograms.com > Cc: xliff@lists.oasis-open.org , Bryan Schnabel < bschnabel@bschnabel.com >, OASIS TAB < tab@lists.oasis-open.org >, Ken Holman < gkholman@cranesoftwrights.com > Ah - ok, that explains why I haven't seen a template request. Have a look at this recent Committee Specification - http://docs.oasis-open.org/tgf/TGF-PL-Core/v1.0/cs01/TGF-PL-Core-v1.0-cs01.html#_Toc308643678 The language around keywords at that link is the language we have used in .doc and .odt templates since before I began. To keep in alignment with the current practice, I recommend including and using this language. Also, I worked with Ken Holman to update the Docbook template and style sheet to produce specs that match our current format. I don't have the new environment posted on the OASIS site yet but I believe that http://www.oasis-open.org/committees/document.php?document_id=46254 contains the complete set. Let me know if you have any questions, /chet On Fri, Jun 15, 2012 at 3:39 PM, Rodolfo M. Raya < rmraya@maxprograms.com > wrote: > Hi Chet, > > We are currently working on a new specification draft, using the latest > DocBook template and XSL stylesheets. > > The current draft is consistent. Keywords are in lower case and the text > clearly says they are not capitalized for style reason, as originally > written in the template. > > Regards, > Rodolfo > -- > Rodolfo M. Raya       rmraya@maxprograms.com > Maxprograms       http://www.maxprograms.com > > >>