Dear Wiki user, You have subscribed to a wiki page or wiki category on "Xerces Wiki" for change notification.
The "gsoc_xs_override_proposal" page has been changed by uswick. http://wiki.apache.org/xerces/gsoc_xs_override_proposal?action=diff&rev1=19&rev2=20 -------------------------------------------------- . XSDHandler#parseSchema() is responsible for coordinating these critical stages of schema composition which includes , . a) constructTrees – constructs XSschema objects .Attempts to resolve <include>,<redefine> schema components and builds a dependency map . . - . b) buildGlobalNameRegistries - builds registries for all globally-referenceable names. Keeps track of <redefine> component mapping. + . b) buildGlobalNameRegistries - builds registries for all globally-referenceable names. Keeps track of <redefine> component mapping for detecting duplicate collisions and redefine preprocessing . . c) traverseSchemas – traverse globally declared elements with appropriate traverser object (ie:-SimpleType/ComplexType/Attribute traversers) and handle them accordingly. @@ -62, +62 @@ . . + . xs:override implementation intends to extend this functionality to implement <override> structure semantics. Implementation would include extending the phase #constructingTrees to include necessary mappings for override schema components (ie:-creating a fOverride2XSDMap , to map override elements with respective schema documents ). Included modification to this phase can closely be related to <REDEFINE> implementation and would include necessary control paths as needed. However most challenging task would be in extending next two phases (in #buildGlobalNameRegistries and #traverseSchemas ) when implementing xs:ovserride semantics. These two phases include depth-first traversal of schema dependencies (ie:-when schema A includes B , A depends on B and vice versa) built in the first phase ,for building primary and subordinate registries on global components , and for travesrsing them for validation , respectively.These are obviously very important in Implementation of xs:override and will require to extend them approprately with mcuh emphasis on design aspects. Main design/implementation areas are , + + . . + * extending XSDHandler#checkForDuplicateNames() - to include necessary control paths for <override> semantics ,detecting the scenarios where duplicate collisions can occur and flagginf these errors appropriately. + * implementing XSDHandler#renameOverriddenComponents(currentSchema,childComponent,componentType,oldName,newName) - renaming overridden components taking into consideration overriding of <includes> and merging <overriding> components on respective schema locations + * extending XSDHandler#traverseSchemas() and traversers( org.apache.xerces.impl.xs.traversers) - to traverse override schema components , and also to take into account the behavior of each individual travereser objects on the application of xs:override semantics. + + . . + - . xs:override implementation intends to extend this functionality to implement <override> structure semantics. Also several supporting structures will be needed so that <override> schema components will be identified during schema processing. For example extending of following class structures. + . Also several supporting structures will be needed so that <override> schema components will be identified during schema processing. For example extending of following class structures. . . • org.apache.xerces.impl.xs.SchemaSymbols – keeps track of collection of symbols used in parsing Schema Grammer. Need to introduce new <override> grammer symbols to this. . . • org.apache.xerces.impl.xs.XSDDescription - keeps track of all information specific to XML Schema grammars. This can be used to indicate the Schema processor that the current schema document is overridden by another schema document @@ -77, +86 @@ ||March 18 - March 29 ||Initiate ideas ,discuss project details , get feed back on different aspects of the project,etc || ||March 29 - April 9 ||preparing project proposals and submission || ||April 26 ||GSoc Accepted student proposals announced by Google || - ||April 26 - May 24 (Community Bonding Period) ||preparation on design aspects,architecture and deployment on xs:overide implementaion preraration on various platform details (ie:-xerces architecture,scheam processing,etc) prepare development environment || + ||April 26 - May 24 (Community Bonding Period) ||preparation on design aspects,architecture on xs:overide implementaion ------------------------------------------------------------------------------------------------------- preraration on various platform details (ie:-xerces architecture,schema processing,etc) ------------------------------------------------------------------------------------------------------- prepare development environment || - ||May 24 - July 12 ||Start coding on xs:override implementation || + ||May 24 - July 12 ||Start coding on xs:override implementation creating necessary API's || ||July 12- July 16 ||Mid term Evaluations - students and mentors submit evaluations || - ||July 16 - August 9 ||start second phase of coding write tests for xs:override validation || + ||July 16 - August 9 ||start second phase of coding -------------------------------------------------------------------------------------------------------- integration of xs:override implementation phases (if any) -------------------------------------------------------------------------------------------------------- write tests for xs:override semantic validation || ||August 9 - August 16 ||Final week of the project - final code submission on August 16th refine/review code finalizing documentaion || ||August 23 ||Final results of GSoc 2010 will be anounced || --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
