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=26&rev2=27 -------------------------------------------------- . 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. I also went through XML schema processing classes available in org.apache.xerces.impl.xs package to get a thorough understanding on exisiting schema processing framework and especially on how <redefine> semantics are applied to schema documents which is in some ways similar to <override> semantics. == Development Schedule == - . develop + . I would initially focus on trying to come up with a good strategy to implement the proposed extension. For this i would need to digg into the existing framework on ways to integrate it correctly without breaking the existing code .I am planning to interact and discuss with the the xerces community (and with my mentor) on their suggestions and on any issues/bugs i may encounter along the way. After a good implementation strategy is in place i would start coding on it in several phases , taking into consideration different components of the proposed extension and their integration.Finally i will prepare the required test cases to validate the implemented extension and also the necessary design documentation,API java docs ,etc. ||<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 ||creating/finalizing necessary API's ; Start coding on xs:override implementation || + ||May 24 - July 12 ||creating/finalizing necessary API's ; Start coding on xs:override implementation (creating required datastructures/registries ,implementing Trasformation Manager ,etc) || ||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) ; writing tests to validate xs:override semantics; || + ||July 16 - August 9 ||start second phase of coding (implementing other sub components required); 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 , API docs; || ||August 23 ||Final results of GSoc 2010 will be anounced || --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
