Jeffrey W. Ouellette

Ooof. Mirroring seems to be such a major pain to handle correctly. From my perspective, it's an end user convenience/shortcut to duplicate things graphically, but ends up being a total...

How about making it optional at the file header level for supporting (legacy) file-based workflows and deprecating it for class/object-based level, which can be handled by a CDE when we...

Maybe this leads to rules of usage based on serialization type? And these rules are related to, but not ensconced in, the schema.

How would this affect efforts to pass enough parametric data for enhanced object translation (design transfer)?

@TLiebich the "naming/ID" of things could be an explicit issue itself. As you point out, there are multiple methods to identifying a single object by some kind of 1. instance...

Ryan, There are so many issues wrapped up in this it may take a bit to unravel. FIRST: Round-tripping? Everyone talks about this being "ideal", but I still don't see...

SECOND: It appears that you are confusing the concepts of software conveniences with a data model to represent a building. At the same time, you are failing to recognize the...

THIRD: IfcGroup, by specification, is an arbitrary assignment of a "logical collection of objects". An IfcGroup could define a collection of furniture or casework for a housing unit, or a...

FINALLY: The software vendors have come a LONG way in the last year to support IFC-based workflows through the buildingSMART International Certification 2.0 process. These results have been worked out...

I'm not sure I understand the reasons all this work was done by the researchers. The problem is solved with the proper implementation of [IfcTypeObject](http://www.buildingsmart-tech.org/ifc/IFC4/Add2/html/schema/ifckernel/lexical/ifctypeobject.htm). As mentioned before, this was...