IfcOwnerHistory per property

[Wilt]

I see a problem with the current versions of IFC where IfcOwnerHistory is linked to a PropertySet and not to the individual underlying properties inside the set.
This would be less of a problem if properties would be grouped in sets that apply only to a certain discipline (fire consultant, architect, structural engineer). But for example the common PropertySets (i.e. Pset_DoorCommon) mix properties of different disciplines like FireRating and AcousticRating. Would be very valuable in my opinion if we could track change history of these properties individually.

Has it been considered to look at this in IFC5?

[aothms]

I would tentatively say that tracking owner history becomes less of a schema construct and more something that resides in layer meta-data, non-destructive editing and composition workflows.

In IFC5 (inspired by USD) people would work in their own layers, which can be composed in the receiving applications. The viewer harmonises the opinions in these layers and can show where (which layer, with which meta-data/author) certain opinions (e.g properties/attributes) come from, whether there are conflicts, etc.

[berlotti]

yes, history is done in a system. The timestamps/versions in the data can be used to generate the history.