[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: [xliff-comment] Schema issues with extensible attributes]
Hi all,
I just noticed that the deprecated attributes from 1.1 (eg. ts, tool) are
still being accepted in 1.2 using the strict schema. They are defined with
use="prohibited" in the strict schema. A good example of this is the example
XLIFF file provided with the specification
(Sample_AlmostEverything_1.2_strict.xlf) - the file still includes all
prohibited attributes, and validates fine with schema validators.
At first I thought this was a bug in the validator I'm using, but then i
noticed how the attribute extension points are defined in the XLIFF schema
(transitional and strict):
<xsd:anyAttribute namespace="##any" processContents="lax"/>
The XLIFF specification states that "Attributes of a namespace different
than XLIFF can be included in several XLIFF elements". The schema allows for
attributes of any namespace to be included, including xliff-namespace
attributes not defined in the specification. The schema and specification
are inconsistent here, and it seems the right thing to do would be to change
all anyAttribute elements to:
<xsd:anyAttribute namespace="##other" processContents="lax"/>
In addition, some issues with the strict sample XLIFF file provided with the
specification:
- schemaLocation points to xliff-core-1.2-strict-20060512.xsd (should point
to xliff-core-1.2-strict.xsd)
- As noted, It still includes the prohibited attributes (eg. tool, ts)
And similar with the transitional sample XLIFF file:
- schemaLocation points to xliff-core-1.2-transitional-20060512.xsd (should
point to xliff-core-1.2-transitional.xsd)
cheers,
asgeir
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]