RE: [xliff-inline] 1.3. Must be able to represent paired codes that have been separated

[Yves Savourel <ysavourel@enlaso.com>]

Hi Bryan,

> I would strongly advocate for idref over (second/paired)
> id, rid, or idr. As a long time XML hacker, I think idref 
> has a rich and understood tradition of being paired with 
> id. And frankly, the brevity of the other choices (by a
> character or two) does not seem very compelling to me
> (my bias: clarity trumps brevity).

I have no problem with idref.

But there are currently two attributes in the code elements that hold reference to another id.
The other is "nid", which points to an element in the outside structure that stores the original data. Technically it is also an "idref", no?

What would be the rational to prefer one over the other to be named idref?

-ys