Relation structure of concepts within a collection. Allows for the specification of complex relationships among concepts.
The ConceptRelationStructure employs a set of ConceptRelations to describe the relationship among concepts. Each ConceptRelation is a one to many description of connections between concepts. Together they can describe relationships as complex as a hierarchy or even a complete cyclical network as in a concept map.
Name | Cardinality | Datatype | Description |
---|---|---|---|
hasRelationSpecification | 1..1 | Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list. Use if all relations within this relation structure are of the same specification. | |
semantic | 0..1 | Provides semantic context for the relationship | |
totality | 0..1 | Type of relation in terms of totality with respect to an associated collection. | |
hasMemberRelation | 0..n | Restricted to ConceptRelation. ConceptRelations making up the relation structure. |
Name | Target Object | Description | Source cardinality | Target cardinality | Relationship type |
---|---|---|---|---|---|
realizes | Collection pattern class realized by this class | 0..n | 0..1 | Neither |
Comments
wendy
Tue, 12/15/2015 - 15:40
Permalink
adding ext base annotated identifiable
On Tue, Dec 15, 2015 at 7:57 AM, Flavio Rizzolo wrote:
I think the only ones that extend Identifiable are the pairs, e.g.ParentChildPair, etc. That's because they are simple objects that would be to heavy to annotate. As far as I know, all others should extend AnnotatedIdentifiable, including ConceptParentChild.
On Mon, Dec 14, 2015 at 3:07 PM, Wendy Thomas wrote:
In reviewing conceptual I noted that ConceptSystem has a relationship to ConceptParentChild. This in itself has no extension base and no identification. Should ConceptParentChild have an extension base of Identifiable or AnnotatedIdentifiable???