Problems: * the pattern has no dependencies, whereas it seems to have strong ties with catalogued patterns such as Situation (of which it seems to be a suitable extension) and Parameter;
the partitioning of states, objects with states, and their resulting properties, into exactly three items is hardwired in the ontology itself. As it is used to exemplify its usage, it should not appear in the core ontology.
Clear Relevance and Consequences: The requirement of modeling states as individuals is a significant example of conformance to best practices.
The current ODP has a strict limitation to tripartite states - if this is not relaxed, it should be mentioned in the consequences.
Clear Figures and Illustrations: Figure is clear, but if possible please use arrows with no fill for subclasses.
As it is meant to represent a usage schema, it is okay to retain the tripartition of Object and State in the figure. Maybe it could be made as State1, State2, ... StateN and the like
Missing Information: The link to the example usage in Known Usage should appear in the field "Examples (OWL files)".
Other than that, missing information is a consequence of the pattern not having been related to other ODPs.
'Ontology Design Patterns'