Hi Ryan,
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.
cheers,
-yves
From: [mailto:] On Behalf Of Ryan King
Sent: Monday, February 25, 2013 6:28 PM
To:
Subject: [xliff] Latest Changes: Resource Data Module
Hello All,
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.
Thanks,
Ryan