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
I have an ontology design question. I think there is a conflict between “Don’t Repeat Yourself” and “Anyone can say Anything about Anything”. The following query produces 194 results when executed against the NQUADS format of a recent FIBO distribution:
While a DESCRIBE query executed against the default graph produces all the triples that define the meaning of the subject, I wonder if it would be helpful if all the contributors to the meaning of a subject were made explicit everywhere the meaning was elaborated by use of rdfs:seeAlso leaving rdfs:isDefinedBy to delineate where specific parts of the meaning is defined?
This discussion was converted from issue #1346 on February 25, 2021 09:50.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have an ontology design question. I think there is a conflict between “Don’t Repeat Yourself” and “Anyone can say Anything about Anything”. The following query produces 194 results when executed against the NQUADS format of a recent FIBO distribution:
While a
DESCRIBE
query executed against the default graph produces all the triples that define the meaning of the subject, I wonder if it would be helpful if all the contributors to the meaning of a subject were made explicit everywhere the meaning was elaborated by use ofrdfs:seeAlso
leavingrdfs:isDefinedBy
to delineate where specific parts of the meaning is defined?Beta Was this translation helpful? Give feedback.
All reactions