Upgrade StorageRDF-Export and rdf:about reference
Hello to all,
I didnt't find anything regarding this topic, so I opened a new discussion.
Maybe I just don't find the correct setting, but after an export into RDF format the reference are not really good.
If a URL to a http-Resource is given, it will be used as identifier for "rdf:about.
Example:
In ZOTERO is given the URL "http://www.somehost.org/example?seq=1#24345"
then in rdf:about stands:
rdf:about="http://www.somehost.org/example?seq=1#24345"
If no URL is give an it has something like: item_23213.
This is NOT persistent and references can lose the link to the resource.
But Zotero als has better IDs to reference an entry inside the own bibliography.
Example:
https://www.zotero.org/my_bibliography/items/itemKey/6WXCHA34
Why not use this?
I didnt't find anything regarding this topic, so I opened a new discussion.
Maybe I just don't find the correct setting, but after an export into RDF format the reference are not really good.
If a URL to a http-Resource is given, it will be used as identifier for "rdf:about.
Example:
In ZOTERO is given the URL "http://www.somehost.org/example?seq=1#24345"
then in rdf:about stands:
rdf:about="http://www.somehost.org/example?seq=1#24345"
If no URL is give an it has something like: item_23213.
This is NOT persistent and references can lose the link to the resource.
But Zotero als has better IDs to reference an entry inside the own bibliography.
Example:
https://www.zotero.org/my_bibliography/items/itemKey/6WXCHA34
Why not use this?
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
That said, RDF export isn't meant to be persistent across exports, why do you need it to be? For anything where that's relevant, you almost certainly want to be using the API.
But thanks for your fast reaction.