[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: XLIFF 1.2 Errata: Asgeir's suggestions
Sorry, forgot the attachments earlier.
-----Original Message-----
From: Doug Domeny
Sent: Thursday, November 15, 2007 2:20 PM
To: 'bryan.s.schnabel@tektronix.com'; asgeirf@Gmail.com;
xliff-comment@lists.oasis-open.org; xliff@lists.oasis-open.org
Subject: XLIFF 1.2 Errata: Asgeir's suggestions
Bryan, Asgeir,
Attached are the updated transitional and strict schemas.
Please review the changes. In my opinion, all the changes are errata. In
fact, most of the errors were inherited from the XLIFF 1.1 schema.
The changes are:
1. W3C canonical form (so I could compare the files for changes)
The effective change was to use long notation for empty tags, e.g.,
<xsd:pattern value="x-[^\s]+"/> becomes <xsd:pattern
value="x-[^\s]+"></xsd:pattern>.
I used xmlcanon version 1.0, June 2002 by ElCel Technology
(http://www.elcel.com/)
2. [Wiki] Small inconsistency between the schema and specification with
regards to count-type attribute values
(http://lists.oasis-open.org/archives/xliff-comment/200710/msg00000.html
)
Removed xlf:state-qualifierValueList from AttrType_count-type.
Change made ONLY to the STRICT schema to remain compatible with the
XLIFF 1.1 schema.
3. [Wiki] Schema glitch in <xliff> element definition
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00000.html
)
Implemented Asgeir's suggested fix.
Change made to BOTH STRICT and TRANSITIONAL schemas.
4. [Wiki] Tool element inconsistency between spec and schema (schema
allows text)
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00001.html
)
Removed mixed="true" and changed ##any to ##other, per Asgeir's
suggested fix.
Change made ONLY to the STRICT schema to remain compatible with the
XLIFF 1.1 schema.
5. [Wiki] Content Model for <alt-trans> element enforces order
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00003.html
)
Allow any order of context-group, prop-group, and note.
Change made ONLY to the TRANSITIONAL schema to become compatible with
XLIFF 1.0. The XLIFF 1.1 schema is NOT compatible with XLIFF 1.0. Strict
schema enforces order as recommended by specification and Asgeir's
suggestion.
6. Implementer FAQ Entry / Suggestion
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00005.html
)
<header>, <trans-unit> and <bin-unit> enforce the order of tags that may
appear in any order in XLIFF 1.0, but where the specification recommends
a certain order. Note that <alt-trans> already enforced the order.
Change made ONLY to the STRICT schema to remain compatible with the
XLIFF 1.1 schema and XLIFF 1.0 DTD.
7. Suggestion for schema cleanup towards 2.0
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00004.html
)
Implemented Asgeir's suggested clean-up.
Change made to BOTH strict and transitional schemas.
8. I also removed the historical comments at the top of the schemas
because they were old.
Best regards,
Doug
-----Original Message-----
From: bryan.s.schnabel@tektronix.com
[mailto:bryan.s.schnabel@tektronix.com]
Sent: Thursday, November 01, 2007 2:44 PM
To: asgeirf@Gmail.com; xliff-comment@lists.oasis-open.org;
xliff@lists.oasis-open.org
Subject: RE: [xliff-comment] XLIFF 1.2 Errata: Schema glitch in <xliff>
element definition
Hi Asgeir,
Thank you for your additional comments, and thank you for continuing to
help us to make XLIFF better. I agree with the characterizations of
each of these as opportunities for errata (not substantive, requiring us
to restart the standard process).
I've collected your 4 observations here:
http://wiki.oasis-open.org/xliff/XLIFF2.0Goals, under the heading
"Issues collected from xliff-comment list (categorized by TC as
necessary for 1.2 errata, and 2.0 requirements)"
I think this is a good place to collect these issues for now. I look
forward to your joining the TC so that we can (with your participation)
consider the best way to *fine-tune* the spec and schema into alignment.
Sometimes a simple edit to one or the other is clear; sometimes
alignment is subjective, and difficult to translate from words to schema
code (spoken as an occasionally bleary schema writer myself).
Thanks as always,
Bryan
* sending to the xliff member mailing list as well
-----Original Message-----
From: Asgeir Frimannsson [mailto:asgeirf@Gmail.com]
Sent: Thursday, November 01, 2007 4:26 AM
To: xliff-comment@lists.oasis-open.org
Subject: [xliff-comment] XLIFF 1.2 Errata: Schema glitch in <xliff>
element definition
Hi all,
First of all: Doug, Bryan, thank you for your comments. I will be
joining to TC soon, I'm simply waiting for some practical/"political"
issues relating to the Oasis membership to be resolved. Until then
there might be some further comments on this list...
Now on to an inconsistency between the schema and the specification:
The <xliff> element contents description is defined as:
One or more <file> elements, followed by
Zero, one or more non-XLIFF elements.
This is represented in the schema as:
<xsd:element name="xliff">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded">
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other"
processContents="skip"/>
<xsd:element ref="xlf:file"/>
</xsd:sequence>
... attributes ...
</xsd:complexType>
</xsd:element>
Notice two things:
1) The sequence is switched around, so you have to end with a <file>
element, hence invalidating the 'followed by zero, one or more
non-XLIFF elements" statement.
2) This definition allows for mixing any number of <file> and other-ns
elements, as long as you end with a <file> element... This
representation allows much more than the specification, for example
the following instance:
<xliff>
<my:bogus ... />
<file ...> ... </file>
<my:bogus ... />
<my:bogus ... />
<my:bogus ... />
<my:bogus ... />
<file ...> ... </file>
<my:bogus ... />
<my:bogus ... />
<file ...> ... </file>
<!--- a file element must be the last element -->
</xliff>
To represent the intent of the specification, the <xliff> element
definition can be rewritten as:
<xsd:element name="xliff">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="xlf:file" maxOccurs="unbounded" minOccurs="1" />
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other"
processContents="skip"/>
</xsd:sequence>
... attributes ...
</xsd:complexType>
</xsd:element>
cheers,
asgeir
--
Asgeir Frimannsson
PhD Candidate
School of Software Engineering and Data Communications
Queensland University of Technology
126 Margaret Street, Level 3
Brisbane QLD 4001, Australia
Phone: (+61) 7 3138 9332 Mob: (+61) 405 412 696
Email: asgeirf@gmail.com
This publicly archived list offers a means to provide input to the
OASIS XML Localisation Interchange File Format (XLIFF) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: xliff-comment-subscribe@lists.oasis-open.org
Unsubscribe: xliff-comment-unsubscribe@lists.oasis-open.org
List help: xliff-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/xliff-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
This publicly archived list offers a means to provide input to the
OASIS XML Localisation Interchange File Format (XLIFF) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: xliff-comment-subscribe@lists.oasis-open.org
Unsubscribe: xliff-comment-unsubscribe@lists.oasis-open.org
List help: xliff-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/xliff-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]