StructuredCollection

Version: 
1
Is Abstract: 
yes
Is Pattern: 
yes
Definition: 

Structured Collection container extends a Simple Collection allowing it to optionally have an RelationshpStructure to model hierarchies and nesting or more complex network structures. Like Simple Collection it is also a subtype of Member to allow for nested collections. A Collection can be described directly as having unordered members or an indexed array of members through a set of MemberIndicators.

Explanatory Notes: 

Members have to belong to some Collection, except in the case of nested Collections where the top level Collection is a Member that doesn't belong to any Collection.
If a Collection is ordered as a simple list that ordering can be indicated by an index property of each MemberIndicator. If the Collection is unordered, the index is not necessary.
Collection is not extended, it is realized (see Collection Pattern documentation).

Example: 
Node Sets, Schemes, Groups, Concept Systems are all types of Collections.
Property: 
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
isStructuredBy
A relation structure that provides complex organization of the collection
0..n
0..n
Neither

Stage:

Is extendable: 
GSIM: 
Node Set
Is property: 
0
RDF Mapping: 

Comments

doesn't this imply that anything you want to be able to create a "collection" of would have to have the extension base Member rather than AnnotatedIdentifiable. My point here is not that this is wrong but that modelers need to be aware of this so that any object that can be grouped should have the extension base Member

We are using Collections as a pattern to avoid multiple inheritance, in which case objects in a Collection won't have to be extensions of Member.

But to match the pattern must it be an AnnotatedIdentifiable? Or could it just be Identifiable??