[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Definition of "core" and "modules"
Specifically concerning the following points, I agree with Rodolfo completely – I don’t think there can be such a thing as a “specialization of the core”; if so I might fully support XLIFF 2.0 but not specialized XLIFF 2.0 “core” files which doesn’t make sense. If specializations are part of a particular module, as an addition to the core, I can openly state I don’t support it and still be XLIFF 2.0 compliant.
Such a module may add additional constructs to the XLIFF document that are fundamental to the data to be translated, not a representation of a process applied to the document. I’m not trying to be pedantic with this question, because I think it's rather important: is a module only something applied to a core, or can it be a specialization of the core for a particular purpose from the beginning?
A module defines elements that are not essential for creating an XLIFF file from common documents. If you are interested on gaming, you can add a request in the wiki for creating a module that defines the elements and attributes that the core lacks. The schema for gaming and the corresponding documentation can be added to XLIFF 2.0 if the TC agrees.
This language might imply that the starting point is always a pure-core XLIFF file.
Yes, that's right.
If, however, the module can represent a specialization for something like gaming with requirements that cannot be represented in a core-only format, it has implications for interoperability and they may not be optional at all: you couldn't just ignore the modules in the file and do some processing and the module would go beyond just embedding some tool-specific data in the XLIFF file. So if I create a variable text module like this, have I violated the fundamentals of XLIFF?
It is OK to have modules that create specializations. XLIFF enabled tools will have to support core, support for specializations would be optional.
Please see my comments below marked in blue.
--------------------------------------------------------------------- To unsubscribe, e-mail: firstname.lastname@example.org For additional commands, e-mail: email@example.com