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
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
Hi Luca,
You mean things like
http://sameas.org/?uri=http%3A%2F%2Fdbpedia.org%2Fresource%2FEdinburgh
I think.
And for something many years old, and with other flags:
I am proud to announce the release of PAV (Provenance, Authoring and
Versioning) ontology version 2.3.0.
PAV is a lightweight ontology for tracking Provenance, Authoring and
Versioning. PAV specializes the W3C provenance ontology PROV-O in
order to describe authorship, curation and digital
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
Hi Ruben,
Cool posting.
Can you tell me id there is a pattern for the uri= style stuff, where you want
everything the service wants to say about the URI, in any position?
For a simple site this might look like the SCBD for the URI?
And I guess that raises the question of bnodes as well.
I have
On 8/22/14 4:44 PM, Luca Matteis 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 -
On 8/17/14 1:14 PM, Kingsley Idehen wrote:
On 8/16/14 2:19 PM, Ruben Verborgh wrote:
Hi Kingsley,
The issues arise from the conclusions.
But I don't really see issues on Vapour. Where did you find them?
There is an aspect to Vapour's conclusions that we need to make a
little clearer.
FYI On 8/22/14 6:00 PM, Tim Berners-Lee wrote, on the Tag and Semantic
Web lists:
There is a massive and reasonable push to get everything from HTTP space into
HTTPS.
While this is laudable, the effect on the web as a hypertext system could be
very severe, in that links into http: space will
Hi John,
Let us know about the VIVO extension that your team is working on to ingest
into VIVO data from CrossRef . Sure that it will be very useful. Does any
one of your team was in the last VIVO Conference in Austin?
The team from Cornell has developed the integration of ORCID with VIVO. See
10 matches
Mail list logo
