- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Wed, 3 Dec 2014 06:49:04 -0700
- To: "'XLIFF Main List'" <xliff@lists.oasis-open.org>
- CC: <public-i18n-its-ig@w3.org>
Hi David, all, >> If the module does not seem to have enough normative information, I am >> open to hear what it should contain in your and TC opinion. > > I'll try to provide a mock-up, maybe it'll clearer. I posted a mock-up here: https://lists.oasis-open.org/archives/xliff/201411/msg00096.html But I have not heard back anything yet. To summarize: - I think the appendix (informative) should deal with just the guidelines on how to extract to XLIFF a document that has ITS information. - I think the ITS Module section (normative) should state how each data category is represented (or not) in XLIFF, regardless how it is represented: through the core and/or existing modules, using itsm, or a mix of both. Otherwise we do not have a normative statement say for example that the Translate data category is represented by the translate core attribute. Cheers, -yves
Received on Wednesday, 3 December 2014 13:49:34 UTC