RE: [xliff-comment] XLIFF 2.0 Comments - attributes from xml namespace

OK, but at the very least, we should give an example of how to declare a namespace for a module so that it can be included properly in the XLIFF document. People not familiar with xml namespaces will not understand that in order for <val:validation>
 to be valid, they need to declare it like so:

 

<xliff xmlns:val="urn:oasis:names:tc:xliff:validation …>

 

Ryan

 

From: Yves Savourel [mailto:] 

Sent: Wednesday, May 29, 2013 3:27 AM

To: 

Subject: RE: [xliff-comment] XLIFF 2.0 Comments - attributes from xml namespace

 

I don’t think it’s needed.

That attribute is treated as a special case and does not need to be declared. Actually it’s not possible to define them in a schema.

 

-ys

 

From: Ryan King [mailto:]

Sent: Tuesday, May 28, 2013 11:52 PM

To: 

Cc: 

Subject: [xliff-comment] XLIFF 2.0 Comments - attributes from xml namespace

 

In section 2.3.2, both xml:lang and xml:namespace are defined. They are also listed as optional attributes for <source> and <target>. Shouldn’t we also define xmlns in that section and list it as an optional attribute
 for <xliff> since this is the main mechanism for declaring a module’s namespace? For example:

 

<xliff xmlns:xlf="urn:oasis:names:tc:xliff:document:2.0" xmlns:val="urn:oasis:names:tc:xliff:validation:2.0" xmlns:ctr="urn:oasis:names:tc:xliff:changeTracking:2.0" xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0"
 xmlns:mtc="urn:oasis:names:tc:xliff:matches:2.0" xmlns:res="urn:oasis:names:tc:xliff:resourceData:2.0" version="2.0" srcLang="en-US" tgtLang="de-DE">

 

Thanks,

Ryan