Page MenuHome

Collada Schema Violation
Confirmed, LowPublicKNOWN ISSUE


System Information
Operating system: Windows 10 64-bit
Graphics card: Nvidia GEForce GT 555M

Blender Version
Broken: v2.80
Worked: 2.78c

Short description of error
Reading a Collada file exported by Blender, Collada DOM 2.2.1 reports the following warning:

Warning: The DOM was unable to create an attribute xmlns:xsi = at line 11.
Probably a schema violation.

Exact steps for others to reproduce the error

It is related to this line in the output file:

<COLLADA xmlns="" version="1.4.1" xmlns:xsi="">

If instead we use

<COLLADA xmlns="" version="1.4.1">

there is no warning. The xmlns:xsi attribute was not included in Collada documents exported by previous versions of Blender. Looking at the Collada 1.4.1 spec it seems xmlns:xsi is not a valid attribute.

Event Timeline

Gaia Clary (gaiaclary) lowered the priority of this task from 90 to Low.Aug 23 2019, 4:51 PM


Since this is only a warning i set the priority to "confirmed, low"
Lets wait for a response from openCollada.

It is valid. xmlns is not an attribute. It just shows OpenCOLLADA is immature. Truth is, if xmlns is not implemented, then COLLADA is not really extensible, since it can't mix XML namespaces.

(I implemented this for COLLADA-DOM earlier this year. I'm right now busy trying to piece together modeling software to make use of COLLADA-DOM.)

@Mick Pearson (Mick-P) Would you mind to comment on the Issue that i set up in the openCollada project ? ( see )

After trying to make sense of all of this i wonder:

  • Should openCollada do something different during export as it does now? (what should it do then?)
  • Is it openCollada that is broken or is it the collada xml schema that is broken ?
  • or is it an issue with dom-2.2.1 that issues a warning where no warning needs to be given?
Aaron Carlisle (Blendify) changed the subtype of this task from "Report" to "Known Issue".