Dear Linked Data community,
we're glad to announce Vapour 3.0, a validator for Linked Data, now
online at [1]. As usual, the source code is also available at
Sourceforge [2].
This new version includes a simpler and cleaner interface, but more
realistic scenarios (testing mixed accept headers,
On 4/20/12 8:13 AM, Sergio Fernández wrote:
Dear Linked Data community,
we're glad to announce Vapour 3.0, a validator for Linked Data, now
online at [1]. As usual, the source code is also available at
Sourceforge [2].
This new version includes a simpler and cleaner interface, but more
On Thu, Apr 19, 2012 at 11:00 AM, Richard Wallis
richard.wal...@dataliberate.com wrote:
I presume the server doing the 301 is going to stay around for a while.
This is at least part of the problem. In theory, LOD clients should cache a
301 (unless specifically instructed not to) and resolve
Thanks a lot for your feedback! That's really precious.
@Richard, Jon: yes, we'll try to have the 301 working for a while. But not
forever, so it would be good if something could function as a more stable
solution. Though I'm not sure the requirement is too strong, in our case. It's
not as if
On 4/20/12 9:11 AM, Antoine Isaac wrote:
Thanks a lot for your feedback! That's really precious.
@Richard, Jon: yes, we'll try to have the 301 working for a while. But
not forever, so it would be good if something could function as a more
stable solution. Though I'm not sure the requirement
Antoine
In fact it seems that the dcterms:replaces option considers two resources
(one that replace the other).
Indeed. The bnf resource replaces, by all means of the term, the stitch
one.
Which in turns hints that you're considering that the URIs denote the URI
themselves (or a
That is an impressive list of new features Barry. Congratulations to the
OWLIM dev team with this new release!
Cheers,
Jeen
this message brought to you by Toronto airport free wifi :)
On Apr 20, 2012 8:47 AM, Barry Bishop barry.bis...@ontotext.com wrote:
Ontotext are pleased to announce the
