[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLIFF Variants - Wording in Spec
Dear fellow TC members,
I just reread the „variants“ section of the spec (see http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#Intro_Flavors) …
· Transitional - Applications that produce older versions of XLIFF may still use deprecated items. Deprecated elements and attributes are allowed. Non-XLIFF items are validated only to ensure they are well-formed. Use this variant to validate XLIFF documents that you read.
· Strict - All deprecated elements and attributes are not allowed. Obsolete items from previous versions of XLIFF are deprecated and should not be used when writing new XLIFF documents. In order for XLIFF documents with extensions to validate, the parser MUST find the schema for namespaced elements and attributes, and elements and attributes MUST be valid. Use this variant to validate XLIFF documents that you create.
To me, the wording sounds a bit weird if you look at tools that both read and write XLIFF.
From my point of view, these tools (or rather their implementers) could interpret the wording as “When you write, do “strict” even if the input was “transitional”. I guess that not the message we want to convey, since producers who supply transitional XLIFF expect that to get transitional XLIFF back.
Example: “prop-group” is deprecated and thus not part of “strict”. Thus, a scenario like the following would be possible/required with the current wording
- Read “prop-group”
- Write something else (that captures “prop-group”)
What’s your view on this?
I could imagine to add a clarification for this in the XLIFF 1.2 errata (see http://wiki.oasis-open.org/xliff/XLIFF1.2/Errata).