Hi Michael,Hi developers,
I am continuing the developments of the streamable subset of
xpointer() scheme.At the moment there are five classes in my development.
1. SchemeHandler
2. XPointerSchemeHandler
3. NameSpaceSchemeHandler
4. XPointerNodeDetails
5. XPointerAttribDetails
- SchemeHandler class implements the XPointerPart interface and it is an
abstract class.
- XPointerSchemeHandler class and NameSpaceSchemeHandler class extend the
SchemeHandler.
- The common methods with similar implementation of the above child
classes are implemented in the parent class
- The parseXPointer() and resolveXPointer() are kept as abstract methods
in the parent class.
- XPointerNodeDetails is for keep nodes which are specified in the
xpointer with their namespaces and their attributes.
- XPointerAttribDetails is for keep attributes which are specified in the
xpointer with their namespaces and values.
I have implemented the parseXPointer() for XPointerSchemeHandler and
NameSpaceSchemeHandler.And also the scanExpr() method for tokenizing the
xpointer and xmlns.
At the moment I just began to implement the resolveXPointer() for xmlns()
scheme.
Thank you very much Michael for
helping me and put me on the right track.
Thank you.
Sanjaya Liyanage.
On Thu, Jul 8, 2010 at 2:23 PM, udayanga wickramasinghe <
[email protected]> wrote:
> Hi Michael , Hi devs,
> XML Schema 1.1 override implementation is progressing and i have been able
> to implement most of the core parts needed for the implementation. One major
> requirement for the xs:override was to perform override transformations on
> a given <schema> document. As i did discuss in this list , my initial
> intention was to use override.xslt[1] style sheet to perform transforms on
> the schema documents. But as it turned out ,currently there is no xslt 2.0
> schema aware processor to do the necessary transformations as specified in
> [1]. Therefore i had to go for a programmatic transformation that does all
> override transformations on a given schema document by passing Elements on a
> Schema Document and doing necessary modifications to the tree itself to
> reflect <override> semantics. However i have also implemented a JAXP
> compatible override transformer which would enable to plug in any
> appropriate xslt processor if need arises in the future.... :-)
>
> Implementation also needs to focus on evaluating dependencies during an
> override transformation path (ie:- A-->B'-->C'-->A'-->B''....) since there
> can be invalid documents generated (bcoz of schema component collisions,etc)
> due to <override> semantics. This also include eliminating any cycles in a
> dependency path. A dependency analysing Implementation is in place for this
> , and Khaled and I are currently in the stage of reviewing the
> implementation code and testing it against different scenarios. Still work
> needs to be done on error/collisions handling , integrating <override>
> transformations with different stages of Xerces schema processor,etc.
>
> I would like to thank Khaled as well for the tremendous support and
> feedback he has provided throughout this period . Btw I attached a recently
> taken patch of my implementation here as well. thanks.
>
> Regards,
> Udayanga
>
> [1]http://www.w3.org/TR/xmlschema11-1/#override-xslt
>
>
> On Thu, Jul 8, 2010 at 9:35 PM, Michael Glavassevich
> <[email protected]>wrote:
>
>> Hi all,
>>
>> It's been awhile since I've seen mailing list discussion on the GSoC
>> projects. Mid-term evaluations are coming up next week. I'm wondering how
>> things are going in general.
>>
>> Ishan / Udayanga / Sanjaya,
>>
>> Can each of you share a bit on your progress? Things you've accomplished?
>> Challenges you might be having, possibly that we could help you with?
>>
>> Thanks.
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: [email protected]
>> E-mail: [email protected]
>>
>
>
>
> --
> http://www.udayangawiki.blogspot.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
