Re: [xliff] Uppercasing conformance keywords in OASIS specs

[Chet Ensign <chet.ensign@oasis-open.org>]

Hi Bryan, hi Rudolfo,

Are you asking about a working draft that is in process or the
published OS? I assume you mean the OS or other completed document
because as far as I can tell the TC has not requested a document
template in a few years.

I am not concerned about correcting a completed and published
document. You can of course if you want to but the language changed
sometime before I joined OASIS last year and I don't see a reason to
apply such a change retrospectively.

Frankly, the most important thing from my point of view is internal
consistency. Uppercase or lower, if you used them the same way then I
don't see a problem.

Does this cover it for you?

Best,

/chet

On Thu, Jun 14, 2012 at 3:11 PM, Schnabel, Bryan S
<bryan.s.schnabel@tektronix.com> wrote:
> Hi Chet,
>
>
>
> It seems we have a conflict between what the requirement in David’s link
> below states, vs. what we are seeing in the more recent template provided by
> OASIS.
>
>
>
> Can you please provide us guidance on this?
>
>
>
> Thanks Chet,
>
>
>
> Bryan
>
>
>
> From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On
> Behalf Of Rodolfo M. Raya
> Sent: Thursday, June 14, 2012 4:44 AM
> To: xliff@lists.oasis-open.org
>
>
> Subject: RE: [xliff] Uppercasing conformance keywords in OASIS specs
>
>
>
> The template we use in the specification was provided by OASIS and it uses
> lowercase for those special terms. The template is newer than the
> requirement you mention.
>
>
>
> Notice that we explicitly say that special word meanings are defined in RFC
> 2119 and it does not require key words to be capitalized.
>
>
>
> Capitalization would be important in the conformance clause but we have not
> defined it yet.
>
>
>
> BTW, the official OASIS template explicitly says key words are not
> capitalized as a matter of writing style.
>
>
>
> Regards,
>
> Rodolfo
>
> --
> Rodolfo M. Raya       rmraya@maxprograms.com
> Maxprograms       http://www.maxprograms.com
>
>
>
> From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On
> Behalf Of Dr. David Filip
> Sent: Thursday, June 14, 2012 7:45 AM
> To: xliff@lists.oasis-open.org
> Subject: [xliff] Uppercasing conformance keywords in OASIS specs
>
>
>
> Hi all, Rodolfo, I was recently rereading some OASIS policies and it came up
> today in the SC f-2-f.
>
> There is an OASIS policy that explicitly states this:
>
> RFC2119 allows both uppercase and lowercase to be used for a keyword,
> however to enable easy identification of the keywords and consistency across
> specifications uppercase MUST be used for keywords at all times.
>
>
>
> See http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html#_Toc170119662
>
>
>
> Unfortunately our current draft is in conflict with this regulation. I
> suppose that we should comply..
>
>
>
> Thanks
>
> dF
>
>
> Dr. David Filip
>
> =======================
>
> LRC | CNGL | LT-Web | CSIS
>
> University of Limerick, Ireland
>
> telephone: +353-6120-2781
>
> cellphone: +353-86-0222-158
>
> facsimile: +353-6120-2734
>
> mailto: david.filip@ul.ie
>
>



-- 

/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

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