Mobile Minutes 2008-06-05
From MemberWiki
URL: http://www.openajax.org/member/wiki/Mobile_Minutes_2008-06-05
Contents |
Attendees
- Andrew Sledd, Ikivo
- Guillermo Caudevilla, Vodafone
- Ian Hay, Orange
- John Hardy, Motricity
- Jon Ferraiolo, IBM
- Krishna Sankar, Cisco
- Nikunj Mehta, Oracle
- David Pollington, Vodafone
Minutes
Action Items remaining for the group
- review requirement page and use cases.
Discussion followed and decided that this is optional. So moved to defer.
Add video call as an alternate flow
Discussed and decided to incorporate Rotan’s suggestion – change title and add video call as a sub item. Nikunj to do.
Fast-track exploratory phase post mortem
- Everybody agreed that the group exceeded expectations and the deliverables have value to the industry. The exploratory phase has come to a successful completion.
- Next Steps – a) Start Open Source Shim layer, b) start a wg to develop API architecture and detailed specification
Shim Layer Discussion
Jon discussed the Shim layer
The shim layer is a thin veneer- looks up the system provider, from the system provider looks up implementation for that platform, calls the native API
Nikunj pointed out that this would need changes and might not work in existing browsers as they might not have the API support.
A short discussion followed.
Jon agreed that browser plug-ins or updates would be required.
Nikunj pointed out that we need to set expectations on architecture techniques and evolution. Are we going to take a broad sweep across all APis or are we going to dig deeper on a few APis ? What will be the rate of evolution ?
Jon said that we will take one (or two) scenarios and 2 or 3 APIs in the context of that use case and develop a prototype to be shown in September timeframe. Jon had sent out an e-mail on this – location and Address APIs working together.
Nikunj asked about the relationship of our open source effort with others. He mentioned the philosophy of Apache with regards to APIs external to Apache
Andrew: We will have dialogs as and when necessary and do not plan to redo any work already done. Our goal is to identify important aspects, raise their awareness and provide a way forward
Jon/Nikunj: Gears in particular. Google is a member. We also could possibly add adaptors and plug-ins
Jon: Also need device manufacturers to write the underlying implementations
Nikunj: Do we have device manufacturers willing to donate code ?
Jon: Discussions Yes, Commitments not yet. No commitment from WebKit or Opera or others so far
Andrew: they are monitoring. We should move forward, keep the momentum and lobby/evangelize
Andrew: Is location the good API to start ?
Jon: Discussed demo idea in the mailing list. It has location API as well as address book API
Andrew: This is a good proposal that captures the spirit of the discussions.
Discussion followed. The general consensus was to start working and then evolve. Setup is important. We should give extra weight to folks who are actually working.
A discussion on stricture and process followed.
Jon: Need to setup a project in sourceforge. It is important to pick the right name. device was suggested and accepted.
A discussion on timeframe followed. Decided to kickoff in June and begin work in July. The demo is targeted for the open source in mobile conference in Sept 18. AJAXWorld in Oct 21-22 is another target. David said they might have couple of resources. Vodaphone offered possibility of mobilescript code – need to check.
Quick discussion on the specification work followed.
A good goal is to start the specification work in parallel to the shim implementation. Need to document architectural aspects, structure of the APIs et al.
Andrew/Jon: Let us start discussion in the e-mail list. Will reconvene 2 weeks from now i.e. June 19th 2008.
