[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML design of ((a and b) or c)

• From: "Michael Kay" <mike@s...>
• To: "'Andrew Welch'" <andrew.j.welch@g...>,<xml-dev@l...>
• Date: Tue, 12 Dec 2006 15:57:25 -0000

The first one seems much the cleanest.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: Andrew Welch [mailto:andrew.j.welch@g...] 
> Sent: 12 December 2006 15:23
> To: xml-dev@l...
> Subject:  XML design of ((a and b) or c)
> 
> I've just had to design some XML to model items that can have "and"
> and "or" relationships between each one.
> 
> For example:
> 
> (a and b) or c
> 
> could be designed as:
> 
> <or>
>     <a>
>     <and>
>         <b/>
>         <c/>
>     </and>
> </or>
> 
> another option could be to rely on position:
> 
> <a>
> <and/>
> <b/>
> <or/>
> <c/>
> 
> and another could be model the relationships separately somehow:
> 
> <relationships>
>   <rel ref="r1" type="and">
>     <ent id="a"/>
>     <ent id="b"/>
>   </rel>
>   <rel ref="r2" type="or">
>     <ent id="r1"/>
>     <ent id="c"/>
>   </rel>
> </relationships>
> <a id="a"/>
> <b id="b"/>
> <c id="c"/>
> 
> Each has its own advantages/drawbacks.  Personally I like the 
> first technique, although it can get cluttered when there are 
> 10+ items.
> 
> Are there any better ways that I'm missing?
> 
> cheers
> andrew
> 
> ______________________________________________________________
> _________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by 
> OASIS to support XML implementation and development. To 
> minimize spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l... List archive: 
> http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> 

• Follow-Ups:
  • Re: XML design of ((a and b) or c)
    • From: "Andrew Welch" <andrew.j.welch@g...>

• References:
  • XML design of ((a and b) or c)
    • From: "Andrew Welch" <andrew.j.welch@g...>