Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: xsd substitution groups weird problem

From: sreedevi crk <sreedevi_crk@-----.--->
To: Kasimier Buchcik <K.Buchcik@---------.-->
Date: 11/19/2005 1:59:00 PM
Hi
   
  I had no luck using your codebase with xmlspy and stylus(I am using thier latest versions/validators).
   
  Please let me know the tool name that you used to test your codebase.I would like to try using the same tool.
   
  Please let me know since I am new to xml/xsd, I am trying to understand your advice from the previous email -
" In "Participation.xsd":
  - Removed the declaration of the element "signatureString" and
    imported it from an additional schema with no targetNamespace".
  I am curious to know as how it helped to solve the problem - is it the chameleon namespace design pattern? 
   
  Also I think you are right that there could be bug in xmlspy/stylus while generating the original instance document -
After rereading "Schema definitive guide" book regarding substitution groups and its two alternatives(choice groups, type substitution) - In my example xsds, though, I used SUBSTITUTION GROUPS(more than one level deep),  the generated instance document treates it as TYPE SUBSTITUION  since it has entry for xsi:type and expects user to fill in the type. This happens only in case IMPORT statement usages instead of  INCLUDE statement usuage. 
   
  Your help and time in this regard is highly appreciated.
   
  Thanks in advance.
   
  Regards,
Sreedevi.

Kasimier Buchcik <K.Buchcik@4...> wrote:
  Hi,

On Thu, 2005-11-17 at 11:35 -0800, sreedevi crk wrote:
> Hi
> 
> I have errors while validating your modified xsds that you listed in
> your reply. It happens both in XMLSpy & Stylus. Please help. 
> Meanwhile I will try using w3c xsd validator to double check the
> validity of my original xsd files posted in this forum. 
> 
> Following are the errors I was getting in your modified xsds:
> Error for Particiaption.xsd:
> 
> file:///c:/VHIM3200/Datatypes3203/RDT/Participation-B.xsd:14,53:
> Schema Representation Constraint: Namespace 'Participation' is
> referenced without declaration
> file:///c:/sree/VHIM3200/Datatypes3203/RDT/Participation-B.xsd:10,52:
> Schema Representation Constraint: Namespace 'Participation' is
> referenced without declaration

Unlikely; if you look at "Participation-B.xsd" you'll find:



> Error For Participation-B.xsd:
> Validating Participation-B.xsd...
> file:///c:/VHIM3200/Datatypes3203/RDT/Participation-B.xsd:8,45: The
> namespace of an element must be different from the
> targetNamespace of the ing schema
> file:///c:/sree/VHIM3200/Datatypes3203/RDT/Participation-B.xsd:15,53:
> Schema Representation Constraint: Namespace 'Participation' is
> referenced without declaration
> file:///c:/sree/VHIM3200/Datatypes3203/RDT/Participation-B.xsd:11,52:
> Schema Representation Constraint: Namespace 'Participation' is
> referenced without declaration
> The XML document Participation-B.xsd is NOT valid (3 errors)

[...]

It looks more like those schema processors you used are not able
to handle the imports. If you use the Stylus Studio as I know it, then
you'll find an arrow-button to the right side of the "Validate Document"
button, pressing this button will pop-up a list of custom schema
validation engines. Try to validate the scenario with those and if
it still fails, then please report those validators together with 
their version numbers - your validators might be outdated.

Additionally (but unlikely) it may be that my mail didn't come
through correctly to you, so try to compare the scenario on your side
with the archived version of my mail at:
http://lists.w3.org/Archives/Public/xmlschema-dev/2005Nov/0042.html

Regards,

Kasimier
  


		
---------------------------------
 Yahoo! FareChase - Search multiple travel sites in one click.  


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent