Game Development Reference
In-Depth Information
The error is now clear, the
instance_camera
element is referencing (using #)
the
cameraShape1
element. An element with the id=”cameraShape1” is found, but
it is
cam
, and not
camera
. The coherency test verifies that an element with the
right id exists, and also that it is of the right type where it is referenced in the
document. Renaming the element from
cam
to
camera
will simultaneously fix the
two first errors returned by the coherency test.
The last error returned by the coherency test on the
duck-err2.dae
is related
to external references. It is telling us that it cannot find the ducky.tga image used
for a texture.
9.6 Patching XML Notepad
Microsoft XML implementation has a well-known bug that at the time of this
writing has not been fixed [Microsoft 07b]. Basically the schema validation does
not implement the
<xs:import
statement as used by the COLLADA schema. This
error is specific to .NET, other XML implementations don't seem to have this
problem.
Here is an extract from
collada_schema_1_4.xsd
:
<!
-- import needed for xml:base attribute--
>
< xs:import namespace="
http: // www . w3 . org / XML /1998/ namespace
"
schemaLocation=
"
http: // www . w3 . org /2001/03/xml. xsd
"
/ >
As a result, XML Notepad fails to validate the COLLADA document, even
though the
http://www.khronos.org/files/collada schema 1 4
is entered in the
schema's list (see
Figure 9.9
)
.
Figure 9.9.
Setting XML namespace in XML Notepad.
