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

thors:component and referencePoint subproperty of What? #8

Open
smrgeoinfo opened this issue Sep 2, 2021 · 1 comment
Open

thors:component and referencePoint subproperty of What? #8

smrgeoinfo opened this issue Sep 2, 2021 · 1 comment

Comments

@smrgeoinfo
Copy link

currently have
thors:component rdfs:subPropertyOf skos:hasTopConcept ;
and
thors:referencePoint rdfs:subPropertyOf skos:hasTopConcept ;

I think I see the logic-- skos:hasTopConcept is the only skos property with domain skos:ConceptScheme and range skos:Concept, but semantically this doesn't make sense. Every thors:Era that is part of a thors:ReferenceSystem is not a top concept in that scheme.

we need a thors:isComponentOf relation (inverse of thors:component) from thors:Era to thors:ReferenceSystem to indicate the time scale instances a given era is a member of. Also thors:isReferencePointFor inverse of thors:referencePoint. These would be subProperties of skos:inScheme.

@dr-shorthair
Copy link

You could do it this way:

thors:component rdfs:subPropertyOf [ owl:inverseOf skos:inScheme ] . 

However, component comes from ISO 19108, and is intended to point to the top members of the hierarchy. I think the original axiom is consistent with that. But it does not also say that nested eras are not allowed. Not sure if that can be expressed.

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

2 participants