From jferrai at us.ibm.com Wed Jan 2 10:02:01 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 2 Jan 2008 10:02:01 -0800 Subject: [OpenAjaxMobile] New chair(s) for Mobile TF Message-ID: Happy New Year! As you should all know by now, we are sorry about losing Rhys Lewis as chair of the Mobile TF as he has moved onto a different company and new challenges. Therefore, we need to find a new chair for the Mobile TF. David Boloker of IBM, who was instrumental in pulling together the industry to form OpenAjax Alliance and who is chair of the OpenAjax Alliance Steering Committee, has volunteered to become chair of the Mobile TF. David is willing to share to the responsibility if anyone else is willing and able to help out. David has a strong interest and commitment to pushing progress within OpenAjax Alliance on the Mobile Ajax front, partly because IBM is seeing strong interest from customers in Mobile Ajax as an important emerging technology. Please reply if you have an interest in co-chairing the Mobile TF with David. Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080102/524f6f08/attachment.html From louenas.hamdi at sap.com Wed Jan 2 10:22:42 2008 From: louenas.hamdi at sap.com (Hamdi, Louenas) Date: Wed, 2 Jan 2008 13:22:42 -0500 Subject: [OpenAjaxMobile] New chair(s) for Mobile TF In-Reply-To: References: Message-ID: <6644EC646571D04DA95850E3D803903A05214F6A@usphle12.phl.sap.corp> Hi John, Happy new year to you too J Do you have a reference for your statement below in bold? I'm looking for these kind of statements. Cheers, Louenas From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: Wednesday, Jan 02, 2008 13:02 PM To: mobile at openajax.org Subject: [OpenAjaxMobile] New chair(s) for Mobile TF Happy New Year! As you should all know by now, we are sorry about losing Rhys Lewis as chair of the Mobile TF as he has moved onto a different company and new challenges. Therefore, we need to find a new chair for the Mobile TF. David Boloker of IBM, who was instrumental in pulling together the industry to form OpenAjax Alliance and who is chair of the OpenAjax Alliance Steering Committee, has volunteered to become chair of the Mobile TF. David is willing to share to the responsibility if anyone else is willing and able to help out. David has a strong interest and commitment to pushing progress within OpenAjax Alliance on the Mobile Ajax front, partly because "IBM is seeing strong interest from customers in Mobile Ajax as an important emerging technology". Please reply if you have an interest in co-chairing the Mobile TF with David. Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080102/6b1b281e/attachment.html From jferrai at us.ibm.com Wed Jan 2 11:00:37 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 2 Jan 2008 11:00:37 -0800 Subject: [OpenAjaxMobile] New chair(s) for Mobile TF In-Reply-To: <6644EC646571D04DA95850E3D803903A05214F6A@usphle12.phl.sap.corp> Message-ID: Hi Louenas, I don't have any public URLs that I can point to that shows increased customer interest in Mobile Ajax. Most of my personal knowledge comes from word of mouth, such as talking to people at trade shows, talking with some of my colleagues at IBM about some of the mobile projects that are in process with some leading edge customers, and observing various web sites that are providing specialized user interfaces for selected mobile platforms such as the iPhone. Jon "Hamdi, Louenas" To Sent by: "OpenAjax Alliance discussion list mobile-bounces at op on Mobile Ajax" enajax.org cc 01/02/2008 10:22 Subject AM Re: [OpenAjaxMobile] New chair(s) for Mobile TF Please respond to OpenAjax Alliance discussion list on Mobile Ajax Hi John, Happy new year to you too J Do you have a reference for your statement below in bold? I?m looking for these kind of statements. Cheers, Louenas From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: Wednesday, Jan 02, 2008 13:02 PM To: mobile at openajax.org Subject: [OpenAjaxMobile] New chair(s) for Mobile TF Happy New Year! As you should all know by now, we are sorry about losing Rhys Lewis as chair of the Mobile TF as he has moved onto a different company and new challenges. Therefore, we need to find a new chair for the Mobile TF. David Boloker of IBM, who was instrumental in pulling together the industry to form OpenAjax Alliance and who is chair of the OpenAjax Alliance Steering Committee, has volunteered to become chair of the Mobile TF. David is willing to share to the responsibility if anyone else is willing and able to help out. David has a strong interest and commitment to pushing progress within OpenAjax Alliance on the Mobile Ajax front, partly because ?IBM is seeing strong interest from customers in Mobile Ajax as an important emerging technology?. Please reply if you have an interest in co-chairing the Mobile TF with David. Thanks. Jon_______________________________________________ mobile mailing list mobile at openajax.org http://openajax.org/mailman/listinfo/mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080102/3e1b892c/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available Url : http://openajax.org/pipermail/mobile/attachments/20080102/3e1b892c/attachment-0003.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: pic13968.gif Type: image/gif Size: 1255 bytes Desc: not available Url : http://openajax.org/pipermail/mobile/attachments/20080102/3e1b892c/attachment-0004.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available Url : http://openajax.org/pipermail/mobile/attachments/20080102/3e1b892c/attachment-0005.gif From jferrai at us.ibm.com Wed Jan 2 11:43:09 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 2 Jan 2008 11:43:09 -0800 Subject: [OpenAjaxMobile] First draft of Mobile Ajax White Paper Message-ID: Hi everyone, Rick Saletta has come through in grand fashion (Thanks, Rick!) and has pulled together a first draft of the Mobile Ajax White Paper. He sent the contents to me privately and I have converted it to wiki format and uploaded it to the white paper wiki page: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax I did a first pass review and included various inline comments about the white paper. I encourage everyone to add their own comments and suggestions to that wiki page. Rick, feel free to edit the document as you see fit based on comments you see on the wiki page. I assume we will have a phone call sometime in January to discuss various issues, but given that not everyone is back from holiday yet, I'm not sure when the next phone call will be. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080102/e101e45c/attachment.html From RSaletta at wavemaker.com Wed Jan 2 12:01:11 2008 From: RSaletta at wavemaker.com (Rick Saletta) Date: Wed, 2 Jan 2008 12:01:11 -0800 Subject: [OpenAjaxMobile] First draft of Mobile Ajax White Paper In-Reply-To: References: Message-ID: Thanks Jon, Folks, the content provided now flows with a more singular voice but there are a couple areas of the document that need to be strengthened. Does anyone intend to contribute additional content before a final edit pass is taken? If so, please let us know ASAP. Rick Rick Saletta Director of Marketing & Product Mgmt. WaveMaker M:650.218.9090 RSaletta at wavemaker.com On Jan 2, 2008, at 11:43 AM, Jon Ferraiolo wrote: > Hi everyone, > Rick Saletta has come through in grand fashion (Thanks, Rick!) and > has pulled together a first draft of the Mobile Ajax White Paper. > He sent the contents to me privately and I have converted it to > wiki format and uploaded it to the white paper wiki page: > > * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax > > I did a first pass review and included various inline comments > about the white paper. I encourage everyone to add their own > comments and suggestions to that wiki page. Rick, feel free to edit > the document as you see fit based on comments you see on the wiki > page. I assume we will have a phone call sometime in January to > discuss various issues, but given that not everyone is back from > holiday yet, I'm not sure when the next phone call will be. > > Jon > > > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080102/948b34c6/attachment.html From jferrai at us.ibm.com Tue Jan 8 07:14:50 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 8 Jan 2008 07:14:50 -0800 Subject: [OpenAjaxMobile] No meeting this week Message-ID: We won't have a Mobile TF phone call this week. We will resume phone calls sometime in January, but I need to coordinate with our new chair, David, to start finding a time slot that works for most people. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080108/aca02ce8/attachment.html From jferrai at us.ibm.com Tue Jan 15 16:22:28 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 15 Jan 2008 16:22:28 -0800 Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phone call Message-ID: Hi everyone, I am sending this email on behalf of our new Mobile TF chair, David Boloker. David and I have been coordinating on a date/time for the next phone call and are proposing the following: Date: Thursday Jan. 24 Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris Toll Free: 1-877-422-0052 Toll: 1-314-655-1417 Participant Pin access code: 142380 Please RSVP about this proposed time slot. If this time doesn't work for enough people, then we will have to try to find a time slot on the following week (Jan 28). The primary topic will be the Mobile Ajax white paper: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Rick Saletta has put in a lot of effort on the above white paper, so we now have a complete initial draft. Charles McCathie-Nevile and I have inserted feedback comments. I encourage others to review the current draft and also insert feedback comments inline within the above wiki page. That will help make the meeting more productive. Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080115/a7f67bde/attachment.html From chaals at opera.com Tue Jan 15 18:13:53 2008 From: chaals at opera.com (Charles McCathieNevile) Date: Wed, 16 Jan 2008 03:13:53 +0100 Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phone call In-Reply-To: References: Message-ID: On Wed, 16 Jan 2008 01:22:28 +0100, Jon Ferraiolo wrote: > > > Hi everyone, > I am sending this email on behalf of our new Mobile TF chair, David > Boloker. David and I have been coordinating on a date/time for the next > phone call and are proposing the following: > > Date: Thursday Jan. 24 > Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris > Toll Free: 1-877-422-0052 > Toll: 1-314-655-1417 > Participant Pin access code: 142380 > > Please RSVP about this proposed time slot. Ouch. 5am Melbourne, where I will be. Although I have not attended many calls, I have followed this document. A less-horrible time outside australian business hours would suit me better... cheers chaals -- Charles McCathieNevile Opera Software, Standards Group je parle fran?ais -- hablo espa?ol -- jeg l?rer norsk http://my.opera.com/chaals Try Opera 9.5: http://snapshot.opera.com From Torkel.Hambraeus at ikivo.com Tue Jan 15 23:25:26 2008 From: Torkel.Hambraeus at ikivo.com (Torkel Hambraeus) Date: Wed, 16 Jan 2008 08:25:26 +0100 Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phone call In-Reply-To: References: Message-ID: <234EB4699C751A4A95DF4FD8D041BBFDB33E0B@SESTHSRV10.zoomon.local> Time works fine for me. Are there any European numbers available to reach the bridge? That would be positive for my phone bill. /Torkel ________________________________ From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: den 16 januari 2008 01:22 To: mobile at openajax.org Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phone call Hi everyone, I am sending this email on behalf of our new Mobile TF chair, David Boloker. David and I have been coordinating on a date/time for the next phone call and are proposing the following: Date: Thursday Jan. 24 Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris Toll Free: 1-877-422-0052 Toll: 1-314-655-1417 Participant Pin access code: 142380 Please RSVP about this proposed time slot. If this time doesn't work for enough people, then we will have to try to find a time slot on the following week (Jan 28). The primary topic will be the Mobile Ajax white paper: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Rick Saletta has put in a lot of effort on the above white paper, so we now have a complete initial draft. Charles McCathie-Nevile and I have inserted feedback comments. I encourage others to review the current draft and also insert feedback comments inline within the above wiki page. That will help make the meeting more productive. Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080116/cdfb8997/attachment.html From rotan.hanrahan at mobileaware.com Wed Jan 16 04:24:42 2008 From: rotan.hanrahan at mobileaware.com (Rotan Hanrahan) Date: Wed, 16 Jan 2008 07:24:42 -0500 Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phonecall References: <234EB4699C751A4A95DF4FD8D041BBFDB33E0B@SESTHSRV10.zoomon.local> Message-ID: Totally agree :) We've cut teleconference costs substantially by using VoIP. Of course, now the number of calls per week has gone up substantially. The bridge for the Mobile TF will not accept an incoming connection from a VoIP source, so this does present a bit of a problem. Skype anyone? ---Rotan. ________________________________ From: mobile-bounces at openajax.org on behalf of Torkel Hambraeus Sent: Wed 16/01/2008 07:25 To: OpenAjax Alliance discussion list on Mobile Ajax Subject: Re: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phonecall Time works fine for me. Are there any European numbers available to reach the bridge? That would be positive for my phone bill. /Torkel ________________________________ From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: den 16 januari 2008 01:22 To: mobile at openajax.org Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phone call Hi everyone, I am sending this email on behalf of our new Mobile TF chair, David Boloker. David and I have been coordinating on a date/time for the next phone call and are proposing the following: Date: Thursday Jan. 24 Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris Toll Free: 1-877-422-0052 Toll: 1-314-655-1417 Participant Pin access code: 142380 Please RSVP about this proposed time slot. If this time doesn't work for enough people, then we will have to try to find a time slot on the following week (Jan 28). The primary topic will be the Mobile Ajax white paper: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Rick Saletta has put in a lot of effort on the above white paper, so we now have a complete initial draft. Charles McCathie-Nevile and I have inserted feedback comments. I encourage others to review the current draft and also insert feedback comments inline within the above wiki page. That will help make the meeting more productive. Thanks. Jon From jferrai at us.ibm.com Wed Jan 16 09:27:12 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 16 Jan 2008 09:27:12 -0800 Subject: [OpenAjaxMobile] Phone bridges In-Reply-To: Message-ID: Hi Rotan, Chaals, Torkel and others, At the moment I don't have any suggestions for how to lower expenses for people calling in from Europe and Australia. I don't think Skype is a viable option because (from what I can tell) it only supports 9 people on a conference call and the moderator has to know which 9 people will be attending and then actively dial each of the 9 people. Given how loosey goosey things are at OpenAjax, I don't think such an approach is workable. Because OpenAjax Alliance collects no fees and therefore has no money to spend, it is dependent on the generosity of its members for phone bridges. We have been using IBM's bridge, with IBM footing the bills. I am now trying to figure out if there is another IBM voice bridge system with toll-free European and Australian call-in numbers. (You'd think IBM would have such a system, but it turns out that all internal phone calls use an internal VOIP network.) For the time being, let's assume that I can't figure out anything in time for this next phone call, therefore people outside of the US will get punished, but I will try to find alternatives that won't punish in the future. If anyone has suggestions for alternative strategies, please speak up. Jon "Rotan Hanrahan" To Sent by: "OpenAjax Alliance discussion list mobile-bounces at op on Mobile Ajax" enajax.org cc 01/16/2008 04:24 Subject AM Re: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phonecall Please respond to OpenAjax Alliance discussion list on Mobile Ajax Totally agree :) We've cut teleconference costs substantially by using VoIP. Of course, now the number of calls per week has gone up substantially. The bridge for the Mobile TF will not accept an incoming connection from a VoIP source, so this does present a bit of a problem. Skype anyone? ---Rotan. ________________________________ From: mobile-bounces at openajax.org on behalf of Torkel Hambraeus Sent: Wed 16/01/2008 07:25 To: OpenAjax Alliance discussion list on Mobile Ajax Subject: Re: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phonecall Time works fine for me. Are there any European numbers available to reach the bridge? That would be positive for my phone bill. /Torkel ________________________________ From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: den 16 januari 2008 01:22 To: mobile at openajax.org Subject: [OpenAjaxMobile] Please RSVP: Proposed date/time for next phone call Hi everyone, I am sending this email on behalf of our new Mobile TF chair, David Boloker. David and I have been coordinating on a date/time for the next phone call and are proposing the following: Date: Thursday Jan. 24 Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris Toll Free: 1-877-422-0052 Toll: 1-314-655-1417 Participant Pin access code: 142380 Please RSVP about this proposed time slot. If this time doesn't work for enough people, then we will have to try to find a time slot on the following week (Jan 28). The primary topic will be the Mobile Ajax white paper: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Rick Saletta has put in a lot of effort on the above white paper, so we now have a complete initial draft. Charles McCathie-Nevile and I have inserted feedback comments. I encourage others to review the current draft and also insert feedback comments inline within the above wiki page. That will help make the meeting more productive. Thanks. Jon _______________________________________________ mobile mailing list mobile at openajax.org http://openajax.org/mailman/listinfo/mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080116/61e638c4/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available Url : http://openajax.org/pipermail/mobile/attachments/20080116/61e638c4/attachment-0003.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: pic21625.gif Type: image/gif Size: 1255 bytes Desc: not available Url : http://openajax.org/pipermail/mobile/attachments/20080116/61e638c4/attachment-0004.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available Url : http://openajax.org/pipermail/mobile/attachments/20080116/61e638c4/attachment-0005.gif From jferrai at us.ibm.com Thu Jan 17 13:48:25 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Thu, 17 Jan 2008 13:48:25 -0800 Subject: [OpenAjaxMobile] New international toll-free call-in numbers Message-ID: Hi everyone, We now have international toll-free numbers for the Jan. 24th phone call. See below for the passcode and the various toll-free numbers that are available for various countries. Charles, Sorry about how early this phone call is on the 24th. I think we need to have this phone call anyway because all other replies were positive. If you can't get up for the phone call, then perhaps you can send as many of your opinions on the white paper either via email or by adding additional comments to the white paper's wiki page. Going forward, let's try to shift the meeting later in the day. Thanks. Jon Next Conference Call Date: Thursday Jan. 24 Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris Agenda White paper: http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax See below for call-in information. Conference Call PIN and Phone Numbers Passcode: 460566 Conference Access: Toll free: 1-888-619-1583 Toll: 1-719-457-1414 International toll free - Argentina: 0800 666 3149 International toll free - Australia: 1 800 105 680 International toll free - Austria: 0 800 291 941 International toll free - Belgium: 0 800 75 240 International toll free - Chile: 123 0020 9725 International toll free - China, Northern Region: 10 800 714 1201 International toll free - China, Southern Region: 10 800 140 1180 International toll free - Colombia: 01 800 518 0789 International toll free - Costa Rica: 0800 015 0616 International toll free - Czech Republic: 800 700 294 International toll free - Denmark: 80 886 215 International toll free - Dominican Republic: 1 888 751 4488 International toll free - Ecuador: 1 800 020 321 International toll free - France: 0 800 90 0161 International toll free - Germany: 0 800 181 9019 International toll free - Greece: 00 800 161 2205 5955 International toll free - Hong Kong: 800 901 110 International toll free - Hungary: 06 800 162 50 International toll free - India: 000 800 1006 980 International toll free - Indonesia: 001 803 017 5955 International toll free - Ireland: 1 800 760 547 International toll free - Israel: 1 809 246 041 International toll free - Italy: 800 873 739 International toll free - Japan: 00531 16 0844 International toll free - Lithuania: 8 800 3 05 25 International toll free - Luxembourg: 800 2 7665 International toll free - Malaysia: 1 800 813 714 International toll free - Mexico: 001 800 514 5955 International toll free - Monaco: 800 93 416 International toll free - Netherlands: 0 800 023 5303 International toll free - New Zealand: 0 800 451 015 International toll free - Norway: 800 196 65 International toll free - Panama: 00 800 226 5955 International toll free - Poland: 00 800 111 49 58 International toll free - Portugal: 800 819 728 International toll free - Russia: 810 800 2704 1012 International toll free - Singapore: 800 101 2002 International toll free - Slovenia: 0 800 80203 International toll free - South Africa: 0 800 980 988 International toll free - South Korea: 003 0813 1963 International toll free - Spain: 900 947 604 International toll free - Sweden: 02 079 7556 International toll free - Switzerland: 0 800 564 397 International toll free - Thailand: 001 800 156 205 5955 International toll free - Trinidad-Tobago: 1 800 205 5955 International toll free - UK: 0 808 101 1146 International toll free - Uruguay: 0004 019 0188 International toll free - Venezuela: 0 800 100 8300 IRC channel IRC channel: irc.freenode.net, #oaa-mobile Free online IRC client: http://java.freenode.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080117/b07db873/attachment.html From chaals at opera.com Thu Jan 17 16:42:25 2008 From: chaals at opera.com (Charles McCathieNevile) Date: Fri, 18 Jan 2008 01:42:25 +0100 Subject: [OpenAjaxMobile] New international toll-free call-in numbers In-Reply-To: References: Message-ID: On Thu, 17 Jan 2008 22:48:25 +0100, Jon Ferraiolo wrote: > Hi everyone, > We now have international toll-free numbers for the Jan. 24th phone call. > See below for the passcode and the various toll-free numbers that are > available for various countries. Wow! Impressive list. I am curious that Finland isn't on it though, given such a large set of countries that are. But not curious enough to worry about it. > Charles, > Sorry about how early this phone call is on the 24th. I think we need to > have this phone call anyway because all other replies were positive. If > you can't get up for the phone call, then perhaps you can send as many > of your opinions on the white paper either via email or by adding > additional > comments to the white paper's wiki page. I will try to do this > Going forward, let's try to shift the meeting later in the day. Actually, I am normally in Europe these days - this was just a one-off bit of pain. Cheers Chaals -- Charles McCathieNevile Opera Software, Standards Group je parle fran?ais -- hablo espa?ol -- jeg l?rer norsk http://my.opera.com/chaals Try Opera 9.5: http://snapshot.opera.com From jferrai at us.ibm.com Wed Jan 23 14:15:32 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 23 Jan 2008 14:15:32 -0800 Subject: [OpenAjaxMobile] Tomorrow's phone call Message-ID: Hi everyone, Here is the agenda and call-in information for the Mobile TF phone call tomorrow. We will start off with a brief (5-15 minutes) introduction and discussion of a recent Vodafone document that explains what they feel needs to be done with the Web Runtime (i.e., the HTML/Ajax engine) to satisfy the community's requirements. Then we will spend the rest of the time going through the Mobile Ajax white paper. If we need more than one phone call to go through the white paper, then I suggest we have another phone call soon to keep going on the white paper. (Apologies to Rick and everyone else for the white paper not moving very much for a few weeks, but it did allow time for feedback comments. BTW - I encourage others to review and insert feedback comments onto the white paper wiki page.) Jon Next Conference Call Date: Thursday Jan. 24 Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris Agenda Vodafone paper on what's needed with Web Runtime on mobile devices http://www.openajax.org/member/wiki/Image:Vodafone_Web_Runtimes.pdf White paper: http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax See below for call-in information. Conference Call PIN and Phone Numbers Passcode: 460566 Conference Access: Toll free: 1-888-619-1583 Toll: 1-719-457-1414 International toll free - Argentina: 0800 666 3149 International toll free - Australia: 1 800 105 680 International toll free - Austria: 0 800 291 941 International toll free - Belgium: 0 800 75 240 International toll free - Chile: 123 0020 9725 International toll free - China, Northern Region: 10 800 714 1201 International toll free - China, Southern Region: 10 800 140 1180 International toll free - Colombia: 01 800 518 0789 International toll free - Costa Rica: 0800 015 0616 International toll free - Czech Republic: 800 700 294 International toll free - Denmark: 80 886 215 International toll free - Dominican Republic: 1 888 751 4488 International toll free - Ecuador: 1 800 020 321 International toll free - France: 0 800 90 0161 International toll free - Germany: 0 800 181 9019 International toll free - Greece: 00 800 161 2205 5955 International toll free - Hong Kong: 800 901 110 International toll free - Hungary: 06 800 162 50 International toll free - India: 000 800 1006 980 International toll free - Indonesia: 001 803 017 5955 International toll free - Ireland: 1 800 760 547 International toll free - Israel: 1 809 246 041 International toll free - Italy: 800 873 739 International toll free - Japan: 00531 16 0844 International toll free - Lithuania: 8 800 3 05 25 International toll free - Luxembourg: 800 2 7665 International toll free - Malaysia: 1 800 813 714 International toll free - Mexico: 001 800 514 5955 International toll free - Monaco: 800 93 416 International toll free - Netherlands: 0 800 023 5303 International toll free - New Zealand: 0 800 451 015 International toll free - Norway: 800 196 65 International toll free - Panama: 00 800 226 5955 International toll free - Poland: 00 800 111 49 58 International toll free - Portugal: 800 819 728 International toll free - Russia: 810 800 2704 1012 International toll free - Singapore: 800 101 2002 International toll free - Slovenia: 0 800 80203 International toll free - South Africa: 0 800 980 988 International toll free - South Korea: 003 0813 1963 International toll free - Spain: 900 947 604 International toll free - Sweden: 02 079 7556 International toll free - Switzerland: 0 800 564 397 International toll free - Thailand: 001 800 156 205 5955 International toll free - Trinidad-Tobago: 1 800 205 5955 International toll free - UK: 0 808 101 1146 International toll free - Uruguay: 0004 019 0188 International toll free - Venezuela: 0 800 100 8300 IRC channel IRC channel: irc.freenode.net, #oaa-mobile Free online IRC client: http://java.freenode.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080123/126e4b84/attachment.html From ajit.jaokar at futuretext.com Thu Jan 24 10:01:24 2008 From: ajit.jaokar at futuretext.com (Ajit Jaokar) Date: Thu, 24 Jan 2008 18:01:24 +0000 Subject: [OpenAjaxMobile] cant dial in .. Message-ID: <9e4f714f0801241001q73066c3cl882e0374f420aaa8@mail.gmail.com> Hi Jon I cant seem to dial in. Is the number correct? rgds Ajit On 23/01/2008, Jon Ferraiolo wrote: > > > Hi everyone, > Here is the agenda and call-in information for the Mobile TF phone call > tomorrow. > > We will start off with a brief (5-15 minutes) introduction and discussion > of a recent Vodafone document that explains what they feel needs to be done > with the Web Runtime (i.e., the HTML/Ajax engine) to satisfy the community's > requirements. Then we will spend the rest of the time going through the > Mobile Ajax white paper. If we need more than one phone call to go through > the white paper, then I suggest we have another phone call soon to keep > going on the white paper. (Apologies to Rick and everyone else for the white > paper not moving very much for a few weeks, but it did allow time for > feedback comments. BTW - I encourage others to review and insert feedback > comments onto the white paper wiki page.) > > Jon > > Next Conference Call > > > Date: Thursday Jan. 24 > Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris > Agenda > > > Vodafone paper on what's needed with Web Runtime on mobile devices > > > http://www.openajax.org/member/wiki/Image:Vodafone_Web_Runtimes.pdf > White paper: > http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax See > below for call-in information. > > > Conference Call PIN and Phone Numbers > Passcode: 460566 > > Conference Access: > Toll free: 1-888-619-1583 > Toll: 1-719-457-1414 > > International toll free - Argentina: 0800 666 3149 > International toll free - Australia: 1 800 105 680 > International toll free - Austria: 0 800 291 941 > International toll free - Belgium: 0 800 75 240 > International toll free - Chile: 123 0020 9725 > International toll free - China, Northern Region: 10 800 714 1201 > International toll free - China, Southern Region: 10 800 140 1180 > International toll free - Colombia: 01 800 518 0789 > International toll free - Costa Rica: 0800 015 0616 > International toll free - Czech Republic: 800 700 294 > International toll free - Denmark: 80 886 215 > International toll free - Dominican Republic: 1 888 751 4488 > International toll free - Ecuador: 1 800 020 321 > International toll free - France: 0 800 90 0161 > International toll free - Germany: 0 800 181 9019 > International toll free - Greece: 00 800 161 2205 5955 > International toll free - Hong Kong: 800 901 110 > International toll free - Hungary: 06 800 162 50 > International toll free - India: 000 800 1006 980 > International toll free - Indonesia: 001 803 017 5955 > International toll free - Ireland: 1 800 760 547 > International toll free - Israel: 1 809 246 041 > International toll free - Italy: 800 873 739 > International toll free - Japan: 00531 16 0844 > International toll free - Lithuania: 8 800 3 05 25 > International toll free - Luxembourg: 800 2 7665 > International toll free - Malaysia: 1 800 813 714 > International toll free - Mexico: 001 800 514 5955 > International toll free - Monaco: 800 93 416 > International toll free - Netherlands: 0 800 023 5303 > International toll free - New Zealand: 0 800 451 015 > International toll free - Norway: 800 196 65 > International toll free - Panama: 00 800 226 5955 > International toll free - Poland: 00 800 111 49 58 > International toll free - Portugal: 800 819 728 > International toll free - Russia: 810 800 2704 1012 > International toll free - Singapore: 800 101 2002 > International toll free - Slovenia: 0 800 80203 > International toll free - South Africa: 0 800 980 988 > International toll free - South Korea: 003 0813 1963 > International toll free - Spain: 900 947 604 > International toll free - Sweden: 02 079 7556 > International toll free - Switzerland: 0 800 564 397 > International toll free - Thailand: 001 800 156 205 5955 > International toll free - Trinidad-Tobago: 1 800 205 5955 > International toll free - UK: 0 808 101 1146 > International toll free - Uruguay: 0004 019 0188 > International toll free - Venezuela: 0 800 100 8300 > > > IRC channel > > > IRC channel: irc.freenode.net, #oaa-mobile > Free online IRC client: http://java.freenode.net/ > > > > > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile > > From ryan at elooMobile.com Thu Jan 24 10:29:58 2008 From: ryan at elooMobile.com (Ryan XU) Date: Fri, 25 Jan 2008 02:29:58 +0800 Subject: [OpenAjaxMobile] cant dial in .. In-Reply-To: <9e4f714f0801241001q73066c3cl882e0374f420aaa8@mail.gmail.com> Message-ID: <200801241821.m0OIL1eg024482@server.eloomobile.com> Please review this article from Drucker Associates: http://www.drucker-associates.com/MUE.htm From zuojihong at elooMobile.com Thu Jan 24 10:13:20 2008 From: zuojihong at elooMobile.com (zuojihong) Date: Fri, 25 Jan 2008 02:13:20 +0800 Subject: [OpenAjaxMobile] =?gb2312?B?tPC4tDogW09wZW5BamF4TW9iaWxlXSBjYW50IGRpYWwgaW4gLi4=?= In-Reply-To: <9e4f714f0801241001q73066c3cl882e0374f420aaa8@mail.gmail.com> References: <9e4f714f0801241001q73066c3cl882e0374f420aaa8@mail.gmail.com> Message-ID: <004901c85eb4$cdbf7520$3f01a8c0@zuojhoffice> Same problem with me:( Regards, Jihong ZUO -----????????----- ??????: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] ?? ?? Ajit Jaokar ????????: 2008??1??25?? 2:01 ??????: OpenAjax Alliance discussion list on Mobile Ajax; Jon Ferraiolo ????: [OpenAjaxMobile] cant dial in .. Hi Jon I cant seem to dial in. Is the number correct? rgds Ajit On 23/01/2008, Jon Ferraiolo wrote: > > > Hi everyone, > Here is the agenda and call-in information for the Mobile TF phone call > tomorrow. > > We will start off with a brief (5-15 minutes) introduction and discussion > of a recent Vodafone document that explains what they feel needs to be done > with the Web Runtime (i.e., the HTML/Ajax engine) to satisfy the community's > requirements. Then we will spend the rest of the time going through the > Mobile Ajax white paper. If we need more than one phone call to go through > the white paper, then I suggest we have another phone call soon to keep > going on the white paper. (Apologies to Rick and everyone else for the white > paper not moving very much for a few weeks, but it did allow time for > feedback comments. BTW - I encourage others to review and insert feedback > comments onto the white paper wiki page.) > > Jon > > Next Conference Call > > > Date: Thursday Jan. 24 > Time: 10amPT, 1pmET, 6pm GMT, 7pm Paris > Agenda > > > Vodafone paper on what's needed with Web Runtime on mobile devices > > > http://www.openajax.org/member/wiki/Image:Vodafone_Web_Runtimes.pdf > White paper: > http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax See > below for call-in information. > > > Conference Call PIN and Phone Numbers > Passcode: 460566 > > Conference Access: > Toll free: 1-888-619-1583 > Toll: 1-719-457-1414 > > International toll free - Argentina: 0800 666 3149 > International toll free - Australia: 1 800 105 680 > International toll free - Austria: 0 800 291 941 > International toll free - Belgium: 0 800 75 240 > International toll free - Chile: 123 0020 9725 > International toll free - China, Northern Region: 10 800 714 1201 > International toll free - China, Southern Region: 10 800 140 1180 > International toll free - Colombia: 01 800 518 0789 > International toll free - Costa Rica: 0800 015 0616 > International toll free - Czech Republic: 800 700 294 > International toll free - Denmark: 80 886 215 > International toll free - Dominican Republic: 1 888 751 4488 > International toll free - Ecuador: 1 800 020 321 > International toll free - France: 0 800 90 0161 > International toll free - Germany: 0 800 181 9019 > International toll free - Greece: 00 800 161 2205 5955 > International toll free - Hong Kong: 800 901 110 > International toll free - Hungary: 06 800 162 50 > International toll free - India: 000 800 1006 980 > International toll free - Indonesia: 001 803 017 5955 > International toll free - Ireland: 1 800 760 547 > International toll free - Israel: 1 809 246 041 > International toll free - Italy: 800 873 739 > International toll free - Japan: 00531 16 0844 > International toll free - Lithuania: 8 800 3 05 25 > International toll free - Luxembourg: 800 2 7665 > International toll free - Malaysia: 1 800 813 714 > International toll free - Mexico: 001 800 514 5955 > International toll free - Monaco: 800 93 416 > International toll free - Netherlands: 0 800 023 5303 > International toll free - New Zealand: 0 800 451 015 > International toll free - Norway: 800 196 65 > International toll free - Panama: 00 800 226 5955 > International toll free - Poland: 00 800 111 49 58 > International toll free - Portugal: 800 819 728 > International toll free - Russia: 810 800 2704 1012 > International toll free - Singapore: 800 101 2002 > International toll free - Slovenia: 0 800 80203 > International toll free - South Africa: 0 800 980 988 > International toll free - South Korea: 003 0813 1963 > International toll free - Spain: 900 947 604 > International toll free - Sweden: 02 079 7556 > International toll free - Switzerland: 0 800 564 397 > International toll free - Thailand: 001 800 156 205 5955 > International toll free - Trinidad-Tobago: 1 800 205 5955 > International toll free - UK: 0 808 101 1146 > International toll free - Uruguay: 0004 019 0188 > International toll free - Venezuela: 0 800 100 8300 > > > IRC channel > > > IRC channel: irc.freenode.net, #oaa-mobile > Free online IRC client: http://java.freenode.net/ > > > > > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile > > _______________________________________________ mobile mailing list mobile at openajax.org http://openajax.org/mailman/listinfo/mobile From jferrai at us.ibm.com Thu Jan 24 15:33:09 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Thu, 24 Jan 2008 15:33:09 -0800 Subject: [OpenAjaxMobile] White paper has been split as we discussed at today's phone call Message-ID: I have created 11 separate wiki pages for the various sections in our white paper. The table of contents is found at the top of the existing white paper wiki page: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Here is a list of the wiki pages that I created: MobileAjaxWhitePaper Title MobileAjaxWhitePaper Introduction MobileAjaxWhitePaper Characterizing Mobile Ajax Support Today MobileAjaxWhitePaper Mobile Ajax in Practice MobileAjaxWhitePaper Challenges and Opportunities for Developers MobileAjaxWhitePaper The Mobile Opportunity MobileAjaxWhitePaper Differences in User Interfaces MobileAjaxWhitePaper Top 10 Tips for Developers MobileAjaxWhitePaper Future MobileAjaxWhitePaper References MobileAjaxWhitePaper Glossary For each of the sections in the white paper, I have set things up as follows: * The main "article" page contains Rick's original white paper text without any comments * The "discussion" tab contains the original text plus any annotative comments that people have supplied so far. As we discussed at today's phone call, please post your comments and proposed revised text on the "discussion" tabs, not on the main article. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080124/a375e88a/attachment.html From jferrai at us.ibm.com Fri Jan 25 10:15:24 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 25 Jan 2008 10:15:24 -0800 Subject: [OpenAjaxMobile] Fw: MobEA 2008 CFP Message-ID: I thought people might want to be aware of the upcoming MobEA conference, so I am forwarding this call-for-papers email. Jon -------------------------------------------------- Dear Authors, Please consider submitting a paper to the MobEA 2008 workshop, collocated with WWW 2008, Beijing China. Thank you Rittwik Jana, Dan Appelquist, Galit Zadok, Bin Wei ---- MobEA VI - Personal Rich Social Media http://www.research.att.com/~rjana/mobea2008.htm Beijing, China, April 22, 2008 Collocated with WWW2008 conference Aim and Scope 2008 will be the "Mobile Eureka! Moment". With the Olympics just round the corner and the mobile market experiencing a phenomenal growth, we believe that WWW 2008 will truly be the climax and focal point in the midst of this mobile revolution. Mobile Web Initiative spearheaded by W3C is making a strong stand on how to realize the vision of pervasive mobile computing. Three screen services (TV, PC, Phone) are demanding new architectures to be developed. Furthermore, the need to go beyond technology, demands an embrace of the human-centric aspects of mobile computing. The objective of this workshop is to provide a single forum for researchers, sociologists, and technologists to discuss the state-of-the-art, present their contributions, and set future directions in Personal applications for mobile users with a focus in rich social media. W3C has started a number of initiatives along the direction of Mobile Web Best Practices, Device Description Working Group, Device Independence Working Group and others. Topics of interest for technical papers and demos include, but are not limited to the following: * Mobile browser as a rich content creation environment * Convergence and emergence of Social Networking trends on the mobile * User Generated Content, content authoring from a mobile phone * Mobile browser as a rich application environment * Role of voice and multimodal technologies/applications * Mobile Ajax, JSF, SVG-T etc. What role do Ajax toolkits play in bringing rich experience to the mobile browser? * Models for rich media client (thin / thick) * Media adaptation and content filtering * Key rich media applications to leverage the development/use of mobile web in developing countries * Use of the mobile web and social media as a tool of political activism * Mobile gaming and location based services, mobile P2P applications * 3D mobile technologies * Wireless/wireline convergence? IMS, seamless mobility, interactive mobile TV * VOIP, mobile rich messaging/advertising services and business models * Next generation IPTV service infrastructure and Cross Platform Services (e.g. 3 screen services (TV, PC, phone) * Experience for IPTV and socially aware mobile entertainment services * Emerging Mobile Rich Media and IPTV standards Important dates February 18th 2008: Submission of full and position papers March 7th 2008: Notification of acceptance March 10th 2008: Camera-ready copies due April 22nd 2008: Workshop day Submission Submissions will be evaluated according to the relevance and originality of the work and to their ability to generate discussions between the participants of the workshop. The format of submitted papers must follow the same style as regular WWW2008 proceedings format, including no page numbers. Position papers should be up to 4 pages in length and full papers up to 8 pages. Submissions will be handled by EasyChair. Include an abstract, five to ten keywords, and the corresponding author's e-mail address. At least one author of accepted papers must register for the WWW2008 workshop. Registration information will be available at the conference web site: http://www2008.org Submission Information and Requirements Workshop submissions for WWW2008 workshops must be submitted via the workshop submission web site, http://www.easychair.org/conferences/?conf=mobea2008 All accepted papers for all workshops will appear in the conference CD handed out to all conference attendees. Workshop papers papers must be submitted as PDF documents. Organizing Committee Members Rittwik Jana, Bin Wei AT&T Labs Research 180 Park Ave Florham Park, NJ, 07932 {rjana, bw}@research.att.com Daniel Appelquist Vodafone Group Services The Connection, Newbury, Berkshire, RG14 2FN United Kingdom Daniel.Appelquist at vodafone.com Ms. Galit Zadok, me at galit.co.uk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080125/51bcadc2/attachment.html From jferrai at us.ibm.com Fri Jan 25 12:19:07 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 25 Jan 2008 12:19:07 -0800 Subject: [OpenAjaxMobile] Minutes from 2008-01-24 Message-ID: I am not sure that I recorded everyone who was on the phone call yesterday. If I neglected to include your name in the list of attendees, please go add your name to the wiki page that holds the minutes. Jon Mobile Minutes 2008-01-24 URL: http://www.openajax.org/member/wiki/Mobile_Minutes_2008-01-24 Attendees David Boloker, IBM (chair) Rick Saletta, Wavemaker Louenas Hamdi, SAP Rotan Hanrahan, Mobile Aware David Pollington, Vodafone Torkel Hambraeus, Ikivo Andrew Sledd, Ikivo Ryan XU, elooMobile Minutes Vodafone slide deck http://www.openajax.org/member/wiki/Image:Vodafone_Web_Runtimes.pdf DavidP: VF has been working for past 6 months on Web Runtime for mobile widgets and other applications. We want to unlock device APIs to be available for Web RT. We have MobileScript that allows browsers to bind to Windows Mobile and Symbian. Mobile browsing is increasing. Can bring great capabilities such as mashups and innovative environments. But to fulfill the potential, need packaging format (WAF standard for widgets), device APIs spec, and a security model. Jon: There has been strong OpenAjax member interest in this area. In the past six months there has been lots of progress, particular associated with due diligence work about what exists today in the device APIs space. It was perhaps the top item to come out of the Workshop on Mobile Ajax that happened in September. DavidB: Everyone is on the same page. Jon/DavidP: We will be talking with others at 3GSM in a few weeks about device APIs. Jon: Might have a call-to-action once we get back from 3GSM. DavidP: Vodafone will be hosting a meeting at 3GSM which is similar to the similar meeting on mobile ajax that occurred at last year's 3GSM, to determine next steps. DavidP: People should read documents and send feedback. Andrew: Ikivo is very interested in this area. White paper Jon: Thanks to Rick for all of his work on the first draft. Rick: I don't think we have a white paper but more of a contributed article. Jon: Maybe you are right, but we have called similar articles "white papers" before and no one has complained. Rick: Can get article into publications. Jon: Yes, in fact we have done this in the past. AJAXWorld is a great venu for this. They usually have both a print and online version for submitted articles. Has to be 1000-1500 words. Rick: I can shrink it. Jon: But we want to first finish the longer version, with the Mktg WG publishing it, and then have the Mktg WG shrink it and submit it. Jon: How about the title? DavidB: Don't like "top 10". How about simply "Introduction to Mobile Ajax"? DavidP: Are we going to give guidelines to developers? DavidB: We are somewhere in the middle. Jon: I think that's where we should be. An introduction, but the meat is around guidelines. Ryan: There is an article from Drucker and Associates about mobile user experiences Jon: Need to look at that article and decide how to reconcile and whether to reference it. Can you send the url? Ryan: Yes. Will send to the list. Jon: What about the outline. Is it correct? I know we have had lots of discussion before, and came up with what we have, but here is a chance to talk again. DavidB: Does everyone have same vision of one Web where a single URL works on any device? Jon: For example, go to ibm.com and you get information about IBM on either desktop or mobile. (no objections) DavidB: What other technologies should be or should not be used? DavidP: It's should be about the mobile Web Runtime, not different technology. But not just browsing. Bringing the web to mobile. Andrew: What about bring mobile to the web? Bring mobile experience in step with the web to have same technology and usage paradigms. Jon: Agree that we need to take into account widgets and installed apps. DavidP: Yes, on mobile, widget paradigm makes a lot of sense on mobile devices. We need to emphasize these workflows more. Ryan: I think that white paper is missing what Andrew said about bringing web to existing mobile devices. Andrew: Yes, need to emphasize Web RT is being used outside of the browser as a developer tip. Jon: Need to emphasize better the non-browser scenarios. Rotan: I want to point out that widgets aren't just a mobile thing. Jon: I agree. We don't want to phrase things to appear to say that widgets are only for mobile devices. Rotan: Let's take a step back. In title we have "Mobile Ajax 1.0". No spec or version for Mobile Ajax. Will OpenAjax create a spec and define version 1.0? Jon: No, no one is writing such a spec, and definitely we couldn't do it here as it is too big and anyways W3C would be more appropriate. Rotan: In intro, need to be honest about the status of Mobile Ajax. Some implementations and some commonality, but not ... (widespread?) Jon: I agree. At least remove "1.0". Rotan: Perhaps need HTML, XHR and widgets as locations where standards are being defined. People will hit this paper via Google search, so we should point to standards. Jon: Makes a lot of sense to me. (few others) agree Jon: Do we have a consensus on the outline and topics? DavidB: Yes, that's what I am hearing. Now, who wants to help? Rotan: I can take the lead on the W3C things Rick: I can take another editorial pass. Jon: I am available also. DavidP: I can help edit. DavidB: I am also willing to help. Andrew: We are also willing. Rotan: Let's use the discussion tab. It's the mediawiki way. Break the document into subsections. Jon: Yes, for short-term, but bring back together later. Jon: Next meeting - when? Next meeting will be Feb. 6, 9am California time. Jon: A little time left. Let's talk about the Bundeliga example. DavidP: Yes, can't use SVG. While it is true that it is using concepts, it isn't using Ajax. (discussion about why a concrete example adds values to the paper) DavidP: We have some examples we are working on. I could describe those examples and include screengrabs. Jon: Please! Rotan: In the future, would be better if everyone would log into the IRC channel. Jon: Yes. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080125/6b234de1/attachment.html From jferrai at us.ibm.com Tue Feb 5 07:35:56 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 5 Feb 2008 07:35:56 -0800 Subject: [OpenAjaxMobile] Postponing this week's phone call by 2 weeks Message-ID: Hi everyone, When looking at the white paper history on the wiki, there have been very few updates to the white paper since our last phone call. (I also haven't had much chance to contribute.) I talked with David Boloker and we have decided that it is best to postpone the Mobile TF phone call this week until after 3GSM. Therefore, let's resume discussion on Wednesday, Feb. 20. In the meantime, I encourage everyone to propose revised text for various sections of the white paper. Please make as much progress as you can by Feb. 20. I split the white paper into multiple separate wiki pages to help modularize the white paper editing effort. * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Title * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Introduction * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Characterizing_Mobile_Ajax_Support_Today * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Mobile_Ajax_in_Practice * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Challenges_and_Opportunities_for_Developers ** http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_The_Mobile_Opportunity ** http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Differences_in_User_Interfaces * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Top_10_Tips_for_Developers * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Future * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_References * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Glossary Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080205/3e84337c/attachment.html From ajit.jaokar at futuretext.com Tue Feb 5 08:47:24 2008 From: ajit.jaokar at futuretext.com (Ajit Jaokar) Date: Tue, 5 Feb 2008 16:47:24 +0000 Subject: [OpenAjaxMobile] Postponing this week's phone call by 2 weeks In-Reply-To: References: Message-ID: <9e4f714f0802050847g14b31643l3c47b8217445a8a1@mail.gmail.com> Thanks Jon. This is a good idea. 3GSM is taking a lot of my time as well and I look fwd to meeting everyone there. kind rgds Ajit On 05/02/2008, Jon Ferraiolo wrote: > > > Hi everyone, > When looking at the white paper history on the wiki, there have been very > few updates to the white paper since our last phone call. (I also haven't > had much chance to contribute.) > > I talked with David Boloker and we have decided that it is best to postpone > the Mobile TF phone call this week until after 3GSM. Therefore, let's resume > discussion on Wednesday, Feb. 20. > > In the meantime, I encourage everyone to propose revised text for various > sections of the white paper. Please make as much progress as you can by Feb. > 20. > > I split the white paper into multiple separate wiki pages to help > modularize the white paper editing effort. > > * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Title > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Introduction > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Characterizing_Mobile_Ajax_Support_Today > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Mobile_Ajax_in_Practice > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Challenges_and_Opportunities_for_Developers > ** > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_The_Mobile_Opportunity > ** > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Differences_in_User_Interfaces > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Top_10_Tips_for_Developers > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Future > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_References > * > http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Glossary > > Thanks. > Jon > > > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile > > From jferrai at us.ibm.com Mon Feb 18 13:56:49 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 18 Feb 2008 13:56:49 -0800 Subject: [OpenAjaxMobile] Postponing the next phone call by one more week (until Feb 27) Message-ID: Hi everyone, Based on some conversations at 3GSM/MWC last week, I heard from people that they could really use one more week to make their changes to the Mobile Ajax white paper. I know that I can benefit from one more week. Therefore, let's push the next phone call back one week to Wednesday, Feb. 27, at the usual time and call-in numbers. Date: Wednesday, Feb. 27 Time: 9amPT, noonET, 5pm GMT, 6pm Paris Call in numbers can be found on the Mobile TF wiki page: http://www.openajax.org/member/wiki/Mobile_TF#Conference_Call_PIN_and_Phone_Numbers Be sure to complete your editing assignments by then! Jon ----------------------------------------------------------------------------------------- --- PREVIOUS MESSAGE --- Hi everyone, When looking at the white paper history on the wiki, there have been very few updates to the white paper since our last phone call. (I also haven't had much chance to contribute.) I talked with David Boloker and we have decided that it is best to postpone the Mobile TF phone call this week until after 3GSM. Therefore, let's resume discussion on Wednesday, Feb. 20. In the meantime, I encourage everyone to propose revised text for various sections of the white paper. Please make as much progress as you can by Feb. 20. I split the white paper into multiple separate wiki pages to help modularize the white paper editing effort. * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Title * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Introduction * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Characterizing_Mobile_Ajax_Support_Today * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Mobile_Ajax_in_Practice * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Challenges_and_Opportunities_for_Developers ** http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_The_Mobile_Opportunity ** http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Differences_in_User_Interfaces * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Top_10_Tips_for_Developers * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Future * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_References * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Glossary Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080218/e9052e80/attachment.html From Torkel.Hambraeus at ikivo.com Fri Feb 22 08:06:51 2008 From: Torkel.Hambraeus at ikivo.com (Torkel Hambraeus) Date: Fri, 22 Feb 2008 17:06:51 +0100 Subject: [OpenAjaxMobile] Postponing the next phone call by one more week(until Feb 27) In-Reply-To: References: Message-ID: <234EB4699C751A4A95DF4FD8D041BBFDBE79D2@SESTHSRV10.zoomon.local> Hi everyone, Will probably be on the road at this time. I would prefer a meeting earlier in the week or the week after. Best regards, /Torkel ________________________________ From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: den 18 februari 2008 22:57 To: mobile at openajax.org Subject: [OpenAjaxMobile] Postponing the next phone call by one more week(until Feb 27) Hi everyone, Based on some conversations at 3GSM/MWC last week, I heard from people that they could really use one more week to make their changes to the Mobile Ajax white paper. I know that I can benefit from one more week. Therefore, let's push the next phone call back one week to Wednesday, Feb. 27, at the usual time and call-in numbers. * Date: Wednesday, Feb. 27 * Time: 9amPT, noonET, 5pm GMT, 6pm Paris Call in numbers can be found on the Mobile TF wiki page: * http://www.openajax.org/member/wiki/Mobile_TF#Conference_Call_PIN_and_Ph one_Numbers Be sure to complete your editing assignments by then! Jon ------------------------------------------------------------------------ ----------------- --- PREVIOUS MESSAGE --- Hi everyone, When looking at the white paper history on the wiki, there have been very few updates to the white paper since our last phone call. (I also haven't had much chance to contribute.) I talked with David Boloker and we have decided that it is best to postpone the Mobile TF phone call this week until after 3GSM. Therefore, let's resume discussion on Wednesday, Feb. 20. In the meantime, I encourage everyone to propose revised text for various sections of the white paper. Please make as much progress as you can by Feb. 20. I split the white paper into multiple separate wiki pages to help modularize the white paper editing effort. * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Title * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Introduction * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Characterizing_ Mobile_Ajax_Support_Today * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Mobile_Ajax_in_ Practice * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Challenges_and_ Opportunities_for_Developers ** http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_The_Mobile_Oppo rtunity ** http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Differences_in_ User_Interfaces * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Top_10_Tips_for _Developers * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Future * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_References * http://www.openajax.org/member/wiki/MobileAjaxWhitePaper_Glossary Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080222/4ac71155/attachment.html From jferrai at us.ibm.com Fri Feb 22 09:26:02 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 22 Feb 2008 09:26:02 -0800 Subject: [OpenAjaxMobile] Welcome to Andrew Sledd as co-chair of Mobile Task Force Message-ID: Hi everyone, Andrew Sledd of Ikivo is now co-chair of the Mobile Task Force, helping out the other co-chair, David Boloker of IBM, whose travel schedule makes it difficult for him to be available for every meeting. Welcome and congratulations to Andy on taking on this new role. Jon PS: Reminder that we have a phone call on next Wednesday --------------------------------------------- Next Conference Call Date: Wednesday, Feb. 27 Time: 9amPT, noonET, 5pm GMT, 6pm Paris Agenda Device APIs - next steps White paper: http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Individual sections: MobileAjaxWhitePaper Title MobileAjaxWhitePaper Introduction MobileAjaxWhitePaper Characterizing Mobile Ajax Support Today MobileAjaxWhitePaper Mobile Ajax in Practice MobileAjaxWhitePaper Challenges and Opportunities for Developers MobileAjaxWhitePaper The Mobile Opportunity MobileAjaxWhitePaper Differences in User Interfaces MobileAjaxWhitePaper Top 10 Tips for Developers MobileAjaxWhitePaper Future MobileAjaxWhitePaper References MobileAjaxWhitePaper Glossary See below for call-in information. Conference Call PIN and Phone Numbers Passcode: 460566 Conference Access: Toll free: 1-888-619-1583 Toll: 1-719-457-1414 International toll free - Argentina: 0800 666 3149 International toll free - Australia: 1 800 105 680 International toll free - Austria: 0 800 291 941 International toll free - Belgium: 0 800 75 240 International toll free - Chile: 123 0020 9725 International toll free - China, Northern Region: 10 800 714 1201 International toll free - China, Southern Region: 10 800 140 1180 International toll free - Colombia: 01 800 518 0789 International toll free - Costa Rica: 0800 015 0616 International toll free - Czech Republic: 800 700 294 International toll free - Denmark: 80 886 215 International toll free - Dominican Republic: 1 888 751 4488 International toll free - Ecuador: 1 800 020 321 International toll free - France: 0 800 90 0161 International toll free - Germany: 0 800 181 9019 International toll free - Greece: 00 800 161 2205 5955 International toll free - Hong Kong: 800 901 110 International toll free - Hungary: 06 800 162 50 International toll free - India: 000 800 1006 980 International toll free - Indonesia: 001 803 017 5955 International toll free - Ireland: 1 800 760 547 International toll free - Israel: 1 809 246 041 International toll free - Italy: 800 873 739 International toll free - Japan: 00531 16 0844 International toll free - Lithuania: 8 800 3 05 25 International toll free - Luxembourg: 800 2 7665 International toll free - Malaysia: 1 800 813 714 International toll free - Mexico: 001 800 514 5955 International toll free - Monaco: 800 93 416 International toll free - Netherlands: 0 800 023 5303 International toll free - New Zealand: 0 800 451 015 International toll free - Norway: 800 196 65 International toll free - Panama: 00 800 226 5955 International toll free - Poland: 00 800 111 49 58 International toll free - Portugal: 800 819 728 International toll free - Russia: 810 800 2704 1012 International toll free - Singapore: 800 101 2002 International toll free - Slovenia: 0 800 80203 International toll free - South Africa: 0 800 980 988 International toll free - South Korea: 003 0813 1963 International toll free - Spain: 900 947 604 International toll free - Sweden: 02 079 7556 International toll free - Switzerland: 0 800 564 397 International toll free - Thailand: 001 800 156 205 5955 International toll free - Trinidad-Tobago: 1 800 205 5955 International toll free - UK: 0 808 101 1146 International toll free - Uruguay: 0004 019 0188 International toll free - Venezuela: 0 800 100 8300 IRC channel IRC channel: irc.freenode.net, #oaa-mobile Free online IRC client: http://java.freenode.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080222/637e9043/attachment-0001.html From jferrai at us.ibm.com Tue Feb 26 11:07:05 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 26 Feb 2008 11:07:05 -0800 Subject: [OpenAjaxMobile] I moved comments from the discussion tab to the article tab Message-ID: Hi everyone, I have been doing some proposed edits to the Mobile Ajax white paper (http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax) and decided that it would be more efficient at this point in the development of the white paper for people to place their comments within the main article page than to place them on the discussion tab. That way, for each section of the white paper, we can see the original text, any discussion on the original text, any proposed new text, and any discussion on proposed new text, all within the same page, rather than forcing people to flip back and forth between the article tab and discussion tab. I hope that's OK with everyone. Don't forget to complete your writing assignments before tomorrow's phone call! Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080226/cc985bfb/attachment.html From jferrai at us.ibm.com Tue Feb 26 11:03:23 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 26 Feb 2008 11:03:23 -0800 Subject: [OpenAjaxMobile] Phone call tomorrow Message-ID: Next Conference Call Date: Wednesday, Feb. 27 Time: 9amPT, noonET, 5pm GMT, 6pm Paris Agenda Device APIs - next steps White paper: http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Individual sections: MobileAjaxWhitePaper Title MobileAjaxWhitePaper Introduction MobileAjaxWhitePaper Characterizing Mobile Ajax Support Today MobileAjaxWhitePaper Mobile Ajax in Practice MobileAjaxWhitePaper Challenges and Opportunities for Developers MobileAjaxWhitePaper The Mobile Opportunity MobileAjaxWhitePaper Differences in User Interfaces MobileAjaxWhitePaper Top 10 Tips for Developers MobileAjaxWhitePaper Future MobileAjaxWhitePaper References MobileAjaxWhitePaper Glossary See below for call-in information. Conference Call PIN and Phone Numbers Passcode: 460566 Conference Access: Toll free: 1-888-619-1583 Toll: 1-719-457-1414 International toll free - Argentina: 0800 666 3149 International toll free - Australia: 1 800 105 680 International toll free - Austria: 0 800 291 941 International toll free - Belgium: 0 800 75 240 International toll free - Chile: 123 0020 9725 International toll free - China, Northern Region: 10 800 714 1201 International toll free - China, Southern Region: 10 800 140 1180 International toll free - Colombia: 01 800 518 0789 International toll free - Costa Rica: 0800 015 0616 International toll free - Czech Republic: 800 700 294 International toll free - Denmark: 80 886 215 International toll free - Dominican Republic: 1 888 751 4488 International toll free - Ecuador: 1 800 020 321 International toll free - France: 0 800 90 0161 International toll free - Germany: 0 800 181 9019 International toll free - Greece: 00 800 161 2205 5955 International toll free - Hong Kong: 800 901 110 International toll free - Hungary: 06 800 162 50 International toll free - India: 000 800 1006 980 International toll free - Indonesia: 001 803 017 5955 International toll free - Ireland: 1 800 760 547 International toll free - Israel: 1 809 246 041 International toll free - Italy: 800 873 739 International toll free - Japan: 00531 16 0844 International toll free - Lithuania: 8 800 3 05 25 International toll free - Luxembourg: 800 2 7665 International toll free - Malaysia: 1 800 813 714 International toll free - Mexico: 001 800 514 5955 International toll free - Monaco: 800 93 416 International toll free - Netherlands: 0 800 023 5303 International toll free - New Zealand: 0 800 451 015 International toll free - Norway: 800 196 65 International toll free - Panama: 00 800 226 5955 International toll free - Poland: 00 800 111 49 58 International toll free - Portugal: 800 819 728 International toll free - Russia: 810 800 2704 1012 International toll free - Singapore: 800 101 2002 International toll free - Slovenia: 0 800 80203 International toll free - South Africa: 0 800 980 988 International toll free - South Korea: 003 0813 1963 International toll free - Spain: 900 947 604 International toll free - Sweden: 02 079 7556 International toll free - Switzerland: 0 800 564 397 International toll free - Thailand: 001 800 156 205 5955 International toll free - Trinidad-Tobago: 1 800 205 5955 International toll free - UK: 0 808 101 1146 International toll free - Uruguay: 0004 019 0188 International toll free - Venezuela: 0 800 100 8300 IRC channel IRC channel: irc.freenode.net, #oaa-mobile Free online IRC client: http://java.freenode.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080226/bbb52bc9/attachment.html From nikunj.mehta at oracle.com Tue Feb 26 14:32:15 2008 From: nikunj.mehta at oracle.com (Nikunj Mehta) Date: Tue, 26 Feb 2008 14:32:15 -0800 Subject: [OpenAjaxMobile] I moved comments from the discussion tab to the article tab In-Reply-To: References: Message-ID: <47C4936F.6060707@oracle.com> Hi Jon, A last minute meeting came up and I wouldn't be able to join the call tomorrow at 9 AM as I was expecting. I will look over the minutes post-facto. Regards, Nikunj Jon Ferraiolo wrote: > > Hi everyone, > I have been doing some proposed edits to the Mobile Ajax white paper > (http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax) and decided > that it would be more efficient at this point in the development of > the white paper for people to place their comments within the main > article page than to place them on the discussion tab. That way, for > each section of the white paper, we can see the original text, any > discussion on the original text, any proposed new text, and any > discussion on proposed new text, all within the same page, rather than > forcing people to flip back and forth between the article tab and > discussion tab. I hope that's OK with everyone. > > Don't forget to complete your writing assignments before tomorrow's > phone call! > > Jon > > ------------------------------------------------------------------------ > > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile > From jferrai at us.ibm.com Wed Feb 27 11:59:47 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 27 Feb 2008 11:59:47 -0800 Subject: [OpenAjaxMobile] Minutes from today's phone call 2008-02-27 Message-ID: Mobile Minutes 2008-02-27 URL: http://www.openajax.org/member/wiki/Mobile_Minutes_2008-02-27 Attendees David Boloker, IBM (co-chair) Andrew Sledd, Ikivo (co-chair) Rick Saletta, Wavemaker David Pollington, Vodafone Paddy Byers, Aplix Rich Thompson, IBM Paulo Neves, Present Technologies Minutes Device APIs Jon: Vodafone hosted a meeting in Barcelona at 3GSM/MWC with about 20 companies to talk about Mobile Ajax. It was the second such meeting. The year earlier, we decided that the industry needed to have a workshop on Mobile Ajax, and that happened in September, hosted by W3C and OpenAjax Alliance. At the September meeting, one of the critical areas that was identified was to open up device APIs to the Web Runtime. Since then, at OpenAjax, in this committee, we did a bunch of due diligence on what exists today and captured it on a long wiki page. Now, the meeting two weeks ago. At the meeting we discussed next steps. There were people who felt that we needed to move aggressively on an industry basis to develop standards and there were people who were on the other extreme and felt that we should let things shake out in the industry and then look to codify what exists. I proposed a middle ground approach where the industry gets together in an intense, short-term exploratory effort to articulate use cases and requirements and describe the key security issues. I suggested an arbitrary date of April 30, 2008, as the end point for the exploratory efforts. At the meeting and in subsequent discussion after the meeting, a good number of people felt this was a good approach. Andy: What would be the nature of the use cases? Jon: I was thinking we would describe a set of use cases at a high-level. One example would be a search web page that might leverage the current location API of your phone to create a more personalized, location-aware set of results. Another example might be a search web page that returns a phone number, and if it has access to the phone dialer API, then an icon might appear next to the phone number that would allow one-click dialing to the number. Also, use cases for widgets and installed desktop applications. But quick descriptions of scenarios. Jon: At the meeting, I also proposed a strawman technical approach for how the industry might pursue a unified technical approach. Before I describe this strawman, let me first say that our thinking is that this strawman will be put aside for a couple months as we articulate our use cases and requirements, and then brought back and looked at again after April 30, to see if the strawman is a good match for the use cases, requirements, and security issues that we develop. OK, here is the strawman. I proposed that OpenAjax launch an open source effort to develop a simple shim JavaScript APIs for things like access to location, access to contact list, access to email, access to phone dialer, etc.. Our JavaScript shim doesn't do anything, but underneath the shim, other JavaScript would plug in to map our shim APIs to other APIs that hook up to resident services. There might be a provider plugin that maps our shim APIs to other JavaScript that integrates with J2ME MSA. There might be another provider plugin that maps our shim APIs to other JavaScript that integrates with Windows Mobile. (some other discussion) Jon: Any objectives to the proposed intense effort between now and April 30? Paddy: From our point of view, this is a good way forward. On the open source area, we would be happy to work on the shim or work on implementations that go to the device area. Are you aware of Rococo? I have talked with them about joining OpenAjax Alliance. They helped to lead the Java Bluetooth spec. They are an example of a company that might help the open source effort focused on one particular API area. Jon: Great to hear. Andy: This proposal is along the lines of what Ikivo would like to see happen. Ikivo volunteered me to be co-chair largely due to our interest in seeing this effort move forward. Jon: I created 3 new wiki pages to capture our work on use cases, requirements, and security concerns. Right now those wiki pages are just shells. I would like to have a call-to-action for people to fill out those wiki pages between now and April 30. Jon: Is everyone OK with weekly phone calls between now and April 30 to work on the device APIs? I talked with some other companies, and they said they would be willing to call in each week. (general agreement with weekly phone calls) Rick: What impact will this have on the white paper? Jon: We will be doing two things at once. I am hoping that after today's phone call, we will be able to make progress on lots of white paper issues via email, but we shall see. (discussion about phone times) Resolution: Weekly phone calls at 9amPT, noonET, 6pm Paris each Thursday, starting March 6. White paper Title Jon: It looks like only DavidP and I have made contributions lately. Anyone else? (silence) My contributions have been to go through some of the sections and propose new text that attempts to address the feedback comments. Can we start with the title? (various opinions about the title. most people are flexible. question about whether we have enough meat to call it a developer's guide. jon thinks yes, but only if people agree with some of the meat he has written for other sections) Resolution: Title = "Introduction to Mobile Ajax for Developers" Tips for developers Jon: I think it would be good to jump to the meat. In trying to figure out a good way to organize this section, I thought it would be good to have subsections based on the challenge area, such as small screen size, and then propose techniques that are available for addressing the challenge. DavidP: Exactly the kind of content that we would like to see Paddy: This approach is better than the previous approach, which was more intense and pessimistic. Better to describe things to think about. Jon: I am only about half-done with finishing a strawman initial writeup for this section. If this is a reasonable approach, I can finish the other half. Rick: What is there is essentially an outline for filling out the rest of the paper. Andy: What can others do to help? Jon: I might have left out one, two or three major challenges. If so, add a new subsection. I might have left out an important technique within a particular subsection. If so, add that technique. And there is always improvements with wordsmithing. Paddy: To be devil's advocate, there are a bunch of considerations, and yes already know that. My problem is finding more detailed information. For example, WURFL would help me understand device issues. Jon: Yes, I agree, and we should provide some additional detail and links to important resources, such as WURFL. (question about whether we need to provide complete and comprehensive info) Rick: OK if the 1.0 release provides good value but doesn't provide complete answer. We can always update the document. Jon: One additional detail I thought made sense was to talk about the iPhone viewport. Everyone know what that is? (no one does, so jon explains) DavidP: One emerging industry standard is quarter VGA, 320x240. Half of the devices coming up support that profile. iPhone doubles one dimension to 480. Paddy: But people need to know. W3C says if you target a particular low-res, something like 220x???, you get 95% of the devices. Good to provide some sort of measure. DavidP: Good point. Paddy: If I'm targeting an iphone, go here. If I'm targeting more devices, go here. Let developers choose their target, but help them with links relative to that target. But if you want to discuss the iPhone as the state of the art today, then explicit information about the iPhone would have a role. Jon: Agree. iPhone should be a small part of the document, but worth pointing out at particular points. Paddy: Agree. Intro DavidP: I think the proposed text is good. Andrew: Brief, which is good. Characterizing... (no proposed text, no comments, so skip to next section) In practice Jon: I think the train example is good, but we need more. It talks about the widget case. We also need browser case. DavidP: Can we use the Google/iPhone example that Dave Burke showed in Barcelona? Jon: Yes, that's a great example of Ajax. Jon: I can take a crack at writing up Google as an example. Andrew: Remove train example or augment? Jon: I'm thinking the train example shows the use of the Web Runtime as a widget. Andrew: Sounds good. DavidP: Is the objective to show how it exists today or how cool it's going to be? Jon: I think we want to reflect both evidence that it already exists today but make sure users understand how cool it's going to be Andrew: iPhone shows both evidence and examples of how cool it's going to be Next steps Jon: I'll work on the WP between now and next Thursday to finish up more sections. I'll send email as I make progress so people can review. Please everyone else contribute also, particularly on the tips for developers section. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080227/e5596ddc/attachment.html From rotan.hanrahan at mobileaware.com Thu Feb 28 05:07:59 2008 From: rotan.hanrahan at mobileaware.com (Rotan Hanrahan) Date: Thu, 28 Feb 2008 08:07:59 -0500 Subject: [OpenAjaxMobile] Minutes from today's phone call 2008-02-27 In-Reply-To: References: Message-ID: Belated apologies, but we had a technical crisis that demanded my attention. I was hoping to join the meeting to draw attention to developments in the DDWG. We're close to an API to access device information (e.g. the kind of stuff held in WURFL) and that would be beneficial to anyone considering automated adaptation of Ajax applications to the abilities/limits of a mobile context. It's only just coming together now, and we expect to be ready for formal publication after our meetings in Korea next week. If you are interested, check out the editors' drafts, linked from the top of the DDWG's home page: http://www.w3.org/2005/MWI/DDWG/ Again, sorry about my absence. I hope that my earlier contributions to the sandbox have helped in some way, and in future I should be able to contribute properly. Meanwhile for the next week or so I'll be busy dealing with the matters in Korea. ---Rotan. From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Jon Ferraiolo Sent: 27 February 2008 20:00 To: mobile at openajax.org Subject: [OpenAjaxMobile] Minutes from today's phone call 2008-02-27 Mobile Minutes 2008-02-27 URL: http://www.openajax.org/member/wiki/Mobile_Minutes_2008-02-27 Attendees * David Boloker, IBM (co-chair) * Andrew Sledd, Ikivo (co-chair) * Rick Saletta, Wavemaker * David Pollington, Vodafone * Paddy Byers, Aplix * Rich Thompson, IBM * Paulo Neves, Present Technologies Minutes Device APIs Jon: Vodafone hosted a meeting in Barcelona at 3GSM/MWC with about 20 companies to talk about Mobile Ajax. It was the second such meeting. The year earlier, we decided that the industry needed to have a workshop on Mobile Ajax, and that happened in September, hosted by W3C and OpenAjax Alliance. At the September meeting, one of the critical areas that was identified was to open up device APIs to the Web Runtime. Since then, at OpenAjax, in this committee, we did a bunch of due diligence on what exists today and captured it on a long wiki page. Now, the meeting two weeks ago. At the meeting we discussed next steps. There were people who felt that we needed to move aggressively on an industry basis to develop standards and there were people who were on the other extreme and felt that we should let things shake out in the industry and then look to codify what exists. I proposed a middle ground approach where the industry gets together in an intense, short-term exploratory effort to articulate use cases and requirements and describe the key security issues. I suggested an arbitrary date of April 30, 2008, as the end point for the exploratory efforts. At the meeting and in subsequent discussion after the meeting, a good number of people felt this was a good approach. Andy: What would be the nature of the use cases? Jon: I was thinking we would describe a set of use cases at a high-level. One example would be a search web page that might leverage the current location API of your phone to create a more personalized, location-aware set of results. Another example might be a search web page that returns a phone number, and if it has access to the phone dialer API, then an icon might appear next to the phone number that would allow one-click dialing to the number. Also, use cases for widgets and installed desktop applications. But quick descriptions of scenarios. Jon: At the meeting, I also proposed a strawman technical approach for how the industry might pursue a unified technical approach. Before I describe this strawman, let me first say that our thinking is that this strawman will be put aside for a couple months as we articulate our use cases and requirements, and then brought back and looked at again after April 30, to see if the strawman is a good match for the use cases, requirements, and security issues that we develop. OK, here is the strawman. I proposed that OpenAjax launch an open source effort to develop a simple shim JavaScript APIs for things like access to location, access to contact list, access to email, access to phone dialer, etc.. Our JavaScript shim doesn't do anything, but underneath the shim, other JavaScript would plug in to map our shim APIs to other APIs that hook up to resident services. There might be a provider plugin that maps our shim APIs to other JavaScript that integrates with J2ME MSA. There might be another provider plugin that maps our shim APIs to other JavaScript that integrates with Windows Mobile. (some other discussion) Jon: Any objectives to the proposed intense effort between now and April 30? Paddy: From our point of view, this is a good way forward. On the open source area, we would be happy to work on the shim or work on implementations that go to the device area. Are you aware of Rococo? I have talked with them about joining OpenAjax Alliance. They helped to lead the Java Bluetooth spec. They are an example of a company that might help the open source effort focused on one particular API area. Jon: Great to hear. Andy: This proposal is along the lines of what Ikivo would like to see happen. Ikivo volunteered me to be co-chair largely due to our interest in seeing this effort move forward. Jon: I created 3 new wiki pages to capture our work on use cases, requirements, and security concerns. Right now those wiki pages are just shells. I would like to have a call-to-action for people to fill out those wiki pages between now and April 30. Jon: Is everyone OK with weekly phone calls between now and April 30 to work on the device APIs? I talked with some other companies, and they said they would be willing to call in each week. (general agreement with weekly phone calls) Rick: What impact will this have on the white paper? Jon: We will be doing two things at once. I am hoping that after today's phone call, we will be able to make progress on lots of white paper issues via email, but we shall see. (discussion about phone times) Resolution: Weekly phone calls at 9amPT, noonET, 6pm Paris each Thursday, starting March 6. White paper Title Jon: It looks like only DavidP and I have made contributions lately. Anyone else? (silence) My contributions have been to go through some of the sections and propose new text that attempts to address the feedback comments. Can we start with the title? (various opinions about the title. most people are flexible. question about whether we have enough meat to call it a developer's guide. jon thinks yes, but only if people agree with some of the meat he has written for other sections) Resolution: Title = "Introduction to Mobile Ajax for Developers" Tips for developers Jon: I think it would be good to jump to the meat. In trying to figure out a good way to organize this section, I thought it would be good to have subsections based on the challenge area, such as small screen size, and then propose techniques that are available for addressing the challenge. DavidP: Exactly the kind of content that we would like to see Paddy: This approach is better than the previous approach, which was more intense and pessimistic. Better to describe things to think about. Jon: I am only about half-done with finishing a strawman initial writeup for this section. If this is a reasonable approach, I can finish the other half. Rick: What is there is essentially an outline for filling out the rest of the paper. Andy: What can others do to help? Jon: I might have left out one, two or three major challenges. If so, add a new subsection. I might have left out an important technique within a particular subsection. If so, add that technique. And there is always improvements with wordsmithing. Paddy: To be devil's advocate, there are a bunch of considerations, and yes already know that. My problem is finding more detailed information. For example, WURFL would help me understand device issues. Jon: Yes, I agree, and we should provide some additional detail and links to important resources, such as WURFL. (question about whether we need to provide complete and comprehensive info) Rick: OK if the 1.0 release provides good value but doesn't provide complete answer. We can always update the document. Jon: One additional detail I thought made sense was to talk about the iPhone viewport. Everyone know what that is? (no one does, so jon explains) DavidP: One emerging industry standard is quarter VGA, 320x240. Half of the devices coming up support that profile. iPhone doubles one dimension to 480. Paddy: But people need to know. W3C says if you target a particular low-res, something like 220x???, you get 95% of the devices. Good to provide some sort of measure. DavidP: Good point. Paddy: If I'm targeting an iphone, go here. If I'm targeting more devices, go here. Let developers choose their target, but help them with links relative to that target. But if you want to discuss the iPhone as the state of the art today, then explicit information about the iPhone would have a role. Jon: Agree. iPhone should be a small part of the document, but worth pointing out at particular points. Paddy: Agree. Intro DavidP: I think the proposed text is good. Andrew: Brief, which is good. Characterizing... (no proposed text, no comments, so skip to next section) In practice Jon: I think the train example is good, but we need more. It talks about the widget case. We also need browser case. DavidP: Can we use the Google/iPhone example that Dave Burke showed in Barcelona? Jon: Yes, that's a great example of Ajax. Jon: I can take a crack at writing up Google as an example. Andrew: Remove train example or augment? Jon: I'm thinking the train example shows the use of the Web Runtime as a widget. Andrew: Sounds good. DavidP: Is the objective to show how it exists today or how cool it's going to be? Jon: I think we want to reflect both evidence that it already exists today but make sure users understand how cool it's going to be Andrew: iPhone shows both evidence and examples of how cool it's going to be Next steps Jon: I'll work on the WP between now and next Thursday to finish up more sections. I'll send email as I make progress so people can review. Please everyone else contribute also, particularly on the tips for developers section. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080228/3610b58a/attachment-0001.html From ajit.jaokar at futuretext.com Thu Feb 28 06:23:57 2008 From: ajit.jaokar at futuretext.com (Ajit Jaokar) Date: Thu, 28 Feb 2008 14:23:57 +0000 Subject: [OpenAjaxMobile] Minutes from today's phone call 2008-02-27 In-Reply-To: References: Message-ID: <9e4f714f0802280623y4675ade8q7ca2ddbac2da601c@mail.gmail.com> apologies from my side as well. All this is great progress and especially a lot of progress in the meeting at MWC. I will send more thoughts later on this. kind rgds Ajit On 28/02/2008, Rotan Hanrahan wrote: > > > > > Belated apologies, but we had a technical crisis that demanded my attention. > > > > I was hoping to join the meeting to draw attention to developments in the > DDWG. We're close to an API to access device information (e.g. the kind of > stuff held in WURFL) and that would be beneficial to anyone considering > automated adaptation of Ajax applications to the abilities/limits of a > mobile context. It's only just coming together now, and we expect to be > ready for formal publication after our meetings in Korea next week. > > > > If you are interested, check out the editors' drafts, linked from the top of > the DDWG's home page: > > > > http://www.w3.org/2005/MWI/DDWG/ > > > > Again, sorry about my absence. I hope that my earlier contributions to the > sandbox have helped in some way, and in future I should be able to > contribute properly. Meanwhile for the next week or so I'll be busy dealing > with the matters in Korea. > > > > ---Rotan. > > > > > > > > > > From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On > Behalf Of Jon Ferraiolo > Sent: 27 February 2008 20:00 > To: mobile at openajax.org > Subject: [OpenAjaxMobile] Minutes from today's phone call 2008-02-27 > > > > > Mobile Minutes 2008-02-27 > > URL: > http://www.openajax.org/member/wiki/Mobile_Minutes_2008-02-27 > > > > Attendees > > > David Boloker, IBM (co-chair) > Andrew Sledd, Ikivo (co-chair) > Rick Saletta, Wavemaker > David Pollington, Vodafone > Paddy Byers, Aplix > Rich Thompson, IBM > Paulo Neves, Present Technologies > > > Minutes > > Device APIs > > Jon: Vodafone hosted a meeting in Barcelona at 3GSM/MWC with about 20 > companies to talk about Mobile Ajax. It was the second such meeting. The > year earlier, we decided that the industry needed to have a workshop on > Mobile Ajax, and that happened in September, hosted by W3C and OpenAjax > Alliance. At the September meeting, one of the critical areas that was > identified was to open up device APIs to the Web Runtime. Since then, at > OpenAjax, in this committee, we did a bunch of due diligence on what exists > today and captured it on a long wiki page. Now, the meeting two weeks ago. > At the meeting we discussed next steps. There were people who felt that we > needed to move aggressively on an industry basis to develop standards and > there were people who were on the other extreme and felt that we should let > things shake out in the industry and then look to codify what exists. I > proposed a middle ground approach where the industry gets together in an > intense, short-term exploratory effort to articulate use cases and > requirements and describe the key security issues. I suggested an arbitrary > date of April 30, 2008, as the end point for the exploratory efforts. At the > meeting and in subsequent discussion after the meeting, a good number of > people felt this was a good approach. > > Andy: What would be the nature of the use cases? > > Jon: I was thinking we would describe a set of use cases at a high-level. > One example would be a search web page that might leverage the current > location API of your phone to create a more personalized, location-aware set > of results. Another example might be a search web page that returns a phone > number, and if it has access to the phone dialer API, then an icon might > appear next to the phone number that would allow one-click dialing to the > number. Also, use cases for widgets and installed desktop applications. But > quick descriptions of scenarios. > > Jon: At the meeting, I also proposed a strawman technical approach for how > the industry might pursue a unified technical approach. Before I describe > this strawman, let me first say that our thinking is that this strawman will > be put aside for a couple months as we articulate our use cases and > requirements, and then brought back and looked at again after April 30, to > see if the strawman is a good match for the use cases, requirements, and > security issues that we develop. OK, here is the strawman. I proposed that > OpenAjax launch an open source effort to develop a simple shim JavaScript > APIs for things like access to location, access to contact list, access to > email, access to phone dialer, etc.. Our JavaScript shim doesn't do > anything, but underneath the shim, other JavaScript would plug in to map our > shim APIs to other APIs that hook up to resident services. There might be a > provider plugin that maps our shim APIs to other JavaScript that integrates > with J2ME MSA. There might be another provider plugin that maps our shim > APIs to other JavaScript that integrates with Windows Mobile. > > (some other discussion) > > Jon: Any objectives to the proposed intense effort between now and April 30? > > Paddy: From our point of view, this is a good way forward. On the open > source area, we would be happy to work on the shim or work on > implementations that go to the device area. Are you aware of Rococo? I have > talked with them about joining OpenAjax Alliance. They helped to lead the > Java Bluetooth spec. They are an example of a company that might help the > open source effort focused on one particular API area. > > Jon: Great to hear. > > Andy: This proposal is along the lines of what Ikivo would like to see > happen. Ikivo volunteered me to be co-chair largely due to our interest in > seeing this effort move forward. > > Jon: I created 3 new wiki pages to capture our work on use cases, > requirements, and security concerns. Right now those wiki pages are just > shells. I would like to have a call-to-action for people to fill out those > wiki pages between now and April 30. > > Jon: Is everyone OK with weekly phone calls between now and April 30 to work > on the device APIs? I talked with some other companies, and they said they > would be willing to call in each week. > > (general agreement with weekly phone calls) > > Rick: What impact will this have on the white paper? > > Jon: We will be doing two things at once. I am hoping that after today's > phone call, we will be able to make progress on lots of white paper issues > via email, but we shall see. > > (discussion about phone times) > > Resolution: Weekly phone calls at 9amPT, noonET, 6pm Paris each Thursday, > starting March 6. > > > White paper > > Title > > Jon: It looks like only DavidP and I have made contributions lately. Anyone > else? (silence) My contributions have been to go through some of the > sections and propose new text that attempts to address the feedback > comments. Can we start with the title? > > (various opinions about the title. most people are flexible. question about > whether we have enough meat to call it a developer's guide. jon thinks yes, > but only if people agree with some of the meat he has written for other > sections) > > Resolution: Title = "Introduction to Mobile Ajax for Developers" > > > Tips for developers > > Jon: I think it would be good to jump to the meat. In trying to figure out a > good way to organize this section, I thought it would be good to have > subsections based on the challenge area, such as small screen size, and then > propose techniques that are available for addressing the challenge. > > DavidP: Exactly the kind of content that we would like to see > > Paddy: This approach is better than the previous approach, which was more > intense and pessimistic. Better to describe things to think about. > > Jon: I am only about half-done with finishing a strawman initial writeup for > this section. If this is a reasonable approach, I can finish the other half. > > Rick: What is there is essentially an outline for filling out the rest of > the paper. > > Andy: What can others do to help? > > Jon: I might have left out one, two or three major challenges. If so, add a > new subsection. I might have left out an important technique within a > particular subsection. If so, add that technique. And there is always > improvements with wordsmithing. > > Paddy: To be devil's advocate, there are a bunch of considerations, and yes > already know that. My problem is finding more detailed information. For > example, WURFL would help me understand device issues. > > Jon: Yes, I agree, and we should provide some additional detail and links to > important resources, such as WURFL. > > (question about whether we need to provide complete and comprehensive info) > > Rick: OK if the 1.0 release provides good value but doesn't provide complete > answer. We can always update the document. > > Jon: One additional detail I thought made sense was to talk about the iPhone > viewport. Everyone know what that is? (no one does, so jon explains) > > DavidP: One emerging industry standard is quarter VGA, 320x240. Half of the > devices coming up support that profile. iPhone doubles one dimension to 480. > > Paddy: But people need to know. W3C says if you target a particular low-res, > something like 220x???, you get 95% of the devices. Good to provide some > sort of measure. > > DavidP: Good point. > > Paddy: If I'm targeting an iphone, go here. If I'm targeting more devices, > go here. Let developers choose their target, but help them with links > relative to that target. But if you want to discuss the iPhone as the state > of the art today, then explicit information about the iPhone would have a > role. > > Jon: Agree. iPhone should be a small part of the document, but worth > pointing out at particular points. > > Paddy: Agree. > > > Intro > > DavidP: I think the proposed text is good. > > Andrew: Brief, which is good. > > > Characterizing... > > (no proposed text, no comments, so skip to next section) > > > In practice > > Jon: I think the train example is good, but we need more. It talks about the > widget case. We also need browser case. > > DavidP: Can we use the Google/iPhone example that Dave Burke showed in > Barcelona? > > Jon: Yes, that's a great example of Ajax. > > Jon: I can take a crack at writing up Google as an example. > > Andrew: Remove train example or augment? > > Jon: I'm thinking the train example shows the use of the Web Runtime as a > widget. > > Andrew: Sounds good. > > DavidP: Is the objective to show how it exists today or how cool it's going > to be? > > Jon: I think we want to reflect both evidence that it already exists today > but make sure users understand how cool it's going to be > > Andrew: iPhone shows both evidence and examples of how cool it's going to be > > > Next steps > > Jon: I'll work on the WP between now and next Thursday to finish up more > sections. I'll send email as I make progress so people can review. Please > everyone else contribute also, particularly on the tips for developers > section. > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile > > From jferrai at us.ibm.com Mon Mar 3 09:44:08 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 3 Mar 2008 09:44:08 -0800 Subject: [OpenAjaxMobile] Vista sidebar gadgets - APIs to access system services Message-ID: FYI - The following URL contains API documentation for JavaScript APIs to system services, such as contact list, memory utilization, power status, and Outlook Express email boxes: http://msdn2.microsoft.com/en-us/library/aa359256(VS.85).aspx I added this link to the Mobile Device APIs wiki page, even though Vista obviously isn't a mobile OS. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080303/51425fbd/attachment.html From jferrai at us.ibm.com Tue Mar 4 12:53:44 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 4 Mar 2008 12:53:44 -0800 Subject: [OpenAjaxMobile] First pass list of use cases for Mobile Device APIs Message-ID: I scratched out some use cases for Mobile Device APIs on the following wiki page: * http://www.openajax.org/member/wiki/Mobile_Device_APIs_Use_Cases I am sure that I am neglecting many other important use cases. I encourage others to supplement and/or modify the list that I have started. (It doesn't take much time to add a bullet to a wiki page.) Also, sometime soon we need to make start characterizing some of the security framework requirements, so if anyone has something to offer there, please put some text or pictures on the security wiki page: * http://www.openajax.org/member/wiki/Mobile_Device_APIs_Security Finally, don't forget to contribute to add your contributions to the white paper: * http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Remember, for the months of March and April, our phone calls will be on Thursday at 9am California time. Thanks. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080304/66011208/attachment.html From jferrai at us.ibm.com Wed Mar 5 14:47:06 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 5 Mar 2008 14:47:06 -0800 Subject: [OpenAjaxMobile] Reminder: phone call tomorrow Message-ID: Hi everyone, Just a reminder that we have a Mobile TF phone call tomorrow. If you have a chance to add data to the use cases, requirements, or security pages before the meeting, that would be great. If you have a chance to contribute text to the white paper, that is also a big positive. Jon Date: each Thursday (starting with March 6, ending with April 24) Time: 9amPT, noonET, 5pm GMT, 6pm Paris Agenda Device APIs Use cases: Mobile Device APIs Use Cases Requirements: Mobile Device APIs Requirements Security: Mobile Device APIs Security White paper: http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax Individual sections: MobileAjaxWhitePaper Title MobileAjaxWhitePaper Introduction MobileAjaxWhitePaper Characterizing Mobile Ajax Support Today MobileAjaxWhitePaper Mobile Ajax in Practice MobileAjaxWhitePaper Challenges and Opportunities for Developers MobileAjaxWhitePaper The Mobile Opportunity MobileAjaxWhitePaper Differences in User Interfaces MobileAjaxWhitePaper Top 10 Tips for Developers MobileAjaxWhitePaper Future MobileAjaxWhitePaper References MobileAjaxWhitePaper Glossary See below for call-in information. Conference Call PIN and Phone Numbers Passcode: 460566 Conference Access: Toll free: 1-888-619-1583 Toll: 1-719-457-1414 International toll free - Argentina: 0800 666 3149 International toll free - Australia: 1 800 105 680 International toll free - Austria: 0 800 291 941 International toll free - Belgium: 0 800 75 240 International toll free - Chile: 123 0020 9725 International toll free - China, Northern Region: 10 800 714 1201 International toll free - China, Southern Region: 10 800 140 1180 International toll free - Colombia: 01 800 518 0789 International toll free - Costa Rica: 0800 015 0616 International toll free - Czech Republic: 800 700 294 International toll free - Denmark: 80 886 215 International toll free - Dominican Republic: 1 888 751 4488 International toll free - Ecuador: 1 800 020 321 International toll free - France: 0 800 90 0161 International toll free - Germany: 0 800 181 9019 International toll free - Greece: 00 800 161 2205 5955 International toll free - Hong Kong: 800 901 110 International toll free - Hungary: 06 800 162 50 International toll free - India: 000 800 1006 980 International toll free - Indonesia: 001 803 017 5955 International toll free - Ireland: 1 800 760 547 International toll free - Israel: 1 809 246 041 International toll free - Italy: 800 873 739 International toll free - Japan: 00531 16 0844 International toll free - Lithuania: 8 800 3 05 25 International toll free - Luxembourg: 800 2 7665 International toll free - Malaysia: 1 800 813 714 International toll free - Mexico: 001 800 514 5955 International toll free - Monaco: 800 93 416 International toll free - Netherlands: 0 800 023 5303 International toll free - New Zealand: 0 800 451 015 International toll free - Norway: 800 196 65 International toll free - Panama: 00 800 226 5955 International toll free - Poland: 00 800 111 49 58 International toll free - Portugal: 800 819 728 International toll free - Russia: 810 800 2704 1012 International toll free - Singapore: 800 101 2002 International toll free - Slovenia: 0 800 80203 International toll free - South Africa: 0 800 980 988 International toll free - South Korea: 003 0813 1963 International toll free - Spain: 900 947 604 International toll free - Sweden: 02 079 7556 International toll free - Switzerland: 0 800 564 397 International toll free - Thailand: 001 800 156 205 5955 International toll free - Trinidad-Tobago: 1 800 205 5955 International toll free - UK: 0 808 101 1146 International toll free - Uruguay: 0004 019 0188 International toll free - Venezuela: 0 800 100 8300 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080305/420ea5de/attachment.html From chaals at opera.com Wed Mar 5 18:00:43 2008 From: chaals at opera.com (Charles McCathieNevile) Date: Thu, 06 Mar 2008 11:00:43 +0900 Subject: [OpenAjaxMobile] Regrets Re: Reminder: phone call tomorrow In-Reply-To: References: Message-ID: On Thu, 06 Mar 2008 07:47:06 +0900, Jon Ferraiolo wrote: > Hi everyone, > Just a reminder that we have a Mobile TF phone call tomorrow. Sorry folks, I will be in a plane. If for some reason it arrives an hour early, then I will be in U.S.Immigration queues, which is no better (and you are not allowe to use a phone...) :( cheers Chaals -- Charles McCathieNevile Opera Software, Standards Group je parle fran?ais -- hablo espa?ol -- jeg l?rer norsk http://my.opera.com/chaals Try Opera 9.5: http://snapshot.opera.com From rotan.hanrahan at mobileaware.com Wed Mar 5 19:23:18 2008 From: rotan.hanrahan at mobileaware.com (Rotan Hanrahan) Date: Wed, 5 Mar 2008 22:23:18 -0500 Subject: [OpenAjaxMobile] Regrets Re: Reminder: phone call tomorrow In-Reply-To: References: Message-ID: And I'm dealing with a W3C Face-to-Face meeting in Korea, so it could be tricky for me too. Should be back to normal next week. ---Rotan -----Original Message----- From: mobile-bounces at openajax.org [mailto:mobile-bounces at openajax.org] On Behalf Of Charles McCathieNevile Sent: 06 March 2008 02:01 To: OpenAjax Alliance discussion list on Mobile Ajax Subject: [OpenAjaxMobile] Regrets Re: Reminder: phone call tomorrow On Thu, 06 Mar 2008 07:47:06 +0900, Jon Ferraiolo wrote: > Hi everyone, > Just a reminder that we have a Mobile TF phone call tomorrow. Sorry folks, I will be in a plane. If for some reason it arrives an hour early, then I will be in U.S.Immigration queues, which is no better (and you are not allowe to use a phone...) :( cheers Chaals -- Charles McCathieNevile Opera Software, Standards Group je parle fran?ais -- hablo espa?ol -- jeg l?rer norsk http://my.opera.com/chaals Try Opera 9.5: http://snapshot.opera.com _______________________________________________ mobile mailing list mobile at openajax.org http://openajax.org/mailman/listinfo/mobile From paddy at aplixcorp.com Thu Mar 6 07:55:35 2008 From: paddy at aplixcorp.com (Paddy Byers) Date: Thu, 6 Mar 2008 15:55:35 +0000 Subject: [OpenAjaxMobile] Reminder: phone call tomorrow In-Reply-To: References: Message-ID: <59db1b5a0803060755r339030bco2bac3c727894ac42@mail.gmail.com> Hi, My apologies but I won't be able to make the call today. I will make some additions to the wiki. Thanks - Paddy On Wed, Mar 5, 2008 at 10:47 PM, Jon Ferraiolo wrote: > Hi everyone, > Just a reminder that we have a Mobile TF phone call tomorrow. > > If you have a chance to add data to the use cases, requirements, or > security pages before the meeting, that would be great. > > If you have a chance to contribute text to the white paper, that is also a > big positive. > > Jon > > > > - Date: each Thursday (starting with March 6, ending with April 24) > > - Time: 9amPT, noonET, 5pm GMT, 6pm Paris > - Agenda > - Device APIs > - Use cases: *Mobile Device APIs Use Cases* > - Requirements: *Mobile Device APIs > Requirements* > - Security: *Mobile Device APIs > Security* > - White paper: * > http://www.openajax.org/member/wiki/WP3_-_Mobile_Ajax > * > - Individual sections: > - *MobileAjaxWhitePaper Title* > - *MobileAjaxWhitePaper Introduction* > - *MobileAjaxWhitePaper Characterizing > Mobile Ajax Support Today* > - *MobileAjaxWhitePaper Mobile Ajax in > Practice* > - *MobileAjaxWhitePaper Challenges and > Opportunities for Developers* > - *MobileAjaxWhitePaper The > Mobile Opportunity* > - *MobileAjaxWhitePaper > Differences in User Interfaces > * > - *MobileAjaxWhitePaper Top 10 > Tips for Developers* > - *MobileAjaxWhitePaper Future* > - *MobileAjaxWhitePaper References* > - *MobileAjaxWhitePaper Glossary* > > See below for call-in information. > > > *Conference Call PIN and Phone Numbers * > Passcode: 460566 > > Conference Access: > Toll free: 1-888-619-1583 > Toll: 1-719-457-1414 > > International toll free - Argentina: 0800 666 3149 > International toll free - Australia: 1 800 105 680 > International toll free - Austria: 0 800 291 941 > International toll free - Belgium: 0 800 75 240 > International toll free - Chile: 123 0020 9725 > International toll free - China, Northern Region: 10 800 714 1201 > International toll free - China, Southern Region: 10 800 140 1180 > International toll free - Colombia: 01 800 518 0789 > International toll free - Costa Rica: 0800 015 0616 > International toll free - Czech Republic: 800 700 294 > International toll free - Denmark: 80 886 215 > International toll free - Dominican Republic: 1 888 751 4488 > International toll free - Ecuador: 1 800 020 321 > International toll free - France: 0 800 90 0161 > International toll free - Germany: 0 800 181 9019 > International toll free - Greece: 00 800 161 2205 5955 > International toll free - Hong Kong: 800 901 110 > International toll free - Hungary: 06 800 162 50 > International toll free - India: 000 800 1006 980 > International toll free - Indonesia: 001 803 017 5955 > International toll free - Ireland: 1 800 760 547 > International toll free - Israel: 1 809 246 041 > International toll free - Italy: 800 873 739 > International toll free - Japan: 00531 16 0844 > International toll free - Lithuania: 8 800 3 05 25 > International toll free - Luxembourg: 800 2 7665 > International toll free - Malaysia: 1 800 813 714 > International toll free - Mexico: 001 800 514 5955 > International toll free - Monaco: 800 93 416 > International toll free - Netherlands: 0 800 023 5303 > International toll free - New Zealand: 0 800 451 015 > International toll free - Norway: 800 196 65 > International toll free - Panama: 00 800 226 5955 > International toll free - Poland: 00 800 111 49 58 > International toll free - Portugal: 800 819 728 > International toll free - Russia: 810 800 2704 1012 > International toll free - Singapore: 800 101 2002 > International toll free - Slovenia: 0 800 80203 > International toll free - South Africa: 0 800 980 988 > International toll free - South Korea: 003 0813 1963 > International toll free - Spain: 900 947 604 > International toll free - Sweden: 02 079 7556 > International toll free - Switzerland: 0 800 564 397 > International toll free - Thailand: 001 800 156 205 5955 > International toll free - Trinidad-Tobago: 1 800 205 5955 > International toll free - UK: 0 808 101 1146 > International toll free - Uruguay: 0004 019 0188 > International toll free - Venezuela: 0 800 100 8300 > > > > _______________________________________________ > mobile mailing list > mobile at openajax.org > http://openajax.org/mailman/listinfo/mobile > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080306/0238e1d5/attachment-0001.html From jferrai at us.ibm.com Thu Mar 6 12:30:47 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Thu, 6 Mar 2008 12:30:47 -0800 Subject: [OpenAjaxMobile] Minutes from 2008-03-06 Message-ID: If there are any errors in these minutes, please say what corrections need to be made. Thanks. Jon ---------------------- Mobile Minutes 2008-03-06 URL: http://www.openajax.org/member/wiki/Mobile_Minutes_2008-03-06 Attendees Andrew Sledd, Ikivo (co-chair) Rick Saletta, Wavemaker David Pollington, Vodafone Paulo Neves, Present Technologies Nikunj Mehta, Oracle Jon Ferraiolo, IBM Minutes Device APIs Use Cases (part 1) Andy: Jon, you have added some wiki pages. Jon: Yes, I created a wiki pages for use cases, one for requirements, and one for security. I only added text to the use cases page because that seemed like where we should start. Andy: Ok to start with use cases? DavidP: Good idea to get use cases done first. Probably a lot we can provide here. Nikunj: It's hard to know if we have a good breadth of summaries. Is there a way to verify that we have good breadth or verifying our priorities? Rick: The only other use case I can think of is the ability to access a video or a song. Andy: We have until April 30 to decide whether we have a good list. Nikunj: We need to either prioritize or make sure that multiple pepole have contributed. DavidP: The use cases page splits things into 3 groups, web widgets, installable widgets, and device-resident apps. But the last two are much the same thing. Jon: From a technical perspective, yes, they might have the same security implications, but for use cases, these represent different workflows. In one, the user installs. In the other, the device manufacturers decides to include it. DavidP: Maybe have an installed app category with two sub-sections. Jon: That makes sense to me. I'll do it after the call. Nikunj: If we agree on grouping, I'll have more confidence about breadth. Andy: Let's look at the browser section Jon: Is this list valuable and interesting? Will the community actually want and do these things? Andy: Our experience with providers is that this is a key use case. Avoids installation but provides extended services. DavidP: There is an interesting philosophical question. People usually think about telephony services but it's more about the user data, such as calendar. There are more interesting things outside of telephony. For example, use the camera and upload a photo to a blog. This aligns with Web 2.0. This is all my personal view, not a VF view. Regarding security, want to do the easy stuff to get to the market quickly. Andy: I agree that's key. Easy to think of phone stuff. Need to provide the user with real benefits. For example, booking your flight and recording your confirmation number. These are the kinds of things you need. But they also point out key security issues. Nikunj: I agree. Need to target features that are available today. Location is not always available. What are we targeting? Jon: I would suggest we target phones that will ship 1-2 years from now. Whatever we do probably won't impact existing phones. Therefore, we need to be more forward thinking than backwards thinking. Nikunj: Yes, but still target features that are likely to be there. Jon: The generalization of this is to say we need to do a cost/benefit analysis and assign low priority to features that will be difficult for us to do and will get low levels of adoptin, and high priority to features that are easy to do and will get high adoption. DavidP: What do we want to put into requirement? Jon: For browser case, I was thinking two simple requirements. Need access to device APIs and need an appropriate security management system. DavidP: Maybe data persistence requirement falls out DavidP: Maybe requirement to notify the user Jon: One aspect of our security requirements would be either user notification or approval of particular attempts to access APIs DavidP: Would we have a separate framework for different scenarios, browser and installed? Jon: I want to suspend judgment until we get further in our discussions. Maybe yes, maybe no. Andy: Let's go to the next section, installable widgets. Jon: Like David said, it's installable. One question I have is whether the industry will care about anything OpenAjax might say about installable mobile widgets security. Andy: We will make them pay attention!?:-) Either the widget gets full access or limited access. Like a browser, whether something is fully trusted or has limited trust. Fully trusted hosts are granted extra rights. Andy: With a location-aware widget, it might upload your current location to a web site. This would be great in LA to find a way around traffic, but you have shared some privacy information with that web site. My assumption is that users already give trust to certain sites on the desktop and will do similar on mobile. DavidP: Aren't all APIs likely to be available across both browser and installable apps? Same issues. User privacy. Opt-in vs opt-out, levels of granularity. Andy: Probably not different security rights between browser and widget. DavidP: A web page that you can trust is likely to be the key. Jon: Good points! DavidP: Then comes the issue with Facebook. You might trust Facebook but not necessarily the components that might appear in Facebook. Andy: The key thing with security is what to *enable* versus disable. DavidP: For next week, we should all attempt to flesh out the use cases. And then start into the nitty gritty about security. (various): March 20 is a holiday in Europe. Also, week of AJAXWorld. Jon: Let's skip that week. White paper Rick: With the white paper, what's going on. We could take various people's comments and translate into revised text. Andy: Maybe move to preliminary final draft. That's what we talked about. DavidP: Need to consolidate and then review Rich: Need a date to close comments DavidP: I think we can close comments now. People have had enough time. Andy: I agree wholeheartedly. Get into a final document state, one final round of reviews, then set a final review date. (agreement) Rick: I'll start editing the full document next Monday. Device APIs Use Cases (part 2) (agree on a schedule) March 13th: use cases March 20th: no phone call, people should be working on security implications March 27th: discuss security implications, schedule a liaison call with Security TF Then 4 more weeks, where we need to Define criteria for prioritizing APIs Define what APIs we need and prioritize them -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080306/d4276d2e/attachment.html From jferrai at us.ibm.com Mon Mar 10 10:35:01 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 10 Mar 2008 10:35:01 -0700 Subject: [OpenAjaxMobile] Links to Vodafone MobileScript added to Mobile Device APIs page Message-ID: Using information provided by Vodafone, I updated our wiki page (http://www.openajax.org/member/wiki/Mobile_Device_APIs) that lists the various Mobile Device APIs technologies used in industry today to include a new section on Vodafone's MobileScript technologies. Below is a copy/paste of what I have added. I encourage our friends from Vodafone to review the introduction sentence I wrote below and make sure sure it is accurate, and if not, please fix it. Thanks. Jon ---------------------------------------- Vodafone's MobileScript Vodafone has done extensive work around both a specification and open source for a technology called MobileScript that provides JavaScript access to many different device-resident services, including location, mail, messaging (SMS and MMS), connection status, phone dialer, and more: Link to the project in Betavine: http://www.vodafonebetavine.net/web/MobileScripting Link to the project in Betavine Forge: https://forge.vodafonebetavine.net/projects/mobilescript/ Link to the installers and documentation: https://forge.vodafonebetavine.net/frs/download.php/48/VodafoneMobileScript2.0_WM_Installer.zip Link to a video of an standalone console using MobileScript: http://www.youtube.com/watch?v=4Qhn7lt_u7A Links to some videos of widgets using MobileScript + Opera Mobile: http://www.youtube.com/watch?v=DOswb88gJn4 http://www.youtube.com/watch?v=wch2q3Cdyjo http://www.youtube.com/watch?v=i0sh0wsUugE http://www.youtube.com/watch?v=2B7gic1FRaA Same videos but embedded within a device: http://www.youtube.com/watch?v=VRp-tjKdKVk http://www.youtube.com/watch?v=tBGVldNQPL4 http://www.youtube.com/watch?v=LK_vSjbLtdE http://www.youtube.com/watch?v=ANK3JQIE5UA -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080310/dd13e784/attachment.html From jferrai at us.ibm.com Tue Mar 11 08:15:47 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 11 Mar 2008 08:15:47 -0700 Subject: [OpenAjaxMobile] Vodafone Mobile Script 2.0 spec uploaded to wiki Message-ID: I uploaded the Vodafone MobileScript 2.0 spec to the wiki at the following location: http://www.openajax.org/member/wiki/Image:Vodafone_MobileScript_2.0_Spec_and_examples.pdf Please note that Vodafone MobileScript is a strawman specification created by Group R&D for demonstration and prototyping purposes. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/mobile/attachments/20080311/ac41a249/attachment.html From jferrai at us.ibm.com Tue Mar 11 17:54:04 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 11 Mar 2008 17:54:04 -0700 Subject: [OpenAjaxMobile] Adobe AIR approach to security Message-ID: http://labs.adobe.com/wiki/index.php/AIR:HTML_Security_FAQ This has relevance to our Mobile Device APIs work. What Adobe is doing is defining two sandboxes that can communicate with each other over a bridge: * The AIR Application Sandbox - contains logic that was installed on the local machine. This sandbox can access the AIR device APIs, such as the file system APIs (pretty much the equivalent functionality as stdio.h). This sandbox also can access any web url via cross-domain XHR. The big new security restriction with the latest version of AIR is that dynamically loaded JavaScript logic is disabled. You can't execute eval() [except for JSON subset], link to "javascript:", or include a