Linked Data Compatibility

[GoogleCodeExporter]

I am trying to consume the RDF from Simal as Linked Data.

I think you need to review the provision against the best practice, as it has 
quite a few problems.

As an example, as far as I can see,
you have a project with URI 
http://registry.oss-watch.ac.uk/project/simalID/prj4368
Asking for RDF from this gives html.
The project page gives a URI for the RDF as
http://registry.oss-watch.ac.uk/simal-rest/project/source-simal/project-prj4368/
xml
but this RDF says it is about
http://simal.oss-watch.ac.uk/doap/132246b7-6873-4708-96bc-0278780baa1c-prj4368#P
roject
which gives a 301 to http://simal.googlecode.com/

In short, you should have URIs for each project that somehow return RDF (either 
with a 303 or a hash URI)

Best
Hugh
hg@ecs.soton.ac.uk

Original issue reported on code.google.com by hugh.gla...@gmail.com on 6 Mar 2011 at 10:23

[GoogleCodeExporter]

Thanks for the report Hugh. Since I hacked this code without a proper 
understanding of RDF and linked data this doesn't surprise me. Now that we have 
Sander with a more complete understanding of this stuff it will get addressed 
before we leave alpha.

Original comment by ross.gardler on 7 Mar 2011 at 4:08

• Changed state: Accepted
• Added labels: Milestone-0.3, Priority-High, Usability
• Removed labels: ****

[GoogleCodeExporter]

Yes, getting Linked Data right is surprisingly tricky.
One option is to avoid having to do the awkward stuff yourself, and to put the 
RDF in a store and then serve it using a Linked Data service - the Linked Data 
API can be of help here.

Original comment by hugh.gla...@gmail.com on 8 Mar 2011 at 3:40

• Added labels: ****
• Removed labels: ****