Instructions, Annotations, Translations & Co

We generate _IDS_ files from user models mapped to _IFC_. In a user model a lot of definitions are possible, such as description for the object class (entity) and attributes. The object class names, attribute names or enumeration values etc. are proper names in the user context language.

Few _IDS XML_ elements have the `instructions` attribute, so in our _IDS_ export we put a lot of this information in `annotations` elements. The receiving side could use this information to configure their application (tooltips, label translation etc.). But in the form of `annotations` elements, the information is unstructured. E.g. the receiving side can’t distinguish between an information describing an object class (entity) and a translation for the object class name.

An _IDS_ example from our export below.

I'm looking for ways _IDS_ can provide more guidance to structure such information. Any ideas or proposals?

```

DBM für Betriebsphase aufbereiten
FHNW
IDS 0.9.3
DBM für Betriebsphase aufbereiten
Author sample@sample.ch
2023-03-13
FDK
Projekt abgeschlossen







Identifkation: FB-1
Art der Verortung: Linear, Linie
eBKP-Zuweisung: Zuweisung offen
LOGO-Klasse: Schicht

IFCBUILDINGELEMENTPROXY


USERDEFINED






CHTBAZH_Oberbau


Bindemitteltyp



Bindemitteltyp




? Unbekannt




B 100/150




B 120/150




B 20/30




B 40/50




B 50/70




B 55/70




B 70/100




B 80/100




Bitumen




Emulsion




HB Hartbitumen




hydraulischer Kalk




PmB-E 10/30-70 (CH-E)




PmB-E 30/50-65 (CH-E)




PmB-E 50/70-65 (CH-E)




PmB 10/40 (CH-E)




PmB 25/55 (CH-E)




PmB 30/50-65 (CH-E)




PmB 45/80 (CH-E)




PmB 65/105 (CH-E)




PmB Polymodifizierte Bindelmittel (alt)




PmB Polymodifizierte Bindemittel




Spez NV




Zement

```