-
```
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:i…
-
```
What steps will reproduce the problem?
1. When exporting drawings from different CAD programs (like ArchieCad) to
ifcxml the name space in the exported file is not allways like
"xmlns:ex="urn:i…
-
```
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:i…
-
```
What steps will reproduce the problem?
1. When exporting drawings from different CAD programs (like ArchieCad) to
ifcxml the name space in the exported file is not allways like
"xmlns:ex="urn:i…
-
```
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:i…
-
```
What steps will reproduce the problem?
1. When exporting drawings from different CAD programs (like ArchieCad) to
ifcxml the name space in the exported file is not allways like
"xmlns:ex="urn:i…
-
```
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:i…
-
```
What steps will reproduce the problem?
1. When exporting drawings from different CAD programs (like ArchieCad) to
ifcxml the name space in the exported file is not allways like
"xmlns:ex="urn:i…
-
```
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:i…
-
```
What steps will reproduce the problem?
1. When exporting drawings from different CAD programs (like ArchieCad) to
ifcxml the name space in the exported file is not allways like
"xmlns:ex="urn:i…