Namespaces are dead.

[Rick Jelliffe]

 From: Marc.McDonald at Design-Intelligence.com
<Marc.McDonald at Design-Intelligence.com>

 >To put it plainly, the basic problem is putting document consumer
>information in the document. Doing so results in needing to modify
every
>document every time a new consumer is created.

I have written to the W3C a suggestion on this topic. It is in an
article "How to Promote Organic Plurality on the WWW" at
http://www.ascc.net/xml/en/utf-8/monolith.html

The concrete suggestions are these:

1) To prevent "data kidnap", every new technology or application class
introduced onto the WWW must be preceded by a mechanism, as an
intermediate layer, to allow alternatives to that technology

2) To prevent "workflow kidnap", that mechanism should have a phase
attribute.

3) To prevent "data lockout", names should be fixed for a schema:
vocabularies that require a schema with to check names based on regular
expressions should be deprecated.

I hope anyone interested in building an open WWW that provides a
level-playing field for innovators can support it.


Rick Jelliffe

P.S. "Organic Plurarity" sounds like something from Barbarella I know,
but it is the best I could come up with.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
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 at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)