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.
And in fact I think all the prefixing patterns fail that test?
On 4 September 2014 20:57, Hugh Glaser h...@glasers.org 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
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,
Hi Mark,
Indeed. Interestingly, this use case was the first one I published as an
example of RDF Forms;
http://www.markbaker.ca/2003/10/UriProxy/
It's then probably not a coincidence that the first iteration of triple pattern
fragments
worked with the RDF Forms vocabulary :-)
Hi Luca,
I'm wondering however if *form URIs* could themselves be resources
rather than datasets.
Sure, why not. They're just URIs.
For example imagine the example from earlier:
http://bar.com/?subject=http%3A%2F%2Ffoo.com%2Falice a void:Dataset .
http://foo.com/alice #some #data .
On 8/25/14 7:26 AM, Ruben Verborgh wrote:
Hi Luca,
I'm wondering however if*form URIs* could themselves be resources
rather than datasets.
Sure, why not. They're just URIs.
For example imagine the example from earlier:
http://bar.com/?subject=http%3A%2F%2Ffoo.com%2Falice a
On 22 Aug 2014, at 22:43, Ruben Verborgh ruben.verbo...@ugent.be wrote:
Hi Hugh,
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?
The current triple pattern fragments spec does not
bnodes are Semantic Web, but not Linked Data.
If a node doesn't have a universal identifier, it cannot be addressed.
I find this comment strange.
If you mean that I can’t query using a bnode, then sure.
If you mean that I never get any bnodes back as a result of a Linked Data URI
GET, then
One of the advantages of bNodes is that they don't have names so that
people can't add things to them. This is useful in the case of RDF
Collections and in places of the OWL spec where you can use them to say
that 'these things are in the collection' and others can't add to them.
On Mon, Aug
On Aug 25, 2014, at 9:38, Paul Houle ontolo...@gmail.com wrote:
One of the advantages of bNodes is that they don't have names so that people
can't add things to them. This is useful in the case of RDF Collections
Yes, because RDF Collections are collections without identity. But, in many
On 8/25/14 11:17 AM, Ruben Verborgh wrote:
bnodes are Semantic Web, but not Linked Data.
If a node doesn't have a universal identifier, it cannot be addressed.
I find this comment strange.
If you mean that I can’t query using a bnode, then sure.
If you mean that I never get any bnodes back as a
On Aug 22, 2014 12:23 PM, Ruben Verborgh ruben.verbo...@ugent.be wrote:
This gets us to a deeper difference between (current) Linked Data and the
rest of the Web:
Linked Data uses only links as hypermedia controls,
whereas the remainder of the Web uses links *and forms*.
Forms are a much more
On Fri, Aug 22, 2014 at 6:19 PM, Ruben Verborgh ruben.verbo...@ugent.be wrote:
This gets us to a deeper difference between (current) Linked Data and the
rest of the Web:
Linked Data uses only links as hypermedia controls,
whereas the remainder of the Web uses links *and forms*.
Forms are a
On 8/24/14 1:16 PM, Mark Baker wrote:
On Aug 22, 2014 12:23 PM, Ruben Verborgh ruben.verbo...@ugent.be
mailto:ruben.verbo...@ugent.be wrote:
This gets us to a deeper difference between (current) Linked Data
and the rest of the Web:
Linked Data uses only links as hypermedia controls,
Hey all,
the only specification I know that actually solves practical RDF input
problems is RDF/POST encoding:
http://www.lsrn.org/semweb/rdfpost.html
It can be easily incorporated into XSLT stylesheets to provide
reusable layout templates, and with SPIN constraints to provide
validation:
On 08/22/2014 11:44 AM, 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.
That is the technique used
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:
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 -
22 matches
Mail list logo
