RE: [xliff] namespace declaration

["Rodolfo M. Raya" <rmraya@maxprograms.com>]

Hi Yves,

Another case to analyze (I've actually seen this done with XLIFF 1.1) is:

<xlf:xliff version="2.0" srcLang="en" xmlns:xlf="urn:oasis:names:tc:xliff:document:2.0">
 < xlf:file>
  <xlf:unit id="u1">
   <xlf:segment>
    <xlf:source>text</xlf:source>
   </xlf:segment>
  </xlf:unit>
 </xlf:file>
</xlf:xliff>

I would prefer that XLIFF core elements don't have a prefix.

Perhaps we should define XLIFF 2.0 documents in section 1 of the specification as something like "XML documents that declare the namespace "urn:oasis:names:tc:xliff:document:2.0" as their main namespace, have <xliff> as root element and comply with the schemas that are part of the XLIFF specification".

Regards,
Rodolfo
--
Rodolfo M. Raya       rmraya@maxprograms.com
Maxprograms       http://www.maxprograms.com


> -----Original Message-----
> From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf
> Of Yves Savourel
> Sent: Thursday, July 05, 2012 10:42 AM
> To: xliff@lists.oasis-open.org
> Subject: RE: [xliff] namespace declaration
> 
> Hi Rodolfo, all,
> 
> > Nevertheless, I would make the declaration of the core namespace
> > required in the conformance clause.
> 
> +1.
> 
> > From XML point of view, declaring the namespace is optional.
> 
> Just to clarify though:
> Should/Must an XLIFF 2.0 processor be able to process this:
> 
> <xliff version="2.0" srcLang="en">
>  <file>
>   <unit id="u1">
>    <segment>
>     <source>text</source>
>    </segment>
>   </unit>
>  </file>
> </xliff>
> 
> I'm asking because without a namespace declaration that document could be
> any format that just happens to start with <xliff>.
> 
> Cheers,
> -ys
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: xliff-help@lists.oasis-open.org