Altova Mailing List Archives

Re: [xml-dev] Registered Namespace prefixes

From: Daniel Veillard <veillard@------.--->
To: Chiusano Joseph <chiusano_joseph@---.--->
Date: 2/27/2003 7:52:00 PM
On Thu, Feb 27, 2003 at 02:45:11PM -0500, Chiusano Joseph wrote:
> Absolutely. As mentioned in my previous e-mails on this thread, the
> registration of namespace prefixes is not a viable idea, but the
> registration of namespace identifiers is (in my opinion).

  Okay the unicity being actually managed by other means (DNS or
IANA) it seems one of the main problems associated to registries 
vanishes. There is still the trouble associated to the centralized
aspect of such a database, but that can be minimized by sharing 
openly the content of the database and allowing free mirroring of
the information herein.

  That may actually be useful, 


P.S.: After all is nothing else than such a database
      but targetting a different set of informations. But are you sure
      you will be able to handle the service over years and years ?

Daniel Veillard      | Red Hat Network
veillard@r...  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.