Hello everyone.
I'm working on an ontology project -- designing a baseline ontology describing a business domain. The source content is being gleaned from a series of presentations and info graphics.
So far, some design patterns have emerged to distinguish between concepts, attributes of concepts, relationships among concepts, and attributes of relationships. However, the implied patterns are not being applied consistently across the ontology.
Does anyone have any resource recommendations for ontology design best practices -- specifically answering these questions:
a) when to build an association as an attribute -- e.g., freeform text v. boolean v. pick list sourced from another concept
b) when to build an association as a relationship (in a mapping table, so to speak, rather than as a metadata attribute -- I recognize this might be a tool-specific question, but I'm not 100% sure)
c) what make for good relationship type names -- e.g., is_a_part_of v. has_part; is_subordinate_to v. type_of
d) is it common to apply attributes to relationship types? e.g., A depends on B, where an attribute of 'depends' could be 'degree' with values: critically, partially, minimally... (an example for illustration purposes only)
I have some opinions here, but it would really help if I could point to an external reference. Please let me know if you can think of anything that would be targeted to these considerations.
Many thanks!
Ruth