Altova Mailing List Archives
Re: [xml-dev] URN vs URL
To: Andy Greener <andy@---.--.-->, Alaric B Snell <alaric@------------.--->, xml-dev@-----.---.---
Date: 7/30/2003 9:52:00 PM
<Quote> As a sidenote, I recommended that this document be updated to also include URL formats for namespace identifiers. Oh, which reminds me: I need to check on its status... </Quote> I am now told that my recommendation was accepted, and that this document is being updated to allow for URL formats for namespace identifiers as well. Sorry Len. ;) Joe Chiusano Booz | Allen | Hamilton Chiusano Joseph wrote: > > <Quote> > Supplementary question: if I was, say, a Government department, what > would you recommend? > </Quote> > > Here in the US, the Federal CIO Council XML Working Group created a > draft "Recommended XML Namespace for Government Organizations" document > in March 2003 [1]. You may find pp.10-12 of this document useful, where > the suggested formats for URNs are discussed. > > As a sidenote, I recommended that this document be updated to also > include URL formats for namespace identifiers. Oh, which reminds me: I > need to check on its status... > > Kind Regards, > Joe Chiusano > Booz | Allen | Hamilton > > [1] http://xml.gov/documents/in_progress/GS301L1_namespace.328.doc > > Andy Greener wrote: > > > > At 7:40 pm +0100 30/7/03, Alaric B Snell wrote: > > >>Andy Greener wrote: > > > > > >>>Maybe I'm just looking in the wrong places, so any pointers to resources > > >>>would be appreciated. > > > > > >Well, there's the urn:pin: namespace > > > > > >ftp://ftp.rfc-editor.org/in-notes/rfc3043.txt > > > > > >Or you can get an OID from your friendly neighbourhood ISO member body - the BSI in my case - and use urn:oid: like I did: > > > > > >http://www.warhead.co.uk/oid.html > > > > Both very handy references, thanks (though neither results in what > > might be called a "memorable" or mnemonic urn :-) > > > > Supplementary question: if I was, say, a Government department, what > > would you recommend? Neither a "pin" urn or an "oid" in the UK company > > namespace seems appropriate... > > -- > > > > Andy Greener Mob: +44 7836 331933 > > GID Ltd, Reading, UK Tel: +44 118 956 1248 > > andy@g... Fax: +44 118 958 9005 > > > > ----------------------------------------------------------------- > > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an > > initiative of OASIS <http://www.oasis-open.org> > > > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > > > To subscribe or unsubscribe from this list use the subscription > > manager: <http://lists.xml.org/ob/adm.pl> > > ------------------------------------------------------------------------ > ----------------------------------------------------------------- > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an > initiative of OASIS <http://www.oasis-open.org> > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > To subscribe or unsubscribe from this list use the subscription > manager: <http://lists.xml.org/ob/adm.pl> begin:vcard n:Chiusano;Joseph tel;work:(703) 902-6923 x-mozilla-html:FALSE url:www.bah.com org:Booz | Allen | Hamilton;IT Digital Strategies Team adr:;;8283 Greensboro Drive;McLean;VA;22012; version:2.1 email;internet:chiusano_joseph@b... title:Senior Consultant fn:Joseph M. Chiusano end:vcard
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.