HerbertDobernig

@janbrouwer Thx for providing the reference to the OPM discussion. For efficient change tracking ("audit trail") by L3-CDEs there is the need "to track changes on attribute values AND properties"...

From CDE to authoring-software (checkout): #101= IFCOWNERHISTORY(#22,#7,.READWRITE,$,$,$,$,1574162571); #102= IFCOWNERHISTORY(#22,#7,.READONLY,$,$,$,$,1574162571); All elements referencing #101 are editable in authoring-software All elements referencing #102 are NOT editable in authoring-software (e.g. indicated by color...

From authoring-software to CDE (at checkin): #101= IFCOWNERHISTORY(#22,#7,$,.MODIFIED,'2020-05-01','user1234','authSwXy',1574162571); #102= IFCOWNERHISTORY(#22,#7,$,.ADDED,$,$,$,1574162571); #103= IFCOWNERHISTORY(#22,#7,$,.DELETED,$,$,$,1574162571); All elements referencing #101 have been modified in authoring-software since last checkout from CDE All elements referencing #102...

@Moult: Tracking changes (maintaining history) is the responsibility of CDE. IfcOwnerHistory (misleading name) provides attributes to ease transactional exchange between CDE and authoring software as described above. If we deprecate...