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

Expand gufo:isDerivedFrom domain and range? #3

Open
tgoprince opened this issue Sep 16, 2021 · 2 comments
Open

Expand gufo:isDerivedFrom domain and range? #3

tgoprince opened this issue Sep 16, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@tgoprince
Copy link
Member

tgoprince commented Sep 16, 2021

The object property gufo:isDerivedFrom has gufo:EndurantType as its range.

That prevents us from representing that a historical relation is derived from an event.

For instance:

:wasWrittenBy rdf:type owl:ObjectProperty;
    rdfs:subPropertyOf gufo:historicallyDependsOn ;
    rdfs:domain :Book;
    rdfs:range :Author;
    gufo:isDerivedFrom :CompositionProcess .

:CompositionProcess rdfs:subClassOf gufo:Event .

Shouldn't we expand this range to also include gufo:Event?

Maybe even make it gufo:ConcreteIndividual

This truthmaking pattern is discussed in:

Guarino, N., Sales, T. P., & Guizzardi, G. (2018, October). Reification and truthmaking patterns. In International Conference on Conceptual Modeling (pp. 151-165). Springer, Cham.

@tgoprince
Copy link
Member Author

tgoprince commented Sep 16, 2021

What do you think @claudenirmf?

@claudenirmf
Copy link
Member

I agree with you, we should open the range to include events to support historical relations. We should also check if it is ok to "bypass" the endurant in other to have the "strong truthmaking pattern" without the "weak truthmaking pattern".

@jpalmeida jpalmeida added the enhancement New feature or request label Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants