OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [xliff] charclass and XLIFF namespace identifier

Hi All,

In response to Yves's email  3/19/02 9:35:44 AM >>>

-1- charclass Attribute

Yves, Isn't CSS2 a style sheet specification? Does it allow me to
restrict the translation to Katakana or 7-bit ASCII or Uppercase without
forcing me to give other details? If I remember correctly, the reason we
didn't use CSS2 here was we felt it was like using a sledgehammer where
a tack hammer was needed. However, if it gives us what we want, i.e.
restrict the translation to some character class, without imposing a lot
of syntax, it could be acceptable. Does anyone know of something
comparable but simpler?

-2- XLIFF Namespace

I didn't know if this was verified with Karl Best, Director of
Technical Operations at OASIS, or not. According the RFC referenced, he
maintains the namespace identifiers. So I contacted him. Our thread is
included below. In summary, the namespace Yves proposes works. However,
if this NSS is pointing at the spec, should we put in the type
"document"; e.g. "urn:oasis:names:tc:xliff:document:1.0"?  This is based
on the the RFC3121, ftp://ftp.isi.edu/in-notes/rfc3121.txt.


>>> "Karl F. Best" <karl.best@oasis-open.org> 4/17/02 11:38:33 AM >>>

1. Given lack of resources and mechanisms for assigning and tracking
URNs, I have made it a practice to assign to each TC a branch of the
namespace tree and allow the TC to manage that themselves.

2. Yes, the XLIFF TC owns urn:oasis:names:tc:xliff:*

3. The specification branch should be resrved for approved OASIS
so until a spec is approved at the OASIS level it should exist only at
the TC level in the URN tree.

Karl F. Best
OASIS - Director, Technical Operations
+1 978.667.5115 x206
karl.best@oasis-open.org  http://www.oasis-open.org

> -----Original Message-----
> From: John Reid [mailto:JREID@novell.com]
> Sent: Wednesday, April 17, 2002 1:25 PM
> To: karl.best@oasis-open.org
> Subject: URN clarification
> Hi Karl,
> In the XLIFF TC we are discussing the namespace URN for XLIFF.
> According to RFC 3121, "The Director of Technical Operations at
> assigns document types, subtypes, and all unique identifiers." It
> been proposed that we use the following:
> "urn:oasis:names:tc:xliff:1.0"
> Questions:
> 1. Has RFC 3121 been implemented? Or better, do you make those
> assignments?
> 2. Does the above namespace identifier meet your requirements?
> 3. Can the document class identifier 'specification' be used for a
> committee specification; e.g.
> "urn:oasis:names:specification:xliff:document:1.0"? Or is it
> only for OASIS specifications?
> Thanks in advance,
> John

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC