Lists Home |
Date Index |
- From: "Simon St.Laurent" <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Tue, 05 Jan 1999 13:08:40 -0500
At 12:52 PM 1/5/99 -0500, John Cowan wrote:
>This strikes me as an ideal application of architectural forms
>(as implemented in XAF: see http://www.megginson.com/XAF).
>By specifying the desired standard form as an architecture,
>you allow the element types to be locally meaningful, while
>letting applications (XSL, validation, or whatever) to act)
>on architectural element types. XAF does the donkey work of
>reducing one to the other.
I definitely agree; my primary concern remains that architectural forms
transformations will typically take place _after_ validation has already
occurred, requiring developers to create complete translated DTDs rather
than simpler tables of equivalent elements.
In this, and in a significant number of situations like it, I suspect the
XML spec's lack of a layered processing model is a hindrance. In other
words, having a parser check basic document syntax and a validator check to
see if the document structure corresponds to a schema would have made it
easier to stick things in between the initial parse and the validation -
like architectural forms transformations. Instead, we have parsers that do
both syntax and structure checking and spit out results.
This separation is something I hope to see come out of the upcoming W3C
schema discussions, and is a promising aspect of XSchema (which layered
itself on top of XML 1.0) as well.
XML: A Primer / Cookies
Building XML Applications (February)
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)