Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Best Practices for Establishing Namespace Name

From: "Tsao, Scott" <scott.tsao@------.--->
To: "Henry S. Thompson" <ht@---.--.--.-->
Date: 9/3/2009 11:42:00 PM
Henry,

Thanks for the confirmation!
 
Is this the document you were referring to as far as W3C TAG's strong
recommendation is concerned:
http://www.w3.org/2001/tag/doc/URNsAndRegistries-50 ?
 
Scott

-----Original Message-----
From: Henry S. Thompson [mailto:ht@i...]
Sent: Wednesday, September 02, 2009 2:40 AM
To: Tsao, Scott
Cc: G. Ken Holman; xmlschema-dev@w...
Subject: Re: Best Practices for Establishing Namespace Name

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
...
> And, is the use of them for namespace names (in lieu of URN)
> recommended by standards organizations such as W3C and OASIS?

Absolutely.  OASIS have backed off using URNs as namespace names, and
W3C TAG strongly recommends using http: URIs for this purpose.
...
ht
- --
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131
650-4440
                Fax: (44) 131 651-1426, e-mail: ht@i...
                       URL: http://www.ltg.ed.ac.uk/~ht/ [mail really
from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFKnj1akjnJixAXWBoRAgpnAJ946RWeMWRT4NA3S1hHT0bCc63GPgCcDCJp
3NNY0Glqx4E0BJeWcEZs0z8=
=zpxU
-----END PGP SIGNATURE-----



transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent