Neil, Henry, Lisa
Firstly thanks for the info and feedback - hope you don't mind a communal
answer.
I'd sort of worked out that it parsed the whole schema - but I was unsure
whether the parser would issue errors for those items not used by a document.
This (false) notion was based on the fact that different documents produced
different errors ascribed to the schema.
I do appreciate the fact that the example was huge - but I felt that was part
of the problem (with array out of bounds?).
This was complicated by the fact that the parser issues line numbers for the
document and not for the schema.
Maybe the parser could incorporate a schema checking facility - (much like SQC)
as a debug aid to locate these problems?
For example 1.4.1 produced over 50 identical errors
[Error] _test4.xml:17:211: Schema error: Attribute that appeared in the
base should nnot appear in a derivation by extension.
which were all due to three errors in the schema - difficult to locate (thanks
to Lisa here!)
I've fixed up the errors outlined by Henry and Lisa and am testing against
1.4.1, the combination of which has cleared up most of the problems.
There are still some odd ones saying that Element and Attribute need to be
declared - I've just started a build from CVS to see if these are the ones that
Lisa checked in (after 1.4.1 was released?)
Again ta very much for the assistance and feedback.
Graham Mann
Adobe Systems Europe Ltd.
Tel: +44 (0)1603 226749
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
