Hi Michael, thnx for adding that to the JIRA list.. Regards, Udayanga
On Mon, Mar 29, 2010 at 7:06 PM, Michael Glavassevich <[email protected]>wrote: > Hi Udayanga, > > Thanks for providing the description for the xs:override project. It's now > being tracked with XERCESJ-1433 [1]. > > [1] https://issues.apache.org/jira/browse/XERCESJ-1433 > > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] > > udayanga wickramasinghe <[email protected]> wrote on 03/29/2010 > 08:41:42 AM: > > > On Mon, Mar 29, 2010 at 5:20 PM, Michael Glavassevich < > [email protected] > > > wrote: > > FYI. > > > > Michael Glavassevich > > XML Parser Development > > IBM Toronto Lab > > E-mail: [email protected] > > E-mail: [email protected] > > > > Bertrand Delacretaz <[email protected]> wrote on 03/29/2010 > 04:40:44 AM: > > > > > Hi Apache project and podling PMCs, > > > > > > This is just a reminder that the student applications for Google > > > Summer of Code open on March 29th (see [1] for timeline), which > > > is...today ;-) > > > > > > Please make sure your GSoC project proposals appear on the JIRA list > > > of issues at http://tinyurl.com/asfgsoc - just add a "gsoc" label to > > > those issues if using JIRA as your tracker, and if not you can create > > Since the project i'm working on "xs:override implementation" is not > > currently mentioned under GSoc JIRAs can you please add it to the > > above list as well . > > Here is the description of the JIRA. > > > > Summary : Implementing XMLSchema1.1 overriding component > > definitions (<xs:override>) > > Component/s: XML Schema 1.1 Structures > > Affects Version/s: 2.9.1 > > Labels: gsoc > > Description : > > > > XML schema specification version 1.1 [1] specifies syntax and > > semantics of “Overriding component definitions<override>”[2] or > > xs:override , under “Schemas and Namespaces: Access and Composition” > > . The new component definition is a powerful addition to the XML > > schema composition framework ,which tries to mitigate some of the > > constraints present in similar constructs such as xs:redefine or > > <redefine> schema component. > > The <redefine> construct defined in “Including modified component > > definitions (<redefine>) “[3] on XMLSchema specification is useful > > in schema evolution and versioning. It can be used only when there > > exists some restriction or extension relation between the old > > component and the new redefined component. But there are occasions > > when the schema author simply wants to replace old components with > > new ones without any constraint. Also, existing XSD processors have > > implemented conflicting and non-interoperable interpretations of > <redefine> > > . The implementation of new construct <override> on Xerces > > XMLSchema processor ,would avoid these bottlenecks and allow > > unconstrained replacement as and when needed by the schema author. > > Possible Mentors: Khaled Noaman > > > > [1] http://www.w3.org/TR/2006/REC-xml11-20060816/ > > [2] http://www.w3.org/TR/xmlschema11-1/#override-schema > > [3] http://www.w3.org/TR/xmlschema11-1/#modify-schema > > > > thanx in advance... > > > > -Udayanga > > > > an issue like COMDEV-31 so that your proposal appears in the list. > > > > > > See http://community.apache.org/gsoc.html for more info, or contact > > > the Community Development group at [email protected] for any > > > question. > > > > > > Cheers, and looking forward to a successful GSoC 2010 @apache! > > > -Bertrand, for the Community Development group. > > > > > > [1] http://socghop.appspot.com/document/show/gsoc_program/google/ > > gsoc2010/faqs > > > > > > > > -- > > http://www.udayangawiki.blogspot.com > -- http://www.udayangawiki.blogspot.com
