Change in my email address

This information should be considered when using XMLSpy 2005 for complex
schema design. I have noticed that XML schemas that contain multiple
includes/imports are being validated differently in XMLSpy 2004/2005 and
their respective views. Here are a few answers from the Altova support team
that may clarify things. I have made it a practice to validate schemas in
the text view as well as use external parsers to assess possible errors and
interpretations.

----- Forwarded by Michael Roytman/Construction/Vertexinc on 01/21/2005
10:58 AM -----
|---------+---------------------------->
|         |           "Altova Support |
|         |           Team"            |
|         |           <support@altova.c|
|         |           om>              |
|         |                            |
|         |           01/21/2005 10:32 |
|         |           AM               |
|         |                            |
|---------+---------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|                                                                                                                               |
|       To:       <michael.roytman@vertexinc.com>                                                                               |
|       cc:                                                                                                                     |
|       Subject: RE: Schema validation error[ALTOVA Case # 13006]                                                              |
>-------------------------------------------------------------------------------------------------------------------------------|

Dear Michael,

                         XML Spy includes two validators. There is a
partial
validator implementation for the schema design view and a separate
validator for the grid and text view. As of version 2005 the text and
grid view validator implementation is new and more accurate (according
to the specifications) than the text and grid view validator
implementation available in earlier versions of Spy.

The error message that is shown when validating CoRApplication.xml
refers to the reference 'ContactNumber' in CoRApplication.xsd i.e.
cannot resolve declaration or definition "Contact Number" in namespace
urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0. This error message is in
fact correct as it would be necessary to directly import the xCIL.xsd
schema directly into CoRApplication.xsd. According to the
specifications it is not valid to indirectly reference an element from
another namespace.

             <xsd:import
namespace="urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0"
schemaLocation="..\ciq\2.0\xCIL.xsd"/>

The fact that the schema design view has not picked up on this is indeed
a bug and has now been submitted to our internal bug databse for our
developers to take a look at. # 8716

With regard to the validation speed: which schema are you validating and
generating documentation from and what are you generating, Word or HTML?

Thank you kindly.

Best Regards,

... Christian Luntzer
... Support Manager
... Altova GmbH

===================================================================
Altova(r) accelerates development and integration projects with soft-
ware, services and solutions that enhance productivity and maximize
results. Uncover why Altova is the smart choice of over 1.5 million
applications developers worldwide! Look into www.altova.com today!
XMLSpy(r) 2005 - MapForce(tm) 2005 - StyleVision(r) 2005 - Authentic(r)
2005
NEW: Advanced standards compliance, XSLT 2.0, XPath 2.0, XQuery 1.0
SchemaAgent, Eclipse integration, Visual function builder, Word/RTF
output, database-enabled electronic forms, XML<->flat-file mapping
===================================================================

The information transmitted in this message and/or as an attachment
to it is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. Altova GmbH and Altova, Inc. do not
accept legal responsibility for the contents of this message. Any
views or opinions presented are solely those of the author and do
not necessarily represent those of Altova GmbH and Altova, Inc.
unless otherwise specifically stated. Thank you!

-----Original Message-----
From: michael.roytman@vertexinc.com
[mailto:michael.roytman@vertexinc.com]
Sent: 14 January 2005 14:02
To: Altova Support Team
Subject: Schema validation error[ALTOVA Case # 13006]

Case Number:13006

===============================================================
                               Equipment Information

===============================================================
Operating System: Windows 2000
OS Service Pack: SP4
OS Language: English
CPU Speed: 1.6G Intel M
Ram: 1GB
IE Version: 6.0
IE service Pack: Latest
Office Version: 2000 (9.0.6926)
Office Language: English
Office Service Pack: SP-3

===============================================================
                                 Product Information

===============================================================
Product: XMLSpy Enterprise Edition
Component:
Version: 2005sp1

===============================================================
                                 Support Request

===============================================================
Summary:
Schema validation error

Description:
Validation of an element that is referenced from an imported schema
validates in XML Schema view but fails in the text or grid view. The
error occurs sporatically, since multiple elements are referenced and
only one fails. Works fine in XMLSpy 2004. Also, same schema, which is
very complex takes too much time to validate. The documentation
generation crashes the system with 1GB of RAM.

Any plans to clean up the application or should I revert to using the
XMLSpy 2004.

Thanks.

Steps to Reproduce:
Please open the CoRApplication.xml which fails validation pointing to
the CoRApplicaiton.xsd CoRApplication.xsd validates in Schema view but
does not in Text/Grid.

There are references to the declarations in the imported schemas.

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ciq/members/leave_workgroup.php.

ciq message