# Pset\_\* and their property renamings

**URL:** <https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051>\
**Category:** Developers\
**Tags:** ifc4x3\
**Created:** [November 24, 2023, 1:52pm UTC](https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051 "2023-11-24T13:52:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastian](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@Sebastian](https://forums.buildingsmart.org/u/Sebastian)\
**Post date:** [November 24, 2023, 1:52pm UTC](https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051/1 "2023-11-24T13:52:13Z")

</div>

There are a lot of renamings for ifc-defined dynamic property sets, both in the property set names and the properties themselves.

E.g. Ifc4 Add2 Tc1 : Pset\_BuildingElementProxyProvisionForVoid : Shape maps onto Ifc4x3 Add2 : Pset\_ProvisionForVoid : VoidShape.

For developers, it’s very time consuming to figure this out. Can you provide a complete map of these renamings?

On importing an Ifc4 file in an Ifc4x3 program and exporting it as an Ifc4x3 file, all these renamings need to happen (automagically).

---

<div class="post-metadata">

**Author:** ![daviddelven](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/daviddelven/32/2384_2.png) [@daviddelven](https://forums.buildingsmart.org/u/daviddelven)\
**Post date:** [December 4, 2023, 9:17am UTC](https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051/2 "2023-12-04T09:17:02Z")

</div>

Many of those renamings come from the changes applied from one IFC Schema version to the next. You can always check the [Annex F ChangeLog](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/annex-f.html). As you probably know, there are different types of version changes according to the model below:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/buildingsmart1/original/2X/2/2fcb8fe555b938695acfbb9fd36ff4944e45b3aa.png)

---

<div class="post-metadata">

**Author:** ![Sebastian](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@Sebastian](https://forums.buildingsmart.org/u/Sebastian)\
**Post date:** [December 5, 2023, 7:55am UTC](https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051/3 "2023-12-05T07:55:53Z")

</div>

Thank you for your answer.

It’s not really useful…

- Obvious property renamings aren’t linked (e.g. Pset\_ActuatorPHistory: Position =\> PositionHistory).
- The generalization of e.g. Pset\_BuildingElementProxyProvisionForVoid to e.g. Pset\_ProvisionForVoid is also not linked.

---

<div class="post-metadata">

**Author:** ![daviddelven](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/daviddelven/32/2384_2.png) [@daviddelven](https://forums.buildingsmart.org/u/daviddelven)\
**Post date:** [December 22, 2023, 3:05pm UTC](https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051/4 "2023-12-22T15:05:36Z")

</div>

Maybe @aothms can help in that regard.

---

<div class="post-metadata">

**Author:** ![aothms](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@aothms](https://forums.buildingsmart.org/u/aothms)\
**Post date:** [December 22, 2023, 6:40pm UTC](https://forums.buildingsmart.org/t/pset-and-their-property-renamings/5051/5 "2023-12-22T18:40:36Z")

</div>

We don’t have a complete map. We’re talking about changes occurring over a 10y time frame and we frankly just didn’t set that high of a standard in terms of psets, as compatibility for these was considered a secondary concern.

> For developers, it’s very time consuming to figure this out. Can you provide a complete map of these renamings?

I agree. I know the blenderbim crew also maintains migration scripts around (maybe only schema). Maybe as a community we can work on this together in the form of a light weight json structure.