<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Open Design Alliance Releases new IFC Software Development Kit (SDK)	</title>
	<atom:link href="https://architosh.com/2019/07/open-design-alliance-releases-new-ifc-software-development-kit-sdk/feed/" rel="self" type="application/rss+xml" />
	<link>https://architosh.com/2019/07/open-design-alliance-releases-new-ifc-software-development-kit-sdk/</link>
	<description>architosh™ — a global-leading CAD / 3D / AEC industry technology publication and #1 source for Mac and iOS users in these segments.</description>
	<lastBuildDate>Mon, 29 Jul 2019 08:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: stefkeb		</title>
		<link>https://architosh.com/2019/07/open-design-alliance-releases-new-ifc-software-development-kit-sdk/#comment-55725</link>

		<dc:creator><![CDATA[stefkeb]]></dc:creator>
		<pubDate>Mon, 29 Jul 2019 08:08:00 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=27872#comment-55725</guid>

					<description><![CDATA[The advantage of having an open standard: everybody can implement support for it in their software tools. The disadvantage? Everybody does it in a particular way... E.g. Right now, we have IFCs coming from ARCHICAD or Revit which both use the same EDM toolkit but with widely different IFCs. Compare that with the IFCs generated by Vectorworks, Allplan, Tekla, Bentley etc... Even when they all are IFC2x3 certified and the first IFC4 certifications are around the corner or have been released (in the case of Vectorworks).

As every system is mapping the IFC schema to an internal (closed) format you still get very different outcomes.

Solibri is using their own libraries (I think) and they look differently at IFC as Tekla BIMsight, Navisworks, SimpleBIM, BIMvision, FZK Viewer.
There are the toolkits such as IfcOpenShell, IfcPlusPlus, GeometryGym, IfcEngine, XBIM, BIMserver.org ...
There are multiple other platforms, including the CDEs and online IFC viewers, which often parse the IFC using one of these toolkits and turn the IFC into a geometry model and some kind of list or tree of properties.

At the same time, buildingSMART has announced that they will also release some kind of reference implementation, but in the past shared examples using IfcEngine and GeometryGym libraries. 

ODA has a good reputation for their DWG libraries and are a capable player, but it is very early to think that all of a sudden software vendors will adopt their libraries.

And even then, I don&#039;t see how e.g. Revit and ARCHICAD would have &quot;better&quot; IFC support comparing to the current toolkit they are using right now.

To me it is yet another IFC toolkit, with its own merits and probably idiosyncrasies...]]></description>
			<content:encoded><![CDATA[<p>The advantage of having an open standard: everybody can implement support for it in their software tools. The disadvantage? Everybody does it in a particular way&#8230; E.g. Right now, we have IFCs coming from ARCHICAD or Revit which both use the same EDM toolkit but with widely different IFCs. Compare that with the IFCs generated by Vectorworks, Allplan, Tekla, Bentley etc&#8230; Even when they all are IFC2x3 certified and the first IFC4 certifications are around the corner or have been released (in the case of Vectorworks).</p>
<p>As every system is mapping the IFC schema to an internal (closed) format you still get very different outcomes.</p>
<p>Solibri is using their own libraries (I think) and they look differently at IFC as Tekla BIMsight, Navisworks, SimpleBIM, BIMvision, FZK Viewer.<br />
There are the toolkits such as IfcOpenShell, IfcPlusPlus, GeometryGym, IfcEngine, XBIM, BIMserver.org &#8230;<br />
There are multiple other platforms, including the CDEs and online IFC viewers, which often parse the IFC using one of these toolkits and turn the IFC into a geometry model and some kind of list or tree of properties.</p>
<p>At the same time, buildingSMART has announced that they will also release some kind of reference implementation, but in the past shared examples using IfcEngine and GeometryGym libraries. </p>
<p>ODA has a good reputation for their DWG libraries and are a capable player, but it is very early to think that all of a sudden software vendors will adopt their libraries.</p>
<p>And even then, I don&#8217;t see how e.g. Revit and ARCHICAD would have &#8220;better&#8221; IFC support comparing to the current toolkit they are using right now.</p>
<p>To me it is yet another IFC toolkit, with its own merits and probably idiosyncrasies&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: stefkeb		</title>
		<link>https://architosh.com/2019/07/open-design-alliance-releases-new-ifc-software-development-kit-sdk/#comment-58159</link>

		<dc:creator><![CDATA[stefkeb]]></dc:creator>
		<pubDate>Mon, 29 Jul 2019 04:08:00 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=27872#comment-58159</guid>

					<description><![CDATA[The advantage of having an open standard: everybody can implement support for it in their software tools. The disadvantage? Everybody does it in a particular way... E.g. Right now, we have IFCs coming from ARCHICAD or Revit which both use the same EDM toolkit but with widely different IFCs. Compare that with the IFCs generated by Vectorworks, Allplan, Tekla, Bentley etc... Even when they all are IFC2x3 certified and the first IFC4 certifications are around the corner or have been released (in the case of Vectorworks).

As every system is mapping the IFC schema to an internal (closed) format you still get very different outcomes.

Solibri is using their own libraries (I think) and they look differently at IFC as Tekla BIMsight, Navisworks, SimpleBIM, BIMvision, FZK Viewer.
There are the toolkits such as IfcOpenShell, IfcPlusPlus, GeometryGym, IfcEngine, XBIM, BIMserver.org ...
There are multiple other platforms, including the CDEs and online IFC viewers, which often parse the IFC using one of these toolkits and turn the IFC into a geometry model and some kind of list or tree of properties.

At the same time, buildingSMART has announced that they will also release some kind of reference implementation, but in the past shared examples using IfcEngine and GeometryGym libraries. 

ODA has a good reputation for their DWG libraries and are a capable player, but it is very early to think that all of a sudden software vendors will adopt their libraries.

And even then, I don&#039;t see how e.g. Revit and ARCHICAD would have &quot;better&quot; IFC support comparing to the current toolkit they are using right now.

To me it is yet another IFC toolkit, with its own merits and probably idiosyncrasies...]]></description>
			<content:encoded><![CDATA[<p>The advantage of having an open standard: everybody can implement support for it in their software tools. The disadvantage? Everybody does it in a particular way&#8230; E.g. Right now, we have IFCs coming from ARCHICAD or Revit which both use the same EDM toolkit but with widely different IFCs. Compare that with the IFCs generated by Vectorworks, Allplan, Tekla, Bentley etc&#8230; Even when they all are IFC2x3 certified and the first IFC4 certifications are around the corner or have been released (in the case of Vectorworks).</p>
<p>As every system is mapping the IFC schema to an internal (closed) format you still get very different outcomes.</p>
<p>Solibri is using their own libraries (I think) and they look differently at IFC as Tekla BIMsight, Navisworks, SimpleBIM, BIMvision, FZK Viewer.<br />
There are the toolkits such as IfcOpenShell, IfcPlusPlus, GeometryGym, IfcEngine, XBIM, BIMserver.org &#8230;<br />
There are multiple other platforms, including the CDEs and online IFC viewers, which often parse the IFC using one of these toolkits and turn the IFC into a geometry model and some kind of list or tree of properties.</p>
<p>At the same time, buildingSMART has announced that they will also release some kind of reference implementation, but in the past shared examples using IfcEngine and GeometryGym libraries. </p>
<p>ODA has a good reputation for their DWG libraries and are a capable player, but it is very early to think that all of a sudden software vendors will adopt their libraries.</p>
<p>And even then, I don&#8217;t see how e.g. Revit and ARCHICAD would have &#8220;better&#8221; IFC support comparing to the current toolkit they are using right now.</p>
<p>To me it is yet another IFC toolkit, with its own merits and probably idiosyncrasies&#8230;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
