[
Lists Home |
Date Index |
Thread Index
]
Ahh, but which spec are we talking about conforming to?
There's an inconsistency between the Schema spec and the XInclude spec, see
http://weblogs.asp.net/cazzu/archive/2005/01/10/XsdAndXInclude.aspx "So,
either you modify all your schemas to that each and every element includes
those attributes (either by inheriting from a base type or using an
attribute group reference), or you validation is bound to fail if someone
decides to include something." The problem is that we get bug reports from
people wanting to use XInclude with schemas they can't fix up to be
compatible with XInclude.
Stan talks about the rationale behind Microsoft's approach to addressing
this in http://blogs.msdn.com/xmlteam/archive/2005/05/11/416639.aspx
>From: "Michael Kay" <mike@saxonica.com>
>To: "'Stan Kitsis'" <skits@microsoft.com>,"'Mark Seaborne'"
><MSeaborne@origoservices.com>,<xml-dev@lists.xml.org>
>Subject: RE: [xml-dev] Validating XML documents containing xml:*
>Date: Mon, 7 Nov 2005 21:37:20 -0000
>
> > .NET 2.0 gives you an option to allow or disallow xml:* attributes in
> > the instance documents when the schema doesn't explicitly
> > declare them.
>
>I'm surprised. I don't think that's conformant behavior.
>
>Michael Kay
>http://www.saxonica.com/
>
>
>
>-----------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>
>To subscribe or unsubscribe from this list use the subscription
>manager: <http://www.oasis-open.org/mlmanage/index.php>
>
_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
|
