Subject: RE: [xliff] XLIFF and ITS mapping-ID value
Dear Felix, Yves,
Thanks for your help, your notes will be applied.
From: Felix Sasaki [email@example.com]
Sent: 20 December 2015 20:41
Subject: Re: [xliff] XLIFF and ITS mapping-ID value
HI Soroush and all,
There is no example because as the wiki says: „Note that the identifiers in XLIFF are not unique per document, so using the Id Value data category to specify IDs in an XLIFF document is largely useless“. So I would leave this as as, without an example about such contexts.
From: firstname.lastname@example.org [email@example.com] on behalf of Yves Savourel [firstname.lastname@example.org]
Sent: 19 December 2015 12:38
To: XLIFF Main List
Subject: RE: [xliff] XLIFF and ITS mapping- Elements within text
Several of the examples have "curly quotes" instead of normal ASCII double quotes to enclose attribute values.
A side effect of editing in an email probably, but they need to be correct in the spec.
<source>This sentence has a breakpoint<ph id="ph1" dataRef="d1"
The example above has a dangling "-->" after </originalData>.
<source>A paragraph where <sc id="sc1" dataRef="d1" type="fmt"
subType="xlf:u"/>the formatted text takes more than one
<source> The second sentence here.<ec dataRef="d2"
In the example above, the <ec/> element seems to be missing the attributes type="fmt" and subType="xlf:u".
Now, the Okapi validator gives an error on this, but I don't see in the spec any constraint that says type and subType must have the
same values in two corresponding <sc/> and <ec/>. That constraint exists only for canCopy, canDelete and canOverlap.
I don't see anywhere either that the processor should magically complement the undefined attributes in <ec/> by looking at the
corresponding <sc/>. At the same time, obviously, it would be illogical to have different values.
Are we missing yet another "implicit" constraint?
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: