# What character are allowed for a IfcPropertySingleValue s name

**URL:** <https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186>\
**Category:** Uncategorized\
**Created:** [December 7, 2020, 10:11am UTC](https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186 "2020-12-07T10:11:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bernd](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@bernd](https://forums.buildingsmart.org/u/bernd)\
**Post date:** [December 7, 2020, 10:11am UTC](https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186/1 "2020-12-07T10:11:06Z")

</div>

What is according ifc standard allowed to be used as key for a pset properties?

I found …

> **[IfcPropertySingleValue](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_1/FINAL/HTML/schema/ifcpropertyresource/lexical/ifcpropertysinglevalue.htm)**

according inheritance

> **[IfcProperty](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_1/FINAL/HTML/schema/ifcpropertyresource/lexical/ifcproperty.htm)**

the name is a IfcIdentifier

> **[IfcIdentifier](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_1/FINAL/HTML/schema/ifcmeasureresource/lexical/ifcidentifier.htm)**

Which would mean a property key (Its name in IFC) could be any alphanumeric string up to 255 characters including spaces and special characters like German Umlaute ä ü ö Merely most utf-8 character can be used for the key.

Would some one confirm this?

How about practic work. Do you guys out there use special character and spaces in property keys?

cheers bernd

---

<div class="post-metadata">

**Author:** ![tim.sharrock](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@tim.sharrock](https://forums.buildingsmart.org/u/tim.sharrock)\
**Post date:** [December 11, 2020, 11:19am UTC](https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186/2 "2020-12-11T11:19:27Z")

</div>

At least one of our customers wishes to use characters with accents (for their own property set with names for the properties in French).

---

<div class="post-metadata">

**Author:** ![Moult](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/moult/32/196_2.png) [@Moult](https://forums.buildingsmart.org/u/Moult)\
**Post date:** [December 12, 2020, 6:41am UTC](https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186/3 "2020-12-12T06:41:28Z")

</div>

`IfcIdentifier` is defined as follows:

> ```
> NOTE The set of characters that may appear in STRINGs exchanged in the exchange structure as defined in ISO 10303.21 is provided in ISO 10646. The encoding of characters in case of file-based exchange is defined in ISO 10303-21 and ISO 10303-28. Among else, these specifications define the encoding of 8-bit characters from ISO 8859-1...-16 and of 2-byte and 4-byte Unicode characters from ISO 10646.
> 
> NOTE While IfcIdentifier is restricted to 255 characters, the size in exchange files after encoding may be considerably larger than 255 octets, depending on the particular encoding and on the contents of the identifier.
> 
> ```

If I view [ISO/IEC 8859-1 - Wikipedia](https://en.wikipedia.org/wiki/ISO/IEC_8859-1) - I can see that the characters “ä ü ö” are allowed.

Alphanumeric _may_ be most strictly interpreted to mean `[A-Za-z0-9]`. This may conflict with the note and disallow the accented characters. It may also disallow underscores and spaces.

Clearly, more clarity is required.

---

<div class="post-metadata">

**Author:** ![bernd](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@bernd](https://forums.buildingsmart.org/u/bernd)\
**Post date:** [December 16, 2020, 10:58am UTC](https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186/4 "2020-12-16T10:58:30Z")

</div>

> [@Moult](#):
>
> It may also disallow underscores and spaces.

This would be very important to know because both are widely used in property keys.

---

<div class="post-metadata">

**Author:** ![agron](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/agron/32/1158_2.png) [@agron](https://forums.buildingsmart.org/u/agron)\
**Post date:** [December 17, 2020, 5:09pm UTC](https://forums.buildingsmart.org/t/what-character-are-allowed-for-a-ifcpropertysinglevalue-s-name/3186/5 "2020-12-17T17:09:59Z")

</div>

I had a similiar case with the characters in another forum. It was the case of the subscribt number that is used in ISO 13501-2 for FireProtection such as:

![grafik](https://us1.discourse-cdn.com/flex016/uploads/buildingsmart1/original/2X/6/679f872a1f7239ed29756c1d4485ebb52f3c3733.png)

I saw that the IFC Structure is capable to handle such numbers. The problem sometimes appears at the BIM Tool, which is not capable to interpret these numbers correctly.
