Lists Home |
Date Index |
- From: Murray Maloney <email@example.com>
- To: "'XML Dev'" <firstname.lastname@example.org>
- Date: Tue, 15 Jun 1999 23:48:07 -0400
At 10:44 AM 6/16/99 +1000, Rick Jelliffe wrote:
>A schema is "processing" not "data": it is tied to whatever applications
>understand the schema format. Editing, creating and validating against a
>schema are all applications.
Well. Maybe meta-data, but a schema is simply declarative.
It does not perform any processing. Editing, creating and
validating are all applications. So what?
The point is that a schema actually defines some aspect of
the meaning of 'names' in a 'namespace'. That seems useful.
>There is no schema language yet that can express all useful constraints.
>To propose a mechanism that does not allow a plurality of schemas is, in
>fact, to say that the schema language should defines the (bounds of the)
>possible schemas: if XML-Data does not support a constraint, it cannot
>be part of schemas. This is putting the cart before the horse.
Using the namespace URI to be locate a schema does not preclude
the possibility of there being any number of schemas associated
with that URI.
>It is not that the namespace URI identifies a schema that it is the
>problem, it is :
>* the notion that a document has only *one* schema and
>* there is no mechanism yet to allow alternative schemas to be assigned.
Nobody is proposing that a document has only *one* schema.
The mechanism is known in the biz as 'content negotiation'.
This is known to work for multiple languages and devices.
>If W3C made a mechanism to allow alternative schemas (like Jonathon
>Bordon's recent post), then the namespace URI could be overloaded to
>provide a schema, as a defaulting behaviour in the absense of a PI. But
>it is bad for the WWW if there is no mechanism to allow alternatives;
>without such a mechanism, requiring overloaded use of the namespace URL
As I said, there is such a mechanism.
Murray Maloney, Esq. Phone: (905) 509-9120
Muzmo Communication Inc. Fax: (905) 509-8637
671 Cowan Circle Email: email@example.com
Pickering, Ontario Web: http://www.muzmo.com
Canada, L1W 3K6
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 (un)subscribe, 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)