Collada Schema Violation #69025

Open
opened 2019-08-22 02:06:50 +02:00 by Robert Basler · 8 comments

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 = http://www.w3.org/2001/XMLSchema-instance 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:

If instead we use

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 http://www.khronos.org/files/collada_spec_1_4.pdf it seems xmlns:xsi is not a valid attribute.

**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 = http://www.w3.org/2001/XMLSchema-instance 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="http:*www.collada.org/2005/11/COLLADASchema" version="1.4.1" xmlns:xsi="http:*www.w3.org/2001/XMLSchema-instance"> If instead we use <COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" 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 http://www.khronos.org/files/collada_spec_1_4.pdf it seems xmlns:xsi is not a valid attribute.
Author

Added subscriber: @onemanmmo

Added subscriber: @onemanmmo
Member

Added subscribers: @GaiaClary, @lichtwerk

Added subscribers: @GaiaClary, @lichtwerk
Member
CC @GaiaClary
Member

See https://github.com/KhronosGroup/OpenCOLLADA/issues/621

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

See https://github.com/KhronosGroup/OpenCOLLADA/issues/621 Since this is only a warning i set the priority to "confirmed, low" Lets wait for a response from openCollada.

Added subscriber: @Mick-P-2

Added subscriber: @Mick-P-2

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.)

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.)
Member

@Mick-P-2 Would you mind to comment on the Issue that i set up in the openCollada project ? ( see https://github.com/KhronosGroup/OpenCOLLADA/issues/621 )

@Mick-P-2 Would you mind to comment on the Issue that i set up in the openCollada project ? ( see https://github.com/KhronosGroup/OpenCOLLADA/issues/621 )
Member

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?
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?
Philipp Oeser removed the
Interest
Pipeline, Assets & IO
label 2023-02-10 08:54:21 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#69025
No description provided.