← Prev in month ← Prev in thread
Next in thread → Next in month →

1.8. Must be able to identify uniquely an inline code within a segment

From
Yves Savourel <>
Date
2011-08-05T03:55:33+00:00
ID
assp.0198607f9a.assp.0198101688.001301cc5323$7fc96e90$7f5c4bb0$@com
Thread
1.8. Must be able to identify uniquely an inline code within a segment
There are two main questions remaining for this item I think:

== A) Use of xml:id

It seems the requirement that values for xml:id must be unique per document (http://www.w3.org/TR/xml-id/#processing) prevents its use in this context: we need to be able to specify the same value between the source and the target.


== B) Id for closing code

We've discuss some of this here: http://lists.oasis-open.org/archives/xliff-inline/201107/threads.html#00000

And it seems there is a consensus building toward using id in the opening part of the code and idref/rid in the corresponding closing part. (I'm using rid for now because we started with that in 1.2 and it's shorter, but idref/idr would be fine too (and maybe better English?)).

This would give us the following usage: <ph id='1'/>, <sc id='2'>...<ec rid='2'>, <pc id='3'>...</pc>

Is this something we are all comfortable with?
And do we have other issues or questions to resolve with this topic?

-ys
← Prev in month ← Prev in thread
Next in thread → Next in month →