nasa / LSDAO

1 stars 2 forks source link

Problem including dcterms ontology #1

Open DanBerrios opened 2 years ago

DanBerrios commented 2 years ago

Trying to include dcterms properties into the build, but getting punning errors:

Cannot pun between properties: http://purl.org/dc/terms/valid [AnnotationPropertyRange(http://purl.org/dc/terms/valid http://www.w3.org/2000/01/rdf-schema#Literal) in OntologyID(OntologyIRI(http://purl.obolibrary.org/obo/lsdao.owl) VersionIRI(http://purl.obolibrary.org/obo/lsdao/releases/2022-08-09/lsdao.owl))

I have converted/saved the dcterms rdf file as an OWL files, but still the same errors. Is it due to use of these properties by other ontology imports?

DanBerrios commented 2 years ago

Correction to the above..I was getting the punning errors but with a few changes to Makefile, I don't get them anymore, however...Not sure if the build is correct... imported DC terms properties are each listed in Protege search 3 times....once as data properties, once as annotationproperties and once as individuals...

matentzn commented 2 years ago

This is a quite complicated problem to solve to be honest. I recommend to delete these properties from your imports

DanBerrios commented 2 years ago

@matentzn You mean, forcibly delete them from the import module build from all imported ontologies (except DC) ?

matentzn commented 2 years ago

Which ontology exactly are you trying to import?

If it is dc, then better don't. I recommend importing http://purl.obolibrary.org/obo/omo.owl

instead, which has a few of the most important dc properties relevant to ontology development (not restricted to OBO!)

DanBerrios commented 2 years ago

DC Terms....

OMO doesn't have entities which we would find useful for this application ontology, which is focused on curating scientific data sets. DC Terms like "dateSubmitted", "dateReleased", etc. are what we are looking for....

matentzn commented 2 years ago

Ok, in that case, I recomment to create your own dc module using a robot template, like

ID Label TYPE
ID LABEL TYPE
dcterms:dateSubmitted date submitted owl:AnnotationProperty

and use that instead of an official import. You will get the exact same benefit (FAIR data wise) without any of the downsides!

You don't even need the label, just the first and third column is enough.

DanBerrios commented 2 years ago

@matentzn Is this the cause of my problem? Seems like other users have had problems working with dcterms rdf file...and the solution is to use instead the ttl file of dcterms:

https://twitter.com/DublinCore/status/1369219886598262784

Update: Switching the ttl file seems to have solved the issues I was having (as were others, I guess) using the imported DC terms in Protege.

Thanks for helping to debug!

matentzn commented 2 years ago

Ok! If it works, it works :) Thanks for keeping me posted.