rplante at poplar.ncsa.uiuc.edu
Thu Jun 7 07:43:16 PDT 2007
On Thu, 7 Jun 2007, Guy Rixon wrote:
> Note how I've had to do the form: qualified by default on the schema as a
> whole and unqualified explicitly on the local element inside the complex
> type. If I put elementFormDefault="unqualified" then the schema checker
> rejects cap:capability, so _it_ think the default applies to global elements.
> Maybe it's wrong.
I believe oXygen is incorrect in this case. I've studied this pretty
closely when we were making the change, but I'd have to go back to the
spec to find where this is spelled out.
> I can handle this now that I know what is going on, but it took me two days
> to work it out. Can we maybe draft some explanation or guidelines for
> implementors (of did you do that already?).
I tried to handle these questions in the VOResource spec
there's more coverage on how to define extensions. Info about
elementFormDefault and container schemas can be found at the end of
section 2.1 and in 2.2. I can see if I can beef this up a bit.
More information about the registry