Re: [Keitaidata-devel] licence/xml/format

[Thomas O'D. <to...@no...>]

Hi Nick,

Wish I had some more time to put into this right now, but anyway
here's some quick input.

> 1) Licence.
> 
> If any list member has objections to the LGPL, can they say what it is and
> what licence they would prefer and why?

I'm happy with LGPL.

> 2) XML.
> 
> Can we take this as read? I know there was comment about making something
> that was more Java friendly. My own take on this is that 
> 
> a) XML is widely known and used.
> b) Parse speed of the data is very important in this application. But
> nothing in a form fast enough to be parsed directly "in real time" in one
> language is going to be useful to another language. So we are building a
> data container that can be transformed into a quickly parsable structure
> at run time. E.g, I may write something to parse the xml file into a php
> class, then distribute the php class as well as the xml.
> 
> php and Java are my major interests.
> 
> Do list members have a view on this?

I think XML is the way to go. Its got API bindings in many languages
that I use, python, perl, php, java. Its pretty easy to read XML and 
write a different format if someone requires it. Its easy to read/edit
XML by hand and there are also lots of XML editors out there now.
 
> 3) file formats.

Looking forward to what people come up with but my own opinion is
to keep it as simple as possible so that its easy to edit and 
update without breaking stuff and wondering where the hell a 
new phone fits in some complex mesh.

Shall we start by taking a look at a basic excerpt from kis.xml?
I've not really had a look at it yet.

For those of you who would like to check it out, instructions
are at: http://sourceforge.net/cvs/?group_id=47730

The module name is: kis

Nick, how many are on the maillist?

Tom.
-- 
Thomas O'Dowd. - Nooping - http://nooper.com
to...@no... - Testing - http://nooper.co.jp/labs