[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespace URI address resources

• From: "Rick Jelliffe" <ricko@a...>
• To: "'XML Dev'" <xml-dev@i...>
• Date: Wed, 16 Jun 1999 10:44:16 +1000

From: Andrew Layman <andrewl@m...>

 >If we follow the principle of cleanly separating data from its
processing,
>we want firm ties to the definition of data, and loose ties to its
>processing.

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.

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.

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.

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
is bad.


Rick Jelliffe



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: Namespace URI address resources
    • From: Murray Maloney <murray@m...>

• Prev by Date: CSS and XML attributes
• Next by Date: RE: Just require URLs
• Previous by thread: RE: Namespace URI address resources
• Next by thread: Re: Namespace URI address resources
• Index(es):
  • Date
  • Thread