|Kasun Gajasinghe||Feb 7, 2011 1:54 pm|
|Arthur De Magalhaes||Feb 8, 2011 1:07 pm|
|Michael Glavassevich||Feb 8, 2011 8:47 pm|
|Kasun Gajasinghe||Feb 10, 2011 11:56 am|
|Sandy Gao||Mar 8, 2011 2:44 pm||.gif, .gif|
|Kasun Gajasinghe||Mar 17, 2011 4:17 am||.gif, .gif|
|Kasun Gajasinghe||Mar 24, 2011 10:29 am||.gif, .gif|
|Michael Glavassevich||Mar 30, 2011 11:10 pm|
|Subject:||Re: [XERCESJ-1362] [GSoC] Implement "Schema 1.1 PSVI Changes" feature as a GSoC project|
|From:||Kasun Gajasinghe (kasu...@gmail.com)|
|Date:||Mar 24, 2011 10:29:24 am|
Hi Sandy, Michael, and devs,
On Wed, Mar 9, 2011 at 4:14 AM, Sandy Gao <sand...@ca.ibm.com> wrote:
Michael has provided some useful thoughts for this topic. I'll add a couple more.
As you may have already noticed, PSVI is discussed in the 3.x.5 sections in the spec. Xerces implemented the full PSVI for schema 1.0, so the Schema 1.1 work only need to worry about PSVI properties that changed between 1.0 and 1.1. There is a "diffed" version of the spec . If you look at sections 3.2.5, 3.3.5, and 3.4.5, you should see most of the PSVI changes. You may want to take a look there and compare against the PSVI interfaces (ItemPSVI, ElementPSVI, and AttributePSVI) to see what's missing.
The diffed version at  needed authorization, so I am referencing , I assume both are same?
As I saw, each Schema Component has separate interfaces along with their implementations under org.apache.xerces.xs and org.apache.xerces.impl.xs respectively. For example, "XSAttributeDeclaration" interface for Attribute Schema component. And, some of these components has interfaces to represent a PSVI item for these. I saw only AttributePSVI, ElementPSVI, and ItemPSVI there. Is there any particular reason for not having a PSVI items implementations for other components such as "Notation"? (Notation API seems to have been covered from ElementPSVI!)
Some of the properties will be quite interesting to implement, e.g. [subsequence-valid], [local element validity], [local type validity], and [descendent validity].
Sure. Looking forward to it! :)
It may very well take 2 months to have a well-tested implementation for all these, especially since you'll likely spend some time coming up to speed with the specification and the current implementation.
I would not recommend including the other half of PSVI (the XSModel API Michael mentioned ) in the project, both because it may make the work too big to fit in 2 months, and also it's more interface design than coding, which can easily span much longer than 2 months.
Great. Guess that defines the scope of the project. With some digging, I'll be able to figure out how much deep I have to go in the needed implementations.
I'm referencing schema 1.0 as well to understand the current implementation, hope it will be useful. Further, I'm trying to map the Schema 1.0 recommendation with the current Xerces implementation. Interfaces are pretty clear to understand, but the Impls needs a little more time to get digested. If you have any further suggestions please be kind enough to let me know.
[image: Inactive hide details for Kasun Gajasinghe ---10/02/2011 02:58:18 PM---Hi, Arthur, thanks for letting me pick it. Further, I'd]Kasun Gajasinghe ---10/02/2011 02:58:18 PM---Hi, Arthur, thanks for letting me pick it. Further, I'd very much appreciate if
From: Kasun Gajasinghe <kasu...@gmail.com> To: j-d...@xerces.apache.org, Michael Glavassevich/Toronto/IBM@IBMCA Cc: Arthur De Magalhaes/Toronto/IBM@IBMCA, Sandy Gao/Toronto/IBM@IBMCA Date: 10/02/2011 02:58 PM Subject: Re: [XERCESJ-1362] [GSoC] Implement "Schema 1.1 PSVI Changes" feature as a GSoC project
Arthur, thanks for letting me pick it. Further, I'd very much appreciate if you can help me to get to know about changes needed to be implemented in the due course.
Thanks Michael, I'm going through the code-base thoroughly starting from the given samples. I see that the code is well-commented, so it's fairly easier to go through it. I'll ask if I have further questions from the list if there's any questions related to it. I hope all the devs give a good corporation.
Sandy, I see that you are a member of the XML Schema Working Group. So, you must be having a good understanding about the questions I asked previously in this thread. So, can you please spend some of your valuable time to answer the questions I asked before? It'll be really helpful.
I'm going through the XML Schema 1.1 recommendation to get familiar with the schema. Frankly, lot of things are not understandable by the first reading because I'm new to it. But, I'm hoping to constantly go through it and grab the core concepts of the schema and then the concepts related to PSVI. I'm glad that there's lot of time ahead until the Google Summer of Code coding period begins to cover these things.
> Hi devs,
> I'm a final year undergraduate from University of Moratuwa, and am > interested in applying to Google Summer of Code 2011 with a Xerces2-
> J project. I have some experience in using Xerces, though I'm new to > the Xerces development. I'm very interested to contribute to Xerces > as a developer. > > I've talked with Michael for a possible GSoC idea, and he suggested > on implementing features still lack in the XML Schema 1.1 Xerces > implementation. He pointed towards XERCESJ-1362, "Implementing the > changes to post-schema-validation-infoset in XML Schema 1.1" > feature  filed at JIRA, assuring it hasn't yet implemented. I'm > interested in doing this project because it'll probably achieve my > purpose of getting familiarized with the code-base better. But, I > see that currently, it's reporter Arthur (De Magalhaes) has assigned > it to himself. > > So, first of all, Arthur, I'd like to know whether you are OK with > me picking this. Hoping that Arthur wouldn't mind if I pick this, > I'd like to focus on this idea further. Currently, I'm reading XML > Schema 1.1 recommendation, and the PSVI changes in Schema 1.1  to > get a clear idea about what is needed to be implemented. For that, I > have to understand the current recommendation in XML Schema along > with implementation of PSVI in Xerces. So, I'd appreciate if someone > can answer these questions. > > 1. Any recommended links/suggestions to get to know about the > existing PSVI implementation in Xerces, as well as for the XML > Schema (if any, apart from )
Xerces has an XML Schema API for accessing and querying the PSVI. The most recent version of the API is documented on-line here . The PSVIWriter/PSVIParser , the xs.QueryXS and xs.XSSerializer samples demonstrate how to use it.
> 2. Where does the PSVI implementation reside in the code so that I > can begin poking around? It'll help me to get familiar with the > code-base as well.
The interfaces are located under org.apache.xerces.xs.*. You'll find the implementation under org.apache.xerces.impl.xs.* and org.apache.xerces.impl.dv.xs.* (XSSimpleTypeDecl in particular in the impl.dv.xs package).
> 3. Does the scope of this idea is sufficient/not much/go beyond that > of the GSoC in your opinion? (in terms of time constraint, > difficulty level etc. )
It's been some time since I've looked at the details for XML Schema 1.1. Hoping Sandy will answer here.
> Any answers regarding any of these questions are very much
> Giving some information about myself and some background; I've
> started studying about Xerces development. These days I'm reading
> the Xerces Native Interface, along with few other references.
> Further, I got the Xerces samples working and now I'm debugging them
> to gain an understanding about the internals. I have already
> participated in GSoC 2010 under DocBook Open Repository, where I
> developed the WebHelp XSL Customization for DocBook documents . I
> have contributed to Apache Axiom's DOM module a little as well.
*http://blog.kasunbg.org/search/label/gsoc*<http://blog.kasunbg.org/search/label/gsoc> > > Thanks, > --Kasun > > ~~~*******'''''''''''''*******~~~ > Kasun Gajasinghe, > University of Moratuwa, > Sri Lanka. > Blog: *http://kasunbg.blogspot.com* <http://kasunbg.blogspot.com/> > Twitter: *http://twitter.com/kasunbg* <http://twitter.com/kasunbg>