X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=mcs%2Fclass%2FSystem.XML%2FSystem.Xml.Schema%2FBUGS-MS.txt;h=cda2ebeb2dce6dede30f2d1c819ffe174d1ff7fb;hb=018c4be8c5ef6e23ccd9bf798513a6178631e1ea;hp=6ee02cdf6acddda631b9bfef6d7e3ed77f34e282;hpb=dac1a705ea8721eeff8b2a91da1747d04706f0bb;p=mono.git

diff --git a/mcs/class/System.XML/System.Xml.Schema/BUGS-MS.txt b/mcs/class/System.XML/System.Xml.Schema/BUGS-MS.txt
index 6ee02cdf6ac..cda2ebeb2dc 100755
--- a/mcs/class/System.XML/System.Xml.Schema/BUGS-MS.txt
+++ b/mcs/class/System.XML/System.Xml.Schema/BUGS-MS.txt
@@ -1,11 +1,21 @@
 BUGS in MS Implementation of XmlSchema:
 
+Here we summarize bugs found in MS.NET, including some comment excerpt from
+Microsoft development team (as of 2004/07).
+
+
 001. Does not allow duplicate values in lists for final* and block* attributes. 
    For example "restriction restriction" is not allowed even though its a valid
    value for blockDefault.
 
+(MS: This is fixed in .NET 2.0)
+
+
 002. Resets the minOccurs to 0 if maxOccurs="0", whereas it should raise an error.
 
+(MS: This WON'T be fixed in .NET 2.0. MS users may depend on this bug.)
+
+
 003. Allows abstract="true" in the a localElement whereas it is not allowed.
 	<?xml version="1.0"?>
 	<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xsdtesting" xmlns:x="http://xsdtesting" elementFormDefault="qualified">
@@ -19,6 +29,9 @@ BUGS in MS Implementation of XmlSchema:
 		</xsd:element>
 	</xsd:schema>
 
+(MS: This is fixed in .NET 2.0)
+
+
 004. QName value constraint
 
 	When xs:QName based type is specified to an attribute or element
@@ -26,6 +39,9 @@ BUGS in MS Implementation of XmlSchema:
 	default or fixed value), even though they have those namespace 
 	declaration by XmlSerializerNamespaces.
 
+(MS: This is fixed in .NET 2.0)
+
+
 005.  derivation by extension of xs:all
 
 	As it is discussed on w3c xmlschema-dev ML, MS System.Xml.Schema
@@ -42,6 +58,9 @@ BUGS in MS Implementation of XmlSchema:
 	ctH019.xsd, ctH020.xsd, ctH021.xsd, ctH022.xsd, ctH023.xsd, ctJ001.xsd
 	and in msxsdtest/ModelGroups: mgA016.xsd, mgO007.xsd (9 testcases).
 
+(MS: This is fixed in .NET 2.0)
+
+
 006. xs:all minOccurs="0" not allowed
 
 	W3C WXS Structures REC. says that model group xs:all is limited to have
@@ -52,17 +71,32 @@ BUGS in MS Implementation of XmlSchema:
 
 	Related msxsdtest is ParticlesEa022.xsd
 
+(MS: This happens only when a group ref targets to xs:all. This is bug.)
+
+
 007. Insufficient unique particle attribution of xs:any
 
 	MS.NET allows <xs:choice><xs:any /><xs:element ... /></xs:choice>.
 
+	<del>
 	Related msxsdtests are: ParticlesJd002.xsd, ParticlesJd003.xsd and
 	ParticlesJd004.xsd. 
+	</del>
+	[Update] They are sequence not choice. Thus does not apply to this
+	case. MS validator handles such schema as invalid correctly.
+
 	ParticlesIb001.xsd is also related, but it is not necessarily said as
 	incorrect. Both elements are of the same type, so *in a sense* they are
 	the same declaration. MSV, XSV and I stands different.
 
-008. Occurence Range OK (3.9.6) incorrectly assessed
+[Still on discussion on ParticlesIb001.xsd]
+
+
+<del>008. Occurence Range OK (3.9.6) incorrectly assessed</del>
+
+	[Update] MS team pointed out that it is incorrect and I found that 
+	XML Schema Structures 3.3.2 explicitly denotes that when minOccurs=
+	maxOccurs=0 it corresponds to no component at all.
 
 	Particles that have maxOccurs="0" looks simply ignored *before*
 	evaluating particle restriction valid, but it might get incorrect
@@ -88,6 +122,7 @@ BUGS in MS Implementation of XmlSchema:
 
 	Related msxsdtest is groupG001.xsd.
 
+
 009. derived list incorrectly allowed
 
 	"Type Derivation OK" by list simple type of atomic simple type is
@@ -111,6 +146,9 @@ BUGS in MS Implementation of XmlSchema:
 
 	Related msxsdtests are elemT015.xsd and elemT022.xsd.
 
+(MS: This will be fixed in the next version of .NET 2.0)
+
+
 010. derived union incorrectly allowed
 
 	Similar problem to No.9 above resides in xs:union. Derived union type
@@ -118,7 +156,13 @@ BUGS in MS Implementation of XmlSchema:
 
 	Related msxsdtest is elemT014.xsd.
 
-011. schema finalDefault with list and/or union
+[ditto]
+
+
+<del>011. schema finalDefault with list and/or union</del>
+
+	[Update] This is not MS bug. We have to fix this problem. XML Schema
+	errata corrected this part of the spec by allowing 'list'.
 
 	In xs:schema, finalDefault = (#all | List of (extension | restriction)),
 	but MS.NET failed to handle blockDefault='list' as an error.
@@ -126,20 +170,24 @@ BUGS in MS Implementation of XmlSchema:
 
 	Related msxsdtest is stF034.xsd and stF036.xsd.
 
+
 012. derived types cannot duplicate fixed facet
 
-  If you have a facet like <xsd:minLength value="5" fixed="true" />, you should
-  be able to have <xsd:minLength value="5" /> in restrictions of it, as long as
-  the values are the same. MS says: 
-    "Base type has {fixed} equal to true."
+	If you have a facet like <xsd:minLength value="5" fixed="true" />, 
+	you should be able to have <xsd:minLength value="5" /> in 
+	restrictions of it, as long as the values are the same. MS says: 
+	"Base type has {fixed} equal to true."
+
+	XML-Schema part2 Datatype, 4.3.2.1: 
+	"If {fixed} is true, then types for which the current type is the
+	{base type definition} cannot specify a value for minLength other than
+	{value}."
+
+	Which implies that you can specify a value for minLength that is the
+	same as {value}.
 
-  XML-Schema part2 Datatype, 4.3.2.1: 
-    "If {fixed} is true, then types for which the current type is the {base
-    type definition} cannot specify a value for minLength other than
-    {value}."
+(MS: This is bug.)
 
-  Which implies that you can specify a value for minLength that is the same as
-  {value}.
 
 013. Some facets are incorrectly allowed for list simple type.
 
@@ -147,12 +195,35 @@ 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
+(MS: "whitespace" is incorrectly allowed. It is bug.)
+
+
+<del>014. Incorrectly disallowed mixed derivation with empty content from
+elementOnly</del>
+
+	[Update] MS team pointed out that XSD Errata replaced -explicit 
+	content- with -effective content- . Thus, such schema should be
+	rejected. (See E1-5 of http://www.w3.org/2001/05/xmlschema-errata .)
 
 	When a complexType whose mixed='true' and -explicit content- is empty,
-	is derived from a complexType whose {content type} is ElementOnly,
+	and 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
 
+
+015. Included schema ignores incorrect element name which belongs to 
+XmlSchema.Namespace
+
+	MS Schema compiler fails to catch an error when an incorrect schema
+	(such as below) is included by any other schemas:
+
+	<xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'>
+	  <xs:foo />
+	</xs:schema>
+
+	This does not apply to general compilation error such as missing 
+	sub components that should result in an error.
+
+	This seems fixed in Whidbey.