Closed SpyrosKou closed 5 years ago
You are totally correct. We started having the sto:hasLicense
as datatype property and those that you pointed out are some errors left. Great that you have identified and corrected those errors. Please make a pull request.
Thank you,
I have created the pull request with all aforementioned changes. I also noticed that dcterms:hasLicense is used as an annotationProperty. By replacing dcterms:hasLicense with dcterms:license dcterms:hasLicense is only used as an annotationPropery.
I removed the property dcterms:hasLicense
.
Hello and congratulations on the good work done so far.
One issue I noticed is that instead of using the http://purl.org/dc/terms/license which is documented here: http://dublincore.org/documents/dcmi-terms/#terms-license A similar property has been defined, namely: http://purl.org/dc/terms/hasLicense
This property is defined as an object propery, linking with a dcterms:LicenseDocument object:
However out of the 19 times used in the Standards Ontology 18 times it is used as a DataProperty in the ontology. In particular: dcTerms:hasLicense "Private"@en ; Appears 12 times. dcterms:hasLicense "Public"@en ; Appears 4 times. dcterms:hasLicense "Open"@en ; Appears 2 times. dcterms:hasLicense sto:GPLv2 ; Appears 1 time.
A suggestion would be to replace the above statements with ObjectProperties.
I would also recommend using the original dcterms:license object propery and adding it to the sto:Standard class instead of defining dcterms;hasLicense.
I have prepared the aforementioned changes, I can push them if this is OK with you.