IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

XML Schema is valid or invalid depending on view in XMLSpy Options · View
gabrieleneumann
Posted: Wednesday, November 16, 2005 10:33:00 AM
Rank: Member

Joined: 11/22/2005
Posts: 2
Location: DE
Hi everybody,
I´m using XMLSpy 2006sp1 and it acts strangely with one particular XML Schema (this one):

- in Schema/WSDL Design view the file is valid
- in text view and in grid view it is invalid:

[red]This schema doesn´t appear to be valid by itself (as a part of another schema, it might still be OK): Type definition "local_header-cont.model" does not exist in the redefined schema with target namespace "urn::hl7-org/cda"[/red]

In Schema/WSDL Design view the redefined complexType does exist!

Shouldn´t this defect be already fixed with v2006sp1 (defect# 11314)?
Is there a workaround? I need to be able to create and validate instance documents.

Cheers,
Gabi



paul
Posted: Monday, November 21, 2005 10:42:00 AM
Rank: Advanced Member

Joined: 9/9/2005
Posts: 483
Location: AT
Hello Gabi,

The schema you reference redefines another, which in turn imports another, which includes another, etc...

To save us chasing after all of these files, please zip up the entire collection and send it to us via the Support Center so we can take a closer look at the matter.

B
gabrieleneumann
Posted: Tuesday, November 22, 2005 3:48:00 AM
Rank: Member

Joined: 11/22/2005
Posts: 2
Location: DE
Hi Paul,
it it not possible to send the files via Support Center. I am receiving: "Error 76 in LoadRequest: Path not found" :confused:
The entire collection includes 5 schema files:
sciphox-cda.xsd
header_1.0.xsd
levelone_1.0.xsd
sciphox10.xsd
v3dt_1.0.xsd

Thanks,
Gabi



AnttiSissonen
Posted: Monday, November 28, 2005 6:30:00 AM
Rank: Member

Joined: 11/28/2005
Posts: 2
Location: FI
Hi.

I"ve noticed similar behaviour with several different schema module setups, all of them having imports and namespace declarations. Ones that you could try out as test cases are the ESIDEL schemas available at:

http://www.eurofer.org/edifer/publications_ESIDEL1_0.htm

Download for example:

http://www.eurofer.org/edifer/publicpdfv10/BP_Ordering.xsd

plus also include modules Library.xsd and CoreComponentTypes.xsd that are needed as imports.

Regards,

Antti

tdcthree
Posted: Tuesday, December 6, 2005 11:05:00 AM
Rank: Member

Joined: 11/18/2003
Posts: 1
Location: US
FWIW, we have the same problem and just submitted a bug report (Spy 2006 sp1).



+
ctreglio
Posted: Tuesday, December 6, 2005 4:19:00 PM
Rank: Member

Joined: 12/6/2005
Posts: 1
Location: US
another schema that exhibits this behavior can be seen here:

http://www.cdisc.org/models/def/v1.0/define1-0-0.xsd

dtemme
Posted: Friday, December 9, 2005 6:50:00 AM
Rank: Member

Joined: 12/9/2005
Posts: 3
Location: NL
The same behaviour in 2006 SP2. See my Post in the Generic Forum.

Users browsing this topic
guest

Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.