- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Wed, 20 Mar 2013 07:34:57 -0600
- To: <public-multilingualweb-lt@w3.org>
Hi all, To follow-up on the question of local Domain and External Resource. Currently those two data categories have only global rules. The idea is that the host vocabulary has some element ITS can point to where the information is stored. DITA, HTML5, and a few other formats are examples of that. XLIFF is simply an example where such element/attribute (where to store the domain info) does not exist. So we have to use an extended attribute. It's not a problem for the ITS/XLIFF mapping (we use extended attributes for other mappings). But it shows that there is a user case for local Domain and External Resource. The question is: Is it worth to take to pain to add local markup for Domain? The case of External Resource is a bit different. 2.0 defines a way to point to things that are external references, so the host format always has the elements/attributes to store the local info. In XLIFF we simply need a way to store the info, and that is likely a need rather unique to XLIFF. I would say: there is no need for local markup for External Reference. cheers, -yves
Received on Wednesday, 20 March 2013 13:35:29 UTC