[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


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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to