Class Reference is misused, and probably of marginal use #1402
Unanswered
rivettp
asked this question in
Foundations (FND)
Replies: 1 comment
-
Conversely, by this definition of Reference, https://spec.edmcouncil.org/fibo/ontology/FND/Parties/Roles/ThingInRole should subclass Reference but does not, since the thing in role inherently does represent/stand in for the thing. And https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/hasIdentity should be (and is not) a subProperty of identifies. Or refersTo? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
https://spec.edmcouncil.org/fibo/ontology/FND/Relations/Relations/Reference, as used in FIBO (which is not in line with its definition), is spectacularly useless, and probably harmful.
It's defined as "a concept that refers to (or stands in for) another concept".
It's hence OK as the superclass of https://spec.edmcouncil.org/fibo/ontology/FBC/FunctionalEntities/RegistrationAuthorities/RegistryEntry
And https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/IdentifiersAndIndices/Identifier
But then it's used as the superclass of
And as the domain of several properties in relations, the most egregious of which are:
They should all be reviewed. And Reference itself, if we retain it, should have more value e.g. something useful you an infer or query on.
Beta Was this translation helpful? Give feedback.
All reactions