Lists Home |
Date Index |
- From: Len Bullard <firstname.lastname@example.org>
- To: Rick Jelliffe <email@example.com>
- Date: Wed, 03 Nov 1999 18:10:59 -0600
Rick Jelliffe wrote:
> Tim is of course correct that a schema is only part of the whole
> picture, but a schema language can be judged on how readily it allows
> useful systems and tools to be built.
Ok. Another way to look at it is to look at the frequency of
change in the information and determine if a schema is an
where in the process the schema is an effective tool. There
are a lot of applications whose market loosely hangs
in the "authoring" category. Is anyone applying schemas to dimensions
for multi-dimensional database designs, yeVenerableHypercubes
for online analytical processing?
> That being so, it may be a strong
> schema system is one which has some 'use' information as well as the
> "pure" schemas: documentation, forms building, validation, style, etc.:
> where the type information from the schema can directly be used for some
> DTDs provide simple stucture models but also have infoset contributions
> with #FIXED attributes and default attribute values (i.e., a simple
> transformation of the instance). This makes them 'impure' as a schema
> language, but undoubtedly more useful.
Schemas that gracefully handle time volatility issues will be useful.
However for that to work, the schema has to be dynamic, and I rather
thought that was the attractiveness of XML schemas. I can instrument
processes and use the events to modify a schema via the DOM, thus
closing the loop. Better than hardwiring templates, I would think.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)