On 4 September 2014 20:57, Hugh Glaser <[email protected]> wrote: > Nice. > That enumerates the choices, I think. > In a world where the services are themselves being used as LD URIs > (because everything is a LD URI, of course!) there is the orthogonal > question of whether the URI needs to be URLEncoded. >
Surely they should normally be urlencoded, how else would you send a #? However that's not very readable or simple. But there are cases where you can get away without it, if you have a well defined set of possibilities, I think? > And in fact I think all the prefixing patterns fail that test? > If you are still updating patterns, you might like to add a note? > Cheers > > > On 28 Aug 2014, at 15:12, Leigh Dodds <[email protected]> wrote: > > > > Hi, > > > > I documented all the variations of this form of URI construction I was > > aware of in the Rebased URI pattern: > > > > http://patterns.dataincubator.org/book/rebased-uri.html > > > > This covers generating one URI from another. What that new URI returns > > is a separate concern. > > > > Cheers, > > > > L. > > > > On Fri, Aug 22, 2014 at 4:56 PM, Bill Roberts <[email protected]> wrote: > >> Hi Luca > >> > >> We certainly find a need for that kind of feature (as do many other > linked data publishers) and our choice in our PublishMyData platform has > been the URL pattern {domain}/resource?uri={url-encoded external URI} to > expose info in our databases about URIs in other domains. > >> > >> If there was a standard URL route for this scenario, we'd be glad to > implement it > >> > >> Best regards > >> > >> Bill > >> > >> On 22 Aug 2014, at 16:44, Luca Matteis <[email protected]> wrote: > >> > >>> Dear LOD community, > >>> > >>> I'm wondering whether there has been any research regarding the idea > >>> of having URIs contain an actual URI, that would then resolve > >>> information about what the linked dataset states about the input URI. > >>> > >>> Example: > >>> > >>> http://foo.com/alice -> returns data about what foo.com has regarding > alice > >>> > >>> http://bar.com/endpoint?uri=http%3A%2F%2Ffoo.com%2Falice -> doesn't > >>> just resolve the alice URI above, but returns what bar.com wants to > >>> say about the alice URI > >>> > >>> For that matter http://bar.com/?uri=http%3A%2F%2Ffoo.com%2Falice > could return: > >>> > >>> <http://bar.com/?uri=http%3A%2F%2Ffoo.com%2Falice> a void:Dataset . > >>> <http://foo.com/alice> <#some> <#data> . > >>> > >>> I know SPARQL endpoints already have this functionality, but was > >>> wondering whether any formal research was done towards this direction > >>> rather than a full-blown SPARQL endpoint. > >>> > >>> The reason I'm looking for this sort of thing is because I simply need > >>> to ask certain third-party datasets whether they have data about a URI > >>> (inbound links). > >>> > >>> Best, > >>> Luca > >>> > >> > >> > > > > > > > > -- > > Leigh Dodds > > Freelance Technologist > > Open Data, Linked Data Geek > > t: @ldodds > > w: ldodds.com > > e: [email protected] > > > > -- > Hugh Glaser > 20 Portchester Rise > Eastleigh > SO50 4QS > Mobile: +44 75 9533 4155, Home: +44 23 8061 5652 > > > >
