- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Mon, 9 Nov 2015 22:09:20 +0100
- To: "Ruben Verborgh" <ruben.verborgh@ugent.be>, "Markus Lanthaler" <markus.lanthaler@gmx.net>
- Cc: "Hydra" <public-hydra@w3.org>
We're using similar approach in our (with Tomasz Pluskiewicz)
RomanticWeb.net ORM class solution that wraps RDF with C# strong types.
Default implementation assigns a named graph to each non-blank resource. The
difference is that we also have a "special" meta-graph, that binds graphs
with their resources. Example:
<meta:graph> {
<graph://a> foaf:primaryTopic <http://a> .
<graph://b> foaf:primaryTopic <http://b> .
}
<graph://a> {
<http://a> some:value "" .
}
<graph://b> {
<http://b> some:relation <a> .
}
This way we can easily bind graphs with their respective resources and
vice-versa. I think Nanopublications lacks this mechanism (unless they
assume some convention which is somehow "volatile").
Best
Karol
Received on Monday, 9 November 2015 21:09:43 UTC