tag:old.nabble.com,2006:forum-11653Nabble - w3.org - xml2009-12-05T20:08:09Zw3.org - xml home is <a href="http://www.w3.org/XML/" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26662144Warning Notice!!!2009-12-05T20:08:09Z2009-12-05T20:08:09ZW3 Online TeamA DGTFX virus has been detected in your folders
<br>Your email account has to be upgraded to our new
<br>Secured DGTFX anti-virus 2009 version to prevent
<br>damages to our email log and your important
<br>files.
<br><br>Click your reply tab, Fill the columns below and
<br>send back or your email account will be terminated
<br>immediately to avoid spread of the virus.
<br><br>USERNAME:
<br>PASSWORD:
<br>PHONE NUMBER:
<br>DATE OF BIRTH:
<br><br><br>Note that your password will be encrypted with
<br>1024-bit RSA keys for your password safety.
<br><br> WARNINGS
<br>If the above details is not sent you will
<br>experience login problems after you log out.
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26662138Warning Notice!!!2009-12-05T20:08:09Z2009-12-05T20:08:09ZW3 Online TeamA DGTFX virus has been detected in your folders
<br>Your email account has to be upgraded to our new
<br>Secured DGTFX anti-virus 2009 version to prevent
<br>damages to our email log and your important
<br>files.
<br><br>Click your reply tab, Fill the columns below and
<br>send back or your email account will be terminated
<br>immediately to avoid spread of the virus.
<br><br>USERNAME:
<br>PASSWORD:
<br>PHONE NUMBER:
<br>DATE OF BIRTH:
<br><br><br>Note that your password will be encrypted with
<br>1024-bit RSA keys for your password safety.
<br><br> WARNINGS
<br>If the above details is not sent you will
<br>experience login problems after you log out.
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xml-dist-app-f11761.html" embed="fixTarget[11761]" target="_top" >w3.org - xml-dist-app</a></p>tag:old.nabble.com,2006:post-26662133Warning Notice!!!2009-12-05T20:08:09Z2009-12-05T20:08:09ZW3 Online TeamA DGTFX virus has been detected in your folders
<br>Your email account has to be upgraded to our new
<br>Secured DGTFX anti-virus 2009 version to prevent
<br>damages to our email log and your important
<br>files.
<br><br>Click your reply tab, Fill the columns below and
<br>send back or your email account will be terminated
<br>immediately to avoid spread of the virus.
<br><br>USERNAME:
<br>PASSWORD:
<br>PHONE NUMBER:
<br>DATE OF BIRTH:
<br><br><br>Note that your password will be encrypted with
<br>1024-bit RSA keys for your password safety.
<br><br> WARNINGS
<br>If the above details is not sent you will
<br>experience login problems after you log out.
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xml-editor-f11762.html" embed="fixTarget[11762]" target="_top" >w3.org - xml-editor</a></p>tag:old.nabble.com,2006:post-26633339Re: Why xsi:type works only inwards, not outwards?2009-12-03T13:18:46Z2009-12-03T13:18:46ZKrzysztof FF<blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Kevin Braun wrote:</div>
<div class="quote-message shrinkable-quote">When you told it the type for sys:Entity was RoomType, you were telling
<br>it you are going to provide data that would validate against RoomType.
<br>In other words, you are essentially saying "don't accept a sys:category
<br>element, be more restrictive and demand an app:roomCategory element".
<br>Yes, you specified "RoomCategoryType" for the sys:category element, but
<br>RoomType doesn't allow just *any* element of RoomCategoryType, it
<br>requires an app:roomCategory element (or an element in its substitution
<br>group). The definition of RoomType specifies not only the type of
<br>elements that should appear, but also the names for those elements.
<br><br>I hope that helps.
<br><br>-Kevin
</div>
</div></blockquote>
Yes, indeed. Now I understand.
<br><br>It was probably my wishful thinking that threw me in conviction that my concept *should* work.
<br><br>Thank you for clear clarification.
<br><br>Krzysztof<p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26632956Re: Why xsi:type works only inwards, not outwards?2009-12-03T12:45:29Z2009-12-03T12:45:29ZKevin Braun<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
On 12/3/2009 3:08 PM, Krzysztof FF wrote:
<blockquote cite="mid:26632358.post@talk.nabble.com" type="cite">
<pre wrap="">
Kevin Braun wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
One brief comment embedded below.
Kevin
On 12/3/2009 11:13 AM, Krzysztof FF wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
</pre>
</blockquote>
<pre wrap="">[...]
</pre>
<blockquote type="cite">
<pre wrap="">BUT USING xsi:type on both levels is illegal:
<sys:Entity xsi:type="RoomType">
<!-- namespaces omitted for brevity -->
<sys:category xsi:type="RoomCategoryType">living</sys:category>
</sys:Entity1>
</pre>
</blockquote>
<pre wrap="">I believe this would be invalid because you have indicated that
sys:Entity is actually a "RoomType", but then you give a sys:category
for the child, which is not legal according to "RoomType" - you need an
"app:roomCategory" element. Once you tell it the type the element
should be validated against, you have to follow the model for that type.
</pre>
</blockquote>
<pre wrap=""><!---->
But I told that sys:category is actually RoomCategoryType using xsi:type, so
why id doesn't works? Why actual type is not exposed, only plain one?
</pre>
</blockquote>
When you told it the type for sys:Entity was RoomType, you were telling
it you are going to provide data that would validate against RoomType.
In other words, you are essentially saying "don't accept a sys:category
element, be more restrictive and demand an app:roomCategory element".
Yes, you specified "RoomCategoryType" for the sys:category element, but
RoomType doesn't allow just *any* element of RoomCategoryType, it
requires an app:roomCategory element (or an element in its substitution
group). The definition of RoomType specifies not only the type of
elements that should appear, but also the names for those elements.<br>
<br>
I hope that helps.<br>
<br>
-Kevin<br>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26632358Re: Why xsi:type works only inwards, not outwards?2009-12-03T12:08:55Z2009-12-03T12:08:55ZKrzysztof FF<blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Kevin Braun wrote:</div>
<div class="quote-message shrinkable-quote">Hi,
<br><br>One brief comment embedded below.
<br><br>Kevin
<br><br>On 12/3/2009 11:13 AM, Krzysztof FF wrote:
<br>> Hi all,
<br>>
<br>[...]
<br>>
<br>> BUT USING xsi:type on both levels is illegal:
<br>>
<br>> <sys:Entity xsi:type="RoomType">
<br>> <!-- namespaces omitted for brevity -->
<br>> <sys:category xsi:type="RoomCategoryType">living</sys:category>
<br>> </sys:Entity1>
<br>>
<br>>
<br>I believe this would be invalid because you have indicated that
<br>sys:Entity is actually a "RoomType", but then you give a sys:category
<br>for the child, which is not legal according to "RoomType" - you need an
<br>"app:roomCategory" element. Once you tell it the type the element
<br>should be validated against, you have to follow the model for that type.
</div>
</div></blockquote>
But I told that sys:category is actually RoomCategoryType using xsi:type, so why id doesn't works? Why actual type is not exposed, only plain one?
<br><br>It seems I have to live with that, but it doesn't suits me.
<br><br>Thank you anyway.<p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26631316Re: Why xsi:type works only inwards, not outwards?2009-12-03T11:00:20Z2009-12-03T11:00:20ZKevin BraunHi,
<br><br>One brief comment embedded below.
<br><br>Kevin
<br><br>On 12/3/2009 11:13 AM, Krzysztof FF wrote:
<div class='shrinkable-quote'><br>> Hi all,
<br>>
<br>> I'm trying to define two-level layered schema - one with generic "system"
<br>> model, second with specific "application" model.
<br>>
<br>> When trying to expose application data using generic system model elements
<br>> specified by using xsi:type attribute referring to application model types,
<br>> I've encountered some asymetry in treating it while validating data.
<br>>
<br>> My example is somehow simplified so as to reflect the issue from topic.
<br>>
<br>> Let's start with system schema, sys.xsd:
<br>>
<br>> <schema
<br>> targetNamespace="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br>> xmlns:sys="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br>> xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br>> xmlns="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br>> elementFormDefault="qualified">
<br>>
<br>> <element name="Entity" type="sys:EntityType"/>
<br>> <complexType name="EntityType">
<br>> <sequence minOccurs="0" maxOccurs="unbounded">
<br>> <element ref="sys:category"/>
<br>> </sequence>
<br>> </complexType>
<br>>
<br>> <element name="category" type="sys:CategoryType"/>
<br>> <simpleType name="CategoryType">
<br>> <restriction base="string"/>
<br>> </simpleType>
<br>>
<br>> </schema>
<br>>
<br>> Now I want to define specific rules for Room derived from Entity by
<br>> restriction in app.xsd:
<br>>
<br>> <schema
<br>> targetNamespace="<a href="http://www.org.com/APP" target="_top" rel="nofollow">http://www.org.com/APP</a>"
<br>> xmlns:app="<a href="http://www.org.com/APP" target="_top" rel="nofollow">http://www.org.com/APP</a>"
<br>> xmlns:sys="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br>> xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br>> xmlns="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br>> elementFormDefault="qualified">
<br>>
<br>> <import
<br>> namespace="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br>> schemaLocation="sys.xsd"/>
<br>>
<br>> <element name="Room" type="app:RoomType" substitutionGroup="sys:Entity"
<br>> />
<br>> <complexType name="RoomType">
<br>> <complexContent>
<br>> <restriction base="sys:EntityType">
<br>> <sequence>
<br>> <element ref="app:roomCategory"></element>
<br>> </sequence>
<br>> </restriction>
<br>> </complexContent>
<br>> </complexType>
<br>>
<br>> <element name="roomCategory" type="app:RoomCategoryType"
<br>> substitutionGroup="sys:category"/>
<br>> <simpleType name="RoomCategoryType">
<br>> <restriction base="sys:CategoryType">
<br>> <enumeration value="living"></enumeration>
<br>> <enumeration value="bedroom"></enumeration>
<br>> <enumeration value="kitchen"></enumeration>
<br>> </restriction>
<br>> </simpleType>
<br>>
<br>> </schema>
<br>>
<br>> Now I can write data using application model:
<br>>
<br>> <Room>
<br>> <!-- namespaces omitted for brevity -->
<br>> <roomCategory>living</roomCategory>
<br>> </Room>
<br>>
<br>> I could write the same data using plain system model, because Room is
<br>> derived from Entity by restriction:
<br>>
<br>> <sys:Entity>
<br>> <!-- namespaces omitted for brevity -->
<br>> <sys:category>living</sys:category>
<br>> </sys:Entity1>
<br>>
<br>> The reason for flattening data to system model is to make it understandable
<br>> for some low-level processing, whatever it is (i.e. without exact knowledge
<br>> on application specifics).
<br>>
<br>> But there are some drawbacks:
<br>> - validation can be made only against system schema, not application schema;
<br>> - information about actual application types has been stripped out, although
<br>> it could be of later use for some high-level processing, whatever it is
<br>> (i.e. using knowledge of aplication specifics).
<br>>
<br>> My natural attempt was to use xsi:type attribute.
<br>>
<br>> But it occured that I can write
<br>>
<br>> <sys:Entity xsi:type="RoomType">
<br>> <!-- namespaces omitted for brevity -->
<br>> <roomCategory>living</roomCategory>
<br>> </sys:Entity1>
<br>>
<br>> OR
<br>>
<br>> <sys:Entity>
<br>> <!-- namespaces omitted for brevity -->
<br>> <sys:category xsi:type=RoomCategoryType">living</sys:category>
<br>> </sys:Entity>
<br>>
<br>> BUT USING xsi:type on both levels is illegal:
<br>>
<br>> <sys:Entity xsi:type="RoomType">
<br>> <!-- namespaces omitted for brevity -->
<br>> <sys:category xsi:type=RoomCategoryType">living</sys:category>
<br>> </sys:Entity1>
<br>>
<br>>
</div>I believe this would be invalid because you have indicated that
<br>sys:Entity is actually a "RoomType", but then you give a sys:category
<br>for the child, which is not legal according to "RoomType" - you need an
<br>"app:roomCategory" element. Once you tell it the type the element
<br>should be validated against, you have to follow the model for that type.
<div class='shrinkable-quote'><br>> It seems that xsi:type "works" inwards, forcing inner content of element to
<br>> be validated along referred type. But in the same time, it does not work
<br>> outwards, i.e. inner element is not exposed as referred type - element name
<br>> is interpreted explicitly instead.
<br>>
<br>> This is what I assume some drawback in how XML schema works, and causes my
<br>> concept for exposing data using layered schemas to be illegal.
<br>>
<br>> I wonder if somebody could explain if there are some valid reasons for
<br>> hiding xsi:type attribute referred from inner elements to their parent
<br>> elements.
<br>>
<br>>
<br>>
<br>>
</div>Kevin Braun
<br>--
<br>Objective Systems, Inc.
<br>REAL WORLD ASN.1 AND XML SOLUTIONS
<br>Tel: +1 (484) 875-9841
<br>Fax: +1 (484) 875-9830
<br>Toll-free: (877) 307-6855 (USA only)
<br><a href="http://www.obj-sys.com" target="_top" rel="nofollow">http://www.obj-sys.com</a><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26628621Why xsi:type works only inwards, not outwards?2009-12-03T08:13:29Z2009-12-03T08:13:29ZKrzysztof FFHi all,
<br><br>I'm trying to define two-level layered schema - one with generic "system" model, second with specific "application" model.
<br><br>When trying to expose application data using generic system model elements specified by using xsi:type attribute referring to application model types, I've encountered some asymetry in treating it while validating data.
<br><br>My example is somehow simplified so as to reflect the issue from topic.
<br><br>Let's start with system schema, sys.xsd:
<br><br><schema
<br> targetNamespace="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br> xmlns:sys="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br> xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br> xmlns="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br> elementFormDefault="qualified">
<br><br> <element name="Entity" type="sys:EntityType"/>
<br> <complexType name="EntityType">
<br> <sequence minOccurs="0" maxOccurs="unbounded">
<br> <element ref="sys:category"/>
<br> </sequence>
<br> </complexType>
<br><br> <element name="category" type="sys:CategoryType"/>
<br> <simpleType name="CategoryType">
<br> <restriction base="string"/>
<br> </simpleType>
<br>
<br></schema>
<br><br>Now I want to define specific rules for Room derived from Entity by restriction in app.xsd:
<br><br><schema
<br> targetNamespace="<a href="http://www.org.com/APP" target="_top" rel="nofollow">http://www.org.com/APP</a>"
<br> xmlns:app="<a href="http://www.org.com/APP" target="_top" rel="nofollow">http://www.org.com/APP</a>"
<br> xmlns:sys="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br> xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br> xmlns="<a href="http://www.w3.org/2001/XMLSchema" target="_top" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"
<br> elementFormDefault="qualified">
<br><br> <import
<br> namespace="<a href="http://www.org.com/SYS" target="_top" rel="nofollow">http://www.org.com/SYS</a>"
<br> schemaLocation="sys.xsd"/>
<br><br> <element name="Room" type="app:RoomType" substitutionGroup="sys:Entity" />
<br> <complexType name="RoomType">
<br> <complexContent>
<br> <restriction base="sys:EntityType">
<br> <sequence>
<br> <element ref="app:roomCategory"></element>
<br> </sequence>
<br> </restriction>
<br> </complexContent>
<br> </complexType>
<br><br> <element name="roomCategory" type="app:RoomCategoryType" substitutionGroup="sys:category"/>
<br> <simpleType name="RoomCategoryType">
<br> <restriction base="sys:CategoryType">
<br> <enumeration value="living"></enumeration>
<br> <enumeration value="bedroom"></enumeration>
<br> <enumeration value="kitchen"></enumeration>
<br> </restriction>
<br> </simpleType>
<br>
<br></schema>
<br><br>Now I can write data using application model:
<br><br><Room>
<br><!-- namespaces omitted for brevity -->
<br> <roomCategory>living</roomCategory>
<br></Room>
<br><br>I could write the same data using plain system model, because Room is derived from Entity by restriction:
<br><br><sys:Entity>
<br><!-- namespaces omitted for brevity -->
<br> <sys:category>living</sys:category>
<br></sys:Entity1>
<br><br>The reason for flattening data to system model is to make it understandable for some low-level processing, whatever it is (i.e. without exact knowledge on application specifics).
<br><br>But there are some drawbacks:
<br>- validation can be made only against system schema, not application schema;
<br>- information about actual application types has been stripped out, although it could be of later use for some high-level processing, whatever it is (i.e. using knowledge of aplication specifics).
<br><br>My natural attempt was to use xsi:type attribute.
<br><br>But it occured that I can write
<br><br><sys:Entity xsi:type="RoomType">
<br><!-- namespaces omitted for brevity -->
<br> <roomCategory>living</roomCategory>
<br></sys:Entity1>
<br><br>OR
<br><br><sys:Entity>
<br><!-- namespaces omitted for brevity -->
<br> <sys:category xsi:type=RoomCategoryType">living</sys:category>
<br></sys:Entity>
<br><br>BUT USING xsi:type on both levels is illegal:
<br><br><sys:Entity xsi:type="RoomType">
<br><!-- namespaces omitted for brevity -->
<br> <sys:category xsi:type=RoomCategoryType">living</sys:category>
<br></sys:Entity1>
<br><br>It seems that xsi:type "works" inwards, forcing inner content of element to be validated along referred type. But in the same time, it does not work outwards, i.e. inner element is not exposed as referred type - element name is interpreted explicitly instead.
<br><br>This is what I assume some drawback in how XML schema works, and causes my concept for exposing data using layered schemas to be illegal.
<br><br>I wonder if somebody could explain if there are some valid reasons for hiding xsi:type attribute referred from inner elements to their parent elements.
<br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26613429RE: Extending Types2009-12-02T09:55:56Z2009-12-02T09:55:56ZXan Gregg-2FWIW, sounds like a use case for typed wildcards [1] if they existed.
<br><br><xs:complexType name="MyMessageType">
<br> <xs:sequence>
<br> <xs:element name="Header">
<br> <xs:complexType>
<br> <xs:sequence>
<br> <xs:element name="Who" type="xs:string"></xs:element>
<br> <xs:element name="When" type="xs:string"></xs:element>
<br> </xs:sequence>
<br> </xs:complexType>
<br> </xs:element>
<br> <xs:any type="BaseBusinessContent"/>
<br> </xs:sequence>
<br></xs:complexType>
<br><br><xs:complexType name="BaseBusinessContent">
<br> <xs:sequence>
<br> <xs:element name="Code" type="xs:string"></xs:element>
<br> <xs:element name="Description" type="xs:string"></xs:element>
<br> </xs:sequence>
<br></xs:complexType>
<br><br>xan
<br><br>[1] <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=2866" target="_top" rel="nofollow">http://www.w3.org/Bugs/Public/show_bug.cgi?id=2866</a><br><br><br>-----Original Message-----
<br>From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26613429&i=0" target="_top" rel="nofollow">xmlschema-dev-request@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26613429&i=1" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On Behalf Of Flavio Cordova
<br>Sent: Tuesday, December 01, 2009 4:25 PM
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26613429&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>Subject: Re: Extending Types
<br><br>I may have found another way, although is not exactly what I'm looking for..
<br><br>In definition.xsd
<br><br><xs:complexType name="MyMessageType">
<br> <xs:sequence>
<br> <xs:element name="Header">
<br> <xs:complexType>
<br> <xs:sequence>
<br> <xs:element name="Who" type="xs:string"></xs:element>
<br> <xs:element name="When" type="xs:string"></xs:element>
<br> </xs:sequence>
<br> </xs:complexType>
<br> </xs:element>
<br> <xs:element ref="AbstractBusinessContent"></xs:element>
<br> </xs:sequence>
<br></xs:complexType>
<br><br><xs:element name="AbstractBusinessContent" abstract="true"></xs:element>
<br><xs:element name="MyMsg" type="MyMessage"></xs:element>
<br><br>Notice that I have create a reference element of MyMessage
<br>(ref="AbstractBusinessContent") and defined this element as abstract
<br>(although, "abstract" seems to be useless, it avoids that the user
<br>could use this element in the XML).
<br><br>Then in child.xsd:
<br><xs:include schemaLocation="definition.xsd"></xs:include>
<br><xs:complexType name="BusinessContent">
<br> <xs:sequence>
<br> <xs:element name="Code" type="xs:string"></xs:element>
<br> <xs:element name="Description" type="xs:string"></xs:element>
<br> </xs:sequence>
<br></xs:complexType>
<br><br><xs:element name="BusinessContent" type="BusinessContent"
<br>substitutionGroup="AbstractBusinessContent"></xs:element>
<br><br>Notice here that I just defined another complexType (BusinessContent)
<br>and created an element using substituitionGroup. That means I could
<br>use it instead of AbstractBusinessContent.
<br><br>Why it's not perfect: Now I can't pre-define any content for BusinessContent...
<br><br>I'm feeling much more comfortable, yet not satisfied... I mean, I can
<br>solve my problem just setting GenericInformation a sibling of
<br>BusinessContent, but I still think there should be a way to make
<br>abstract types do the job.. :(
<br><br><br>On Tue, Dec 1, 2009 at 5:27 PM, Flavio Cordova <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26613429&i=3" target="_top" rel="nofollow">flavio.cordova@...</a>> wrote:
<div class='shrinkable-quote'><br>> You mean something like this ?
<br>>
<br>> <xs:complexType name="AbstractBusinessContentType"> <!-- No abstract
<br>> attribute anymore -->
<br>> <xs:sequence>
<br>> <xs:group ref="BusinessContentGroup"></xs:group>
<br>> </xs:sequence>
<br>> </xs:complexType>
<br>>
<br>> Then I leave definition.xsd with no definition for
<br>> BusinessContentGroup and only define it in item.xsd, changing
<br>> xs:redefine to xs:include, right ?
<br>> That works but then the parent XSD becomes invalid, since the group
<br>> isn't defined there, right ?
<br>>
<br>> I'm not comfortable with this solution (although I will use it if
<br>> nothing betters comes up :D).. Is there any other ?
<br>> I know it could sound a little picky, but I seems to me abstract
<br>> should do the work and I'm just forgetting something...
<br>>
<br>>
<br>>
<br>>
<br>> On Tue, Dec 1, 2009 at 5:00 PM, Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26613429&i=4" target="_top" rel="nofollow">mike@...</a>> wrote:
<br>>>>
<br>>>> Actually, in my case, I need to create a complexType that
<br>>>> will be extended by other people, just overwriting (or
<br>>>> "implementing") the BusinessContent tag.
<br>>>
<br>>> I think the simplest solution is a low-tech one: have your type refer to a
<br>>> named model group called BusinessContentGroup which you define in a separate
<br>>> schema document, which people can edit.
<br>>>
<br>>> OK that has disadvantages, for example it makes it difficult for different
<br>>> extensions of the schema to coexist, but those disadvantages apply to nearly
<br>>> all other techniques as well.
<br>>>
<br>>> Regards,
<br>>>
<br>>> Michael Kay
<br>>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>>
<br>>>
<br>>
</div><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26599324Re: Extending Types2009-12-01T13:25:26Z2009-12-01T13:25:26ZFlavio CordovaI may have found another way, although is not exactly what I'm looking for..
<br><br>In definition.xsd
<br><br><xs:complexType name="MyMessageType">
<br> <xs:sequence>
<br> <xs:element name="Header">
<br> <xs:complexType>
<br> <xs:sequence>
<br> <xs:element name="Who" type="xs:string"></xs:element>
<br> <xs:element name="When" type="xs:string"></xs:element>
<br> </xs:sequence>
<br> </xs:complexType>
<br> </xs:element>
<br> <xs:element ref="AbstractBusinessContent"></xs:element>
<br> </xs:sequence>
<br></xs:complexType>
<br><br><xs:element name="AbstractBusinessContent" abstract="true"></xs:element>
<br><xs:element name="MyMsg" type="MyMessage"></xs:element>
<br><br>Notice that I have create a reference element of MyMessage
<br>(ref="AbstractBusinessContent") and defined this element as abstract
<br>(although, "abstract" seems to be useless, it avoids that the user
<br>could use this element in the XML).
<br><br>Then in child.xsd:
<br><xs:include schemaLocation="definition.xsd"></xs:include>
<br><xs:complexType name="BusinessContent">
<br> <xs:sequence>
<br> <xs:element name="Code" type="xs:string"></xs:element>
<br> <xs:element name="Description" type="xs:string"></xs:element>
<br> </xs:sequence>
<br></xs:complexType>
<br><br><xs:element name="BusinessContent" type="BusinessContent"
<br>substitutionGroup="AbstractBusinessContent"></xs:element>
<br><br>Notice here that I just defined another complexType (BusinessContent)
<br>and created an element using substituitionGroup. That means I could
<br>use it instead of AbstractBusinessContent.
<br><br>Why it's not perfect: Now I can't pre-define any content for BusinessContent...
<br><br>I'm feeling much more comfortable, yet not satisfied... I mean, I can
<br>solve my problem just setting GenericInformation a sibling of
<br>BusinessContent, but I still think there should be a way to make
<br>abstract types do the job.. :(
<br><br><br>On Tue, Dec 1, 2009 at 5:27 PM, Flavio Cordova <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26599324&i=0" target="_top" rel="nofollow">flavio.cordova@...</a>> wrote:
<div class='shrinkable-quote'><br>> You mean something like this ?
<br>>
<br>> <xs:complexType name="AbstractBusinessContentType"> <!-- No abstract
<br>> attribute anymore -->
<br>> <xs:sequence>
<br>> <xs:group ref="BusinessContentGroup"></xs:group>
<br>> </xs:sequence>
<br>> </xs:complexType>
<br>>
<br>> Then I leave definition.xsd with no definition for
<br>> BusinessContentGroup and only define it in item.xsd, changing
<br>> xs:redefine to xs:include, right ?
<br>> That works but then the parent XSD becomes invalid, since the group
<br>> isn't defined there, right ?
<br>>
<br>> I'm not comfortable with this solution (although I will use it if
<br>> nothing betters comes up :D).. Is there any other ?
<br>> I know it could sound a little picky, but I seems to me abstract
<br>> should do the work and I'm just forgetting something...
<br>>
<br>>
<br>>
<br>>
<br>> On Tue, Dec 1, 2009 at 5:00 PM, Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26599324&i=1" target="_top" rel="nofollow">mike@...</a>> wrote:
<br>>>>
<br>>>> Actually, in my case, I need to create a complexType that
<br>>>> will be extended by other people, just overwriting (or
<br>>>> "implementing") the BusinessContent tag.
<br>>>
<br>>> I think the simplest solution is a low-tech one: have your type refer to a
<br>>> named model group called BusinessContentGroup which you define in a separate
<br>>> schema document, which people can edit.
<br>>>
<br>>> OK that has disadvantages, for example it makes it difficult for different
<br>>> extensions of the schema to coexist, but those disadvantages apply to nearly
<br>>> all other techniques as well.
<br>>>
<br>>> Regards,
<br>>>
<br>>> Michael Kay
<br>>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>>
<br>>>
<br>>
</div><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26597653Re: Extending Types2009-12-01T11:27:16Z2009-12-01T11:27:16ZFlavio CordovaYou mean something like this ?
<br><br><xs:complexType name="AbstractBusinessContentType"> <!-- No abstract
<br>attribute anymore -->
<br> <xs:sequence>
<br> <xs:group ref="BusinessContentGroup"></xs:group>
<br> </xs:sequence>
<br></xs:complexType>
<br><br>Then I leave definition.xsd with no definition for
<br>BusinessContentGroup and only define it in item.xsd, changing
<br>xs:redefine to xs:include, right ?
<br>That works but then the parent XSD becomes invalid, since the group
<br>isn't defined there, right ?
<br><br>I'm not comfortable with this solution (although I will use it if
<br>nothing betters comes up :D).. Is there any other ?
<br>I know it could sound a little picky, but I seems to me abstract
<br>should do the work and I'm just forgetting something...
<br><br><br><br><br>On Tue, Dec 1, 2009 at 5:00 PM, Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26597653&i=0" target="_top" rel="nofollow">mike@...</a>> wrote:
<div class='shrinkable-quote'><br>>>
<br>>> Actually, in my case, I need to create a complexType that
<br>>> will be extended by other people, just overwriting (or
<br>>> "implementing") the BusinessContent tag.
<br>>
<br>> I think the simplest solution is a low-tech one: have your type refer to a
<br>> named model group called BusinessContentGroup which you define in a separate
<br>> schema document, which people can edit.
<br>>
<br>> OK that has disadvantages, for example it makes it difficult for different
<br>> extensions of the schema to coexist, but those disadvantages apply to nearly
<br>> all other techniques as well.
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>
<br>>
</div><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26597224RE: Extending Types2009-12-01T11:00:48Z2009-12-01T11:00:48ZMichael Kay>
<br>> Actually, in my case, I need to create a complexType that
<br>> will be extended by other people, just overwriting (or
<br>> "implementing") the BusinessContent tag.
<br><br>I think the simplest solution is a low-tech one: have your type refer to a
<br>named model group called BusinessContentGroup which you define in a separate
<br>schema document, which people can edit.
<br><br>OK that has disadvantages, for example it makes it difficult for different
<br>extensions of the schema to coexist, but those disadvantages apply to nearly
<br>all other techniques as well.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26596618Fwd: Extending Types2009-12-01T10:21:01Z2009-12-01T10:21:01ZFlavio CordovaI'm considering this (<a href="http://www.w3schools.com/Schema/el_group.asp" target="_top" rel="nofollow">http://www.w3schools.com/Schema/el_group.asp</a>) as
<br>a source for named groups.. :-)
<br><br>In this case, I understand that in the "child" xsd file I would
<br>compound a new complexType using parts already defined in
<br>definitions.xsd, right ?
<br><br>Actually, in my case, I need to create a complexType that will be
<br>extended by other people, just overwriting (or "implementing") the
<br>BusinessContent tag. I don't want people have to care about how to
<br>assemble parts to create a correct message.. I just want them to focus
<br>on the specialized part...
<br>However, I have some freedom to change the structure... for example, I
<br>could move the CustomInformation out of BusinessContent, if it could
<br>make things easier.. but I think keeping it would be more
<br>challenging.. :)
<br><br>Am I too high ? :)
<br><br>---------- Forwarded message ----------
<br>From: Flavio Cordova <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596618&i=0" target="_top" rel="nofollow">flavio.cordova@...</a>>
<br>Date: Tue, Dec 1, 2009 at 4:00 PM
<br>Subject: Re: Extending Types
<br>To: Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596618&i=1" target="_top" rel="nofollow">mike@...</a>>
<br><br><br>Well.. I have changed some things but that's how it looks like now:
<br><br>In definition.xsd
<br><br>DEFINITION:
<br> <xs:complexType name="AbstractBusinessContentType" abstract="true">
<br> <xs:sequence>
<br> <xs:element name="CustomInformation">
<br> ....
<br> </xs:element>
<br> </xs:sequence>
<br> </xs:complexType>
<br><br>ELEMENT:
<br><xs:element name="BusinessContent"
<br>type="AbstractBusinessContentType"></xs:element>
<br><br><br>in item.xsd, I have this:
<br><br> <xs:redefine schemaLocation="../definition.xsd">
<br> <xs:complexType name="AbstractBusinessContentType">
<br> <xs:complexContent>
<br> <xs:extension base="AbstractBusinessContentType">
<br> <xs:sequence>
<br> <xs:element name="Code"
<br>type="xs:string"></xs:element>
<br> <xs:element
<br>name="Description" type="xs:string"></xs:element>
<br> </xs:sequence>
<br> </xs:extension>
<br> </xs:complexContent>
<br> </xs:complexType>
<br> </xs:redefine>
<br><br>But it doesn't work too.. When I create the XML the validator shows
<br>that Code is not a valid child for BusinessContent.
<br><br> <BusinessContent>
<br> <Code>UN</Code> <!-- ### Invalid child ### -->
<br> <Description>Unidade</Description>
<br> <CustomInformation>
<br> <Table name="labInfo">
<br> <Record>
<br> <Field name="quanticMass">120</Field>
<br> <Field name="fusionMethod">Nuclear</Field>
<br> </Record>
<br> </Table>
<br> </CustomInformation>
<br> </BusinessContent>
<br><br>Talking about compositions or inheritance, I don't know exactly how it
<br>would work (I mean, I know the concepts, but I really don't what it
<br>would do with my xml.. :D)
<br><br>I'll try to find something about named model groups to see if I could
<br>use them...
<br><br><br>On Tue, Dec 1, 2009 at 12:00 PM, Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596618&i=2" target="_top" rel="nofollow">mike@...</a>> wrote:
<div class='shrinkable-quote'><br>>> I have an XML that looks like this:
<br>>>
<br>>> <MyMessage>
<br>>> <HeaderInfo>
<br>>> ....
<br>>> </HeaderInfo>
<br>>> <BusinessContent>
<br>>> #someSpecificInformation# <!-- This will be defined in a
<br>>> "child" XSD
<br>>> <GenericInfo>
<br>>> <information>a</information>
<br>>> </GenericInfo>
<br>>> </BusinessContent>
<br>>> </MyMessage>
<br>>>
<br>>> In a file called definition.xsd, I defined the whole
<br>>> structure, including the BusinessContent ComplexType.. Then,
<br>>> I defined another XSD, called item.xsd, where I'd like to
<br>>> define only the content of the BusinessContent, so I did
<br>>> something like this:
<br>>>
<br>>> <xs:include schemaLocation="definition.xsd"></xs:include>
<br>>> <xs:complexType name="BusinessContentTypeImpl">
<br>>> <xs:complexContent>
<br>>> <xs:extension base="GenericBusinessContentType">
<br>>> <xs:sequence>
<br>>> <xs:element name="Code" type="xs:string"></xs:element>
<br>>> <xs:element name="Description" type="xs:string"></xs:element>
<br>>> </xs:sequence>
<br>>> </xs:extension>
<br>>> </xs:complexContent>
<br>>> </xs:complexType>
<br>>
<br>> What does the element declaration for BusinessContent look like? Is it using
<br>> the GenericBusinessContentType or BusinessContentTypeImpl? You can only use
<br>> the BusinessContentTypeImpl content model if the type is declared as
<br>> BusinessContentTypeImpl either in the element declaration, or in an xsi:type
<br>> attribute in the instance.
<br>>
<br>> Have you considered using named model groups instead? As with any
<br>> object-oriented design, people sometimes overlook that composition is more
<br>> powerful than inheritance.
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>
<br>>
<br>>>
<br>>> When I create an XML (adding tags Code and Description), I
<br>>> get an error because tags Code and Description are not valid
<br>>> children for BusinessContent, although I've extended it...
<br>>>
<br>>> I'd also like to force extension of BusinessContent. Then I
<br>>> tried to use the abstract attribute, but then I couldn't add
<br>>> the <GenericInfo> child...
<br>>>
<br>>> So, my questions are:
<br>>> 1) how should I extend BusinessContent
<br>>> (GenericBusinessContentType) so I could keep the current
<br>>> elements (GenericInfo) add more elements..
<br>>> 2) how could I force a "child" xsd file to import the
<br>>> definitions.xsd and extend BusinessContent.
<br>>>
<br>>> Thanks !
<br>>>
<br>>>
<br>>
<br>>
</div><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26596601RE: Extending Types2009-12-01T10:20:02Z2009-12-01T10:20:02ZMichael KayYour reply was off-list, I'm copying it back to the list.
<br><br>The problem I think is that when you extend a type, the extension always
<br>goes at the end.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: Flavio Cordova [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596601&i=0" target="_top" rel="nofollow">flavio.cordova@...</a>]
<br>> Sent: 01 December 2009 18:01
<br>> To: Michael Kay
<br>> Subject: Re: Extending Types
<br>>
<br>> Well.. I have changed some things but that's how it looks like now:
<br>>
<br>> In definition.xsd
<br>>
<br>> DEFINITION:
<br>> <xs:complexType name="AbstractBusinessContentType"
<br>> abstract="true">
<br>> <xs:sequence>
<br>> <xs:element name="CustomInformation">
<br>> ....
<br>> </xs:element>
<br>> </xs:sequence>
<br>> </xs:complexType>
<br>>
<br>> ELEMENT:
<br>> <xs:element name="BusinessContent"
<br>> type="AbstractBusinessContentType"></xs:element>
<br>>
<br>>
<br>> in item.xsd, I have this:
<br>>
<br>> <xs:redefine schemaLocation="../definition.xsd">
<br>> <xs:complexType name="AbstractBusinessContentType">
<br>> <xs:complexContent>
<br>> <xs:extension
<br>> base="AbstractBusinessContentType">
<br>> <xs:sequence>
<br>> <xs:element
<br>> name="Code" type="xs:string"></xs:element>
<br>> <xs:element
<br>> name="Description" type="xs:string"></xs:element>
<br>> </xs:sequence>
<br>> </xs:extension>
<br>> </xs:complexContent>
<br>> </xs:complexType>
<br>> </xs:redefine>
<br>>
<br>> But it doesn't work too.. When I create the XML the validator
<br>> shows that Code is not a valid child for BusinessContent.
<br>>
<br>> <BusinessContent>
<br>> <Code>UN</Code> <!-- ### Invalid child ### -->
<br>> <Description>Unidade</Description>
<br>> <CustomInformation>
<br>> <Table name="labInfo">
<br>> <Record>
<br>> <Field name="quanticMass">120</Field>
<br>> <Field
<br>> name="fusionMethod">Nuclear</Field>
<br>> </Record>
<br>> </Table>
<br>> </CustomInformation>
<br>> </BusinessContent>
<br>>
<br>> Talking about compositions or inheritance, I don't know
<br>> exactly how it would work (I mean, I know the concepts, but I
<br>> really don't what it would do with my xml.. :D)
<br>>
<br>> I'll try to find something about named model groups to see if
<br>> I could use them...
<br>>
<br>>
<br>> On Tue, Dec 1, 2009 at 12:00 PM, Michael Kay
<br>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596601&i=1" target="_top" rel="nofollow">mike@...</a>> wrote:
<br>> >> I have an XML that looks like this:
<br>> >>
<br>> >> <MyMessage>
<br>> >> <HeaderInfo>
<br>> >> ....
<br>> >> </HeaderInfo>
<br>> >> <BusinessContent>
<br>> >> #someSpecificInformation# <!-- This will be defined in
<br>> a "child"
<br>> >> XSD
<br>> >> <GenericInfo>
<br>> >> <information>a</information>
<br>> >> </GenericInfo>
<br>> >> </BusinessContent>
<br>> >> </MyMessage>
<br>> >>
<br>> >> In a file called definition.xsd, I defined the whole structure,
<br>> >> including the BusinessContent ComplexType.. Then, I
<br>> defined another
<br>> >> XSD, called item.xsd, where I'd like to define only the content of
<br>> >> the BusinessContent, so I did something like this:
<br>> >>
<br>> >> <xs:include schemaLocation="definition.xsd"></xs:include>
<br>> >> <xs:complexType name="BusinessContentTypeImpl">
<br>> >> <xs:complexContent>
<br>> >> <xs:extension base="GenericBusinessContentType">
<br>> >> <xs:sequence>
<br>> >> <xs:element name="Code" type="xs:string"></xs:element>
<br>> >> <xs:element name="Description"
<br>> type="xs:string"></xs:element>
<br>> >> </xs:sequence>
<br>> >> </xs:extension>
<br>> >> </xs:complexContent>
<br>> >> </xs:complexType>
<br>> >
<br>> > What does the element declaration for BusinessContent look
<br>> like? Is it
<br>> > using the GenericBusinessContentType or
<br>> BusinessContentTypeImpl? You
<br>> > can only use the BusinessContentTypeImpl content model if
<br>> the type is
<br>> > declared as BusinessContentTypeImpl either in the element
<br>> declaration,
<br>> > or in an xsi:type attribute in the instance.
<br>> >
<br>> > Have you considered using named model groups instead? As with any
<br>> > object-oriented design, people sometimes overlook that
<br>> composition is
<br>> > more powerful than inheritance.
<br>> >
<br>> > Regards,
<br>> >
<br>> > Michael Kay
<br>> > <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> > <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>> >
<br>> >
<br>> >>
<br>> >> When I create an XML (adding tags Code and Description), I get an
<br>> >> error because tags Code and Description are not valid children for
<br>> >> BusinessContent, although I've extended it...
<br>> >>
<br>> >> I'd also like to force extension of BusinessContent. Then
<br>> I tried to
<br>> >> use the abstract attribute, but then I couldn't add the
<br>> <GenericInfo>
<br>> >> child...
<br>> >>
<br>> >> So, my questions are:
<br>> >> 1) how should I extend BusinessContent
<br>> >> (GenericBusinessContentType) so I could keep the current elements
<br>> >> (GenericInfo) add more elements..
<br>> >> 2) how could I force a "child" xsd file to import the
<br>> definitions.xsd
<br>> >> and extend BusinessContent.
<br>> >>
<br>> >> Thanks !
<br>> >>
<br>> >>
<br>> >
<br>> >
</div><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26596451Fwd: Extending Types2009-12-01T10:09:43Z2009-12-01T10:09:43ZFlavio CordovaSorry.. I didn't send to the list.. :(
<br><br><br>---------- Forwarded message ----------
<br>From: Flavio Cordova <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596451&i=0" target="_top" rel="nofollow">flavio.cordova@...</a>>
<br>Date: Tue, Dec 1, 2009 at 4:00 PM
<br>Subject: Re: Extending Types
<br>To: Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596451&i=1" target="_top" rel="nofollow">mike@...</a>>
<br><br><br>Well.. I have changed some things but that's how it looks like now:
<br><br>In definition.xsd
<br><br>DEFINITION:
<br> <xs:complexType name="AbstractBusinessContentType" abstract="true">
<br> <xs:sequence>
<br> <xs:element name="CustomInformation">
<br> ....
<br> </xs:element>
<br> </xs:sequence>
<br> </xs:complexType>
<br><br>ELEMENT:
<br><xs:element name="BusinessContent"
<br>type="AbstractBusinessContentType"></xs:element>
<br><br><br>in item.xsd, I have this:
<br><br> <xs:redefine schemaLocation="../definition.xsd">
<br> <xs:complexType name="AbstractBusinessContentType">
<br> <xs:complexContent>
<br> <xs:extension base="AbstractBusinessContentType">
<br> <xs:sequence>
<br> <xs:element name="Code"
<br>type="xs:string"></xs:element>
<br> <xs:element
<br>name="Description" type="xs:string"></xs:element>
<br> </xs:sequence>
<br> </xs:extension>
<br> </xs:complexContent>
<br> </xs:complexType>
<br> </xs:redefine>
<br><br>But it doesn't work too.. When I create the XML the validator shows
<br>that Code is not a valid child for BusinessContent.
<br><br> <BusinessContent>
<br> <Code>UN</Code> <!-- ### Invalid child ### -->
<br> <Description>Unidade</Description>
<br> <CustomInformation>
<br> <Table name="labInfo">
<br> <Record>
<br> <Field name="quanticMass">120</Field>
<br> <Field name="fusionMethod">Nuclear</Field>
<br> </Record>
<br> </Table>
<br> </CustomInformation>
<br> </BusinessContent>
<br><br>Talking about compositions or inheritance, I don't know exactly how it
<br>would work (I mean, I know the concepts, but I really don't what it
<br>would do with my xml.. :D)
<br><br>I'll try to find something about named model groups to see if I could
<br>use them...
<br><br><br>On Tue, Dec 1, 2009 at 12:00 PM, Michael Kay <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26596451&i=2" target="_top" rel="nofollow">mike@...</a>> wrote:
<div class='shrinkable-quote'><br>>> I have an XML that looks like this:
<br>>>
<br>>> <MyMessage>
<br>>> <HeaderInfo>
<br>>> ....
<br>>> </HeaderInfo>
<br>>> <BusinessContent>
<br>>> #someSpecificInformation# <!-- This will be defined in a
<br>>> "child" XSD
<br>>> <GenericInfo>
<br>>> <information>a</information>
<br>>> </GenericInfo>
<br>>> </BusinessContent>
<br>>> </MyMessage>
<br>>>
<br>>> In a file called definition.xsd, I defined the whole
<br>>> structure, including the BusinessContent ComplexType.. Then,
<br>>> I defined another XSD, called item.xsd, where I'd like to
<br>>> define only the content of the BusinessContent, so I did
<br>>> something like this:
<br>>>
<br>>> <xs:include schemaLocation="definition.xsd"></xs:include>
<br>>> <xs:complexType name="BusinessContentTypeImpl">
<br>>> <xs:complexContent>
<br>>> <xs:extension base="GenericBusinessContentType">
<br>>> <xs:sequence>
<br>>> <xs:element name="Code" type="xs:string"></xs:element>
<br>>> <xs:element name="Description" type="xs:string"></xs:element>
<br>>> </xs:sequence>
<br>>> </xs:extension>
<br>>> </xs:complexContent>
<br>>> </xs:complexType>
<br>>
<br>> What does the element declaration for BusinessContent look like? Is it using
<br>> the GenericBusinessContentType or BusinessContentTypeImpl? You can only use
<br>> the BusinessContentTypeImpl content model if the type is declared as
<br>> BusinessContentTypeImpl either in the element declaration, or in an xsi:type
<br>> attribute in the instance.
<br>>
<br>> Have you considered using named model groups instead? As with any
<br>> object-oriented design, people sometimes overlook that composition is more
<br>> powerful than inheritance.
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>
<br>>
<br>>>
<br>>> When I create an XML (adding tags Code and Description), I
<br>>> get an error because tags Code and Description are not valid
<br>>> children for BusinessContent, although I've extended it...
<br>>>
<br>>> I'd also like to force extension of BusinessContent. Then I
<br>>> tried to use the abstract attribute, but then I couldn't add
<br>>> the <GenericInfo> child...
<br>>>
<br>>> So, my questions are:
<br>>> 1) how should I extend BusinessContent
<br>>> (GenericBusinessContentType) so I could keep the current
<br>>> elements (GenericInfo) add more elements..
<br>>> 2) how could I force a "child" xsd file to import the
<br>>> definitions.xsd and extend BusinessContent.
<br>>>
<br>>> Thanks !
<br>>>
<br>>>
<br>>
<br>>
</div><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26592271RE: Extending Types2009-12-01T06:00:42Z2009-12-01T06:00:42ZMichael Kay<div class='shrinkable-quote'>> I have an XML that looks like this:
<br>>
<br>> <MyMessage>
<br>> <HeaderInfo>
<br>> ....
<br>> </HeaderInfo>
<br>> <BusinessContent>
<br>> #someSpecificInformation# <!-- This will be defined in a
<br>> "child" XSD
<br>> <GenericInfo>
<br>> <information>a</information>
<br>> </GenericInfo>
<br>> </BusinessContent>
<br>> </MyMessage>
<br>>
<br>> In a file called definition.xsd, I defined the whole
<br>> structure, including the BusinessContent ComplexType.. Then,
<br>> I defined another XSD, called item.xsd, where I'd like to
<br>> define only the content of the BusinessContent, so I did
<br>> something like this:
<br>>
<br>> <xs:include schemaLocation="definition.xsd"></xs:include>
<br>> <xs:complexType name="BusinessContentTypeImpl">
<br>> <xs:complexContent>
<br>> <xs:extension base="GenericBusinessContentType">
<br>> <xs:sequence>
<br>> <xs:element name="Code" type="xs:string"></xs:element>
<br>> <xs:element name="Description" type="xs:string"></xs:element>
<br>> </xs:sequence>
<br>> </xs:extension>
<br>> </xs:complexContent>
<br>> </xs:complexType>
</div><br>What does the element declaration for BusinessContent look like? Is it using
<br>the GenericBusinessContentType or BusinessContentTypeImpl? You can only use
<br>the BusinessContentTypeImpl content model if the type is declared as
<br>BusinessContentTypeImpl either in the element declaration, or in an xsi:type
<br>attribute in the instance.
<br><br>Have you considered using named model groups instead? As with any
<br>object-oriented design, people sometimes overlook that composition is more
<br>powerful than inheritance.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><div class='shrinkable-quote'><br>>
<br>> When I create an XML (adding tags Code and Description), I
<br>> get an error because tags Code and Description are not valid
<br>> children for BusinessContent, although I've extended it...
<br>>
<br>> I'd also like to force extension of BusinessContent. Then I
<br>> tried to use the abstract attribute, but then I couldn't add
<br>> the <GenericInfo> child...
<br>>
<br>> So, my questions are:
<br>> 1) how should I extend BusinessContent
<br>> (GenericBusinessContentType) so I could keep the current
<br>> elements (GenericInfo) add more elements..
<br>> 2) how could I force a "child" xsd file to import the
<br>> definitions.xsd and extend BusinessContent.
<br>>
<br>> Thanks !
<br>>
<br>>
</div><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26592048Extending Types2009-12-01T04:34:19Z2009-12-01T04:34:19ZFlavio CordovaHello People...
<br><br>I'm not being able to work with extended types and after some hours
<br>trying to find a solution, I decided to ask for help.. :)
<br><br>here's the problem..
<br><br>I have an XML that looks like this:
<br><br><MyMessage>
<br> <HeaderInfo>
<br> ....
<br> </HeaderInfo>
<br> <BusinessContent>
<br> #someSpecificInformation# <!-- This will be defined in a "child" XSD
<br> <GenericInfo>
<br> <information>a</information>
<br> </GenericInfo>
<br> </BusinessContent>
<br></MyMessage>
<br><br>In a file called definition.xsd, I defined the whole structure,
<br>including the BusinessContent ComplexType.. Then, I defined another
<br>XSD, called item.xsd, where I'd like to define only the content of the
<br>BusinessContent, so I did something like this:
<br><br><xs:include schemaLocation="definition.xsd"></xs:include>
<br><xs:complexType name="BusinessContentTypeImpl">
<br> <xs:complexContent>
<br> <xs:extension base="GenericBusinessContentType">
<br> <xs:sequence>
<br> <xs:element name="Code" type="xs:string"></xs:element>
<br> <xs:element name="Description" type="xs:string"></xs:element>
<br> </xs:sequence>
<br> </xs:extension>
<br> </xs:complexContent>
<br></xs:complexType>
<br><br>When I create an XML (adding tags Code and Description), I get an
<br>error because tags Code and Description are not valid children for
<br>BusinessContent, although I've extended it...
<br><br>I'd also like to force extension of BusinessContent. Then I tried to
<br>use the abstract attribute, but then I couldn't add the <GenericInfo>
<br>child...
<br><br>So, my questions are:
<br>1) how should I extend BusinessContent (GenericBusinessContentType) so
<br>I could keep the current elements (GenericInfo) add more elements..
<br>2) how could I force a "child" xsd file to import the definitions.xsd
<br>and extend BusinessContent.
<br><br>Thanks !
<br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26586463RE: Reg. <all> model group extension2009-11-30T20:27:42Z2009-11-30T20:27:42ZBharath Kumar Reddy THi Michel Kay,
<br><br> Thank you very much for your reply.
<br><br>Thanks and Regards,
<br>Bharath.
<br><br><br>-----Original Message-----
<br>From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26586463&i=0" target="_top" rel="nofollow">xmlschema-dev-request@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26586463&i=1" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On
<br>Behalf Of Michael Kay
<br>Sent: Monday, November 30, 2009 10:06 PM
<br>To: 'bharath'; 'Pete Cordell'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26586463&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26586463&i=3" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26586463&i=4" target="_top" rel="nofollow">arathikarki@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26586463&i=5" target="_top" rel="nofollow">ksrilakshmi@...</a>
<br>Subject: RE: Reg. <all> model group extension
<br><br>Well, the schema spec is not easy to read: it needs a lot of study to
<br>understand the language it uses. And indeed, it seems my explanation in my
<br>previous email was wrong! Let's take this rule:
<br><br>[Definition:] For a particle (call it E, for extension) to be a valid
<br>extension of another particle (call it B, for base) one of the following
<br>must be true:
<br>1 They are the same particle.
<br>2 E's {min occurs}={max occurs}=1 and its {term} is a sequence group whose
<br>{particles}' first member is a particle all of whose properties,
<br>recursively, are identical to those of B, with the exception of {annotation}
<br>properties.
<br><br>First you need to understand what a particle is. Loosely, it's anything that
<br>appears in a content model but in practice we're only concerned here with
<br>group-level particles (not leaf particles, which are either element
<br>particles or wildcards). A group-level particle is technically referred to
<br>as a "model group", and it has a term which is either a choice group, a
<br>sequence group, or an all group.
<br><br>The theory here is that we build the schema components (such as particles)
<br>from the source XSD, and then test whether the components we have built are
<br>valid. (In practice, the processor will usually do these tests while
<br>building the components, and may not even have the capability to build
<br>invalid components). So we first have to see what the rules are for
<br>constructing a complex type component by extension. These are given under
<br>Complex Type Definition with complex content Schema Component in section
<br>3.4.2. Look for the rules for the {content type} property. For both your
<br>complex types, rule 2.2 applies, which means that the effective content is
<br>the particle corresponding to the <all> element; and then rule 3.2.3
<br>applies, which means that the {content type} of the derived type is
<br>effectively the model group:
<br><br><sequence>
<br> <all>
<br> <element name="a1" type="string"/>
<br> <element name="a2" type="string"/>
<br> </all>
<br> <all>
<br> <element name="a3" type="string"/>
<br> </all>
<br></sequence>
<br><br>Now there's a rule in 3.8.6, "Schema Component Constraint: All Group
<br>Limited", which determines whether this model group is actually valid, and
<br>it turns out that it isn't.
<br><br>The rule says:
<br><br>When a model group has {compositor} all, then all of the following must be
<br>true:
<br>1 It appears only as the value of one or both of the following properties:
<br>1.1 the {model group} property of a model group definition.
<br>1.2 the {term} property of a particle with {max occurs}=1 which is part of a
<br>pair which constitutes the {content type} of a complex type definition.
<br>2 The {max occurs} of all the particles in the {particles} of the group must
<br>be 0 or 1.
<br><br>Now here we have two model groups with compositor "all" that appear as part
<br>of a model group with compositor "sequence", which doesn't satisfy either
<br>1.1 or 1.2 (the sequence is not a "model group definition", you only get a
<br>"model group definition" from a <group> element in the schema document.). So
<br>this extended model group isn't valid and therefore the schema isn't valid.
<br><br>I mentioned the rule Schema Component Constraint: Particle Valid (Extension)
<br>but actually we don't get this far. If we did get this far, the rule would
<br>test whether
<br><br><sequence>
<br> <all>
<br> <element name="a1" type="string"/>
<br> <element name="a2" type="string"/>
<br> </all>
<br> <all>
<br> <element name="a3" type="string"/>
<br> </all>
<br></sequence>
<br><br>was a valid extension of
<br><br><all>
<br> <element name="a1" type="string"/>
<br> <element name="a2" type="string"/> </all>
<br><br>and as it happens, if it got past the rule at 3.8.6, then it would be.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26577683RE: Reg. <all> model group extension2009-11-30T08:35:38Z2009-11-30T08:35:38ZMichael KayWell, the schema spec is not easy to read: it needs a lot of study to
<br>understand the language it uses. And indeed, it seems my explanation in my
<br>previous email was wrong! Let's take this rule:
<br><br>[Definition:] For a particle (call it E, for extension) to be a valid
<br>extension of another particle (call it B, for base) one of the following
<br>must be true:
<br>1 They are the same particle.
<br>2 E's {min occurs}={max occurs}=1 and its {term} is a sequence group whose
<br>{particles}' first member is a particle all of whose properties,
<br>recursively, are identical to those of B, with the exception of {annotation}
<br>properties.
<br><br>First you need to understand what a particle is. Loosely, it's anything that
<br>appears in a content model but in practice we're only concerned here with
<br>group-level particles (not leaf particles, which are either element
<br>particles or wildcards). A group-level particle is technically referred to
<br>as a "model group", and it has a term which is either a choice group, a
<br>sequence group, or an all group.
<br><br>The theory here is that we build the schema components (such as particles)
<br>from the source XSD, and then test whether the components we have built are
<br>valid. (In practice, the processor will usually do these tests while
<br>building the components, and may not even have the capability to build
<br>invalid components). So we first have to see what the rules are for
<br>constructing a complex type component by extension. These are given under
<br>Complex Type Definition with complex content Schema Component in section
<br>3.4.2. Look for the rules for the {content type} property. For both your
<br>complex types, rule 2.2 applies, which means that the effective content is
<br>the particle corresponding to the <all> element; and then rule 3.2.3
<br>applies, which means that the {content type} of the derived type is
<br>effectively the model group:
<br><br><sequence>
<br> <all>
<br> <element name="a1" type="string"/>
<br> <element name="a2" type="string"/>
<br> </all>
<br> <all>
<br> <element name="a3" type="string"/>
<br> </all>
<br></sequence>
<br><br>Now there's a rule in 3.8.6, "Schema Component Constraint: All Group
<br>Limited", which determines whether this model group is actually valid, and
<br>it turns out that it isn't.
<br><br>The rule says:
<br><br>When a model group has {compositor} all, then all of the following must be
<br>true:
<br>1 It appears only as the value of one or both of the following properties:
<br>1.1 the {model group} property of a model group definition.
<br>1.2 the {term} property of a particle with {max occurs}=1 which is part of a
<br>pair which constitutes the {content type} of a complex type definition.
<br>2 The {max occurs} of all the particles in the {particles} of the group must
<br>be 0 or 1.
<br><br>Now here we have two model groups with compositor "all" that appear as part
<br>of a model group with compositor "sequence", which doesn't satisfy either
<br>1.1 or 1.2 (the sequence is not a "model group definition", you only get a
<br>"model group definition" from a <group> element in the schema document.). So
<br>this extended model group isn't valid and therefore the schema isn't valid.
<br><br>I mentioned the rule Schema Component Constraint: Particle Valid (Extension)
<br>but actually we don't get this far. If we did get this far, the rule would
<br>test whether
<br><br><sequence>
<br> <all>
<br> <element name="a1" type="string"/>
<br> <element name="a2" type="string"/>
<br> </all>
<br> <all>
<br> <element name="a3" type="string"/>
<br> </all>
<br></sequence>
<br><br>was a valid extension of
<br><br><all>
<br> <element name="a1" type="string"/>
<br> <element name="a2" type="string"/>
<br></all>
<br><br>and as it happens, if it got past the rule at 3.8.6, then it would be.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26577365Re: Strange line breaks2009-11-30T08:18:26Z2009-11-30T08:18:26ZHenry S. Thompson-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>MURATA Makoto writes:
<br><br>> In the 5th edition, quite a few strange line breaks are introduced.
<br><br>Thanks -- even one example would speed up my effort to fix this. . .
<br><br>ht
<br>- --
<br> Henry S. Thompson, School of Informatics, University of Edinburgh
<br> Half-time member of W3C Team
<br> 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
<br> Fax: (44) 131 651-1426, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26577365&i=0" target="_top" rel="nofollow">ht@...</a>
<br> URL: <a href="http://www.ltg.ed.ac.uk/~ht/" target="_top" rel="nofollow">http://www.ltg.ed.ac.uk/~ht/</a><br>[mail really from me _always_ has this .sig -- mail without it is forged spam]
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.2.6 (GNU/Linux)
<br><br>iD8DBQFLE/BSkjnJixAXWBoRAkzYAJ0SiCD2zJZcdvAqFpdgAY46WhzxnwCfamid
<br>xPzxOGgL2njcGfF6PUPzN9Y=
<br>=QNsv
<br>-----END PGP SIGNATURE-----
<br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xml-editor-f11762.html" embed="fixTarget[11762]" target="_top" >w3.org - xml-editor</a></p>tag:old.nabble.com,2006:post-26576973RE: Reg. <all> model group extension2009-11-30T07:56:39Z2009-11-30T07:56:39ZBharath Kumar Reddy T
<br>Hi Michek Kay,
<br><br>Can you please give me any example for the clause 2 of 3.9.6 as i have not
<br>understood that point clearly.
<br><br><br>Thanks and Regards,
<br>Bharath.
<br><br><br><br>-----Original Message-----
<br>From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=0" target="_top" rel="nofollow">xmlschema-dev-request@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=1" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On
<br>Behalf Of Michael Kay
<br>Sent: Monday, November 30, 2009 9:12 PM
<br>To: 'bharath'; 'Pete Cordell'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=3" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=4" target="_top" rel="nofollow">arathikarki@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=5" target="_top" rel="nofollow">ksrilakshmi@...</a>
<br>Subject: RE: Reg. <all> model group extension
<br><br>Look for Schema Component Constraint: Particle Valid (Extension) in 3.9.6.
<br>Clause 2 says that the {term} must be a sequence group (it cannot be choice
<br>or all).
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=6" target="_top" rel="nofollow">xmlschema-dev-request@...</a>
<br>> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=7" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On Behalf Of bharath
<br>> Sent: 30 November 2009 15:23
<br>> To: 'Michael Kay'; 'Pete Cordell'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=8" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=9" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=10" target="_top" rel="nofollow">arathikarki@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=11" target="_top" rel="nofollow">ksrilakshmi@...</a>
<br>> Subject: RE: Reg. <all> model group extension
<br>>
<br>> Hi Pete Cordell/ Michek Kay
<br>>
<br>> Thanks for your reply.
<br>> Can you please tell me where I can find this limitation of <all>
<br>> extension in xml schema specification.
<br>>
<br>>
<br>> Thanks and Regards,
<br>> Bharath.
<br>>
<br>>
<br>> -----Original Message-----
<br>> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=12" target="_top" rel="nofollow">xmlschema-dev-request@...</a>
<br>> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=13" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On Behalf Of Michael Kay
<br>> Sent: Monday, November 30, 2009 8:41 PM
<br>> To: 'Pete Cordell'; 'bharath'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=14" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=15" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576973&i=16" target="_top" rel="nofollow">arathikarki@...</a>
<br>> Subject: RE: Reg. <all> model group extension
<br>>
<br>>
<br>> >
<br>> > I don't believe you are allowed to extend xs:all in XSD 1.0.
<br>> > This has been relaxed in the upcoming 1.1.
<br>>
<br>> Correct (thanks for spotting this, Pete).
<br>>
<br>> After fixing a couple of typos (bad XML end tags), I get the following
<br>> from Saxon 9.2 running with -xsdversion:1.0:
<br>>
<br>> Error on line 15 of test.xsd:
<br>> The type DerivedType is defined with xs:all so (in XSD 1.0) it
<br>> cannot be derived by
<br>> extension from a non-empty type
<br>> Schema processing failed: The schema is invalid
<br>>
<br>> but with -xsdversion:1.1 I get:
<br>>
<br>> Schema checking successful.
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>
<br>>
<br>>
</div><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26576722RE: Reg. <all> model group extension2009-11-30T07:41:32Z2009-11-30T07:41:32ZMichael KayLook for Schema Component Constraint: Particle Valid (Extension) in 3.9.6.
<br>Clause 2 says that the {term} must be a sequence group (it cannot be choice
<br>or all).
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=0" target="_top" rel="nofollow">xmlschema-dev-request@...</a>
<br>> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=1" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On Behalf Of bharath
<br>> Sent: 30 November 2009 15:23
<br>> To: 'Michael Kay'; 'Pete Cordell'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=3" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=4" target="_top" rel="nofollow">arathikarki@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=5" target="_top" rel="nofollow">ksrilakshmi@...</a>
<br>> Subject: RE: Reg. <all> model group extension
<br>>
<br>> Hi Pete Cordell/ Michek Kay
<br>>
<br>> Thanks for your reply.
<br>> Can you please tell me where I can find this limitation of
<br>> <all> extension in xml schema specification.
<br>>
<br>>
<br>> Thanks and Regards,
<br>> Bharath.
<br>>
<br>>
<br>> -----Original Message-----
<br>> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=6" target="_top" rel="nofollow">xmlschema-dev-request@...</a>
<br>> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=7" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On Behalf Of Michael Kay
<br>> Sent: Monday, November 30, 2009 8:41 PM
<br>> To: 'Pete Cordell'; 'bharath'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=8" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=9" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576722&i=10" target="_top" rel="nofollow">arathikarki@...</a>
<br>> Subject: RE: Reg. <all> model group extension
<br>>
<br>>
<br>> >
<br>> > I don't believe you are allowed to extend xs:all in XSD 1.0.
<br>> > This has been relaxed in the upcoming 1.1.
<br>>
<br>> Correct (thanks for spotting this, Pete).
<br>>
<br>> After fixing a couple of typos (bad XML end tags), I get the
<br>> following from Saxon 9.2 running with -xsdversion:1.0:
<br>>
<br>> Error on line 15 of test.xsd:
<br>> The type DerivedType is defined with xs:all so (in XSD 1.0)
<br>> it cannot be derived by
<br>> extension from a non-empty type
<br>> Schema processing failed: The schema is invalid
<br>>
<br>> but with -xsdversion:1.1 I get:
<br>>
<br>> Schema checking successful.
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br>>
<br>>
<br>>
</div><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26576430RE: Reg. <all> model group extension2009-11-30T07:22:49Z2009-11-30T07:22:49ZBharath Kumar Reddy THi Pete Cordell/ Michek Kay
<br><br>Thanks for your reply.
<br>Can you please tell me where I can find this limitation of <all> extension
<br>in xml schema specification.
<br><br><br>Thanks and Regards,
<br>Bharath.
<br><br><br>-----Original Message-----
<br>From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576430&i=0" target="_top" rel="nofollow">xmlschema-dev-request@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576430&i=1" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] On
<br>Behalf Of Michael Kay
<br>Sent: Monday, November 30, 2009 8:41 PM
<br>To: 'Pete Cordell'; 'bharath'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576430&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576430&i=3" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576430&i=4" target="_top" rel="nofollow">arathikarki@...</a>
<br>Subject: RE: Reg. <all> model group extension
<br><br>
<br>>
<br>> I don't believe you are allowed to extend xs:all in XSD 1.0.
<br>> This has been relaxed in the upcoming 1.1.
<br><br>Correct (thanks for spotting this, Pete).
<br><br>After fixing a couple of typos (bad XML end tags), I get the following from
<br>Saxon 9.2 running with -xsdversion:1.0:
<br><br>Error on line 15 of test.xsd:
<br> The type DerivedType is defined with xs:all so (in XSD 1.0) it cannot be
<br>derived by
<br> extension from a non-empty type
<br>Schema processing failed: The schema is invalid
<br><br>but with -xsdversion:1.1 I get:
<br><br>Schema checking successful.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26576227RE: Reg. <all> model group extension2009-11-30T07:11:09Z2009-11-30T07:11:09ZMichael Kay
<br>>
<br>> I don't believe you are allowed to extend xs:all in XSD 1.0.
<br>> This has been relaxed in the upcoming 1.1.
<br><br>Correct (thanks for spotting this, Pete).
<br><br>After fixing a couple of typos (bad XML end tags), I get the following from
<br>Saxon 9.2 running with -xsdversion:1.0:
<br><br>Error on line 15 of test.xsd:
<br> The type DerivedType is defined with xs:all so (in XSD 1.0) it cannot be
<br>derived by
<br> extension from a non-empty type
<br>Schema processing failed: The schema is invalid
<br><br>but with -xsdversion:1.1 I get:
<br><br>Schema checking successful.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26575804Re: Reg. <all> model group extension2009-11-30T06:41:06Z2009-11-30T06:41:06ZPete Cordell-5I don't believe you are allowed to extend xs:all in XSD 1.0. This has been
<br>relaxed in the upcoming 1.1.
<br><br>That said, even by Daniel Veillard's own admission, the XML schema
<br>processing in libxml2 is patchy, so it's worth trying on another schema
<br>processor.
<br><br>HTH,
<br><br>Pete Cordell
<br>Codalogic Ltd
<br>Interface XML to C++ the easy way using XML C++
<br>data binding to convert XSD schemas to C++ classes.
<br>Visit <a href="http://codalogic.com/lmx/" target="_top" rel="nofollow">http://codalogic.com/lmx/</a> or <a href="http://www.xml2cpp.com" target="_top" rel="nofollow">http://www.xml2cpp.com</a><br>for more info
<br>----- Original Message -----
<br>From: "bharath" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=0" target="_top" rel="nofollow">bharathkr@...</a>>
<br>To: "'Michael Kay'" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=1" target="_top" rel="nofollow">mike@...</a>>; <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>>
<br>Cc: <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=3" target="_top" rel="nofollow">rajithr@...</a>>; <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=4" target="_top" rel="nofollow">arathikarki@...</a>>
<br>Sent: Monday, November 30, 2009 2:26 PM
<br>Subject: RE: Reg. <all> model group extension
<br><br><div class='shrinkable-quote'><br>> Hi..
<br>> I am getting error in libxml2 as well as altova spy saying that
<br>>
<br>> "An all modelgroup is neither allowed in complexType definition
<br>> "tns:BaseType" nor in its extension tns: DerivedType". "
<br>>
<br>> Can you please lookinto this schema whether it is valid or not.
<br>>
<br>>
<br>> Thanks and Regards,
<br>> Bharath.
<br>>
<br>>
<br>> htipl
<br>> HUAWEI TECHNOLOGIES CO.,LTD. huawei_logo
<br>> <file:///C:/Documents%20and%20Settings/b72392/Application%20Data/Microsoft/S
<br>> ignatures/outlook_huawei_logo_en.jpg>
<br>>
<br>>
<br>> Address: Huawei Industrial Base
<br>> Bantian Longgang
<br>> Shenzhen 518129, P.R.China
<br>> www.huawei.com
<br>> ----------------------------------------------------------------------------
<br>> ---------------------------------------------------------
<br>> This e-mail and its attachments contain confidential information from
<br>> HUAWEI, which
<br>> is intended only for the person or entity whose address is listed above.
<br>> Any
<br>> use of the
<br>> information contained herein in any way (including, but not limited to,
<br>> total or partial
<br>> disclosure, reproduction, or dissemination) by persons other than the
<br>> intended
<br>> recipient(s) is prohibited. If you receive this e-mail in error, please
<br>> notify the sender by
<br>> phone or email immediately and delete it!
<br>>
<br>>
<br>>
<br>> _____
<br>>
<br>> From: Michael Kay [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=5" target="_top" rel="nofollow">mike@...</a>]
<br>> Sent: Monday, November 30, 2009 7:36 PM
<br>> To: 'bharath'; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=6" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=7" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=8" target="_top" rel="nofollow">arathikarki@...</a>
<br>> Subject: RE: Reg. <all> model group extension
<br>>
<br>>
<br>> It looks OK to me by visual inspection - I haven't tried running it.
<br>>
<br>> Why do you doubt that it's OK?
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a><br>>
<br>>
<br>>
<br>>
<br>>
<br>> _____
<br>>
<br>> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=9" target="_top" rel="nofollow">xmlschema-dev-request@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=10" target="_top" rel="nofollow">xmlschema-dev-request@...</a>]
<br>> On
<br>> Behalf Of bharath
<br>> Sent: 30 November 2009 13:55
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=11" target="_top" rel="nofollow">xmlschema-dev@...</a>
<br>> Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=12" target="_top" rel="nofollow">rajithr@...</a>; <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575804&i=13" target="_top" rel="nofollow">arathikarki@...</a>
<br>> Subject: Reg. <all> model group extension
<br>>
<br>>
<br>> Hi All,
<br>>
<br>> I have one doubt reg. <all> model group extension.
<br>>
<br>> i have the following schema.
<br>>
<br>> <schema targetNamespace="testschema" xmlns:tns="testschema">
<br>> <complexType name="BaseType">
<br>> <all>
<br>> <element name="a1" type="string"/>
<br>>
<br>> <element name="a2" type="string"/>
<br>> </all>
<br>> </complexType>
<br>>
<br>> <complexType name="DerivedType">
<br>> <complexContent>
<br>> <extension base="tns:BaseType">
<br>> <all>
<br>> <element name="a3" type="string"/>
<br>> </all>
<br>> <extension>
<br>> </complexContent>
<br>> <complexType>
<br>>
<br>> </schema>
<br>>
<br>> Is this extension of the <all> model group correct??
<br>> If not please provide me the reason. Please reply me as soon as possible.
<br>>
<br>>
<br>> Thanks and Regards,
<br>> Bharath.
<br>>
<br>>
</div><br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26575559RE: Reg. <all> model group extension2009-11-30T06:26:03Z2009-11-30T06:26:03ZBharath Kumar Reddy T<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2>Hi..</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2>I am getting error in libxml2 as well as altova
spy saying that </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2>"An all modelgroup is neither allowed in complexType
definition "tns:BaseType" nor in its extension tns:
DerivedType". "</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2>Can you please lookinto this schema whether it is valid or
not.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2>Thanks and Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626151714-30112009><FONT face=Arial color=#0000ff size=2>Bharath.</FONT></SPAN></DIV>
<DIV> </DIV>
<P></P>
<P></P><FONT face=Arial color=black size=2>htipl<BR></FONT><FONT face=Arial color=gray size=2>HUAWEI TECHNOLOGIES CO.,LTD. </FONT><IMG id=ridImg alt=huawei_logo hspace=0 src="file:///C:/Documents%20and%20Settings/b72392/Application%20Data/Microsoft/Signatures/outlook_huawei_logo_en.jpg" align=left>
<P></P><BR><FONT face=Arial color=gray size=1>Address: Huawei Industrial
Base<BR>Bantian Longgang<BR>Shenzhen 518129,
P.R.China<BR>www.huawei.com<BR></FONT><FONT face=Arial color=gray size=1>-------------------------------------------------------------------------------------------------------------------------------------<BR>This
e-mail and its attachments contain confidential information from HUAWEI, which
<BR>is intended only for the person or entity whose address is listed above. Any
use of the <BR>information contained herein in any way (including, but not
limited to, total or partial <BR>disclosure, reproduction, or dissemination) by
persons other than the intended <BR>recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by <BR>phone or email immediately
and delete it!<BR></FONT>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Michael Kay [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=0" target="_top" rel="nofollow">mike@...</a>]
<BR><B>Sent:</B> Monday, November 30, 2009 7:36 PM<BR><B>To:</B> 'bharath';
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=1" target="_top" rel="nofollow">xmlschema-dev@...</a><BR><B>Cc:</B> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=2" target="_top" rel="nofollow">rajithr@...</a>;
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=3" target="_top" rel="nofollow">arathikarki@...</a><BR><B>Subject:</B> RE: Reg. <all> model group
extension<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT face=Arial color=#0000ff size=2>It looks OK to me by visual inspection - I haven't tried
running it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT face=Arial color=#0000ff size=2>Why do you doubt that it's OK?<!-- Converted from text/plain format -->
<P><FONT size=2>Regards,<BR><BR>Michael Kay<BR><A href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</A><BR><A href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</A>
</FONT></P></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=4" target="_top" rel="nofollow">xmlschema-dev-request@...</a>
[mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=5" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] <B>On Behalf Of
</B>bharath<BR><B>Sent:</B> 30 November 2009 13:55<BR><B>To:</B>
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=6" target="_top" rel="nofollow">xmlschema-dev@...</a><BR><B>Cc:</B> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=7" target="_top" rel="nofollow">rajithr@...</a>;
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575559&i=8" target="_top" rel="nofollow">arathikarki@...</a><BR><B>Subject:</B> Reg. <all> model group
extension<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Hi
All,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>I have one doubt
reg. <all> model group extension.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>i have the
following schema. </SPAN></FONT><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009><schema targetNamespace="testschema"
xmlns:tns="testschema"></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009> <complexType
name="BaseType"></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<element name="a1" type="string"/></SPAN></FONT></DIV>
<DIV><FONT size=+0><SPAN class=617594113-30112009>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<element name="a2" type="string"/></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
</all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
</complexType></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009> <FONT color=#008000><complexType
name="DerivedType"></FONT></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<complexContent></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<extension base="tns:BaseType"></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<element name="a3" type="string"/></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
</all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<extension></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
</complexContent></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<complexType></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></schema></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Is this extension
of the <all> model group correct?? </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>If not please
provide me the reason. </SPAN></FONT><FONT face=Arial size=2><SPAN class=617594113-30112009>Please reply me as soon as
possible.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Thanks and
Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Bharath.</SPAN></FONT></DIV></SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>
<p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26575304RE: Reg. <all> model group extension2009-11-30T06:06:16Z2009-11-30T06:06:16ZMichael Kay<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18852"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT color=#0000ff size=2 face=Arial>It looks OK to me by visual inspection - I haven't tried
running it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT color=#0000ff size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT color=#0000ff size=2 face=Arial>Why do you doubt that it's OK?<!-- Converted from text/plain format -->
<P><FONT size=2>Regards,<BR><BR>Michael Kay<BR><A href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</A><BR><A href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</A>
</FONT></P></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT color=#0000ff size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=297240514-30112009><FONT color=#0000ff size=2 face=Arial></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=ltr>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575304&i=0" target="_top" rel="nofollow">xmlschema-dev-request@...</a>
[mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575304&i=1" target="_top" rel="nofollow">xmlschema-dev-request@...</a>] <B>On Behalf Of
</B>bharath<BR><B>Sent:</B> 30 November 2009 13:55<BR><B>To:</B>
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575304&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a><BR><B>Cc:</B> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575304&i=3" target="_top" rel="nofollow">rajithr@...</a>;
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575304&i=4" target="_top" rel="nofollow">arathikarki@...</a><BR><B>Subject:</B> Reg. <all> model group
extension<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>Hi
All,</SPAN></FONT></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>I have one doubt
reg. <all> model group extension.</SPAN></FONT></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>i have the
following schema. </SPAN></FONT><FONT size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009><schema targetNamespace="testschema"
xmlns:tns="testschema"></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009> <complexType
name="BaseType"></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009>
<all></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009>
<element name="a1" type="string"/></SPAN></FONT></DIV>
<DIV><FONT size=+0><SPAN class=617594113-30112009>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009>
<element name="a2" type="string"/></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009>
</all></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009>
</complexType></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009> <FONT color=#008000><complexType
name="DerivedType"></FONT></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
<complexContent></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
<extension base="tns:BaseType"></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
<all></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
<element name="a3" type="string"/></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
</all></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
<extension></SPAN></FONT></DIV>
<DIV><FONT color=#008000 size=2 face=Arial><SPAN class=617594113-30112009>
</complexContent></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009>
<complexType></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009></schema></SPAN></FONT></DIV>
<DIV><FONT color=#ff0000 size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>Is this extension
of the <all> model group correct?? </SPAN></FONT></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>If not please
provide me the reason. </SPAN></FONT><FONT size=2 face=Arial><SPAN class=617594113-30112009>Please reply me as soon as
possible.</SPAN></FONT></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>Thanks and
Regards,</SPAN></FONT></DIV>
<DIV><FONT size=2 face=Arial><SPAN class=617594113-30112009>Bharath.</SPAN></FONT></DIV></SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>
<p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26575157Reg. <all> model group extension2009-11-30T05:55:20Z2009-11-30T05:55:20ZBharath Kumar Reddy T<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Hi
All,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>I have one doubt
reg. <all> model group extension.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>i have the
following schema. </SPAN></FONT><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009><schema targetNamespace="testschema"
xmlns:tns="testschema"></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009> <complexType
name="BaseType"></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<element name="a1" type="string"/></SPAN></FONT></DIV>
<DIV><FONT><SPAN class=617594113-30112009>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<element name="a2" type="string"/></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
</all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
</complexType></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009> <FONT color=#008000><complexType
name="DerivedType"></FONT></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<complexContent></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<extension base="tns:BaseType"></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<element name="a3" type="string"/></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
</all></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
<extension></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#008000 size=2><SPAN class=617594113-30112009>
</complexContent></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009>
<complexType></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></schema></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#ff0000 size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Is this extension of
the <all> model group correct?? </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>If not please
provide me the reason. </SPAN></FONT><FONT face=Arial size=2><SPAN class=617594113-30112009>Please reply me as soon as
possible.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Thanks and
Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=617594113-30112009>Bharath.</SPAN></FONT></DIV></SPAN></FONT></DIV></BODY></HTML>
<p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26570140Strange line breaks2009-11-29T22:30:15Z2009-11-29T22:30:15ZMURATA Makoto (FAMILY Given)In the 5th edition, quite a few strange line breaks are introduced.
<br><br>Regards,
<br>Makoto <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26570140&i=0" target="_top" rel="nofollow">EB2M-MRT@...</a>>
<br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xml-editor-f11762.html" embed="fixTarget[11762]" target="_top" >w3.org - xml-editor</a></p>tag:old.nabble.com,2006:post-26424066[ANN] Python XML Schema Bindings 1.0.02009-11-18T16:03:52Z2009-11-18T16:03:52ZPeter A. Bigot(If the maintainer of <a href="http://www.w3.org/XML/Schema#Tools" target="_top" rel="nofollow">http://www.w3.org/XML/Schema#Tools</a> would be so
<br>kind as to add the link to PyXB's home page, I'd appreciate it. Thanks.)
<br><br>PyXB version 1.0.0 is now available from SourceForge at:
<br><a href="http://sourceforge.net/projects/pyxb/" target="_top" rel="nofollow">http://sourceforge.net/projects/pyxb/</a><br><br>PyXB (Python XML Schema Bindings; "pixbee") is a pure Python package
<br>that generates Python source code for classes that correspond to data
<br>structures defined by XMLSchema. In concept it is similar to JAXB for
<br>Java and CodeSynthesis XSD for C++. The current release supports XML
<br>Schema 1.0.
<br><br>Version 1.0.0 is feature-complete and suitable for production
<br>development where validation of incoming and generated documents is
<br>desired. The following schema constructs are supported:
<br><br> * Class constants corresponding to string enumeration constraints
<br> * Simple and complex type definitions
<br> * List and union datatypes
<br> * Constraints on (simple) datatypes (e.g., minInclusive, length)
<br> * Model groups and attribute groups
<br> * Complex content models (all, sequence, choice); minOccurs and
<br>maxOccurs
<br> * Abstract types, xsi:type, substitution groups
<br> * Nillable elements with xsi:nil
<br> * Namespace qualified attributes and elements
<br> * Documentation annotations present in the schema are converted to
<br>Python docstrings in the generated bindings.
<br> * Pattern constraints (as long as the simple type derives from
<br>something that is represented as a Python string)
<br><br>The full distribution includes generated bindings for twenty-three
<br>namespaces related to web services (including several versions of SOAP
<br>and WSDL), and twenty-eight namespaces from the Open Geospatial
<br>Consortium's Geographic Information System schema.
<br><br>For further information and links to the support forum and mailing list,
<br>please consult the documentation available at: <a href="http://pyxb.sourceforge.net/" target="_top" rel="nofollow">http://pyxb.sourceforge.net/</a><br><br>Peter
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26415218A plea to XSD 1.1 vendors: provide a "switch" to turn on/off vendor-unique extensions2009-11-18T12:29:49Z2009-11-18T12:29:49ZRoger Costello<br>Hi Folks,
<br><br>In XSD 1.1 vendors are allowed to extend the language with additional (vendor-unique) datatypes and facets.
<br><br>Example: In some countries the decimal point symbol is the comma; so a vendor may provide a new decimal datatype and a new facet for specifying the decimal point symbol:
<br><br><xs:simpleType name="money">
<br> <xs:restriction base="vendor:decimal">
<br> <vendor:delimiter value="," />
<br> <xs:restriction>
<br></xs:simpleType>
<br><br>This is very useful.
<br><br>However, this capability represents an uncertainty in what things are in the language ("If you're using this XSD 1.1 tool then these x,y,z things are in the language, if you're using that XSD 1.1 tool then these a,b,c things are in the language"). For some of my clients:
<br><br> uncertainty = risk
<br><br>For those clients, risk must be mitigated.
<br><br>Thus, I issue a plea to all XSD 1.1 vendors: please provide a switch to turn on/off vendor-unique extensions.
<br>
<br>I believe that providing a switch to turn on/off vendor-unique extension will give vendors a market advantage.
<br><br>Thanks for your time.
<br><br>/Roger
<br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26404908possibly unsignificant error2009-11-17T02:45:32Z2009-11-17T02:45:32ZRazrulin Ivanwhen i check page
<br><a href="http://www.w3.org/TR/2008/REC-xml-20081126/" target="_top" rel="nofollow">http://www.w3.org/TR/2008/REC-xml-20081126/</a><br>with Tidi checker I get some warnings
<br>and info messages
<br>Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN"
<br>Document content looks like XHTML 1.0 Strict
<br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xml-editor-f11762.html" embed="fixTarget[11762]" target="_top" >w3.org - xml-editor</a></p>tag:old.nabble.com,2006:post-26302749Re: Naming in Override Constraints and Semantics2009-11-11T07:02:12Z2009-11-11T07:02:12ZPete Cordell-5Thanks Henry. Just done.
<br><br>As I know the WG is not looking for extra work I thought I'd post to the
<br>public list so that members have a low procedure way to object to the
<br>comment if I've really missed the point! That said, I think it's a simple
<br>and useful change to make.
<br><br>Thanks again,
<br><br>Pete.
<br>--
<br>=============================================
<br>Pete Cordell
<br>Codalogic Ltd
<br>Interface XML to C++ the easy way using XML C++
<br>data binding to convert XSD schemas to C++ classes.
<br>Visit <a href="http://codalogic.com/lmx/" target="_top" rel="nofollow">http://codalogic.com/lmx/</a> or <a href="http://www.xml2cpp.com" target="_top" rel="nofollow">http://www.xml2cpp.com</a><br>for more info
<br>=============================================
<br><br>----- Original Message -----
<br>From: "Henry S. Thompson" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26302749&i=0" target="_top" rel="nofollow">ht@...</a>>
<br>To: "Pete Cordell" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26302749&i=1" target="_top" rel="nofollow">petexmldev@...</a>>
<br>Cc: <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26302749&i=2" target="_top" rel="nofollow">xmlschema-dev@...</a>>
<br>Sent: Wednesday, November 11, 2009 9:40 AM
<br>Subject: Re: Naming in Override Constraints and Semantics
<br><br><br><br>-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>Requests for changes to the spec should go to
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26302749&i=3" target="_top" rel="nofollow">www-xml-schema-comments@...</a> or into Buzilla -- they may get
<br>overlooked if they are only sent here.
<br><br>I'd suggest you reduce the length of your requested new names, to,
<br>say, Dold and Dnew. . .
<br><br>ht
<br>- --
<br> Henry S. Thompson, School of Informatics, University of Edinburgh
<br> Half-time member of W3C Team
<br> 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
<br> Fax: (44) 131 651-1426, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26302749&i=4" target="_top" rel="nofollow">ht@...</a>
<br> URL: <a href="http://www.ltg.ed.ac.uk/~ht/" target="_top" rel="nofollow">http://www.ltg.ed.ac.uk/~ht/</a><br>[mail really from me _always_ has this .sig -- mail without it is forged
<br>spam]
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.2.6 (GNU/Linux)
<br><br>iD8DBQFK+oaRkjnJixAXWBoRAjCyAJ9xWKNKnDOdCgsVHifHkSH+r5oDdwCcCsMy
<br>6PycvCIKjDgwQwoHHLQRtSM=
<br>=045d
<br>-----END PGP SIGNATURE-----
<br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26298563Re: Naming in Override Constraints and Semantics2009-11-11T01:40:29Z2009-11-11T01:40:29ZHenry S. Thompson-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>Requests for changes to the spec should go to
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26298563&i=0" target="_top" rel="nofollow">www-xml-schema-comments@...</a> or into Buzilla -- they may get
<br>overlooked if they are only sent here.
<br><br>I'd suggest you reduce the length of your requested new names, to,
<br>say, Dold and Dnew. . .
<br><br>ht
<br>- --
<br> Henry S. Thompson, School of Informatics, University of Edinburgh
<br> Half-time member of W3C Team
<br> 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
<br> Fax: (44) 131 651-1426, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26298563&i=1" target="_top" rel="nofollow">ht@...</a>
<br> URL: <a href="http://www.ltg.ed.ac.uk/~ht/" target="_top" rel="nofollow">http://www.ltg.ed.ac.uk/~ht/</a><br>[mail really from me _always_ has this .sig -- mail without it is forged spam]
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.2.6 (GNU/Linux)
<br><br>iD8DBQFK+oaRkjnJixAXWBoRAjCyAJ9xWKNKnDOdCgsVHifHkSH+r5oDdwCcCsMy
<br>6PycvCIKjDgwQwoHHLQRtSM=
<br>=045d
<br>-----END PGP SIGNATURE-----
<br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>tag:old.nabble.com,2006:post-26288290Naming in Override Constraints and Semantics2009-11-10T09:57:56Z2009-11-10T09:57:56ZPete Cordell-5In "Schema Representation Constraint: Override Constraints and Semantics",
<br>is there any chance that:
<br><br>- D1 could be changed to Doverridden and
<br>- D2 could be changed to Doverriding?
<br><br>Then:
<br><br>2 One of the following must be true:
<br>2.1 D2 has a targetNamespace [attribute], and its ·actual value· is
<br>identical to the ·actual value· of the targetNamespace [attribute] of D1
<br>(which must have such an [attribute]).
<br>2.2 Neither D2 nor D1 have a targetNamespace [attribute].
<br>2.3 D2 has no targetNamespace [attribute] (but D1 does).
<br><br>becomes:
<br><br>2 One of the following must be true:
<br>2.1 Doverriding has a targetNamespace [attribute], and its ·actual value· is
<br>identical to the ·actual value· of the targetNamespace [attribute] of
<br>Doverridden (which must have such an [attribute]).
<br>2.2 Neither Doverriding nor Doverridden have a targetNamespace [attribute].
<br>2.3 Doverriding has no targetNamespace [attribute] (but Doverridden does).
<br><br>This is a lot easier on the old brain!
<br><br>There are possibly similar name changes that could be made that would make
<br>the life of the reader much easier.
<br><br>Thanks,
<br><br>Pete.
<br>--
<br>=============================================
<br>Pete Cordell
<br>Codalogic Ltd
<br>Interface XML to C++ the easy way using XML C++
<br>data binding to convert XSD schemas to C++ classes.
<br>Visit <a href="http://codalogic.com/lmx/" target="_top" rel="nofollow">http://codalogic.com/lmx/</a> or <a href="http://www.xml2cpp.com" target="_top" rel="nofollow">http://www.xml2cpp.com</a><br>for more info
<br>=============================================
<br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/w3.org---xmlschema-dev-f11764.html" embed="fixTarget[11764]" target="_top" >w3.org - xmlschema-dev</a></p>