Hi Ahmed, Administratively, I think we should also estabish a few ground rules:
- you should register some public source-code hosting facility - github, etc - as soon as possible, for show-casing your up-coming work and aiding discussion and collaboration. - in general, I expect you to treat this as a summer job. You should write a few words about progress, or thoughts, difficulty encountered, etc, every week or 10 days. Either by posting to the spdx-tech mailing list, or put it up in a blog/wordpress place of your choice, or both. - if you are going to be unresponsive or unreachable by e-mail or otherwise for more than a few days between end of May and August, you should say so now. These are *not* optional - if you fail in any of the above, you fail. As for the actual work itself, besides the suggestions I already made, following the thought on the jython + existing java-work approach, there is also a somewhat similar route via gcj and building the java binding into shared libraries than going C-binding approach. You can also co-ordinate with Nuno on the Go-binding on ideas, etc. Hin-Tak --- On Thu, 24/4/14, Hin-Tak Leung wrote: > From: Hin-Tak Leung > Subject: Re: Google Summer of Code 2014: Ahmed's project > To: "ahi" <[email protected]> > Cc: [email protected] > Date: Thursday, 24 April, 2014, 14:57 > Besides re-using some of > the code-generation and XML/RDF-related > parsing facilities, it just occurs to me that > there is a rather > interesting if cheating > way of going about making > SPDX-related > functionality available to python based work: > use a different python interpreter. > > For most people, python means > CPython (well, the one written > mostly in C), > but there is Jython (or JPython?) and IronPython (java- and > C#- > native respectively) and also some very > odd implementations > like > javascript-based,etc. So it could be quite > straight-forward > to hook up the existing > java-based SPDX functionality to > jython. > > Since that should be > relatively straight-forward, you could also > already starting thinking about what validation > tests are available, > or should be > implemented, assuming you could/might > spend > a few days look into that area. It would also be an > interesting > "reference-implementation", since > full-replacement/compatibility > of the > existing/available SPDX functionalities is what you > should > be aiming for, and nothing beats full > compatibility just by hooking > the existing > libraries. > > Yes, that > requires you to learn enough java to get along, but then > some > familiarity with another language is > always a good thing; and you > probably need > to anyway, since you do need to understand > to some extent the existing mostly java-based > work. > > -------------------------------------------- > On Wed, 23/4/14, Hin-Tak Leung <[email protected]> > wrote: > > Subject: Re: Google Summer > of Code 2014: Ahmed's project > To: > "ahi" <[email protected]> > Date: Wednesday, 23 April, 2014, 23:53 > > https://pypi.python.org/pypi/ctypeslib > https://pypi.python.org/pypi/xmp-tool > > This is 3 years ago, so a > lot > of info might have changed, but could > be useful background > reading: > >http://www.michelepasin.org/blog/2011/02/24/survey-of-pythonic-tools-for-rdf-and-linked-data-programming/ > > > -------------------------------------------- > On Wed, 23/4/14, ahi <[email protected]> > wrote: > > > Subject: Re: Google Summer > of Code 2014: > Ahmed's project > To: [email protected] > Date: Wednesday, 23 April, 2014, 23:20 > > Hello Hin-Tak; > > Thank you for the > quick > reply > and for > taking up my proposal. I > am > looking > forward to > working with you and I am already subscribed > to > the > SPDX-tech > mailing list > for SPDX specific > issues. I was actually > > planning on fully > > > implementing the parser from scratch. I am not > familiar with ctypelib or WSDL, but I am > reading up on them now. > > > On > Thu, Apr 24, 2014 > at 12:01 > AM, Hin-Tak Leung > <[email protected]> > wrote: > > Hi Ahmed, > > > > Welcome to > GSoC. > > > > As a starting > point, > I > hope you are > not thinking of writing a python binding > > > of SPDX by hand one routine at a time > > - > you should looking to > > > > automatic code > > generation such as > ctypelib (which is > capable of > > > > converting c header files into python > > wrapper code), as well as WSDL > > > related > python technology (WSDL is dynamic > typing based on XML > > > exchanges) or > other XML-python code > generation. Do these > > sound > > reasonable > > to > you? > > > > Hin-Tak > > > > > > _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
