W3C home > Mailing lists > Public > www-forms@w3.org > June 2002

AW: XForms processors generalized API

From: Chaudhuri, Hiran (Software AG) <g.s31d05b@lfstad.bayern.de>
Date: Fri, 7 Jun 2002 10:35:55 +0200
Message-ID: <E5027FBFD4E3C34DB0875087976FFE49976D7C@mex1-n2.lfstad.bayern.de>
To: "'Peter V. Mikhalenko'" <xml-dev@sigent.ru>, www-forms@w3.org

Hi, Peter.

Considered the fact that the 'standard' is a working draft and therefore
many implementors keep cautious on changing their code to reflect the latest
changes, I'd appreciate to finish the XForms recommendation before starting
to think of an API.

However the idea of having this API specification is very good.


> -----Ursprungliche Nachricht-----
> Von: Peter V. Mikhalenko [mailto:xml-dev@sigent.ru]
> Gesendet: Mittwoch, 5. Juni 2002 21:48
> An: www-forms@w3.org
> Betreff: XForms processors generalized API
> Hello, members!
> There are some partial XForms WD implementations that can 
> easily be found in
> the net, but each of them is using its own API that is not 
> compatible with
> each other. And at the moment many developers have to wait 
> for the product
> that would implement standard in part they need and that 
> would fit their
> needs.
> In the area of XML parsers, for example, this problem was 
> solved by creating
> some kind of generalized API and after that each parser had 
> to implement
> that interface (Java developers understand me - it is JAXP 
> and other XML
> related APIs (JAXM etc.)). And if I want to change parser, I 
> simply change
> the parser and do not need to change my written code.
> So what do you think, would it be good to create some kind of 
> Java interface
> (for ex. JAFP)?
> __
> Peter V. Mikhalenko
> Lead Developer
> Sigent Interactive Agency
> peter@sigent.ru
Received on Friday, 7 June 2002 04:35:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:06 UTC