Hey all, Graphity Client uses the same ?uri= convention: http://semanticreports.com/?uri=http%3A%2F%2Fwww4.wiwiss.fu-berlin.de%2Feurostat%2Fresource%2Fcountries%2FDanmark
Martynas graphityhq.com On Fri, Aug 22, 2014 at 5:56 PM, Bill Roberts <b...@swirrl.com> 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 <lmatt...@gmail.com> 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 >> > >