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

RE: Subtyping in XML

• To: "'ht@c...'" <ht@c...>, "Xml-Dev (E-mail)" <xml-dev@l...>
• Subject: RE: Subtyping in XML
• From: Jeff Lowery <jlowery@s...>
• Date: Thu, 5 Sep 2002 15:33:24 -0700
• Cc: Paul Prescod <paulp@p...>, 'Dare Obasanjo' <dareo@m...>

I thought someone else would note that the DTD

<!ELEMENT MY-NON-BOOLEAN ((TRUE | FALSE)?, (TRUE | FALSE))>

is nondeterministic and therefore not allowed by XML Schema.  Or does it
matter? 

I guess if the point is that XML doesn't map ideally to objects, then a
particular choice of schema language is moot.  But binding XML to object
data (and back) seems in general easier than, say, porting object data to
relational models (and plenty of people are still doing that). 

What is the argument? That XML should be XML, objects should be objects, and
database tables should remain tables?  But they won't stay in their little
respective corners!   If the argument is instead that all data model
mappings should be carefully crafted on a case-by-case basis, then
personally I'm very dissatisfied with that prescription.  The natural order
of things is that complexity breeds simplicity by necessity.  Did I miss an
alternative solution somewhere?

• Follow-Ups:
  • Re: Subtyping in XML
    • From: ht@c... (Henry S. Thompson)
  • Re: Subtyping in XML
    • From: John Cowan <jcowan@r...>
  • RE: Subtyping in XML
    • From: <paul@p...>
  • Re: Subtyping in XML
    • From: Arjun Ray <aray@n...>

• Prev by Date: Re: Subtyping in XML
• Next by Date: Re: Subtyping in XML
• Previous by thread: RE: Subtyping in XML
• Next by thread: Re: Subtyping in XML
• Index(es):
  • Date
  • Thread