Skip to content
This repository has been archived by the owner on Nov 18, 2017. It is now read-only.

handling alternative namespace in ifcxml #44

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Open

handling alternative namespace in ifcxml #44

GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Some CAD programs (like ArchieCad) that export to ifcxml, don't use the 
namespace 
xmlns:ex="urn:iso.org:standard:10303:part(28):version(2):xmlschema:common"

Instead there is:

- xmlns:ex="urn:iso10303-28:ex"
or
- xmlns:doc="urn:oid:1.0.10303.28.2.1.3".


When deserializing those files you get error:
System.InvalidOperationException : There is an error in XML document (2, 2).
  ----> System.InvalidOperationException : <iso_10303_28 xmlns='urn:iso10303-28:ex'> was not expected.


If I change namespace in the file manually deserialization works fine.

Probably Ifc-DotNet lib should handle those files also.

Original issue reported on code.google.com by marjan....@gmail.com on 17 Aug 2011 at 9:23

Attachments:

@GoogleCodeExporter
Copy link
Author

Thanks for the issue report.  It would seem the other programs generate 
non-standard IfcXml.  At some point in the future Ifc-dotnet will have to 
support those, but it's a low priority at the moment.

Original comment by iainsproat on 25 May 2012 at 4:27

  • Changed state: Accepted
  • Added labels: Priority-Low, Component-IfcXml
  • Removed labels: Priority-Medium

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant