OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xliff] [Fwd: [xliff-comment] Schema issues with extensible attributes]

Hi Rodolfo and all:


Looks like the current Committee Draft ballot needs to be killed …


The TC spent several meetings in the 1.1 timeframe discussing whether to use the ##any or ##other namespaces in the extension definitions, and the decision was to use ##any specifically to enable adding XLIFF namespace attributes at the extension points.  Does anyone have any thoughts on the approach we should take to deal with the validation problems?


As for the sample files, I will correct the schemaLocation bugs and reissue hopefully the final version of the spec w/ supplementary files late today assuming we have addressed the ##any/##other issue.  I assume the strict sample file should have all deprecated structures removed – could someone please confirm this approach?






-----Original Message-----
From: Rodolfo M. Raya [mailto:rmraya@heartsome.net]
Sent: 17 October 2006 21:21
Subject: [xliff] [Fwd: [xliff-comment] Schema issues with extensible attributes]


-------- Forwarded Message --------
From: Asgeir Frimannsson <asgeirf@gmail.com>
To: xliff-comment@lists.oasis-open.org
Subject: [xliff-comment] Schema issues with extensible attributes
Date: Wed, 18 Oct 2006 10:12:32 +1000

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
 - 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)

The information in this e-mail is intended strictly for the addressee, without prejudices, as a confidential document. Should it reach you, not being the addressee, it is not to be made accessible to any other unauthorised person or copied, distributed or disclosed to any other third party as this would constitute an unlawful act under certain circumstances, unless prior approval is given for its transmission. The content of this e-mail is solely that of the sender and not necessarily that of Heartsome.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]