Please register your attendance, by 21 February, via Doodle:
*** Please note that vendors should plan on sending no more than two (2) representatives, to help with keeping attendance manageable for hosts. This is ISG policy.
Please note that I’ve added agenda information to the original post. This will be a very proactive discussion regarding improving implementation of the next version of IFC. Input/feedback from the current ISG members is crucial.
Thank you @jwouellette for sharing the agenda.
Do you have a more detailed view. For instance, how days will be organized ? Can ISG members come to all the topics or some are dedicated only to bSI members ?
@kevin.nahaboo at this point, the proposed agenda is set up to start at the top and work our way through. From past experience, We get through the updates pretty quickly… maybe 1/2 day?. We really need to dive into the meat of IFC5, this time around. Too many people leave early on Friday to catch flights home before the weekend. Attendance starts to suffer Friday after lunch.
@RustlerW I think theses components could be part of the discussion, if you feel there are needs for improvement. Please write down your ideas and let’s discuss!
@r.polasek ok, Roman. But please forward ideas from SCIA on ways we could make improvements to the schema. Try to be more specific than we were in Prague. We want to get into real solutions for making IFC5 easier to implement for every domain and possible software.
In the evolution of IFC, it is time to work towards a technology independent data schema. This is also the time to improve consistency and remove redundancy. Therefore we started collecting issues on the GitHub issue list.