info:openly:sw/words/english/if info:openly:sw/words/english/you info:openly:sw/words/english/mean info:openly:sw/words/english/that info:openly:sw/words/english/it info:openly:sw/words/english/is info:openly:sw/words/english/easier info:openly:sw/words/english/to info:openly:sw/words/english/use info:openly:sw/words/english/short info:openly:sw/words/english/symbols info:openly:sw/words/english/rather info:openly:sw/words/english/than info:openly:sw/words/geek/URIs info:openly:sw/words/english/then info:openly:sw/words/english/of info:openly:sw/words/english/course info:openly:sw/words/english/I info:openly:sw/words/english/agree info:openly:sw/punctuation/%2E Though I'm not sure what that has to do with info: vs urn: vs http: ... ;-) Patrick On 2003-10-16 19:53, "ext Eric Hellman" <eric@openly.com> wrote: > At 9:46 AM +0300 10/15/03, Patrick Stickler wrote: >> There is nothing that >> the info: URI scheme offers that the http: URI scheme does not provide, >> yet there is much that the http: URI scheme offers that the info: >> scheme does not provide and which is IMO very important for the SW. >> >> Patrick > > http://www.openly.com/sw/words/english/There > http://www.openly.com/sw/words/english/are > http://www.openly.com/sw/words/english/many > http://www.openly.com/sw/words/english/cases > http://www.openly.com/sw/words/english/where > http://www.openly.com/sw/words/english/the > http://www.openly.com/sw/words/english/use > http://www.openly.com/sw/words/english/of > http://www.openly.com/sw/words/geek/http > http://www.openly.com/sw/words/geek/uris > http://www.openly.com/sw/words/english/is > http://www.openly.com/sw/words/english/completely > http://www.openly.com/sw/words/english/innapropriate > http://www.openly.com/sw/punctuation/%2E > > http://hellman.net/eric/ > > http://just.kidding/ >Received on Friday, 17 October 2003 07:05:31 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 October 2007 06:11:45 GMT