-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of datacite:hasIdentifier #20
Comments
For @gkirtzou : This is the first time I see datacite, but it looks good! |
The automatically generated rdf representation from metashare xml record
|
This was represented in Metashare XML as follows...
|
This is a clear mistake: _:license datacite:usesIdentifierScheme |
@pennyl67 @gkirtzou This issue has been solved and deployed. Can be tested on https://rdflicense.linkeddata.es/service.html |
@vroddon I just made a test and I'm puzzled; although you have identified an error in the representation, the output seems to be still the wrong one, i.e. _:genid1 http://w3id.org/meta-share/meta-share/LicenceIdentifier http://w3id.org/meta-share/meta-share/SPDX . In the above, the first triple links the identifier to "SPDX" with the "LicenceIdentifier", but
[] (I've kept as is, but I'm still not sure whether rdfs:label is required or of any help) |
Yes! same RDF, different serializations. The first one is NTRIPLES, the second TURTLE. Maybe it is cleaner not using blank nodes. |
I'm still confused :-( |
And I just spotted an error in the first representation: _:license datacite:usesIdentifierScheme the correct one should be _:license datacite:usesIdentifierScheme should be i.e. the first row has the wrong property |
I have created an real example that follows the metashare ontology, so you could see what is the correct structure and vocabulary using the metashare ontology, how we have designed it. The example is the CC-BY-4.0 licence (see attachment). I know that unfortunately all this information cannot derive directly from the metashare xml records, we need to design an extra mapping.
As you could see in the example the relation between a LicenceTerms and its identifier is represented using the datacite:hasIdentifier property and following datacite suggestions we use the property literal:hasLiteralValue to declare the actual value. Though, we are not sure if this is the right approach. We know that it is good as we reuse existing vocabulary, but both vocabularies are not maintained and more importantly are not dereferencable and one needs to manuall search in order to find them. Do you think that this is the right way to approach the issue? Do you think that literal:hasLiteralValue has the correct semantics for our case?
The text was updated successfully, but these errors were encountered: