[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: "Transparent" Change for Next Update to XLIFF XSD
Submitted for review.
I’ve attached the 1.2.1 schemas with both global types and global elements.
Facing my next XLIFF-related work item, I dare to approach you again with a question …
While working with the XLIFF XSD, I discovered that it would be quite handy if the XLIFF elements would be defined by means of types, rather than being defined “inline”.
<xsd:element name="header" type="xlf:headerType"/>
“Inline” (status quo)
<xsd:element name="skl" type="xlf:ElemType_ExternalReference" minOccurs="0"/>
<xsd:element ref="xlf:phase-group" minOccurs="0"/>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element name="glossary" type="xlf:ElemType_ExternalReference"/>
<xsd:element name="reference" type="xlf:ElemType_ExternalReference"/>
<xsd:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
Working with “types” would amongst others allow one to use the XSD “redefine” mechanism. This mechanism in turn is very helpful to enact checking mechanisms very easily (example: I could create an XSD which does not allow some of the XLIFF attribute values for “restype” or “datatype”).
From my understanding, switching to “type” would be transparent: the structure defined by the XSD would not be changed.
I take this to you first, since amongst others someone would have to make the change to the XSD – and my assumption is that you would be in a good position to do this.
If you would be in favor, and available to make the change, I would officially make the request to the TC to target this as part of the upcoming errata.
Disclosure Statements: http://www.sap.com/company/legal/impressum.epx