RE: [xliff] Proposal: mark attribute "startRef" as required in <ec>

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

Hi Yoshito,

it is more complicated than that.

The "id" of the <sc> referenced by <ec> must be unique in the <unit> where it is located, but could be duplicated in other <unit> elements. In case of "isolated", you don't know where to point.

Right now "startRef" is defined as the "id" of the corresponding <sc>. If it is in a different <unit>, it should be the fragment identifier for the <sc> instead of just its "id". 

To simplify pairing, <ec> should always use "startRef". You could say that startRef points to a fragment identifier when in "isolated" or an "id" if it is in the same <unit>

Regards,

Rodolfo 

--
Rodolfo M. Raya
Maxprograms http://www.maxprograms.com

-------- Original Message --------
Subject: Re: [xliff] Proposal: mark attribute "startRef" as required in
<ec>
From: "Yoshito Umaoka" <yoshito_umaoka@us.ibm.com>
Date: Tue, May 18, 2021 10:55 am
To: "Mr. Rodolfo Raya" <rmraya@maxprograms.com>
Cc: xliff@lists.oasis-open.org


> Element <ec> must have a "startRef" pointing to the corresponding
> <sc> for correct pairing.
>
> If there isn't a reasonable objection in next meeting, I'll make the
> change in the specification.

I have one question about this. <sc> and <ec> can have attribute isolated="yes". This allows <sc> and matching <ec> not included in a same <unit>.
When a corresponding <sc> is in another <unit> (or it does not even exist in a XLIFF document? I guess this is also allowed), then there is no way to refer the corresponding <sc> by id attribute, because the scope of id used by <sc> and <ec> is within a same parent <unit>.

<em> does not support isolated="yes". The required attribute - startRef implies it must have a paired <sm> within a same parent <unit> element.

Is my interpretation above right?


-Yoshito