Collection type [Bag | Set] organizationalApproach [Vertical | Horizontal] (depth | breadth) name purpose contains List 0..n haslistRelation ListRelation 0..n List (extension base=Member) reflexivity=ReflexivityType symmetry=SymmetryType transitivity=TranstiveType totality=TotalityType semantic=ECVE subtype StrictOrderList (ext base=List) reflexivity=Anti_Reflexive symmetry=Anti_Semetric transitivity=Transitive criteria=InternationalStructuredString contains ListItem orderNumber xs:decimal Item Member UnorderedList (ext base=List) reflexivity=Reflexive symmetry=Symmetric transitivity=Trasitive contains Member ListRelation (note that a binary relation contains members that are not lists, tuples contain one or members that are lists) reflexivity=ReflexivityType symmetry=SymmetryType transitivity=TranstiveType totality=TotalityType semantic=ECVE contains OrderedPair source Member target Member subtype ImmediatePrecedentRelation (Hierarchy, ParentChild) reflexivity=Anti_Reflexive symmetry=Anti_Symmetric transitivity=Anti_Transitive OrderRelation (Parative, WholePart) reflexivity=Reflexive symmetry=Anti_Semetric transitivity=Transitive criteria=InternationalStructuredString AcyclicPrecedenceRelation reflexivity=Anti-Reflexive symmetry=Anti_Semetric transitivity=Neither REALIZATION (by realizing the abstract extension base for list and listRelation the number of needed subtypes can be recorded, added to or constrained to as appropriate. An xxxCollection can contain any number of lists or listRelations needed for the applied use.) xxxCollection xxxList (abstract) As Needed: xxxUnorderedList (ext base xxxList) xxxStrictOrderList (ext base xxxList) xxxListRelation (abstract) As Needed: xxxHierarchy | ParentChild Relation (ext base xxxListRelation) xxxParative | WholePart Relation (ext base xxxListRelation) xxxAcyclicPrcedenceRelation (ext base xxxListRelation) QUESTION: Regarding Levels: If a list has a definingConcept 0..1 does this address the ability to define the meaning of the level?