Why not simply follow Xlink/CPointer in this question? The GET request Alistair has been talking about is a conforming solution. Example http://blah?concept=666 Thomas Bandholtz Semantic Web Consultant Karl-Friedrich-Schinkelstr. 2 53127 Bonn Germany www.bandholtz.info +49 228 9288490 cell +49 179 4700576 thomas@bandholtz.info ----- Original Message ----- From: "Dan Brickley" <danbri@w3.org> To: "Miles, AJ (Alistair) " <A.J.Miles@rl.ac.uk> Cc: <public-esw-thes@w3.org>; <public-esw@w3.org> Sent: Friday, April 30, 2004 5:18 PM Subject: Re: URI policy for thesaurus concepts Alistair: > > Reason for going with / and not # is so that the concept ID is included in > > an http GET request and not lost as it would be if it came after a #. Dan: > I prefer the / approach, but I should warn that TimBL and others have > made the claim that http://blah/ URIs without a # can only name > 'documents' or 'networked information resources', and that concepts, > classes, properties etc don't count as those.Received on Friday, 30 April 2004 12:03:23 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:13 GMT