CSVW converter does not properly link data to author

[RinkeHoekstra]

It's a tricky thing to associate the nanopublication produced by the converter with the original author information of the CSVW schema file.

In principle, any author information in the schema is author information of the CSVW schema, but as we cannot know beforehand the URI that is generated for the nanopublication/assertion pair by the converters, it is practical to just take that author informaiton, and use it for the nanopublication as well (since the csvw conversion is a purely syntactic effort, we cannot really say there's any additional authorship involved: the authors of the resulting RDF are the same as the ones who devised the schema).

Still, currently the two are not connected. This is mainly because the CSVW schema files do not usually have a root resource with a URI (no @id tag in the root of the JSON).

Possible solutions:

• replace the BNode with the generated URI of the nanopublication/assertion
• owl:sameAs the BNode with the generated URI of the nanopublication/assertion

[rlzijdeman]

@albertmeronyo sorry, to bother you with this, but @melvinroest was asking me whether 'we' still perceive this as a bug?

[albertmeronyo]

@rlzijdeman Sorry I only see this now! I don't think this is much of a bug. At least in our experience nobody cared much about how authorship is modelled/serialised in the nanopub graphs? So I'd say it's rather a 'nice-to-have' :-)