Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


XML Schema Question

From: Matthew Harrison <m.harrisson@-------.--->
To: NULL
Date: 8/6/2007 2:18:00 PM

I am defining an abstract conversation class in XML Schema (using XMLSpy).

The basics are:

Conversation (attr:Reference)
--> Identity (1)
     --> Id
     --> Client
--> Sequence (atrr:Index) (1..n)
     --> Sender
     --> Timestamp

Now I want to define a descendant called

BlahConversation based on Conversation

However, I need to include additional fields in Sequence (status 
information specific to the Blah type).

How do I correctly structure things, such that I don't end up having to 
define the whole structure fully for each different conversation subtype ?

Thanks.

-- 
Pinging self [127.0.0.1] with 32 bites of banana cake:

Ping statistics for 127.0.0.1:
     Slices: Sent = 4, Received = 0, Lost = 4 (100% loss),


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent