• From: "Michael Kay" <M.H.Kay@e...>
• To: <xml-dev@i...>
• Date: Wed, 24 Jun 1998 16:07:41 +0100

>I must be missing something here, because I can't see any
advantage to using
>mixed content here.  In fact, your inability to specify the
format you want in
>your DTD is just another argument to avoid mixed data.  Why
not just use the
>following content models, which you've probably already
thought of?
>
>   NameInfo (Name, Source?, Confidence?, Changed?, Note?,
...)
>   Name (#PCDATA)
>   Source (#PCDATA)
>   Confidence (#PCDATA)
>   ...
1. Because the optional bits are usually absent, so in most
cases I would just be writing <NAMEINFO><NAME>Fred
Bloggs</NAME></NAMEINFO>
2. I need to nest the structure because it can get
arbitrarily deep: I might want a Note about the Date of the
ProfessionalQualifications of the Author of the Source of
the Name of the Person.

As I mentioned, I've seen the same requirement arise in
other "investigative" databases, e.g. in criminal
intelligence work.

Mike Kay


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: Andreessen on XML (InfoWorld)
• Next by Date: XSchema Spec Section 2.4, Draft 2
• Previous by thread: Re: XSchema Spec Section 2.2, Draft 1
• Next by thread: (no subject)
• Index(es):
  • Date
  • Thread