Re: [Bug 5862] Please retain redefine as well as override

David Ezell writes:

>  XML Schema 1.1 notably (at least at this point) does >not< 
> address composition

That's a bit strong, and I expect it's not what you intended. What XSD 1.1 
does not do is to substantially improve the flawed presentation of 
composition that was in XSD 1.0.  XSD 1.1 certainly does address 
composition, it just doesn't do it particularly better than 1.0 did.  In 
fact, even that is a bit pessimistic, since we've made a few 
organizational revisions to the presentation thinks like xsd:import.  I do 
agree with what I take to be the spirit of your comment:  the presentation 
of redfine in XSD 1.0 is at best somewhat confusing and at worst 
ambiguous, underspecified and/or self-contradictory, and XSD 1.1 does 
little if anything to improve that.  That is among the reasons for 
deprecating use of that feature. 

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








bugzilla@wiggum.w3.org
Sent by: www-xml-schema-comments-request@w3.org
08/04/2008 12:26 PM
 
        To:     www-xml-schema-comments@w3.org
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        [Bug 5862] Please retain redefine as well as 
override



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


David Ezell <David_E3@VERIFONE.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |David_E3@VERIFONE.com
             Status|NEW                         |RESOLVED
           Keywords|                            |resolved
         Resolution|                            |WORKSFORME




--- Comment #1 from David Ezell <David_E3@VERIFONE.com>  2008-08-04 
16:26:25 ---
On 2008-08-01 the WG reviewed the request from Mr. Coates and decided not 
to
take any action other than to close this item as "works for me". Following 
is
the rationale for that decision.

Point 1 - the actual request for this bug entry is "please retain redefine 
as
well as override."  Since the WG is deprecating redefine but not removing 
it,
then strictly speaking the WG is retaining redefine.  It will be up to 
some
future working group at some future time to decide whether to eliminate
redefine in some future revision; in no way does the deprecated label 
force a
decision on such a future working group.  So from a very precise point of 
view,
the WG is already complying with the commenter's request -- hence the
WORKSFORME classification.

Point 2 - the WG has struggled with redefine and how it fits into schema
composition.  XML Schema 1.1 notably (at least at this point) does >not<
address composition - the story is the essentially the same as with 1.0. 
Designating redefine as "deprecated" is in part a signal that future work
should address composition and redefine in particular. 

Point 3 - the WG (as a group) was unwilling to extend the rec to include
xs:override without some compensating measure with regard to redefine. 
Hence
the "deprecated" label.

The WG hopes that commenter can understand that this issue is a difficult 
one,
and that we believe that the status quo is the best possible outcome at 
this
time.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 4 August 2008 17:55:24 UTC