13:02:12 RRSAgent has joined #swxg 13:02:12 logging to http://www.w3.org/2009/07/15-swxg-irc 13:02:18 zakim aabb is me 13:02:26 zakim, aabb is jsalvachua 13:02:26 +jsalvachua; got it 13:02:33 +??P1 13:02:37 oh i see ;) 13:02:42 thanks matt 13:03:01 -??P1 13:03:05 Zakim, what's on the agenda? 13:03:05 I see nothing on the agenda 13:03:20 agenda+ Convene SWXG WG meeting of 2009-07-15T13:00-15:00Z 13:03:28 agenda+ General Organization and Task Forces 13:03:29 chair: DKA 13:03:33 agenda+ User Stories 13:03:39 agenda+ Invited Guest Invitations 13:03:43 +??P1 13:03:44 agenda+ Social Network Matrix 13:03:50 agenda+ Invited Speaker: Simon Tennant from Buddycloud (OSLO) 13:03:55 agenda+ Matt Womer (W3C) on W3C Geolocation Work 13:04:10 +??P2 13:04:22 Zakim, what's on the agenda? 13:04:22 I see 7 items remaining on the agenda: 13:04:23 1. Convene SWXG WG meeting of 2009-07-15T13:00-15:00Z [from tpa] 13:04:23 Zakim, ??P2 is hhalpin 13:04:25 2. General Organization and Task Forces [from tpa] 13:04:26 3. User Stories [from tpa] 13:04:27 4. Invited Guest Invitations [from tpa] 13:04:28 5. Social Network Matrix [from tpa] 13:04:30 6. Invited Speaker: Simon Tennant from Buddycloud (OSLO) [from tpa] 13:04:31 7. Matt Womer (W3C) on W3C Geolocation Work [from tpa] 13:04:33 +hhalpin; got it 13:04:52 Zakim, +??P1 is me 13:04:52 sorry, melvster, I do not recognize a party named '+??P1' 13:05:01 scribe: hhalpin 13:05:13 + +0785583aacc 13:05:29 zakim, +0785583aacc is me 13:05:29 +tinkster; got it 13:05:30 Minutes: 13:05:35 zakim, mute me 13:05:35 tinkster should now be muted 13:05:52 + +049178545aadd 13:05:54 http://www.w3.org/2009/07/08-swxg-minutes.html 13:05:58 + +1.314.683.aaee 13:06:05 cperey has joined #SWXG 13:06:08 PROPOSED: Approve July 8th minutes? 13:06:14 +1 13:06:15 +1 13:06:18 +1 13:06:21 RESOLVED: July 8th minutes approved. 13:06:33 zakim, who is present? 13:06:34 I don't understand your question, matt. 13:06:36 zakim, who is here? 13:06:36 On the phone I see tpa, DKA, Matt (muted), oshani (muted), jsalvachua, ??P1, hhalpin, tinkster (muted), +049178545aadd, +1.314.683.aaee 13:06:39 On IRC I see cperey, RRSAgent, matt, jsalvachua, DKA, Zakim, tpa, oshani, hhalpin, melvster, Adam, danbri, tinkster, FabGandon, karl, AlexPassant, Cloud_, CaptSolo, trackbot, dom 13:06:44 + +1.617.848.aaff 13:06:48 Note that DKA will be gone for 3 weeks following. 13:06:53 next meeting 13:06:54 Zakim, next agendum 13:06:54 agendum 1. "Convene SWXG WG meeting of 2009-07-15T13:00-15:00Z" taken up [from tpa] 13:06:56 zakim, who's here? 13:06:57 On the phone I see tpa, DKA, Matt (muted), oshani (muted), jsalvachua, ??P1, hhalpin, tinkster (muted), +049178545aadd, +1.314.683.aaee, +1.617.848.aaff 13:06:59 Zakim, next agendum 13:07:00 On IRC I see cperey, RRSAgent, matt, jsalvachua, DKA, Zakim, tpa, oshani, hhalpin, melvster, Adam, danbri, tinkster, FabGandon, karl, AlexPassant, Cloud_, CaptSolo, trackbot, dom 13:07:03 agendum 1 was just opened, tpa 13:07:17 MacTed has joined #swxg 13:07:18 Zakim, take up next agendum 13:07:18 agendum 1 was just opened, tpa 13:07:21 SimonTenant: Signed in to talk about Oslo 13:07:25 zakim, aadd is SimonTenant 13:07:25 +SimonTenant; got it 13:07:27 zakim, I am +1.617.848.aaff 13:07:27 +cperey; got it 13:07:39 +1 13:07:41 +Kingsley_Idehen 13:07:51 zakim, aaee is Adam 13:07:51 +Adam; got it 13:07:58 Zakim, close agendum 1 13:07:58 agendum 1, Convene SWXG WG meeting of 2009-07-15T13:00-15:00Z, closed 13:07:58 Zakim, Kingsley_Idehen is OpenLink_Software 13:07:59 I see 6 items remaining on the agenda; the next one is 13:08:01 2. General Organization and Task Forces [from tpa] 13:08:02 +OpenLink_Software; got it 13:08:08 Zakim, OpenLink_Software is temporarily MacTed 13:08:08 +MacTed; got it 13:08:12 Zakim, mute me 13:08:12 MacTed should now be muted 13:08:35 It doesn't appear Mischa is on the call 13:08:35 Zakim, ??P1 is me 13:08:35 +melvster; got it 13:09:00 [CONTINUTES] ACTION: Mischa to write up Soren and Jonathan's findings from last telecon for final report. 13:09:04 + +0798919aagg 13:09:17 mischat has joined #swxg 13:09:26 - +0798919aagg 13:09:29 Aha, speak of the devil! 13:09:36 [CONTINUES] ACTION: danbri circulate wookie proposal to the xg 13:10:02 + +0798919aahh 13:10:07 zakim, +0798919aagg is probably mischat 13:10:07 sorry, tinkster, I do not understand your question 13:10:19 zakim, 0798919aahh is me 13:10:19 sorry, mischat, I do not recognize a party named '0798919aahh' 13:10:28 zakim, aahh is mischat 13:10:28 +mischat; got it 13:10:44 hello all, I dont have voice today, I am sorry 13:10:49 no problem mischa 13:10:52 any luck on the actions? 13:11:03 cperey: Note that Christley from Gypsii is next invited speaker 13:11:07 nope I have been doing thesis, I will get them done by the next meeting 13:11:19 Zakim, next agendum 13:11:19 agendum 2. "General Organization and Task Forces" taken up [from tpa] 13:11:22 hhalpin: I propose that we then focus on next meeting 13:11:30 Zakim, really close this agendum 13:11:30 agendum 2 closed 13:11:31 I see 5 items remaining on the agenda; the next one is 13:11:33 3. User Stories [from tpa] 13:12:01 PhilA2 has joined #swxg 13:12:41 Zakim, next agendum 13:12:41 agendum 3. "User Stories" taken up [from tpa] 13:12:41 My action was finished! 13:12:43 -SimonTenant 13:12:47 +Phil_Archer 13:12:47 Zakim, next agendum 13:12:47 about a month or 6 weeks ago 13:12:48 agendum 3 was just opened, hhalpin 13:12:51 I tried to close it out 13:12:55 Zakim, really close this agendum 13:12:55 agendum 3 closed 13:12:56 I see 4 items remaining on the agenda; the next one is 13:12:57 4. Invited Guest Invitations [from tpa] 13:13:00 but the service didn't "accept" 13:13:17 +SimonTenant 13:13:31 cperey: I posted my list 13:13:39 cperey: the main challenge is how do we integrate this list 13:13:56 ... we should then leave them on. 13:14:03 ... we have had list-serv discussions 13:14:10 ... does it include content sharing services? 13:14:17 ... should we have a W3C approved definition? 13:14:21 ... An industry definition? 13:14:31 ... we need a relevant open item. 13:15:22 +1 13:15:31 a principled way of doing metrics 13:15:35 I"m really keen to do this 13:15:51 +1 13:16:14 harry will look at the schedule to see when we can have a metrics discussoin 13:16:15 hhalpin: let's have a metric discussion 13:16:21 DKA: have it for next week call 13:16:26 I will not be available July 29 13:16:29 DKA: Or for next call. 13:16:56 cperey: relevant for next call 13:17:25 hhalpin: useful summary report 13:17:37 cperey: will push to list the past e-mails on this subject 13:17:37 I will point to the past posts on this topic 13:17:54 [CONTINUES] ACTION: danbri circulate wookie proposal to the xg 13:18:10 [CONTINUES] ACTION:Mischa to describe/implement a report of terms and conditions, and how they change between now and the end of the XG. 13:18:20 [DONE] ACTION: Sören to propose addition to the template for user stories for privacy conditions 13:18:31 [CONTINUES] ACTION: adam to write up the boeing use case for enterprise social networks 13:18:41 [CONTINUES] ACTION:hhalpin to write up the social network data exchange story 13:18:50 [DONE] ACTION: danbri to write up widget business story. 13:19:01 [DONE] ACTION: jsalvachua to write up business use-case with the company he's been working with. 13:19:13 [CONTINUES] ACTION: danbri to write up widget business story. 13:19:26 [CONTINUES] ACTION: tpa to look for similar use cases list to expand ours 13:19:33 [CONTINUES] ACTION: tinkster to document danbri's microblogging provenance question as a user story. 13:19:36 i wrote, just in time, a first version its on the wiki 13:19:44 yep, it's marked as done. 13:19:52 DKA: Simon Tenant, guest spaker 13:20:09 Simon Tenant: We are one of the founders of mobile start-up BuddyLand 13:20:20 s/BuddyLand/Buddycloud/ 13:20:46 Simon Tenant: Geolocation is one of the elements of the a larger product 13:20:57 ... looked at Google's efforts 13:21:10 ... applicaitons like Rumble, using location to recommend relevant restaurants 13:21:14 is there a url for the OSLO alliance 13:21:16 ? 13:21:17 ... buddycloud shows you nearby friends 13:21:26 ... we started talking between each other that 13:21:34 ... we need to avoid an AOL IM scenario 13:21:40 ... too many different ways to do this 13:21:46 ... we wanted to come up with a way for this to be done 13:21:51 ... about 30 similar companies 13:21:59 ... it's where we've come from for OSLO. 13:22:20 ... we have working code 13:22:25 ... working federation now 13:22:30 ... so its working quite well 13:22:37 ... we're working through the teething problems 13:22:44 ... we're not trying to reinvent the wheel 13:23:12 ... we're on 13 signatories to first press release 13:23:18 ... looking at best of breed activities. 13:23:23 ... some talk of XMPP 13:23:27 ... we run on top of XMPP 13:23:31 mischat, http://digital.venturebeat.com/2009/02/23/oslo-alliance-wants-to-share-location-across-networks/ (from the agenda) 13:23:44 thanks oshani 13:23:56 ... we've applied a very light specification on top of XMPP. 13:23:57 -> http://code.google.com/p/oslo-protocol/ the code (I believe) 13:24:05 .... these are the simple situations 13:24:11 ... privacy, kickback of error 13:24:41 SimonTentant: Light touch on top of exiting technologies, so within 2 months we have working code and federation between Akai-Akai and BuddyCloud 13:25:26 ... we use XMPP to push this sort of stuff out 13:25:31 ... similar to instant messenger list 13:25:36 ... push location out in particular 13:25:47 ... the other side, these networks rely on mobile phone 13:25:57 ... these applications are running 24 seven 13:26:25 ... but mobile phone batteries can't handle this 13:26:38 ... by not default your not just popping up to everyone nearby 13:26:45 ... but to people that allow them "opt-in" 13:26:52 ... much more exciting for users 13:27:51 ... great business driver 13:27:51 Simon also noted: the increased number of users available via OSLO chairing is a business driver... 13:28:18 Simon Tenant: We can finally see mobile location based advertising actually happen 13:28:31 s/Tenant/Tennant 13:28:46 ok hhalpin 13:28:51 be back in one sec... 13:29:08 scribeNick: hhalpin 13:29:16 scribe: Mischa 13:29:17 nearby advertisements is a driver 13:29:19 -hhalpin 13:29:33 OSLO is a way to help standardise location-sharing in real-time 13:29:50 oslo is open, no master list of companies which can join 13:30:31 to join all you have to do is publish a statement in dns saying that you can share geo location 13:30:57 there is a trust network, networks can dictate which other networks they wish to share with 13:31:18 users are in control of who they share their location with 13:31:20 rrsagent, draft minutes 13:31:20 I have made the request to generate http://www.w3.org/2009/07/15-swxg-minutes.html matt 13:31:20 q+ to ask if these principles of user choice etc... are written down anywhere? 13:31:38 rrsagent, make logs public 13:31:50 user love sharing location, just like facebook, can live with out 13:32:02 hhalpin has joined #swxg 13:32:05 privacy policies, users should always be able to opt-out of sharing location 13:32:40 as well as giving user a level of granularity to control who they share their location with 13:32:50 oslo plan to release code in the next couple of weeks 13:33:36 oslo allows people to share location between networks 13:33:40 Meeting: Social Web Incubator Group Teleconference 13:33:47 Chair: DKA, hhalpin 13:33:49 oslo should scale, 13:35:03 q+ to ask about Google code link, is that where everything is happening? 13:35:10 tpa has joined #swxg 13:35:37 question from DKA (?) you talk about user's ability to select which networks to share with, and how networks can decide to who other networks to share with, have you owriten this up ? 13:35:40 ack me 13:35:41 matt, you wanted to ask about Google code link, is that where everything is happening? 13:35:45 ack matt 13:36:03 answer: no not yet, but good idea, and oslo should write this up 13:36:05 here again - http://code.google.com/p/oslo-protocol/ 13:36:28 question matt: is all of the work happening at the code.google.com url above ^^? 13:36:45 zakim, mute me 13:36:45 Matt should now be muted 13:36:45 answer : yes, but we need to commit to svn more often 13:37:00 question matt: Have you thought about taking this a standards body ? 13:37:18 lkagal has joined #swxg 13:38:19 answer: oslo doesn't state how you get your location, this is up the client/user, oslo is more about best practises when it comes to sharing location 13:38:41 zakim, who is noisy? 13:38:52 matt, listening for 10 seconds I heard sound from the following: SimonTenant (34%), DKA (59%) 13:39:05 OSLO = server-to-server communication of location, rather than user-to-server or user-to-user. 13:39:13 i agree is a wonderful work. 13:39:15 q+ to ask about location history 13:39:23 q? 13:39:35 ack DKA 13:39:35 DKA, you wanted to ask if these principles of user choice etc... are written down anywhere? 13:40:54 so much more context about a user, other than just location, would be nice to be able to share more than just location, oslo would like integrate/be involved with any other context sharing 13:41:26 oshani, you wanted to ask about location history 13:41:50 oslo hasn't created lots of code, BSD license, based on XMPP and other open technologies 13:42:23 question oshani : does oslo handle location history ? 13:42:40 answer: oslo is about real-time sharing of location 13:42:48 sounds like location history saving policies are a place for user education/best practices 13:43:00 A "time to live" on each piece of location data? 13:43:03 oslo-protocol nearby object query spec: http://code.google.com/p/oslo-protocol/wiki/NearbyObjectQuerySpec 13:43:22 you have to trust your friends to not store/create histories of ones location 13:43:38 zakim, unmute me 13:43:38 Matt should no longer be muted 13:43:58 -> http://www.w3.org/2008/geolocation/ 13:44:14 introduces matt, w3c team contact for geolocation working group 13:44:36 they outputted the javascript geolocation API 13:44:43 -> http://www.w3.org/TR/2009/WD-geolocation-API-20090707/ Last Call WD 13:44:49 the last call was last week 13:45:14 there is a public geolocation API mailing list 13:45:43 the API is entirely based on javascript 13:46:06 it is implemented in Opera, Safari, andriod, google gears plugin 13:46:17 and ff3.5 all implementing the geo location API 13:46:40 API is very simple, the ability to get a one shot geo-location, and it can be used to track your position 13:46:57 http://www.w3.org/TR/2009/WD-geolocation-API-20090707/#security 13:47:00 it is only a client side specification 13:47:18 privacy is only considered at a wording level 13:47:34 +??P2 13:47:44 Zakim, ??P2 is me 13:47:44 +AlexPassant; got it 13:47:50 you can try this out with google maps, and ff 3.5 13:47:59 you should be able to see where you are 13:48:35 the geolocation API does not dictate how the user's location is located 13:49:05 it could get the location from wifi-triangulation, based on IP address gazatteer 13:49:35 -SimonTenant 13:49:38 +??P18 13:49:45 Zakim, ??P18 is hhalpin 13:49:45 +hhalpin; got it 13:49:48 currently considering more address based location descriptions, other than just lat/long 13:50:11 for example, I am near a coffee shop, or near this address 13:50:38 DKA: has the group talked around any scenarios about privacy? 13:50:44 +??P3 13:51:11 Matt: privacy is about 90 percent of the volume on the mailing list 13:51:30 matt: we've tried to go a number of ways 13:51:37 matt: IETF geopriv people came in 13:51:48 ... completely different use-cases 13:51:57 ... they were more towards how location is shared on wire 13:52:01 ... emergency services 13:52:11 ... a service built into a cable modem 13:52:13 here's one use case I drafted on the wiki based on geo location: http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Inferences_on_location_based_contextual_data 13:52:16 ... life or death issues 13:52:24 ... in contrast, we are dealing with different use-cases 13:52:33 ... we are talking about "find me the nearest starbucks" 13:52:46 ... completely different privacy needs there 13:52:56 ... we thought about including in API the user's privacy preferences 13:53:00 Probably not going to use Javascript to report life-or-death emergencies. 13:53:23 ... including rights within the API 13:53:42 ... but bad people will do bad things and we cannot stop them with the API but we will let browser take care of it. 13:54:09 ... otherwise, we ended up not including most discussed privacy work 13:54:15 ... we imagine other device APIs 13:54:22 ... so now we have a Device API and Privacy WG 13:54:33 s/Privacy/Policy/ 13:54:35 ... we don't want each API to have a different take on privacy 13:55:24 DKA: I understand that the geolocation API decided not to deal with the question in the WG 13:56:01 ... is there anywhere we in this XG should look to harvest some of this privacy related work? 13:56:11 q? 13:57:04 Simon 13:57:12 Simon: the demos I've seen have always used Skyhooks 13:57:19 SimonTenant: Why not use BuddyCloud? 13:57:28 Matt: We didn't include hooks for this in the API 13:57:44 ...: How much knowledge do we expect users to have 13:57:57 matt: again, we punted this to the browser 13:58:14 ... so the google gears plug-in is the editor 13:58:27 ... of the geolocation APIgoogle gears has a lot of work on this 13:58:53 ... mozilla's implementation allows users to change this 13:58:57 ... had some JSON specification 13:59:02 ... but not baked into API. 13:59:13 Geolocation API = assumes that the browser knows where the user is located, and provides an API to allow Javascript to access it. 13:59:14 SimonTenant: Thanks! 13:59:23 q+ 13:59:30 ack hh 14:00:28 -jsalvachua 14:00:35 jsalvachua has left #swxg 14:00:42 hhalpin: long term prospects for interoperability, given convergence of browser and mobile 14:01:11 Simon: We have a specification to get location, and another one to continously sharing 14:01:28 To an extent, as they each use WGS84, they're already pretty interoperable. 14:01:29 Simon: There is nothing to prevent Oslo to use geolocation API to get the location, and then sharing it via Oslo. 14:01:39 matt: we could not have said it better 14:02:06 ... they work well together 14:02:15 thanks! 14:02:28 DKA: Thanks for coming on the call 14:02:38 Thanks for having us! 14:02:50 are these speakers going to be joining teh SWXG mailing list? 14:03:14 the topic of context will be increasingly important 14:03:15 -> http://lists.w3.org/Archives/Public/public-geolocation/ Geolocation WG's mailing list 14:03:27 we should definitely get someone on that geolocation WG list. 14:05:06 -cperey 14:05:13 bye all 14:05:16 thank you to the speakers! 14:05:20 -mischat 14:05:21 -Adam 14:05:21 -tpa 14:05:24 -tinkster 14:05:25 -Matt 14:05:25 tpa has left #swxg 14:05:27 ACTION: DKA to summarize OSLO and geoLocation conversation in order to spread knowledge of these efforts among W3C members. 14:05:27 Created ACTION-58 - Summarize OSLO and geoLocation conversation in order to spread knowledge of these efforts among W3C members. [on Daniel Appelquist - due 2009-07-22]. 14:05:27 -DKA 14:05:29 -Phil_Archer 14:05:29 -??P3 14:05:32 -AlexPassant 14:05:33 -MacTed 14:05:34 -melvster 14:05:34 RRSAgent, generate minutes 14:05:34 I have made the request to generate http://www.w3.org/2009/07/15-swxg-minutes.html hhalpin 14:05:40 RRSAgent, make logs public 14:06:17 RRSAgent, generate minutes 14:06:17 I have made the request to generate http://www.w3.org/2009/07/15-swxg-minutes.html hhalpin 14:07:00 take care! 14:08:20 -hhalpin 14:10:19 i/sure hh/Scribe: hhalpin/ 14:10:21 PhilA2 has left #swxg 14:10:22 rrsagent, draft minutes 14:10:22 I have made the request to generate http://www.w3.org/2009/07/15-swxg-minutes.html matt 14:14:31 FabGandon has left #swxg 14:15:05 oshani has joined #swxg 14:21:41 tpa_ has joined #swxg 14:41:38 FabGandon has joined #swxg 15:05:00 disconnecting the lone participant, oshani, in INC_SWXG()9:00AM 15:05:01 INC_SWXG()9:00AM has ended 15:05:10 Attendees were +63.59.2.aaaa, DKA, tpa, Matt, oshani, +34.91.549.aabb, jsalvachua, hhalpin, tinkster, +049178545aadd, +1.314.683.aaee, +1.617.848.aaff, SimonTenant, cperey, Adam, 15:05:12 ... MacTed, melvster, +0798919aagg, +0798919aahh, mischat, Phil_Archer, AlexPassant 16:19:40 Well, oshani, Zakim has saved you an enormous phone bill then. 16:21:14 tinkster, MIT's phone bill actually :) 16:21:37 The phone started rebooting half-way through the call and I thought I'd disconneted 16:21:52 not sure what happened 16:41:50 lkagal has joined #swxg