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=20&rev2=21 -------------------------------------------------- . . Additionally xs:override implementation may require quite a few new components/data structures to be added to org.apache.xerces.impl.xs package inorder to handle different scenarios regarding <override> semantics as was described in the beginning. == Things I have Done So far == - . Since this project is about implementing a XMLSchema 1.1 specification construct , I had to go through this specification docs several times to understand the exact structure and semantics of the component I’m going to implement which I think is of vital importance when it comes to the design and implementation. Previous discussions (that has happened in Xerces-j-dev mail archives) about this xs:override support , online articles and tutorials also helped a lot in this cause. I also interacted with Xerces mailing list (especially with my mentor) to clarify critical points and implementation details. Since knowing Xerces and it’s internal framework(XNI) is obviously essential for the implementation I had to dig into various documentation, API information ,samples , regarding Xerces Design,architecture and especially XML schema processing. I did download the source code of Xerces2-j from trunk and build the code inorder to try and test out some samples to get a hang on the flow of things related to schema loading and processing.Running through several samples (xs.QuerryXS , jaxp.SourceValidator, xni samples,etc) and debugging them , really gave me a good inisght into to Xerces framework... + . Since this project is about implementing a XMLSchema 1.1 specification construct , I had to go through this specification docs several times to understand the exact structure and semantics of the component I’m going to implement which I think is of vital importance when it comes to the design and implementation. Previous discussions (that has happened in Xerces-j-dev mail archives) about this xs:override support , online articles and tutorials also helped a lot in this cause. I also interacted with Xerces mailing list (especially with my mentor) to clarify critical points and implementation details. Since knowing Xerces and it’s internal framework(XNI) is obviously essential for the implementation I had to dig into various documentation, API information ,samples , regarding Xerces Design,architecture and especially XML schema processing. I did download the source code of Xerces2-j from trunk and build the code inorder to try and test out some samples to get a hang on the flow of things related to schema loading and processing.Running through several samples (xs.QuerryXS ,xni.GrammerBuilder, jaxp.SourceValidator, xni samples,etc) and debugging them , really gave me a good inisght into to Xerces framework... == Development Schedule == ||<tablewidth="854px" tableheight="291px"width="200px" style="font-weight: bold; font-style: italic;">Time Schedule/Duration ||<style="font-weight: bold; font-style: italic;">Activity || ||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 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 creating necessary API's || + ||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 ||creating necessary API's Start coding on xs:override implementation || ||July 12- July 16 ||Mid term Evaluations - students and mentors submit evaluations || - ||July 16 - August 9 ||start second phase of coding -------------------------------------------------------------------------------------------------------- integration of xs:override implementation phases (if any) -------------------------------------------------------------------------------------------------------- write tests for xs:override semantic validation || + ||July 16 - August 9 ||start second phase of coding; integration of xs:override implementation phases (if any) ; writing tests to validate xs:override semantics; || - ||August 9 - August 16 ||Final week of the project - final code submission on August 16th refine/review code finalizing documentaion || + ||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 || + ---- == Deliverables == * Source/patch related to xs:override implementation * Solid set of test cases to verify related aspects of xs:override schema composition --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
