You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some concepts from the FOAF ontology are used to annotate the SOSA ontology - specifically, there is a blank node defining a foaf:Agent with foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en. This also applies to the SSN ontology.
foaf:name is defined in SOSA as an owl:AnnotationProperty. The FOAF ontology is not imported in SOSA. The defining statement is here today in SSN, here today in SOSA (links are to the last commits affecting those files, 2018-08-09).
Unfortunately, the most recent version of the FOAF specification defines foaf:name as an owl:DatatypeProperty. ("Most recent" meaning the 2014 version. The FOAF page currently links to that release stored on the Internet Archive, due to apparent recovery from an event.) This causes a graph that imports both FOAF and SOSA to be inconsistent with the OWL 2 DL Profile; see OWL 2 Syntax, Section 5.8.1, "Typing Constraints of OWL 2 DL", especially the last bullet under "Property typing constraints".
I haven't exhaustively reviewed other ontologies in this repository for the issue. I came across this issue due to work on a project involving DCAT and SSN, and found the issue using this SHACL shape on a graph incorporating SSN's and FOAF's transitive import closure.
Is it possible for this to be corrected for at least SOSA and SSN? I'm happy to supply a correcting PR, but am unsure of the policy on accepting contributions.
The text was updated successfully, but these errors were encountered:
This patch starts the adoption process of integrating the Semantic
Sensor Network (SSN) ontology into CASE-Corpora's ontology and shapes.
The initial application of SSN is in representing contents of a file
being observed to change.
Due to an issue with a definition conflict between FOAF, SSN, and SOSA,
this initial patch sets up the generation record, but does not
integrate SOSA and SSN into the build process yet.
A follow-on patch will regenerate Make-managed files.
References:
* https://github.com/w3c/sdw/issues/1395
Signed-off-by: Alex Nelson <[email protected]>
With this patch, the dependencies directory passes 'make check' with
sosa.ttl and ssn.ttl integrated.
A follow-on patch will regenerate Make-managed files.
References:
* https://github.com/w3c/sdw/issues/1395
Signed-off-by: Alex Nelson <[email protected]>
Hello,
Some concepts from the FOAF ontology are used to annotate the SOSA ontology - specifically, there is a blank node defining a
foaf:Agent
withfoaf:name "W3C/OGC Spatial Data on the Web Working Group"@en
. This also applies to the SSN ontology.foaf:name
is defined in SOSA as anowl:AnnotationProperty
. The FOAF ontology is not imported in SOSA. The defining statement is here today in SSN, here today in SOSA (links are to the last commits affecting those files, 2018-08-09).Unfortunately, the most recent version of the FOAF specification defines
foaf:name
as anowl:DatatypeProperty
. ("Most recent" meaning the 2014 version. The FOAF page currently links to that release stored on the Internet Archive, due to apparent recovery from an event.) This causes a graph that imports both FOAF and SOSA to be inconsistent with the OWL 2 DL Profile; see OWL 2 Syntax, Section 5.8.1, "Typing Constraints of OWL 2 DL", especially the last bullet under "Property typing constraints".I haven't exhaustively reviewed other ontologies in this repository for the issue. I came across this issue due to work on a project involving DCAT and SSN, and found the issue using this SHACL shape on a graph incorporating SSN's and FOAF's transitive import closure.
Is it possible for this to be corrected for at least SOSA and SSN? I'm happy to supply a correcting PR, but am unsure of the policy on accepting contributions.
The text was updated successfully, but these errors were encountered: