|
|
Rank: Newbie
Joined: 2/7/2006
Posts: 2
Location: England
|
I am currently working on a university research project and as part of the project I am building on the work previously carried out on 'GeotechML', an XML based data exchange format for geotechnical engineering. The AGS (Association of Geotechnical and Geoenvironmental Engineers) have just completed the development stage of their own format 'AGSML' which is used to represent site investigation data.
In my schemas I have imported in the root AGSML schema and also the necessary GML (Geography Markup Labguage) schemas and extended them. However, whenever I try to validate it I get an error saying that there is an error in the schemas I have imported (AGSML, which in turn imports GML schemas). Obviously you're not going to know the actual content of the schemas but I'll give the error just so you know what type it is. It highlights the complex type 'CongArrayType' and gives the error, 'This file is not valid: the content model of complex type agsml:CongArrayType is not a valid restriction of the content model of complex type gml:FeatureArrayPropertyType.' This is the only error that it gives (or this is the always the first to appear at least, I guess there could be more).
However, I know that this is not an error in my schema because the same error is given when I open the top level AGSML schema completely separate from my project. Also, I have contacted the creator of the AGSML schemas and he assures me that they validate fine with XMLSpy 2005 SP2 which he uses. I am using XMLSpy2006 Home Edition and I think this is almost certainly a bug in it.
Does anyone have any ideas?
Thanks
Steve
|
|
Rank: Advanced Member
Joined: 9/9/2005
Posts: 483
Location: AT
|
Hello Steve,
I am afraid that this looks like a problem with the 2006 SP2 validator. At least, I certainly can see no reason why the 'agsml.xsd' file should fail validation - plus the internal daily build of our next release candidate does not flag any errors. Thus I am very hopeful that the next public release will see the issue confirmed resolved.
In the meantime please accept our apologies for the inconvenience.
Were you not using the free Home Edition of XMLSpy (with its restriction on aggregate schemas) I would recommend using the Schema view validator to check these files as this component does not suffer from the problem described. Perhaps the 30 day evaluation version of XMLSpy Pro or Enterprise will allow you to complete your project?
|
|
Rank: Newbie
Joined: 2/7/2006
Posts: 2
Location: England
|
Ok, thanks for letting me know! I'm virtually finished with the development anyhow and so it shouldn't be too much of a problem. I will use the 30 day trial as you suggested if I need to make any changes to my schemas.
Thanks for releasing the home edition though, it's a really useful tool for a student like me (even if it does have a bug or two!), and hopefully they can be resolved.
Steve
|
|
Rank: Newbie
Joined: 3/13/2006
Posts: 1
Location: Canada
|
I'm also seeing this error message using our own schemas. It validates fine in the Schema View, but fails to validate in the text view. I discovered it when I tried to generate a sample schema instance.
|
|
|
guest |
