Re: [xliff] IDs - uniquness and source/target exception (B)

["Dr. David Filip" <David.Filip@ul.ie>]

Hello, Yves,

based on this and other discussions, I propose this solution:

Old text:

"The value MUST be
unique within the <segment> or <ignorable> elements and inline elements with the same id in both source and target MUST be
corresponding elements."

[please note that segment or ignorable had to be replaced with unit to resolve the ID related issue A]

[also inline elements were knocked together with segment and ignorable to resolve the ID related issue C]

Proposed text:

• [When used in <segment>, <ignorable>, <mrk>, <sm>, <pc>, <sc>, <ec> or <ph>:]
  
• Inline elements enclosed by a <target> element MUST use duplicate id values of their corresponding inline elements enclosed within the sibling <source> element if and only if those corresponding elements exist.
• Except for the above exception, the value MUST be unique among all of the above within the enclosing <unit> element.

I would not place the constraints into source and target. I would just have a note on target pointing to the id definition

Dr. David Filip

=======================

LRC | CNGL | LT-Web | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

http://www.cngl.ie/profile/?i=452

mailto: david.filip@ul.ie

On Tue, Oct 22, 2013 at 6:41 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

Hi David, all,

> *B)*
> The current uniqueness Constraints ignore the fact that ids are in
> fact expected to be duplicated between <source> and <target> to signify
> the sameness of the elements between <source> and <target>.
> *Proposed Solution: Add this exception to the relevant uniqueness constraints*

Are you talking about this constraint (in the definition of the id attribute for inline code and annotation): "The value MUST be
unique within the <segment> or <ignorable> elements and inline elements with the same id in both source and target MUST be
corresponding elements."

If so, it looks like the constraint takes the source/target case into account.
But we probably need better wording.
Maybe expressing the constraint for the source content, and then having a separate one for the target.

-yves


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php