[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] RE: ITS Module URI
Thanks for the correct Robin. It’s good to know this. In the case of XLIFF 2 I’m afraid it’ll have to stick with URNs for a while as 2.0 has a processing requirement that involve looking at the start of the namespace URIs to make the difference between XLIFF modules and user extensions. Cheers, -yves From: Robin Cover [mailto:robin@oasis-open.org] Re: > But I think the URN is the official OASIS way: https://tools.ietf.org/html/rfc3121 Caveat: I didn't review the context (your application space), but in general, and in the abstract: URNs are not the "official" way to construct identifier components. It's true that some OASIS TCs (especially, those TCs started in years before 2005) use URNs, for various purposes, but OASIS Staff does not currently recommend that practice. Both methods work, for some purposes. But not for others. Please see the guidance provided in the OASIS Naming Directives, where the use of HTTP scheme URI references are discussed, for XML namespace names and for any (related) kinds of identifiers 8. XML Namespace Identifiers and Namespace Documents "Non-information resources using identifiers associated with XML namespaces may be based upon any HTTP scheme URI XML namespace declared by the TC (i.e., identifiers for named properties, functions, dialects, faults, actions, or any named message types)" -rcc On Wed, Nov 26, 2014 at 10:58 AM, Yves Savourel <ysavourel@enlaso.com> wrote:
-- Robin Cover |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]