W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > April to June 2007

[Bug 2224] R-232: Vacuous Redefinition

From: <bugzilla@wiggum.w3.org>
Date: Fri, 20 Apr 2007 14:00:04 +0000
CC:
To: www-xml-schema-comments@w3.org
Message-Id: <E1Hetee-00070P-4Q@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2224





------- Comment #1 from sandygao@ca.ibm.com  2007-04-20 14:00 -------
This issue involves 2 questions:

1. Do vacuous redefinitions produce the same component as the original?

I think the answer is "no" and the spec is very clear about this. "CT" in XSD1
(call it CT-1) has a base type (the one named in is "base" attribute or
"anyType"). "CT" in XSD2 (call it CT-2) has CT-1 as its base type. This makes
CT-2 a different type from CT-1.

Conclusion from this: how redefinition works is not impacted by whether it's
vacuous or not.

2. Is it leagal to import both the orignal schema document and a redefintion of
it?

This is closely related to (and depends on) the question of what "redefinition
is pervasive" means (see bug 2330). What's interesting about "import" is that
the spec allows processors to "ignore imports for the same namespace but the
first one". So a processor can ignore the XSD2 import and only use XSD1.


Suggestion: open a new issue to track the "pervasive redefinition" issue; mark
this one (and bug 2330 and possible bug 2577) as depending on that new issue,
because all those 3 issues are just different symptoms of the same fundamental
question.
Received on Friday, 20 April 2007 14:00:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 October 2007 06:13:41 GMT