[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Latest Changes: Resource Data Module
Thanks Yves, Are you referring to nid?
Original data reference - Holds the identifier of the <data> element that contains the original data for a given inline code. Value description: An XSD NMTOKEN that must be the value of the id attribute of one of the <data> element listed in the same <unit> element.
<source>Error in '<ph id="1" nid="d1"/>'.</source>
<target>Erreur dans '<ph id="1" nid="d1"/>'.</target>
I modeled resourceDataRef on the ref attribute:
Reference - Holds a reference for the associated annotation.
Value description: A value of the XSD type anyURI. The semantics of the value depends on the type of annotation:
<source>You use your own namespace.</source>
<target>Vous pouvez utiliser votre propre <mrk id="m1" type="comment" ref="#n1">namespace</mrk>.</target>
<note id="n1" appliesTo="target">Please check the translation for 'namespace'. On also can use 'espace de nom', but I think most technical manuals use the English term.</note>
I must confess, I do not understand the difference between these two referencing mechanisms. Can you please explain them to me?
Thanks for the updated document 9and the highlights) I had time to only glance at it but noticed one thing:
The resourceDataRef attribute is a URI.
Is the purpose to be able to point outside the XLIFF document as well?
If not and if the use case is only to reference an id (i.e. the value will be always resourceDataRef="#someid", then I wonder if it should be a URI. I think so far all reference to element has been done using the ID directly. For example in inline code to refer to <data> etc. Maybe it's better to be consistent? just wondering.
Sent: Monday, February 25, 2013 6:28 PM
Subject: [xliff] Latest Changes: Resource Data Module
Please find attached the latest changes for the ResourceData module based on the feedback from TC members in email and from the TC conference calls. Changes are highlighted in yellow. Please sned any additional feedback you may have. I am planning to author the docBook files add them to the specification this week.
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: