RE: [xliff-users] Fragment Identification in XLIFF 2.0

[Yves Savourel <ysavourel@enlaso.com>]

Hi Phil,

It's not that reference by IDs to non-XLIFF namespace is impossible it is just that one cannot have extensions (or modules) that
have nested reference.

For example, imagine you have this extensions:

<unit id="1">
 <ext1:elem1 id="id1">
  <ext2:elem2 id="id3">data
   ...

You can declare prefixes for both extensions.
You can do this: #f=f1/u=1/ext1=id1
Or this: #f=f1/u=1/ext2=id3
But not this: #f=f1/u=1/ext1=id1/ext2=id3

In other words, you cannot have several IDs with the same value for ext2 even if they are within different ext1 elements. But you
can have several IDs with the same value for ext2 as long as they are in different units.

This normally would not affect ITS.

In addition, it's relatively easy to work around the restriction: you can simply define the IDs of your extension to be UUIDs, then
they don't need to depend on some nested scope to use them.

Hope this helps,
-yves



From: Phil Ritchie [mailto:philr@vistatec.ie] 
Sent: Sunday, August 24, 2014 5:04 AM
To: xliff-users@lists.oasis-open.org
Subject: [xliff-users] Fragment Identification in XLIFF 2.0

I am trying to reconcile my understanding of Fragment Identification [1].

The Warning states that ".third party namespaces within Modules or extensions. .is not possible." By what approval/exception
mechanism is "ITS (Internationalization Tag Set)" allowed? [Don't get me wrong, I'm glad it is. Just trying to reconcile what reads
to me as a conflict.]

[1] http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#fragid

Phil.


************************************************************
VistaTEC Ltd. Registered in Ireland 268483. 
Registered Office, VistaTEC House, 700, South Circular Road, 
Kilmainham. Dublin 8. Ireland. 

The information contained in this message, including any accompanying 
documents, is confidential and is intended only for the addressee(s). 
The unauthorized use, disclosure, copying, or alteration of this 
message is strictly forbidden. If you have received this message in
error please notify the sender immediately.
************************************************************