Open GoogleCodeExporter opened 9 years ago
This is related to Issue #3 (provenance information). I'd say that existing
provenance vocabularies, including W3C's PROV-O, are quite suitable and
probably sufficient for expressing this kind of information.
The only thing not obviously covered there is the distinction between
manual/semi-automatic/fully-automatic processes. For this, a specialisation of
PROV-O focused specifically on expressing the provenance of RDF links could be
a good idea.
Whether publishers will include such information in their VoID files is of
course a separate question. A first step here would be to encourage the
developers of link generation tools to generate provenance information along
with the links, in a consistent format.
Original comment by richard....@gmail.com
on 2 Sep 2013 at 12:06
Original issue reported on code.google.com by
csarasua...@gmail.com
on 2 Sep 2013 at 11:36