[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLIFF 1.2 Errata: <alt-trans> element
Hi all, The Content description for <alt-trans> states that: Zero or one <source> element, followed by Zero or one <seg-source> element, followed by One <target> element, followed by Zero, one or more <context-group>, <prop-group>, <note> elements, in any order, followed by Zero, one or more non-XLIFF elements. Followed by this statement: While for backward compatibility reasons no order is enforced for the elements before the non-XLIFF elements, the recommended order is the one in which they are listed here. The schema definition for <alt-trans>: <xsd:element name="alt-trans"> <xsd:complexType> <xsd:sequence> <xsd:element minOccurs="0" ref="xlf:source"/> <xsd:element minOccurs="0" ref="xlf:seg-source"/> <xsd:element maxOccurs="unbounded" ref="xlf:target"/> <xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:context-group"/> <xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:prop-group"/> <xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:note"/> <xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xsd:sequence> ... attributes ... </xsd:complexType> </xsd:element> Note that the schema does indeed enforce the order of <context-group>, <note> and <prop-group> elements. This may cause implementers some pain, and should be included in an errata document. 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]