W3C home > Mailing lists > Public > xmlschema-dev@w3.org > August 2009

RE: [Update #2] XML Schema 1.1 Tutorial

From: Costello, Roger L. <costello@mitre.org>
Date: Wed, 12 Aug 2009 11:29:44 -0400
To: "'Eliot Kimber'" <ekimber@reallysi.com>, "noah_mendelsohn@us.ibm.com" <noah_mendelsohn@us.ibm.com>
CC: "xmlschema-dev@w3.org" <xmlschema-dev@w3.org>, "sandygao@ca.ibm.com" <sandygao@ca.ibm.com>
Message-ID: <9E51F88D5247B648908850C35A3BBB50040394F36E@IMCMBX3.MITRE.ORG>

Here's what the XML Schema 1.1 specification says:

   The <redefine> construct is *deprecated*

/Roger 

> -----Original Message-----
> From: Eliot Kimber [mailto:ekimber@reallysi.com] 
> Sent: Wednesday, August 12, 2009 11:26 AM
> To: noah_mendelsohn@us.ibm.com; Costello, Roger L.
> Cc: xmlschema-dev@w3.org; sandygao@ca.ibm.com
> Subject: Re: [Update #2] XML Schema 1.1 Tutorial
> 
> On 8/12/09 10:14 AM, "noah_mendelsohn@us.ibm.com"
> <noah_mendelsohn@us.ibm.com> wrote:
> 
> > Overall, I think this is excellent, and much improved from the first
> > version.  One quibble, though reasonable people might 
> disagree with my
> > position on this:
> > 
> > You say on Slide 25 that <redefine> is deprecated, but that 
> is followed in
> > the CR draft with a feedback request asking the community 
> whether such
> > deprecation is a good idea.  Speaking for myself (not IBM), 
> I think it's
> > too early to deprecate redefine.  It's a supported feature 
> of 1.0, and as
> > far as I know it's widely used.  Although there's some optimism that
> > <override> will be a good substitute, that's as yet 
> unproven and in any
> > case deprecating features that users have already deployed 
> at best tends
> > to make them nervous.
> 
> The DITA standard depends entirely on the redefine feature in 
> XSD 1.0. While
> we are hoping that XSD 1.1 provides a better alternative to 
> redefine, until
> it's both defined and implemented sufficiently widely (e.g., 
> in Xerces and
> other widely-used XML parsers) we cannot move away from the 
> use of redefine.
> 
> For DITA's sake, I agree with Noah that deprecating redefine 
> in XSD 1.1
> would be premature and probably result in serious PR 
> difficulties for DITA,
> where use of XSD is already dicey because of the current 
> implementation
> status and spec ambiguity of redefine in XSD 1.0.
> 
> Cheers,
> 
> Eliot
> 
> 
> ----
> Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
> email:  ekimber@reallysi.com <mailto:ekimber@reallysi.com>
> office: 610.631.6770 | cell: 512.554.9368
> 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
> www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
> <http://blog.reallysi.com> | www.rsuitecms.com 
> <http://www.rsuitecms.com> 
> 
> 
Received on Wednesday, 12 August 2009 15:30:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:15:14 GMT