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] Designing XML to Support Information Evolution

[ Lists Home | Date Index | Thread Index ]

> hierarchies fail, and this is my struggle with xml at the 
> moment, when they have to support multiple hierarchies simultaneously. 

Perhaps it's time to rediscover the network (or Codasyl) data model, which
was invented to solve this problem. I have always felt this model is the one
that comes closest to a direct representation of the structures that come
out of data modelling. In XPath terms, it just means that instead of having
one child axis and one parent axis, an element can have any number of
different, named, child and parent axes. It's easy enough to represent in
XML, you just use ID and IDREFS attributes for the "non-primary"

The problem in this area is that XML has too many different ways to
represent relationships, and none of them is especially well supported by
declarative mechanisms in the schema or query languages. 

Michael Kay


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

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