Geek Answers Handbook

REST and RDF, what is the presentation strategy?

There are many nodes in your tripe, and you must make this database accessible through the REST interface.

Now my solution will be that each named (non-anonymous) node is exported as a resource whose representation:

  • all triples having node as an object
  • all triples having node as an object
  • All linked anonymous sites.

I am a little reluctant to point number 2: this will mainly give both incoming and outgoing triples.

How do you feel about the representation of REST syntax for a pure RDF-centric data warehouse? Do you share my point of view or not, and if not, what is your attitude towards it?

+4
source share
3 answers

Depending on what the data is and what the user of the interface wants to do with it. This question is similar to querying the SPARQL DESCRIBE query form. (This is determined by the implementation.)

For the use cases that I had with RDF data, I would go with 1 and 3, creating an empty node resource closure. In addition, you may have a separate interface for case 2, returning the incoming resource arcs.

+2
source

One easy way to make the RDF dataset REST inverse is to use the URLs for all roaming items.

When accessing a URL, for example through an HTTP GET, the result shows connected nodes (linked as properties and / or inverse properties).

A more formally returned view may be a short description of the resource.

+1
source

(disclaimer: this may not correspond to the exact content of your question, but matches the name)

I think that the topic of presenting a reposition of RDF data is a common problem of reversing the order of concepts. It would be normal for me to have a collection of Rest documents with RDF data and use the RDF database to index and create global queries.

In this situation, you can organize your resources as you prefer.

Also (if you pretend to use a URI node as an exported resource), your approach will have subtle problems about what your resources mean: the Rest resources that you offer here are “ information resources ” and then they cannot be abstract resources. There is a conflict between information and meta-information.

I published an article here , explaining this view in more detail.

0
source

More articles:


All Articles