W3C home > Mailing lists > Public > public-i18n-its-ig@w3.org > November 2014

RE: Question on domain in XLIFF

From: Yves Savourel <ysavourel@enlaso.com>
Date: Tue, 18 Nov 2014 04:58:50 -0700
To: "'public-i18n-its-ig'" <public-i18n-its-ig@w3.org>
Message-ID: <00d901d00327$04772770$0d657650$@enlaso.com>
Hi Felix,


I'm not sure I understand the issue (if there is one).

I think the rule you came up with is the way to go.

There are no other Domain-related data in the rules for the ITS module, so placing it anywhere in that rules file would be fine, no?
Maybe I'm missing something.





From: Felix Sasaki [mailto:fsasaki@w3.org] 
Sent: Monday, November 17, 2014 10:34 PM
To: public-i18n-its-ig
Subject: Question on domain in XLIFF


Hi all,


looking at Yves' comment at



"The usage of the namespace urn:oasis:names:tc:xliff:its:2.1 is only due to XLIFF 2.0 validation constraints.

Note YS: it's also because the ITS namespace needs at time to be completed: when a data category uses the XLIFF markup and is
missing some features (we would not be able to use the ITS namespace for this); and when ITS local rules are missing things, like a
domain attribute"


I was wondering about domain local. As Yves writes, this is not available in ITS. So an ITS implementation will not look for local
attributes. How should the ITS processor then work with local domain attributes in XLIFF? One answer could be to write a global
domain rule like


 <its:domainRule selector="//xlf:mrk[@type='any' and @itsm:domains]" domainPointer="@itsm:domains" /> 


Using global rules for domain then means that this rule has to come last, so that it has precedence compared to other domain related
global rules and in that way acts like a local markup. 




- Felix
Received on Tuesday, 18 November 2014 11:59:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:11:31 UTC