Commons is missing a class representing a simple ordered list of items. The class StructuredCollections:List is far too heavyweight for general use:
Each member must be an IndexedConstituent which in turn must have a value for comprises which is an IndexValue defined in an IndexingScheme and only that actually refersTo a nonNegativeInteger.
      myList a :List ;
      :hasMember [
            a :IndexedConstituent ;
:comprises [
a :IndexValue ;
:characterizes <member1> ;
:isDefinedIn :myScheme ;
:refersTo ??;
:hasNumericValue 1
]
           ] ,    
           a :ListMember ;
            :refersTo <member3> ;   
            :hasSequence 3 ;
           ] ,    
           a :ListMember ;
            :refersTo <member2> ;   
            :hasSequence 2 ;
           ]    
.
That might represent a StructuredElementList but for a basic list one would only need one class and two properties - something like:
      myList a :List ;
      :hasMember [
            a :ListMember ;
            :refersTo <member1> ;   
            :hasSequence 1 ;
           ] ,    
           a :ListMember ;
            :refersTo <member3> ;   
            :hasSequence 3 ;
           ] ,    
           a :ListMember ;
            :refersTo <member2> ;   
            :hasSequence 2 ;
           ]    
.

The class ChronologicallyOrderedCollection is unclear when it says "structured collection whose elements are ordered by time", since the elements are more than simple (time) values but individuals with potentially many properties which are time-related. Even for the example given of bank transactions there's often a difference between the time the transaction happened and when it was recorded: my credit card statement has both "Post Date" and "Trans Date" - with the statement ordered by Post Date. And in some cases the time-related property might be on a separate linked individual. For some cases it could get a lot more complex e.g. employment for a person - there might be period overlaps.
Even ChronologicallyOrderedConstituent does not help - it seems to select only hasObservedDateTime which is both over-specific (how does it help with Employment?) and still under-specified (since hasObservedDateTime is itself pretty vague "indicates a date and time associated with an event, measurement, record, or observation" which does not discriminate the above examples or help with Employment).

Wrong property used for collection members in restrictions on List and ChronologicallyOrderedCollection.
These make use of hasConstituent but this is disjoint with hasMember and it says "This property is disjoint with hasMember, and should be used in cases where the constituents of something are not considered discrete elements of whatever they are included in, such as a substance or composite."

Ontology StructuredCollections adds properties to Constituent which tend to add confusion rather than value. Specifically it adds a synonym "element" with explanation "an element is part of a set..." yet a set is by definition unstructured - the opposite the whole purpose of the ontology which is structured collections

It's counterintuitive that the class StructuredCollection is not in the ontology StructuredCollections. It breaks the naming pattern that an ontology is named after its principle class.

The definition of List includes "set of related items"

There is a gap in the quantities and units ontology whereby we cannot represent counts of things, which do not necessarily have units, nor can we properly represent ratio values, which may involve scalar quantity values that do not have units. There is also a challenge in representing ratio values more generally, since there is no numeric value representing the ratio on the class.

This is needed for representation of tensor and vector quantities for the quantities and units ontology, and for representation of certain machine learning algorithms, among other requirements.