Hi everyone,

I'm Mark Pimentel, a computer engineering student from Carnegie
Mellon, and I'm currently doing a Google Summer of Code
(code.google.com) project with Apache Axis 2 on binary XML
serialization.  My original proposal is located online at
http://www.andrew.cmu.edu/user/mpimente/MarkPimentel-SummerOfCode.pdf
.  My project mentor for this project is Eran Chinthaka.

I had some delay in getting started, so I've had to push some items
back on my weekly schedule.  The updated schedule is as follows:


WEEKLY SCHEDULE
Mark Pimentel, Google Summer of Code 2005

Week of July 10th
Conclude research of different formats.  Will submit a document
outlining the major aspects of the two representations that I will be
looking into—Fast Infoset & DFDL.  Am currently targeting Fast Infoset
as the first schema to implement, and DFDL as the second.

Week of July 17th 
Begin implementing a StAX parser to write binary XML data using the
Fast Infoset standard.  This week, I will concentrate on writing the
parser and achieving some type of module with binary serialization
functionality.

Week of July 24th
Will continue to adapt parser to handle the Fast Infoset standard. 
Most of the work this week will be towards expanding supported
language.

Week of July 31th
The goal for this week is to clean up the first parser code, and
perform more extensive testing.  I will also prepare any progress
report information needed by the Google Summer of Code program.

Week of August 3rd
Begin development of parser for DFDL standard.  If similar parts of
the parser from the first can be used, then work from later weeks can
be started.

Week of August 14th
Will continue fleshing out and expanding DFDL support.

Week of August 21st
Aiming for more definite testing and verification of second parser. 
If time permits, I will also start on a third parser.

Week of August 28th
Implementation of third representation, if possible.  Otherwise,
return to first two parsers to ensure correctness and correct any
remaining integration issues.


Thanks,
Mark

Reply via email to