Khronos Public Bugzilla
Bug 448 - Schema 1.5 fails xmllint 2.7.8
Schema 1.5 fails xmllint 2.7.8
Status: ASSIGNED
Product: COLLADA
Classification: Unclassified
Component: Schema
1.5.0
Macintosh Mac OS
: P3 normal
: ---
Assigned To: Fabrice Robinet
COLLADA Work Group email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-08 14:32 PST by anotherperson2011
Modified: 2014-01-07 10:23 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description anotherperson2011 2011-03-08 14:32:14 PST
On OSX 10.6.6 (all updates), using xmllint version:


xmllint --version
xmllint: using libxml version 20708
   compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ISO8859X Unicode Regexps Automata Expr Schemas Schematron Modules Debug Zlib 


Running:

xmllint --noout --schema http://www.khronos.org/files/collada_schema_1_5 duck.dae


Produces the following result:


http://www.khronos.org/files/collada_schema_1_5:864: element complexType: Schemas parser error : local list type: A type, derived by list or union, must have the simple ur-type definition as base type, not '{http://www.collada.org/2008/03/COLLADASchema}float3_type'.
http://www.khronos.org/files/collada_schema_1_5:895: element complexType: Schemas parser error : local list type: A type, derived by list or union, must have the simple ur-type definition as base type, not '{http://www.collada.org/2008/03/COLLADASchema}float3_type'.
http://www.khronos.org/files/collada_schema_1_5:9644: element complexType: Schemas parser error : local list type: A type, derived by list or union, must have the simple ur-type definition as base type, not '{http://www.collada.org/2008/03/COLLADASchema}float4_type'.
WXS schema http://www.khronos.org/files/collada_schema_1_5 failed to compile

Implying that Schema 1.5 is in some manner non-W3C conformant.

Impact:
DAE files cannot be validated until this is fixed.
Comment 1 Mark Barnes 2011-03-10 12:47:19 PST
I think this is a known bug in libxml2.

I believe the schema can be changed to work around their bug by changing those types from restrictions to extensions.