[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Enlightenment via avoiding the T-word
- From: "Fuchs, Matthew" <email@example.com>
- To: Ronald Bourret <firstname.lastname@example.org>, email@example.com
- Date: Wed, 29 Aug 2001 11:12:47 -0700
If the mapping from local element names in a schema to ulabels was
one-to-one, and we had the mechanisms in the document to express those
names, as I suggest in my previous email (from Monday), then one would not
need the full PSVI to get all the ulabels - one could actually express them
in the document, just as we do now with "regular" namespaces. This is
partly due to the insufficient support for local types.
Regarding validation vs. typing, validation is a kind of type-checking
(constraints do specify types, just not all the types are named). However,
in validation, you only ask if the document was correct, and don't get to
find out what the types were.
> -----Original Message-----
> From: Ronald Bourret [mailto:firstname.lastname@example.org]
> Sent: Monday, August 27, 2001 11:21 PM
> To: email@example.com
> Subject: Re: Enlightenment via avoiding the T-word
> "Fuchs, Matthew" wrote:
> > DTDs provide a mapping from well formed documents into,
> essentially, a term
> > algebra for a particular set of structures.
> So far so good.
> > I.e., once you've validated a
> > document, any element structure (but, alas, not attributes
> - but at least
> > there's only one level of nesting) with a particular label
> is of the set of
> > structures "labeled" by an element definition with the same
> label. Of
> > course, as you've pointed out, this is only one piece of
> the semantics, the
> > "label->meaning" map, but it's the piece validition provides.
> Mapping elements/attribute to t&*&%s is not validation, since
> includes things above and beyond this mapping, such as checking that
> IDREF values point to actual IDs and that IDs are unique.
> In other words, it is not necessary to generate the complete
> PSVI or to
> validate a document to do this mapping. Unfortunately, the PSVI is
> defined in these terms, rather than having separate layers, a mapping
> layer and a constraint checking layer.
> And, yes, I finally did understand what Elliotte Rusty Harold was
> talking about when he said, "W3C XML Schema Language confuses the two
> separate issues of typing and constraints checking" :)
> -- Ron
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>