← Prev in month
← Prev in thread
Next in thread →
Next in month →
FW: "named types" for XLIFF XSD
Title: Message This is a topic Christian would like to introduce at the upcoming XLIFF TC Meeting. -----Original Message----- From: Doug Domeny [mailto:] Sent: Wednesday, September 05, 2007 2:28 PM To: Lieske, Christian; Schnabel, Bryan S Subject: RE: "named types" for XLIFF XSD Sorry, it took awhile for me to get some time to look at this. Thanks for your thoughts. I'm in favor making extensive use of global types. It provides extensibility of the schema thereby making it easier to adopt without changing the XLIFF specification itself. If there are technical problems in the OASIS release process with changing the XSD files, then we can provide them as non-normative collateral. Regards, Doug From: Lieske, Christian [mailto:] Sent: Tuesday, August 21, 2007 12:39 PM To: Doug Domeny; Subject: "named types" for XLIFF XSD Hi there, Some more material … Cheers, Christian Only after I have created a new global complexType (e.g. for “file”), given a name to the type, and of course used the type for the declaration of the element … <xsd:element name="file" type="xlf:fileType"> <xsd:complexType name="fileType"> <xsd:sequence> <xsd:element ref="xlf:header" minOccurs="0"/> <xsd:element ref="xlf:body"/> </xsd:sequence> … </xsd:complexType> I have been able to work with I call “type substitution” or “redefine” … A. Type substitution <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xlf="urn:oasis:names:tc:xliff:document:1.2" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xsd:import namespace="urn:oasis:names:tc:xliff:document:1.2" schemaLocation="xliff-core-1.2-strict-xliff-24072007-namedTypes.xsd"/> <xsd:complexType name="fileType"> <xsd:complexContent> <xsd:restriction base="xlf:fileType"> <xsd:sequence> <xsd:element ref="xlf:header" minOccurs="0"/> <xsd:element ref="xlf:body"/> </xsd:sequence> </xsd:restriction> <!--<xsd:extension base="xlf:fileType">--> <!--</xsd:extension>--> </xsd:complexContent> </xsd:complexType> </xsd:schema> B. Redefine <xsd:schema xmlns:xlf="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:oasis:names:tc:xliff:document:1.2" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xsd:redefine schemaLocation=" xliff-core-1.2-strict-xliff-24072007-namedTypes.xsd "> <xsd:complexType name="fileType"> <xsd:complexContent> <xsd:restriction base="xlf:fileType"> <xsd:sequence> <xsd:element ref="xlf:header" minOccurs="0"/> <xsd:element ref="xlf:body"/> </xsd:sequence> </xsd:restriction> </xsd:complexContent> </xsd:complexType> </xsd:redefine> </xsd:schema> Christian Lieske MultiLingual Technology Solutions (MLT) SAP Language Services (SLS) SAP Globalization Services SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf Germany T +49 (62 27) 7 - 6 13 03 F +49 (62 27) 7 – 2 54 18 http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Léo Apotheker (stellvertretender Sprecher/Deputy CEO), Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
← Prev in month
← Prev in thread
Next in thread →
Next in month →