"G. Ken Holman" wrote:
When it is a namespace of a vocabulary I've made public, I use HTML
documents at the URI of the URL:
http://www.CraneSoftwrights.com/ns/xslstyle
http://www.CraneSoftwrights.com/ns/xslstyle/vocabulary
... which eventually will be XHTML with RDDL
Yes, I think this is the best practice I've seen so far for public
URIs.
When it is a private or temporary namespace, I use a URN:
urn:X-Crane:project:subproject:module:etc.:etc.:etc.
Interesting, sounds like a good idea!
Per the recommendation I do not use a URI construed as a relative
URI as that practice is deprecated:
Yes (I included those examples on purpose :-p).
I hope this helps.
As usual! Thank you,
--
Florent Georges
http://www.fgeorges.org/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--