On 13/12/2020 19:34, Laura Morales wrote:
What's your interest in RDF*?
...
Another issue for me with property graphs, but I would like to hear your feedback on this, is that
properties are indexed globally and it's my understanding that they only accept one data type (eg.
Integer). So
The source code , with store and SPARQL to retrieve, and a few
explanations, is here:
https://github.com/jmvanel/semantic_forms/blob/master/scala/forms/src/main/scala/deductions/runtime/semlogs/TimeSeries.scala#L27
The trick used is to create a new URI for each modification of the main
database (
> This is an alternative to RDF* , AFAIK .
> If someone is interested, I can document the structure of the secondary TDB
> database.
I don't want to abuse your time but yes, this would be helpful. Even just a
sketch of it, just to get the idea.
I use on the SF (1) site (powered by (2) ) a secondary TDB database, not
exposed via SPARQL, which contains annotations on the primary data.
This enables to have roughly the equivalent of git; its records a history
of user edits.
Via web pages, only a bit of this data is exposed, allowing to show
> What's your interest in RDF*?
There seems to have been this endless debate about triplestores vs property
graphs since as far as I can remember. This new standard apparently promises to
be the best of both world by supporting RDF plus what they call "richer types"
(aka nodes, vertexes).
On 13/12/2020 17:05, Laura Morales wrote:
I've only recently discovered the existence of RDF* and Turtle*. Looks like
they were introduced around 2019. Does Jena have support for these in the
current release?
https://jena.apache.org/documentation/rdfstar/index.html
As RDF* is currently
