(sorry for cross-posting)
Hi all,
the Linked Data Patch Format [1] (LD Patch) is now a Candidate
Recommendation, and has an extensive Test Suite. We are now welcoming
implementations.
The instructions for submitting implementation reports are available [3],
and the reports will be published
Hi,
if I was to knitpick, I would argue that the @id attribute in HTML
identifies a fragment of the HTML document, hence not precisely a video ;
for example, the video element has exactly one parent element (e.g. an
enclosing div or section), which is not true of the video itself (that
could be
Hi Thomas,
On Wed, Dec 4, 2013 at 6:24 PM, Thomas Steiner to...@google.com wrote:
Hi again,
Thanks for your reply, Kingsley.
http://ex.org/video.mp4 denotes one entity.
http://ex.org/video.ogv denotes another.
well, it is actually up to the owner of the namespace to decide what those
Erratum :
this post-doc position is meant to start in the *autumn 2013* (i.e. next
september/october) not 2014...
pa
On Wed, Jul 17, 2013 at 4:40 PM, Pierre-Antoine Champin
pierre-antoine.cham...@liris.cnrs.fr wrote:
(Sorry for cross-posting)
This proposal is available at:
https
engineering/Knowledge engineering, Semantic
Web and associated technologies. They should be fluent in English (written
and spoken). French speaking skills would be a plus.
For more information and to apply, contact:
- Pierre-Antoine Champin pierre-antoine.cham...@univ-lyon1.fr
- Benoît Encelle
Hi,
when I try http://champin.net/#pa, it tells me that it identifies an
information resource, while I'm claiming this is a person (as states the
RDFa in the document at http://champin.net/ [1]).
Apparently, Hyperthing only recognizes RDF/XML for the moment; any plan
to support Turtle and/or
Wonderful.
Any PDF version available?
pa
On 06/04/2010 16:10, Leigh Dodds wrote:
Hi folks,
Ian Davis and I have been working on a catalogue of Linked Data
patterns which we've put on-line as a free book. The work is licensed
under a Creative Commons attribution license.
This is is
Here are my 2¢ about the opacity of resources.
First, let me point out that, contrary to what is often believed/claimed
(and I plead guilty of having done so), URI opacity is *not* a
constraint of the REST architectural style, at least as defined by
Fielding in his thesis [1].
Then, AFAIK, the
Hi all,
This is a cool stuff, indeed.
I think an interesting use case would be to dig into a link to use its
href URI instead of its text. Because let's face it, the web contains
much more links with human-readable labels than plain URIs in the body
of a page...
I'm affraid my poor knowledge of
Hi Hugh,
interesting suggestion; I have also been frustrated with dbpedia URIs in
the adress bar, which you have to (or forget to) change when you want to
feed them to an RDF agent...
However, 406 seems to be the most appropriate answer to give. Falling
back to 301 in too many different
should (or at least could) be 200
rather than 406, right?
:-)
I guess this is because of that hypdrid status of RDF (regardless of its
serialization), being somewhere between data and metadata.
pa
On 24/03/2010 09:06, Pierre-Antoine Champin wrote:
Hi Hugh,
interesting suggestion; I have also
On 11/03/2010 23:55, Nathan wrote:
Pierre-Antoine Champin wrote:
On 11/03/2010 11:04, Toby Inkster wrote:
On Thu, 2010-03-11 at 02:24 +, Nathan wrote:
If I have multiple representations of a resource which I consider
equal, let's say one of each of the following: RDF+XML, RDF+N3, SVG
On 11/03/2010 11:04, Toby Inkster wrote:
On Thu, 2010-03-11 at 02:24 +, Nathan wrote:
If I have multiple representations of a resource which I consider
equal, let's say one of each of the following: RDF+XML, RDF+N3, SVG
Then should all three representations be considered equivalent?
On 02/02/2010 16:20, Leo Sauermann wrote:
* you won't find anything else that really fits RDF because of the
subclass/multiclass/missing properties/too many properties dynamics
you have in RDF. Templating languages are not good for this, also
fresnel data can spread and grow on the web like
On 27/01/2010 03:45, Peter Ansell wrote:
Disambiguating everything is a pipe dream IMO.
I agree with that.
Note also that HTTP makes a difference between a *resource* (identified
by a URI) and the *entity* retrieved when GETting the URI, which is a
mere *representation* of the resource.
From
On 27/01/2010 12:02, Christoph LANGE wrote:
Dear all,
thanks for your helpful replies. I will summarize with a few comments.
Of course the conceptual difference between a non-information resource and an
information resource is clear to me; I was rather concerned about how relevant
this
Interesting :)
You may be interested in having a look at
http://champin.net/t4r/demo
which can be used in a simiar fashion.
The main difference is that T4R mixes the query in the template, while
you are separating the SPARQL query from the presentation.
I have plans to allow T4R templates to
Hi Simon,
basically, I agree with you: having a single namespace makes the
ontology easier to use, even if the terms are described in separate modules.
More generally, there is not reason why the physical splitting into
modules should necessarily result in a logical splitting into
different
I like this! :)
However, some people will still be concerned about naming their
resources under a domain that is not theirs. That is not only a matter
of URI-prettiness, but also of relying on an external service, which may
cease to exist tomorrow.
However, this could easily be solved. All
Mark,
disclaimer: I have nothing against the RDFa solution; I just don't think
that one size fits all :)
ok, the solutions proposed here (by myself and others) still involve
editing the .htaccess. However, compared to configuring HTTP
redirections using mod_rewrite, they have two
Le 05/07/2009 13:54, Toby A Inkster a écrit :
On 5 Jul 2009, at 01:52, Pierre-Antoine Champin wrote:
I guess a PHP version would not even require that .htaccess, but
sorry, I'm not fluent in PHP ;)
The situation with PHP should be much the same, though I suppose web
hosts might be more
free to propose other ones.
enjoy
pa
#!/usr/bin/env python
#EasyPub: easy publication of RDF vocabulary
#Copyright (C) 2009 Pierre-Antoine Champin pcham...@liris.cnrs.fr
#
#EasyPub is free software: you can redistribute it and/or modify
#it under the terms of the GNU Lesser
Pierre-Antoine Champin swlists-040...@champin.net:
I would expect that a DESCRIBE query to the SPARQL endpoint return what
I get when dereferencing the URI.
pa
I would expect that a DESCRIBE query to the SPARQL endpoint return what
I get when dereferencing the URI.
pa
Daniel Schwabe a écrit :
Dan and Hugh,
let me be more specific.
I'm not really advocating that only *one* direction should be returned
(or even both directions).
I am asking a more
24 matches
Mail list logo
