OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] XML Schema question

[ Lists Home | Date Index | Thread Index ]

----- Original Message From: "Pete Cordell" <petexmldev@tech-know-ware.com>
> Hi Wong,
>
> You need do something like:
>
> <xs:element name="myelement">
...
> </xs:element>
>
> I've just completed a beginners primer on XSD that tries to describe 
> Schema in the sort of way you asked your question (i.e. if you want X in 
> your XML, do Y in your Schema).  It may well be 'yet another guide', it 
> certainly doesn't cover all of XSD, and you've probably moved beyond its 
> target audience, but if you find you have any comments on it I'd be 
> delighted to know.

Oh - and it's at:

http://www.tech-know-ware.com/lmx/xsd-overview.html

(Apologies for the extra bandwidth)

> Pete.
> --
> =============================================
> Pete Cordell
> Tech-Know-Ware Ltd
>                         for XML to C++ data binding visit
>                         http://www.tech-know-ware.com/lmx
>                         (or http://www.xml2cpp.com)
> =============================================
>
> ----- Original Message ----- 
> From: "Wong Chin Shin" <publicreg@nascencetech.com>
> To: <xml-dev@lists.xml.org>
> Sent: Wednesday, February 15, 2006 4:05 PM
> Subject: [xml-dev] XML Schema question
>
>
>> Hi,
>>
>> My name's Wong and I'm a new subscriber. Pleased to meet all of you
>> (figuratively).
>>
>> I'm writing a schema document right now and met with a roadblock of 
>> sorts:
>>
>> I'm trying to represent the following snippet in the schema:
>>
>> <myelement myattrib1="hello" myattrib2="goodbye">everybody</myelement>
>>
>> The following schema snippet seems to be wrong, according to the error
>> message when I try to create a class out of it using xsd.exe in the .Net
>> command line toolset.
>>
>> <xs:element name="myelement" type="xs:string">
>> <xs:complexType>
>> <xs:attribute name="myattrib1" type="xs:string" />
>> <xs:attribute name="myattrib2" type="xs:string" />
>> </xs:complexType>
>> </xs:element>
>>
>> So according to the error message, I cannot type an element that already 
>> has
>> a complexType encapsulated within. I guess that'd be double-typing. OK,
>> makes sense.
>>
>> So if I remove the "type='xs:string'" from "myelement", it compiles. But 
>> it
>> sure doesn't look like I have specified that the element "myelement" can
>> have a text value in itself.
>>
>> Thank you!
>> Wong
>>
>>
>>
>> -----------------------------------------------------------------
>> 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>
>>
>>
>
>
>
> -----------------------------------------------------------------
> 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>
>
> 






 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS