You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say I am creating a new entity. In many cases, the constructor requires the GUID of the element, which one creates by using new IfcGloballyUniqueId(). Right now, IfcGloballyUniqueId() expects the user to provide ID. However, GUIDs in the IFC schema are not anything the user like, but something that complies with this. The problem is, we can't let users fight with knowing how to correctly compress IDs to comply with the schema, it's something the same library should care about.
Proposal
Let the IfcGloballyUniqueId() to optionally accept a UUID v4. If the UUID is provided, then the class compress it based on the requirements from the schema. If the UUID is not provided, then the class creates a random GUID that is compressed based on the schema.
The text was updated successfully, but these errors were encountered:
Here, you can find a source code implementation in C but the page says the it has to be used by user responsiblity, so they show as a possible sample but it can't work in some cases.
What is your idea?
Let's say I am creating a new entity. In many cases, the constructor requires the GUID of the element, which one creates by using
new IfcGloballyUniqueId()
. Right now,IfcGloballyUniqueId()
expects the user to provide ID. However, GUIDs in the IFC schema are not anything the user like, but something that complies with this. The problem is, we can't let users fight with knowing how to correctly compress IDs to comply with the schema, it's something the same library should care about.Proposal
Let the
IfcGloballyUniqueId()
to optionally accept a UUID v4. If the UUID is provided, then the class compress it based on the requirements from the schema. If the UUID is not provided, then the class creates a random GUID that is compressed based on the schema.The text was updated successfully, but these errors were encountered: