On Mon, Mar 10, 2014 at 6:45 PM, Philippe Ombredanne
<[email protected]> wrote:
> On Sun, Mar 9, 2014 at 9:55 PM, ahi <[email protected]> wrote:
>> Well I had C++ originally in mind, but I am also considering Python.
>> Which one would benefit the community the most? They are both
>> widely used languages.
>
> My personal preference would be Python. I am not sure C++ would be the
> best suited language for such processing though C++ is fine too.
> How would go about it with C++?

Well, if you are asking about the language's capabilities there are
plenty of XML
and RDF parser libraries out there in C++ and C such as RapidXML,
TinyXML and Raptor.

as for my plan for the project, I would list the following as the
initial set of features:
- Ability to create new SPDX files.
- Ability to load/import existing SPDX files in RDF/XML or tag/value format.
- Ability to export/save SPDX files in the above formats.
- Ability to manipulate, modify and query all aspects of an SPDX document.

My initial plan would be dividing it into the following milestones:

The first milestone would be the in memory representation, In order to
allow library users to easily modify, manipulate and create SPDX
documents. This is a primary concern and the design needs to be solid
as it will have a great impact on the usability and future of the
library , it needs to be easily extendable to support new features
with upcoming specs. Users should be able to create, modify,
manipulate and query fields of a document such as creation info,
packages,files, licenses ,etc. The first milestone would be designing,
implementing and testing this part.

The second milestone would be all about importing existing SPDX files
in either RDF/XML or tag/value format. The existing Java parser can be
used while testing to ensure correctness.

The third milestone would be concerned with the exporting aspect. The
RDF/XML and tag/value generators should be able to export an SPDX
document, from the first milestone, while testing the parsers from the
previous milestone can be used to verify the output.

On Tue, Mar 11, 2014 at 12:58 AM, Gary O'Neall <[email protected]> wrote:
> +1 on Python - I think that would be a great addition to the SPDX parser
> libraries.

Since there seems to be a greater interest in Python from the
community. I am willing to implement the library using it instead.

-- 
Best Regards,
Ahmed
_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech

Reply via email to