Răsfoiți Sursa

2004-02-05 Atsushi Enomoto <[email protected]>

	* BUGS-MS.txt : fixed incorrect thought on case 008. Added case 014.
	* BUGS.txt : FYI.

svn path=/trunk/mcs/; revision=22803
Atsushi Eno 22 ani în urmă
părinte
comite
06dcbf55a3

+ 11 - 3
mcs/class/System.XML/System.Xml.Schema/BUGS-MS.txt

@@ -66,8 +66,7 @@ BUGS in MS Implementation of XmlSchema:
 
 	Particles that have maxOccurs="0" looks simply ignored *before*
 	evaluating particle restriction valid, but it might get incorrect
-	result. For example, it is regarded as valid (while 'e1' must occur 1
-	time for the base 'bar' type):
+	result.
 
 	<xsd:complexType name="foo">
 	<xsd:complexContent>
@@ -87,7 +86,7 @@ BUGS in MS Implementation of XmlSchema:
 	</xsd:choice>
 	</xsd:complexType>
 
-	Related msxsdtest is groupG001.xsd and mgH014.xsd.
+	Related msxsdtest is groupG001.xsd.
 
 009. derived list incorrectly allowed
 
@@ -148,3 +147,12 @@ BUGS in MS Implementation of XmlSchema:
 	minLength, maxLength, pattern and enumeration are allowed. However, MS
 	implementation allows whitespace (and possibly and so on).
 
+014. Incorrectly disallowed mixed derivation with empty content from elementOnly
+
+	When a complexType whose mixed='true' and -explicit content- is empty,
+	is derived from a complexType whose {content type} is ElementOnly,
+	MS.NET rejects such schema. But 3.4.2 (complex content Schema
+	Component) especially 2.1 of {content type} does not say it is an error.
+
+	Related msxsdtest: ctF008.xsd
+

+ 20 - 4
mcs/class/System.XML/System.Xml.Schema/BUGS.txt

@@ -1,6 +1,22 @@
 Bugs in Implementation:
 
-// None of the XmlSchemaObjects except the XmlSchema populate XmlSerializerNamespaces.
-//2. Non schema attributes are not being handled. Need an internal XmlAttribute constructor.
-//3. Documentation and appInfo's Markup is not being read in the Read() Method.
-//4. Handling of unique particle attribution of sequences is incomplete. Note that it is W3C specification that is so buggy. Basically there is neither formalization nor even normative definition about unique particle attribution. Appendix H tried to describe about that, but it is too incomplete.
+1.
+None of the XmlSchemaObjects except the XmlSchema populate XmlSerializerNamespaces.
+
+2.
+Non schema attributes are not being handled. Need an internal XmlAttribute constructor.
+3.
+Documentation and appInfo's Markup is not being read in the Read() Method.
+
+4.
+Handling of unique particle attribution of sequences is almost complete, 
+but not perfect. Note that it is W3C specification that is so buggy. 
+Basically there is neither formalization nor even normative definition 
+about unique particle attribution. Appendix H tried to describe about 
+that, but it is too incomplete.
+
+5.
+Currently ContentTypeParticle was not eliminated "pointless" (see 3.9.6 of
+xml schema part 1) XmlSchemaChoice, like MS.NET. It causes incorrect DBR
+validation.
+

+ 5 - 0
mcs/class/System.XML/System.Xml.Schema/ChangeLog

@@ -1,3 +1,8 @@
+2004-02-05  Atsushi Enomoto <[email protected]>
+
+	* BUGS-MS.txt : fixed incorrect thought on case 008. Added case 014.
+	* BUGS.txt : FYI.
+
 2004-02-03  Atsushi Enomoto <[email protected]>
 
 	* BuiltInDatatype.cs : Fixed some Parse() for token based datatypes.