This use case describes the need to manage information that varies over time. Various solutions can be proposed, as explicit time stamps on properties to solution completely outside the standard (using a versioning system)

In fact, we had something in GeoSciML called "estimated property" stereotype. The idea behind this was to tie any property to "supporting observations". O&M actually says that observedProperty of Observation shall be an existing property of the feature of interest (either directly or through a sampling feature). If we could figure a way to couple Observation and properties, we can use Observation phenomenonTime, resultTime and validTime to handle this issue.

see: https://www.seegrid.csiro.au/wiki/CGIModel/EstimatedPropertyDiscussion

• allow users to get previous values for properties

There are no specific vocabulary. -> it sounds more a technological/implementation issue than a modelling one. we propose to use existing versioning system to address that