Lists Home |
Date Index |
- From: "Don Park" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Wed, 5 Aug 1998 02:37:46 -0700
>Hey! Nice idea! XSchema certainly supports this -- it's just a bunch of
Thanks. Support is, I suppose, unintentional?;-)
>1) You've probably already realized this, but a DTD for such a file would
>little or no use. Because each XSchema section can introduce new elements
>redefine old ones, the DTD would probably consist of a bunch of elements
>content models of ANY. This is of no use either for validation or
>storage structures on the fly.
You are right but it makes perfect sense for transitory documents which
exists only while it is moving from one place to another. Ability to
redefine default attribute values should be enough of a benefit I think.
>2) The above document is not well-formed. You need to wrap it in a
>element such as <log-stream>.
Well, due to possible problems with missing root element's end tag (it ain't
there if the log file is not closed), XLF data is parsed as a well-formed
external entity like below.
<!DOCTYPE xlf [
<!ENTITY logfile SYSTEM "iis-08031998.xlf">
>3) The semantics of how each successive XSchema affects the previous
>not well-defined (additive? total replacement? partial replacement?) and
>probably won't be defined in XSchema 1.0. You are therefore on your own.
>safety's sake, I suggest you treat each XSchema as a completely new
>of the following elements.
Food for thought.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)