Hello,
I've been testing a bit the xs:override implementation that has
been recently committed to Xerces SVN repos. It seems to be working
fine and I'm happy with it's implementation.
Congratulations to Udayanga and also thanks to Khaled :)
I believe we now have nearly all pieces of XML Schema 1.1
implementation available in Xerces-J and I think we might now work to
release the Xerces 2.11.0 version formally. I think Michael is perhaps
the best person to start that process.
On Thu, Nov 11, 2010 at 1:00 AM, Khaled Noaman (JIRA)
<[email protected]> wrote:
>
> [
> https://issues.apache.org/jira/browse/XERCESJ-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Khaled Noaman resolved XERCESJ-1433.
> ------------------------------------
>
> Resolution: Fixed
> Fix Version/s: 2.11.0
>
> Patch applied with some minor modifications
>
>> [GSoC]: Implementing XML Schema 1.1 overriding component definitions
>> (<xs:override>)
>> ------------------------------------------------------------------------------------
>>
>> Key: XERCESJ-1433
>> URL: https://issues.apache.org/jira/browse/XERCESJ-1433
>> Project: Xerces2-J
>> Issue Type: New Feature
>> Components: XML Schema 1.1 Structures
>> Affects Versions: 2.9.1
>> Reporter: Michael Glavassevich
>> Assignee: Khaled Noaman
>> Fix For: 2.11.0
>>
>> Attachments: schema1_1_override_patch.tar.gz
>>
>>
>> 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 XML Schema 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
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
