- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Tue, 3 Sep 2013 08:10:06 +0200
- To: <public-i18n-its-ig@w3.org>
Hi Felix, all, >>> - external resource ref still has a "todo". I tried to add one and >>> run into an issue: what if one element like "video" >>> has two external resouces (poster and src attributes): >>> generate two trans-units? >> >> Good point for the use case of multiple resources on the same element. >> ... > > how would you represent references to external resources in XLIFF? > The answer may not include a text unit - I don't know. There are no defined ways to represent this is 1.2 I think. So using itsx:externalResourceRef is the only thing I could think of. And I guess having the value be a list of IRI is the only solution I can think of. We'll have to see how that works. >> Actually there are many cases where feeding back data is almost >> impossible. For example any concrete piece of info set with >> a global rule. > > Understand and agree to everything else you and Dave said also with > regards to annotatorsRef. Now, with regards to merging back > termInfoRef and locInfoRef: should we then just saw "it cannot > be merged back"? Well, it really depends on how much wok one is willing to do. You could imagine creating place in the HTML or XML original to hold the information. It's just there is no way to standardize how that would be done. So maybe something like: "This document does not prescribe a way to feed back the value of local termInfoRef/locNoteRef markup as there are many valid ways to perform that task." Cheers, -ys
Received on Tuesday, 3 September 2013 06:12:07 UTC