RE: [xml-dev] Who can implement W3C XML Schema ?

["Dare Obasanjo" <dareo@microsoft.com>]

Actually the ambiguities involving the ur-type are a known issue in the
recommendation which have been kind of addressed at 

	http://www.w3.org/2001/05/xmlschema-rec-comments#pfiur-type

-- 
THINGS TO DO IF I BECOME AN EVIL OVERLORD #27
I will never build only one of anything important. All important systems
will
have redundant control panels and power supplies. For the same reason I
will
always carry at least two fully loaded weapons at all times.


> -----Original Message-----
> From: Eric van der Vlist [mailto:vdv@dyomedea.com] 
> Sent: Wednesday, March 20, 2002 7:29 AM
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Who can implement W3C XML Schema ?
> 
> 
> Jiri Jirat wrote:
> > Eee,
> >   Xerces-J is not too bad, but I have spent many hours
> > with the following example, trying to figure out, what's wrong:
> > 
> > 
> > <AAA xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xmlns:jj="http://www.zvon.org/jiratj/"; 
> > xsi:noNamespaceSchemaLocation="correct_0.xsd"><jj:a/></AAA>
> > 
> > schema (correct_0.xsd):
> > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:jj="http://www.zvon.org/jiratj/"; 
> > xmlns:html="http://www.w3.org/TR/REC-html40";>
> >       <xsd:element name="AAA">
> >        <xsd:complexType>
> >         <xsd:complexContent>
> >          <xsd:restriction base="xsd:anyType"/>
> >         </xsd:complexContent>
> >        </xsd:complexType>
> >       </xsd:element>
> >       </xsd:schema>
> > 
> > The schema should specify an element, which is empty, am I right?
> 
> Yes I would guess so, even though it *looks* strange the 
> first time you 
> look at this schema.
> 
> > See:
> > http://www.w3.org/TR/xmlschema-0/#emptyContent
> > and your article somewhere on XML.com :-)
> 
> Please don't take me as an absolute reference :))) !
> 
> > But both xsv and Xerces-J haven't say even "boooo!" and where happy 
> > :-(
> 
> Time to fill a couple of bugs :) ...
> 
> Actually this is a very interesting test case since:
> 
> "The ur-type definition, whose name is anyType, has the unique 
> characteristic that it can function as a complex or a simple type 
> definition, according to context. Specifically, *restrictions* of the 
> ur-type definition can themselves be either simple or complex type 
> definitions."
> 
> and the since the derivation by restriction of simple and 
> complex types 
> use the same xs:restriction element with a different semantic 
> and it's 
> probably a nightmare to implement when a type is both simple 
> and complex...
> 
> Eric
> -- 
> See you in Paris.
>                       
> http://www.afnet.fr/afnet/net200x/programme.ht> ml#T9
> 
> 
> --------------------------------------------------------------
> ----------
> Eric van der Vlist       http://xmlfr.org            
> http://dyomedea.com
> http://xsltunit.org      http://4xt.org   
>         
http://examplotron.org
------------------------------------------------------------------------


-----------------------------------------------------------------
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://lists.xml.org/ob/adm.pl>