OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only

XLIFF namespace design - Was: [xliff] matches as a module

  • 1.  XLIFF namespace design - Was: [xliff] matches as a module

    Posted 05-07-2012 16:53
    Hi, I started to wonder if it would be appropriate to have a general discussion on schema requirements, and namespace design for the XLIFF schemas. At the current point in time, I would assume that we would need to discuss at least the following requirements: 1. Coverage for a "core" schema - covering the XLIFF "core" ratified by the XLIFF TC 2. Coverage for one or more "satellite" schemas - covering one or more XLIFF "modules" ratified by the XLIFF TC 3. Ability to "use" existing namespaces (such as the one containing xml:lang) in 1. and 2. 4. Ability to compose the "core" schema from smaller pieces - e.g. if we decide to have the generic inline markup as a standalone schema so that it can be easily reused in many contexts 5. Ability to reuse parts or complete schemas ratified by the XLIFF TC in many other contexts After a first discussion of these requirements, we would need to match our results against the best practices involving homogeneous, heterogenous, and chameleon namespace design (see for example http://www.xfront.com/ZeroOneOrManyNamespaces.html ). I am unsure that we should mix a discussion on the use of catalogues in here. My feeling is that a statement like "You can only work with the XLIFF schemas when you have catalogue support, and design your catalogue in a certain way" will sound pretty strange to some ears. Cheers, Christian