Removal of NET_1_1 defines and some NET_2_0; Both defines are true these days in...

[mono.git] / mcs / class / System.XML / System.Xml.Schema / BUGS.txt

diff --git a/mcs/class/System.XML/System.Xml.Schema/BUGS.txt b/mcs/class/System.XML/System.Xml.Schema/BUGS.txt
old mode 100755 (executable)
new mode 100644 (file)
index cf60217..d0b4ac9
--- a/mcs/class/System.XML/System.Xml.Schema/BUGS.txt
+++ b/mcs/class/System.XML/System.Xml.Schema/BUGS.txt
@@ -1,5 +1,26 @@
-Bugs in Implementation:\r
+Bugs in Mono Implementation of XmlSchema:\r
+\r
+1.\r
+None of the XmlSchemaObjects except the XmlSchema populate XmlSerializerNamespaces.\r
+\r
+2.\r
+Non schema attributes are not being handled. Need an internal XmlAttribute constructor.\r
+3.\r
+Documentation and appInfo's Markup is not being read in the Read() Method.\r
+\r
+4.\r
+Handling of unique particle attribution of sequences is almost complete, \r
+but not perfect. Note that it is W3C specification that is so buggy. \r
+Basically there is neither formalization nor even normative definition \r
+about unique particle attribution. Appendix H tried to describe about \r
+that, but it is too incomplete.\r
+\r
+5.\r
+Currently ContentTypeParticle does not eliminate "pointless" (see 3.9.6 of\r
+xml schema structures spec) XmlSchemaChoice, like MS.NET. It causes\r
+incorrect DBR validation.\r
+\r
+6.\r
+See MS-BUGS.txt 008 and 014. There are some correction and we should fix our\r
+implementation based on those wrong premises.\r
 \r
-// None of the XmlSchemaObjects except the XmlSchema populate XmlSerializerNamespaces.\r
-//2. Non schema attributes are not being handled. Need an internal XmlAttribute constructor.\r
-//3. Documentation and appInfo's Markup is not being read in the Read() Method.\r