Hi Eric, wang eric <[email protected]> wrote on 03/30/2010 12:23:49 AM:
> Hi everyone, > > I am interested in this GSoC issue (SCD), and I would like to write > a proposal about this one. I know it is a bit late for starting my > disscussion now (I see some students have already prepare their > proposals). But I have an important test in this coming Friday. That > really cost much of my time to prepare. > > About the project, from what I have learned from the document, The > work which should be done is parse the SCD expression like this example: > schema-URI#xscd(/type::purchaseOrderType/model::sequence/ > schemaElement::billTo) > > and then use the information in this expression : type, model, > schemaElement to find the correspond component from an XSModel. Is > this "XSModel" means that the evaluator will try to find the > components in an existed object so that there are some existed > founctions which can help the evaluate? In Xerces the XSModel [1] is the top-level object in the graph of schema components. It and the other XML Schema API interfaces have accessor methods that an evaluator would call as it walks through the graph, searching for the component which matches the SCD expression. This model would have already been built and would be used as one of the input parameters to the evaluator. > And about the parser which I would like to use JavaCC to generate. > The EBNF for Schema Component Path Syntax and the EBNF Schema > Component Designator Syntax as will as other informations which > should be useful to locate the component will be rewrite in the the > requested form of JJTree. Then I can generate the basic parser by > using JavaCC, and through edit the AST classes and the Visitor I can > return necessary information or directly find the component and > return this component. > > I am still working on some details about the existed XSModel and the > necessary informations. (hope some advice ^ ^) > > However before that, I would like to ask some other things. I am > informed that there is another student who is currently working on > this proposal too, and he or she have worked with a potential mentor for > MONTHS (That is really a long time, because the idea list is > pubilshed in March 18). So I would eager to know that to what extend > his or her work has been done. Yes. Ishan's been working on a proposal for SCD for quite awhile now. If you look back in the mailing list archives you'll see discussion for this year's GSoC started at the beginning of February and have actually talked to some students privately even earlier than that. There are idea lists from previous years and some students looking to get a head start approach the communities (in Apache and others) long before the idea lists are posted in some cases even before GSoC is announced for the year. It is a very clever thing to do in my opinion. It gives those students an opportunity to get to know their potential mentors in advance (and vice versa), to learn what is necessary for the project in detail, to educate themselves on the things which are new to them, to gain confidence from their potential mentors and to get a lot of help and feedback on building a strong proposal with the community outside of the rush of the official two week application period. It is something I would recommend to anyone applying and a bit surprised it isn't mentioned in the GSoC FAQs. > If this students have actually finish > part of the work I think it will make my proposal a little meaningless... > > About me, I'm a graduate student in Fudan University, Shanghai, > China. Major in computer science and technology. I have contact with > some XML expressions and also a part of WS-XX relateded standards in > my research work in the school's lab. It is about WS-Management. And > furthermore, I have developed a SQL parser using JavaCC in another project. > > Thanks, > Best Regards > Eric Wang Thanks. [1] http://xerces.apache.org/xerces2-j/javadocs/xs/org/apache/xerces/xs/XSModel.html Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected]
