Re: Re(3): Re(2): Re(2): [Keitaidata-devel] licence/xml/format

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

On Wed, Mar 06, 2002 at 08:42:16AM +0900, Nick May wrote:
> Nick May writes:
> >cj...@cy... writes:
> >Not comparatively. I'd bet that can type in the "supports post"
> >attribute for every Docomo, J-phone and AU phone in existence in
> >far less time than it would take me to devise a clever inheritance
> >scheme for this parameter.
> >
> 
> "supports post" is simply an example. (It is not supported by most/all
> jphone) There are 20 odd additional parameters of a similar type. Most of
> which can be handled with a simple inheritence scheme. 
> 
> I agree that a clever inheritance scheme is more trouble than it is worth.
> But a simple inheritance scheme IS worthwhile. There are lots of things
> that all imode phones have in common - and they should go in to something
> inherited rather than be typed in each time. "post" is one such example.
> As is "supports gif." As are the number of form elements (differs slightly
> from level1 imode html and level2 imode html.) and numerous other
> parameters. 
> 
> An inheritance scheme based around Docomo's html-tag support seems quite
> "simple", but effective.

I'd tend to agree with that. i-mode calls it HTML Version 1.0, 2.0, 3.0.
It incorporates the minimal support that a phone has for i-mode. Of course
we're not only dealing with i-mode here, so it makes sense to also look
at this globally. As Curt said earlier, once this stuff is in the system
we don't have to edit it much anyway so we don't exactly have to worry
about typing.

What do you mostly want though when serving to handsets... I'm thinking
that most peoples requirements are simple, if its i-mode, they probably
know the basic tags it supports, they want to know screen resolution
and number of characters across. For sound they want to know the chip
but mostly the needs are quite basic so I'm wondering exactly how much
detail we do want to go into. 

As for java/foma capabilities and other stuff that will be added in the
future, I'd keep them in each phone defination. Perhaps some kind of
capability tag. This looks like it would be quite long to get all the
different characteristics in there.

<java name="iAppli" version="1.0" maxsize="10k" maxdata="10k" network="http"...>

It all depends on how much detail we want in there like the fact that
some phones have different bugs, like the P503i with the date problem
etc.

Cheers,

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