Hi Shakya,

Congratulations! Looking forward to working with you over the summer.

Thanks.

Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: [email protected]
E-mail: [email protected]

Shakya Wijerama <[email protected]> wrote on 23/04/2012 03:34:51 
PM:

> Hello Michael & Devs,
> 
> It is a great pleasure to tell you that I have been selected to GSoC
> 2012. I would like to make this a chance to thank all the devs in 
> the community who supported me to write a good proposal & my special
> thanks goes to Michael who always responded quickly and reviewed my 
> proposal multiple times. I hope to give my best in this summer and 
> would like to share opinions with you to make the project a success.
> 
> Thanks.
> 
> On Thu, Apr 5, 2012 at 12:15 AM, Shakya Wijerama 
<[email protected]
> > wrote:
> Hello Michael,
> 
> I improved my proposal according to your response. I have attached 
> the finalized proposal herewith and updated the proposal in Google 
melange.
> 
> Thanks.
> 
> On Wed, Apr 4, 2012 at 8:55 PM, Michael Glavassevich 
<[email protected]
> > wrote:
> Hello Shakya, 
> 
> Shakya Wijerama <[email protected]> wrote on 03/04/2012 06:53:59 
PM:
> 
> > Hello Michael, 
> > 
> > I have completed my proposal and submitted it to Google under Apache
> > Software Foundation. I have attached the proposal as a PDF file with
> > this mail. Can you give me a feedback on it so I can change the 
> > proposal before the deadline (April 6th)?
> 
> 
> I've read through your proposal. This looks really great. 
> 
> One thing you might want to expand on is the synthetic schema 
> example and how that might look when there are multiple namespaces 
involved. 
> 
> For instance, given a Source[] containing: 
> 
> a.xsd :: targetNamespace = n 
> b.xsd :: targetNamespace = n 
> c.xsd :: targetNamespace = m 
> d.xsd :: targetNamespace = m 
> 
> ================================== 
> 
> You would need two levels of generated schemas. For example: 
> 
> <?xml version="1.0" encoding="UTF-8"?> 
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";> 
> <xs:import schemaLocation="generated1.xsd"/> 
> <xs:import schemaLocation="generated2.xsd"/> 
> </xs:schema> 
> 
> generated1.xsd: 
> <?xml version="1.0" encoding="UTF-8"?> 
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
targetNamespace="n"> 
> <xs:include schemaLocation="a.xsd"/> 
> <xs:include schemaLocation="b.xsd"/> 
> </xs:schema> 
> 
> generated2.xsd: 
> <?xml version="1.0" encoding="UTF-8"?> 
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
targetNamespace="m"> 
> <xs:include schemaLocation="c.xsd"/> 
> <xs:include schemaLocation="d.xsd"/> 
> </xs:schema> 
> 
> > I am not sure whether others can view the images in the proposal 
> > which I submitted to the Google. How can I know it? 

> I can view the images in the proposal you submitted to Google. I 
> assume others would be able to as well. 
> 
> > Thanks. 
> > 
> > On Tue, Apr 3, 2012 at 9:51 AM, Michael Glavassevich 
<[email protected]
> > > wrote: 
> > Hello Shakya, 
> > 
> > Shakya Wijerama <[email protected]> wrote on 02/04/2012 
05:12:17 PM:
> > 
> > > Hello Michael, 
> > > 
> > > I have completed my proposal to some extent and there are a few 
> > > things to clarify. I am not much familiar with custom entity 
> > > resolver. Can you briefly explain me the idea of that and how we can
> > > apply it in the project. 
> 
> > For each include and import in a schema document, Xerces will make a
> > call out to an entity resolver [1] to locate the include or import. 
> > This allows the application to resolve the location of the schema 
> > document in some other way than the default of opening the URL 
> > specified on the include/import. The includes and imports in the 
> > synthetic schemas you generate should resolve back to the Source 
> > objects that were passed to SchemaFactory.newSchema(). You would 
> > need to create an implementation of XMLEntityResolver which handles 
> > this custom resolution and register it with the SchemaFactory. 
> > 
> > > I have used the name for the project as it is in JIRA. It is more 
> > > like bug name and I think it is better to change the name as 
> > > "Validating against multiple XMl schemas with same namespace". What 
> > > do you suggest for this? 
> 
> > Yes, sounds much better than the JIRA bug id. 
> >  
> > > I have not fully completed the proposal yet and there are some 
> > > modifications to be done. So I can complete the rest with your 
> > > feedback and submit it to Google tomorrow (since the deadline is 
> > 6thof April). 
> > > 
> > > Note:  I have attached the proposal herewith.. 
> 
> > Good work so far. Looking forward to seeing your completed proposal. 
> > 
> > > Thanks.
> > 
> > > On Thu, Feb 23, 2012 at 10:30 AM, Michael Glavassevich <
> [email protected]
> > > > wrote: 
> > > Hi Shakya,
> > > 
> > > I understand what Mukul is saying, but disagree that Xerces is 
> > > working correctly. He described a work around for that specific 
> > > case, not a general solution.
> > > 
> > > I believe users should be able to provide an array of schema 
> > > documents to SchemaFactory.newInstance() which all have the same 
> > > namespace and that Xerces should be fixed so that it can process 
that.
> > > 
> > > It should be possible for the SchemaFactory implementation to 
> > > internally generate a synthetic schema document which combines the 
> > > user's list of schema documents together. From the schema loader's 
> > > perspective this would look like one master schema document for the 
> > > namespace which has includes to all the others. Taking that a step 
> > > further, another schema document could be generated which glues all 
> > > the namespaces together with imports. 
> > > 
> > > 
> > > Thanks.
> > > 
> > > Michael Glavassevich
> > > XML Technologies and WAS Development
> > > IBM Toronto Lab
> > > E-mail: [email protected]
> > > E-mail: [email protected] 
> 
> > Thanks. 
> > 
> > [1] http://xerces.apache.org/xerces2-j/javadocs/xni/org/apache/
> > xerces/xni/parser/XMLEntityResolver.html 
> > 
> > Michael Glavassevich
> > XML Technologies and WAS Development
> > IBM Toronto Lab
> > E-mail: [email protected] 
> > E-mail: [email protected] 
> > 
> > Regards, 
> > 
> > Shakya Wijerama 
> > 
> > Senior Student, 
> > Faculty of Applied Sciences, 
> > Sabaragamuwa University of Sri Lanka. 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected] 
> 
> Thanks. 
> 
> Michael Glavassevich
> XML Technologies and WAS Development
> IBM Toronto Lab
> E-mail: [email protected] 
> E-mail: [email protected]
> 

> 
> -- 
> 

> 
> Regards,
> 
> Shakya Wijerama
> 
> Senior Student,
> Faculty of Applied Sciences,
> Sabaragamuwa University of Sri Lanka.
> 
> 

> 
> -- 
> 

> 
> Regards,
> 
> Shakya Wijerama
> 
> Senior Student,
> Faculty of Applied Sciences,
> Sabaragamuwa University of Sri Lanka.

Reply via email to