Skip to content
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

Is geox:transitiveSfOverlap useful? #1

Open
dr-shorthair opened this issue Aug 23, 2019 · 0 comments
Open

Is geox:transitiveSfOverlap useful? #1

dr-shorthair opened this issue Aug 23, 2019 · 0 comments

Comments

@dr-shorthair
Copy link
Collaborator

geox:transitiveSfOverlap is a sub-property of geo:sfOverlap.

It was added to manage the case where the existence of an overlap has been inferred from the situation where a feature that is contained by the context feature is also within a second feature.

This is axiomatized as follows:

  owl:propertyChainAxiom (
      geo:sfContains
      geo:sfWithin
    ) ;

However, the resulting inferred property differs from a normal geo:sfOverlaps only in terms of the way it was detected - i.e. the provenance of the relationship. IMHO provenance does not belong in a relationship name - it is additional information that might be associated by reification, or named-graph membership, or something.

This approach is related to the way that @nicholascar had used OWL axiomatization in general. The theory was that a lot of relationships could be built by the reasoner, at load-time. This is a fine idea, but does depend on (a) all the ontologies being consistent (b) all the data being correct.

Loading several ontologies developed by different people at different times in different styles, along with several (large) datasets with inferencing turned on is a risky business - you will get way more additional axioms than you need in practice, and there will almost certainly be unintended consequences. Rather I would recommend 'pre-processing' using SPARQL CONSTRUCT/INSERT in order to add specific relationships that are known to be needed. The distinct property based on provenance only is generally unhelpful IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant