[Mono-bugs] [Bug 74860][Nor] Changed - WSDL Utility: XML Schema Error

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by atsushi@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74860

--- shadow/74860	2005-05-09 00:38:34.000000000 -0400
+++ shadow/74860.tmp.3492	2005-05-09 04:39:20.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 74860
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 2.6.10-5-386
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Normal
 Component: Sys.XML
 AssignedTo: atsushi@ximian.com                            
 ReportedBy: helge.stahlmann@web.de               
 QAContact: mono-bugs@ximian.com
@@ -455,6 +455,52 @@
 Created an attachment (id=15088)
 WSDL file
 
 
 ------- Additional Comments From atsushi@ximian.com  2005-05-09 00:38 -------
 -> Sys.XML
+
+------- Additional Comments From atsushi@ximian.com  2005-05-09 04:39 -------
+at line 113
+
+            <xsd:complexType name="ChatServiceException">
+                <xsd:complexContent>
+                    <xsd:extension base="xsd:anyType">
+                        <xsd:sequence/>
+                    </xsd:extension>
+                </xsd:complexContent>
+            </xsd:complexType>
+
+I believe this is a bug in the schema as well as Microsoft.NET. When a
+complex type is a derivation by extension, it must satisfy 
+
+--------
+1.4 One of the following must be true:
+1.4.1 The {content type} of the {base type definition} and the
+{content type} of the complex type definition itself must be the same
+simple type definition.
+1.4.2 The {content type} of both the {base type definition} and the
+complex type definition itself must be empty.
+1.4.3 All of the following must be true:
+1.4.3.1 The {content type} of the complex type definition itself must
+specify a particle.
+1.4.3.2 One of the following must be true:
+1.4.3.2.1 The {content type} of the {base type definition} must be empty.
+1.4.3.2.2 All of the following must be true:
+1.4.3.2.2.1 Both {content type}s must be mixed or both must be
+element-only.
+1.4.3.2.2.2 The particle of the complex type definition must be a
+?valid extension? of the {base type definition}'s particle, as defined
+in Particle Valid (Extension) (§3.9.6).
+--------
+
+The related section (namely 1.4.2) was not originally in W3C
+specification as of 2001. See "Derivation Valid (Extension)"
+http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#coss-ct
+but is fixed in errata
+http://www.w3.org/2001/05/xmlschema-errata#e1-5
+and thus it is included in the latest specification.
+http://www.w3.org/TR/xmlschema-1/#coss-ct
+
+
+Typically when you want to do like that line 113, just use restriction
+instead of extension (extending "anyType" does not make sense).