Lists Home |
Date Index |
- From: "Steven R. Newcomb" <firstname.lastname@example.org>
- To: email@example.com
- Date: Sun, 17 Jan 1999 16:59:58 -0600
> At 11:36 AM 1/17/99 -0800, David LeBlanc wrote:
> What i'm asking, is it the intent that, in the fullness of time, one
> of these will supplant DTDs as a document type notation?
This is really two questions:
(1) Will the set of semantics expressible by DTDs be changed? (This
is the primary question, although it's only implicit in your
(2) Will the existing syntax of DTDs be replaced by another syntax?
The answer two both questions is "Yes, and certainly within the next
The important thing is to go forward, and to avoid going backward,
with respect to the set of semantics that are expressible using DTDs.
I think today the first questions to ask are, "What's the goal?",
"What's the direction toward the goal?", and "How can we minimize the
likelihood of having to backtrack later, when huge investments in
information assets would be jeopardized?"
Then we need to ask, "What are the semantics we need to represent,
in order to achieve the goal or move toward the goal?"
Once we've decided these basic semantic issues, the syntax issues
become a lot more straightforward. Here, just for example, are some
as-yet-unsupported modeling features that it might be good to support:
* Subtyping of element types.
* Lexical modeling of strings in attribute values and in element
* Association of *arbitrary* semantic properties, constraints,
etc. with element types and attribute values. I'm using the term
"arbitrary" here as the opposite of "built into the formalism", in
the way that, for example, in today's DTD formalism, content models
impose certain well-defined (and not at all arbitrary) *kinds* of
constraints. Maybe this is just a matter of providing a means of
associating comments unambiguously with the constructs that they're
about, but maybe it can be more rigorous than that.
Steven R. Newcomb, President, TechnoTeacher, Inc.
firstname.lastname@example.org http://www.techno.com ftp.techno.com
voice: +1 972 231 4098 (at ISOGEN: +1 214 953 0004 x137)
fax +1 972 994 0087 (at ISOGEN: +1 214 953 3152)
3615 Tanner Lane
Richardson, Texas 75082-2618 USA
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)