W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2003

RE: xs:redefine of a imported namespace group

From: Robert Koberg <rob@koberg.com>
Date: Sat, 19 Apr 2003 10:58:51 -0700
Message-Id: <200304191758.KAA15976@s5.servlets.net>
To: "'Henry S. Thompson'" <ht@cogsci.ed.ac.uk>
Cc: <xmlschema-dev@w3.org>

Hi and thanks for responding,

> You're  trying to use redefine exactly as it is intended, as far as I
> can tell without the full schema docs.  Which validator are you using?
> Have you tried XSV?

Yes. I have an example up now. I have run it through the online (and offline
XSV) validator at:

The schemas validate with no errors.

An invalid instance document to use in the online validator is at:

This points to a 'client' specific XSD:

The above schema imports a 'client' global schema:

I want the 'global' schema to be used by all clients as a base. From there I
am hoping that specific clients modify it for their specific needs using

I must be doing something wrong with my redefines because XSV complains the
instance document is invalid at the point it hits one of my redefined

MSXML chokes on it in a different way, saying that the 'Block' redefine
(shown below) could not resolve
{schemaLocation='http://www.livestoryboard.com/Schemas/xhtml_modfd.xsd} of

So, XSV sees the imported XSD and uses it to validate, but ignores my
(attempted) redefines. MSXML does not see the global schema to do the

For example this redefine does not work (in content.xsd):
    <xs:complexType name="Block">
        <xs:restriction base="x:Block">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
            <xs:group ref="c:lsb_core_blocks"/>

Redefining (in xhtml_modfd.xsd):
<xs:complexType name="Block">
    <xs:choice minOccurs="0" maxOccurs="unbounded">
      <xs:element ref="x:FORM"/>
      <xs:group ref="x:edit.inline"/>
      <xs:element ref="x:PRE"/>
      <xs:element ref="x:HR"/>
      <xs:element ref="x:BLOCKQUOTE"/>
      <xs:element ref="x:P"/>
      <xs:group ref="x:lists"/>
      <xs:element ref="x:TABLE"/>
      <!--<xs:group ref="c:lsb_core_blocks"/>-->

Is the problem in the namespaces? In other words, since I redefine in the
content.xsd, does it now live the content.xsd targetNamespace? And when I
refer to x:Block it simply is not the redefine? Hope not... I use x:Block in
the imported schema and want it to pick up any change in the client specific
content.xsd. Hopefully this makes sense and the provided examples give a
better indication as to the problem.

Any help is greatly appreciated - thanks,

> ht
> --
>   Henry S. Thompson, HCRC Language Technology Group, University of
> Edinburgh
>                       Half-time member of W3C Team
>      2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
> 	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
> 		     URL: http://www.ltg.ed.ac.uk/~ht/
>  [mail really from me _always_ has this .sig -- mail without it is forged
> spam]
Received on Saturday, 19 April 2003 13:59:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:56:01 UTC