You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
711 lines
27 KiB
711 lines
27 KiB
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
|
|
<html lang='en' xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
|
|
<head>
|
|
<meta name="generator" content=
|
|
"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
|
|
|
|
<title>Social Web Incubator Group Teleconference -- 15 Jul
|
|
2009</title>
|
|
<link type="text/css" rel="STYLESHEET" href=
|
|
"http://www.w3.org/StyleSheets/base.css" />
|
|
<link type="text/css" rel="STYLESHEET" href=
|
|
"http://www.w3.org/StyleSheets/public.css" />
|
|
<link type="text/css" rel="STYLESHEET" href=
|
|
"http://www.w3.org/2004/02/minutes-style.css" />
|
|
<meta content="Social Web Incubator Group Teleconference" name=
|
|
"Title" />
|
|
<meta content="text/html; charset=utf-8" http-equiv=
|
|
"Content-Type" />
|
|
</head>
|
|
|
|
<body>
|
|
<p><a href="http://www.w3.org/"><img src=
|
|
"http://www.w3.org/Icons/w3c_home" alt="W3C" border="0" height=
|
|
"48" width="72" /></a></p>
|
|
|
|
<h1>Social Web Incubator Group Teleconference</h1>
|
|
|
|
<h2>15 Jul 2009</h2>
|
|
|
|
<p>See also: <a href="http://www.w3.org/2009/07/15-swxg-irc">IRC
|
|
log</a></p>
|
|
|
|
<h2><a name="attendees" id="attendees">Attendees</a></h2>
|
|
|
|
<div class="intro">
|
|
<dl>
|
|
<dt>Present</dt>
|
|
|
|
<dt>Regrets</dt>
|
|
|
|
<dt>Chair</dt>
|
|
|
|
<dd>DKA</dd>
|
|
|
|
<dt>Scribe</dt>
|
|
|
|
<dd>hhalpin, Mischa</dd>
|
|
</dl>
|
|
</div>
|
|
|
|
<h2>Contents</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
<a href="#agenda">Topics</a>
|
|
|
|
<ol>
|
|
<li><a href="#item01">Convene SWXG WG meeting of
|
|
2009-07-15T13:00-15:00Z</a></li>
|
|
|
|
<li><a href="#item02">General Organization and Task
|
|
Forces</a></li>
|
|
|
|
<li><a href="#item03">User Stories</a></li>
|
|
<li><a href="#item043">Simon Tenant and Oslo Alliance</a></li>
|
|
<li><a href="#item05">Matt Womer and W3C Geolocation API</a></li>
|
|
</ol>
|
|
</li>
|
|
|
|
<li><a href="#ActionSummary">Summary of Action Items</a></li>
|
|
</ul>
|
|
<hr />
|
|
|
|
<div class="meeting">
|
|
<p class='phone'> </p>
|
|
|
|
<p class='phone'> </p>
|
|
|
|
<p class='irc'><<cite>jsalvachua</cite>> zakim aabb is
|
|
me</p>
|
|
|
|
<p class='irc'><<cite>jsalvachua</cite>> oh i see ;)</p>
|
|
|
|
<p class='irc'><<cite>jsalvachua</cite>> thanks matt</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> scribe: hhalpin</p>
|
|
|
|
<p class='phone'><cite>Minutes:</cite></p>
|
|
|
|
<p class='phone'><a href=
|
|
"http://www.w3.org/2009/07/08-swxg-minutes.html">http://www.w3.org/2009/07/08-swxg-minutes.html</a></p>
|
|
|
|
<p class='phone'><cite>PROPOSED:</cite> Approve July 8th
|
|
minutes?</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>tpa</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>oshani</cite>> +1</p>
|
|
|
|
<p class='phone'><strong class='resolution'>RESOLUTION: July
|
|
8th minutes approved.</strong></p>
|
|
|
|
<p class='phone'>Note that DKA will be gone for 3 weeks
|
|
following.</p>
|
|
|
|
<p class='phone'>next meeting</p>
|
|
|
|
<h3 id="item01">Convene SWXG WG meeting of
|
|
2009-07-15T13:00-15:00Z</h3>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> Signed in to talk
|
|
about Oslo</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> +1</p>
|
|
|
|
<p class='phone'>It doesn't appear Mischa is on the call</p>
|
|
|
|
<p class='phone'>[CONTINUTES] <strong>ACTION:</strong> Mischa
|
|
to write up Soren and Jonathan's findings from last telecon for
|
|
final report.</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> Aha, speak of the
|
|
devil!</p><a name="action01" id="action01"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> danbri
|
|
circulate wookie proposal to the xg [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action01">http://www.w3.org/2009/07/15-swxg-minutes.html#action01</a>]</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> hello all, I dont
|
|
have voice today, I am sorry</p>
|
|
|
|
<p class='phone'>no problem mischa</p>
|
|
|
|
<p class='phone'>any luck on the actions?</p>
|
|
|
|
<p class='phone'><cite>cperey:</cite> Note that Christley from
|
|
Gypsii is next invited speaker</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> nope I have been
|
|
doing thesis, I will get them done by the next meeting</p>
|
|
|
|
<h3 id="item02">General Organization and Task Forces</h3>
|
|
|
|
<p class='phone'><cite>hhalpin:</cite> I propose that we then
|
|
focus on next meeting</p>
|
|
|
|
<h3 id="item03">User Stories</h3>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> My action was
|
|
finished!</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> about a month or 6
|
|
weeks ago</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> I tried to close it
|
|
out</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> but the service
|
|
didn't "accept"</p>
|
|
|
|
<p class='phone'><cite>cperey:</cite> I posted my list<br />
|
|
... the main challenge is how do we integrate this list<br />
|
|
... we should then leave them on.<br />
|
|
... we have had list-serv discussions<br />
|
|
... does it include content sharing services?<br />
|
|
... should we have a W3C approved definition?<br />
|
|
... An industry definition?<br />
|
|
... we need a relevant open item.</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> a principled way of
|
|
doing metrics</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> I'm really keen to
|
|
do this</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> harry will look at
|
|
the schedule to see when we can have a metrics discussoin</p>
|
|
|
|
<p class='phone'><cite>hhalpin:</cite> let's have a metric
|
|
discussion</p>
|
|
|
|
<p class='phone'><cite>DKA:</cite> have it for next week
|
|
call</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> I will not be
|
|
available July 29</p>
|
|
|
|
<p class='phone'><cite>DKA:</cite> Or for next call.</p>
|
|
|
|
<p class='phone'><cite>cperey:</cite> relevant for next
|
|
call</p>
|
|
|
|
<p class='phone'><cite>hhalpin:</cite> useful summary
|
|
report</p>
|
|
|
|
<p class='phone'><cite>cperey:</cite> will push to list the
|
|
past e-mails on this subject</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> I will point to the
|
|
past posts on this topic</p><a name="action02" id=
|
|
"action02"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> danbri
|
|
circulate wookie proposal to the xg [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action02">http://www.w3.org/2009/07/15-swxg-minutes.html#action02</a>]</p><a name="action03"
|
|
id="action03"></a>
|
|
|
|
<p class='irc'><<cite>scribe</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> Mischa to
|
|
describe/implement a report of terms and conditions, and how
|
|
they change between now and the end of the XG. [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action03">http://www.w3.org/2009/07/15-swxg-minutes.html#action03</a>]</p><a name="action04"
|
|
id="action04"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[DONE]</strong> Sören to
|
|
propose addition to the template for user stories for privacy
|
|
conditions [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action04">http://www.w3.org/2009/07/15-swxg-minutes.html#action04</a>]</p><a name="action05"
|
|
id="action05"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> adam to
|
|
write up the boeing use case for enterprise social networks
|
|
[recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action05">http://www.w3.org/2009/07/15-swxg-minutes.html#action05</a>]</p><a name="action06"
|
|
id="action06"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> hhalpin
|
|
to write up the social network data exchange story [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action06">http://www.w3.org/2009/07/15-swxg-minutes.html#action06</a>]</p><a name="action07"
|
|
id="action07"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[DONE]</strong> danbri to
|
|
write up widget business story. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action07">http://www.w3.org/2009/07/15-swxg-minutes.html#action07</a>]</p><a name="action08"
|
|
id="action08"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[DONE]</strong> jsalvachua to
|
|
write up business use-case with the company he's been working
|
|
with. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action08">http://www.w3.org/2009/07/15-swxg-minutes.html#action08</a>]</p><a name="action09"
|
|
id="action09"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> danbri to
|
|
write up widget business story. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action09">http://www.w3.org/2009/07/15-swxg-minutes.html#action09</a>]</p><a name="action10"
|
|
id="action10"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> tpa to
|
|
look for similar use cases list to expand ours [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action10">http://www.w3.org/2009/07/15-swxg-minutes.html#action10</a>]</p><a name="action11"
|
|
id="action11"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[CONTINUES]</strong> tinkster
|
|
to document danbri's microblogging provenance question as a
|
|
user story. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action11">http://www.w3.org/2009/07/15-swxg-minutes.html#action11</a>]</p>
|
|
|
|
<p class='irc'><<cite>jsalvachua</cite>> i wrote, just in
|
|
time, a first version its on the wiki</p>
|
|
|
|
<p class='phone'>yep, it's marked as done.</p>
|
|
|
|
<p class='phone'><cite>DKA:</cite> Simon Tenant, guest
|
|
spaker</p>
|
|
|
|
<p class='phone'><<cite>SimonTenant</cite>:> We are one of the founders of
|
|
mobile start-up Buddycloud</p>
|
|
|
|
<p class='phone'><<cite>SimonTenant</cite>:> Geolocation is one of the
|
|
elements of the a larger product</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> looked at Google's
|
|
efforts<br />
|
|
... applicaitons like Rumble, using location to recommend
|
|
relevant restaurants</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> is there a url for
|
|
the OSLO alliance</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> ?</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> buddycloud shows you
|
|
nearby friends<br />
|
|
... we started talking between each other that<br />
|
|
... we need to avoid an AOL IM scenario<br />
|
|
... too many different ways to do this<br />
|
|
... we wanted to come up with a way for this to be done<br />
|
|
... about 30 similar companies<br />
|
|
... it's where we've come from for OSLO.<br />
|
|
... we have working code<br />
|
|
... working federation now<br />
|
|
... so its working quite well<br />
|
|
... we're working through the teething problems<br />
|
|
... we're not trying to reinvent the wheel<br />
|
|
... we're on 13 signatories to first press release<br />
|
|
... looking at best of breed activities.<br />
|
|
... some talk of XMPP<br />
|
|
... we run on top of XMPP</p>
|
|
|
|
<p class='irc'><<cite>oshani</cite>> mischat, <a href=
|
|
"http://digital.venturebeat.com/2009/02/23/oslo-alliance-wants-to-share-location-across-networks/">
|
|
http://digital.venturebeat.com/2009/02/23/oslo-alliance-wants-to-share-location-across-networks/</a>
|
|
(from the agenda)</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> thanks oshani</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> we've applied a very
|
|
light specification on top of XMPP.</p>
|
|
|
|
<p class='irc'><<cite>matt</cite>> <a href=
|
|
"http://code.google.com/p/oslo-protocol/">the code (I
|
|
believe)</a></p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> these are the simple
|
|
situations<br />
|
|
... privacy, kickback of error</p>
|
|
|
|
<p class='phone'><cite>SimonTentant:</cite> Light touch on top
|
|
of exiting technologies, so within 2 months we have working
|
|
code and federation between Akai-Akai and BuddyCloud<br />
|
|
... we use XMPP to push this sort of stuff out<br />
|
|
... similar to instant messenger list<br />
|
|
... push location out in particular<br />
|
|
... the other side, these networks rely on mobile phone<br />
|
|
... these applications are running 24 seven<br />
|
|
... but mobile phone batteries can't handle this<br />
|
|
... by not default your not just popping up to everyone
|
|
nearby<br />
|
|
... but to people that allow them "opt-in"<br />
|
|
... much more exciting for users<br />
|
|
... great business driver</p>
|
|
|
|
<p class='irc'><<cite>DKA</cite>> Simon also noted: the
|
|
increased number of users available via OSLO chairing is a
|
|
business driver...</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> We can finally see mobile
|
|
location based advertising actually happen</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> nearby advertisements is a driver</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> OSLO is a way to help standardise
|
|
location-sharing in real-time</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> oslo is open, no master list of companies
|
|
which can join</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> to join all you have to do is publish a
|
|
statement in dns saying that you can share geo location</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> there is a trust network, networks can dictate
|
|
which other networks they wish to share with</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> users are in control of who they share their
|
|
location with</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> user love sharing location, just like
|
|
facebook, can live with out</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> privacy policies, users should always be able
|
|
to opt-out of sharing location</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> as well as giving user a level of granularity
|
|
to control who they share their location with</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> oslo plan to release code in the next couple
|
|
of weeks</p>
|
|
|
|
<p class='phone'><<cite>SimonTennant:</cite>> oslo allows people to share location between
|
|
networks</p>
|
|
|
|
<p class='phone'>oslo should scale,</p>
|
|
|
|
<p class='phone'><cite>DKA</cite>> 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 ?</p>
|
|
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite>> no not yet, but good
|
|
idea, and oslo should write this up</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> here again -
|
|
<a href=
|
|
"http://code.google.com/p/oslo-protocol/">http://code.google.com/p/oslo-protocol/</a></p>
|
|
|
|
<p class='phone'><cite>matt:</cite> is all of the work happening at
|
|
the code.google.com url above ^^?</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> yes, but we need to
|
|
commit to svn more often</p>
|
|
|
|
<p class='phone'><cite>matt:</cite> Have you thought about taking
|
|
this a standards body ?</p>
|
|
|
|
<p class='phone'><cite>SimonTeant:</cite> 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</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> OSLO =
|
|
server-to-server communication of location, rather than
|
|
user-to-server or user-to-user.</p>
|
|
|
|
<p class='irc'><<cite>jsalvachua</cite>> i agree is a
|
|
wonderful work.</p>
|
|
|
|
|
|
<p class='phone'>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</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite>> oslo hasn't created lots of code, BSD license,
|
|
based on XMPP and other open technologies</p>
|
|
|
|
<p class='phone'><cite>Oshani:</cite>>: does oslo handle location
|
|
history ?</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite>> oslo is about real-time
|
|
sharing of location</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> sounds like location
|
|
history saving policies are a place for user education/best
|
|
practices</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> A "time to live"
|
|
on each piece of location data?</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> oslo-protocol
|
|
nearby object query spec: <a href=
|
|
"http://code.google.com/p/oslo-protocol/wiki/NearbyObjectQuerySpec">
|
|
http://code.google.com/p/oslo-protocol/wiki/NearbyObjectQuerySpec</a></p>
|
|
|
|
<p class='phone'>you have to trust your friends to not
|
|
store/create histories of ones location</p>
|
|
|
|
<p class='irc'><<cite>matt</cite>> <a href=
|
|
"http://www.w3.org/2008/geolocation/"></a></p>
|
|
|
|
<p class='phone'>><<cite>DKA</cite>>introduces matt, w3c team contact for
|
|
geolocation working group</p>
|
|
|
|
<p class='phone'>they outputted the javascript geolocation
|
|
API</p>
|
|
|
|
<p class='irc'><<cite>matt</cite>> <a href=
|
|
"http://www.w3.org/TR/2009/WD-geolocation-API-20090707/">Last
|
|
Call WD</a></p>
|
|
|
|
<p class='phone'>the last call was last week</p>
|
|
|
|
<p class='phone'>there is a public geolocation API mailing
|
|
list</p>
|
|
|
|
<p class='phone'>the API is entirely based on javascript</p>
|
|
|
|
<p class='phone'>it is implemented in Opera, Safari, andriod,
|
|
google gears plugin</p>
|
|
|
|
<p class='phone'>and ff3.5 all implementing the geo location
|
|
API</p>
|
|
|
|
<p class='phone'>API is very simple, the ability to get a one
|
|
shot geo-location, and it can be used to track your
|
|
position</p>
|
|
|
|
<p class='irc'><<cite>matt</cite>> <a href=
|
|
"http://www.w3.org/TR/2009/WD-geolocation-API-20090707/#security">
|
|
http://www.w3.org/TR/2009/WD-geolocation-API-20090707/#security</a></p>
|
|
|
|
<p class='phone'>it is only a client side specification</p>
|
|
|
|
<p class='phone'>privacy is only considered at a wording
|
|
level</p>
|
|
|
|
<p class='phone'>you can try this out with google maps, and ff
|
|
3.5</p>
|
|
|
|
<p class='phone'>you should be able to see where you are</p>
|
|
|
|
<p class='phone'>the geolocation API does not dictate how the
|
|
user's location is located</p>
|
|
|
|
<p class='phone'>it could get the location from
|
|
wifi-triangulation, based on IP address gazatteer</p>
|
|
|
|
<p class='phone'>currently considering more address based
|
|
location descriptions, other than just lat/long</p>
|
|
|
|
<p class='phone'>for example, I am near a coffee shop, or near
|
|
this address</p>
|
|
|
|
<p class='irc'><<cite>inserted</cite>> Hhalpin:
|
|
hhalpin</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> sure hhalpin</p>
|
|
|
|
<p class='phone'><cite>DKA:</cite> has the group talked around
|
|
any scenarios about privacy?</p>
|
|
|
|
<p class='phone'><cite>Matt:</cite> privacy is about 90 percent
|
|
of the volume on the mailing list<br />
|
|
... we've tried to go a number of ways<br />
|
|
... IETF geopriv people came in<br />
|
|
... completely different use-cases<br />
|
|
... they were more towards how location is shared on wire<br />
|
|
... emergency services<br />
|
|
... a service built into a cable modem</p>
|
|
|
|
<p class='irc'><<cite>oshani</cite>> here's one use case
|
|
I drafted on the wiki based on geo location: <a href=
|
|
"http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Inferences_on_location_based_contextual_data">
|
|
http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Inferences_on_location_based_contextual_data</a></p>
|
|
|
|
<p class='phone'><cite>matt:</cite> life or death issues<br />
|
|
... in contrast, we are dealing with different use-cases<br />
|
|
... we are talking about "find me the nearest starbucks"<br />
|
|
... completely different privacy needs there<br />
|
|
... we thought about including in API the user's privacy
|
|
preferences</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> Probably not going
|
|
to use Javascript to report life-or-death emergencies.</p>
|
|
|
|
<p class='phone'><cite>matt:</cite> including rights within the
|
|
API<br />
|
|
... but bad people will do bad things and we cannot stop them
|
|
with the API but we will let browser take care of it.<br />
|
|
... otherwise, we ended up not including most discussed privacy
|
|
work<br />
|
|
... we imagine other device APIs<br />
|
|
... so now we have a Device API and Policy WG<br />
|
|
... we don't want each API to have a different take on
|
|
privacy</p>
|
|
|
|
<p class='phone'><cite>DKA:</cite> I understand that the
|
|
geolocation API decided not to deal with the question in the
|
|
WG<br />
|
|
... is there anywhere we in this XG should look to harvest some
|
|
of this privacy related work?</p>
|
|
|
|
<p class='irc'><<cite>DKA</cite>> Simon</p>
|
|
|
|
<p class='phone'><cite>Simon:</cite> the demos I've seen have
|
|
always used Skyhooks</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> Why not use
|
|
BuddyCloud?</p>
|
|
|
|
<p class='phone'><cite>Matt:</cite> We didn't include hooks for
|
|
this in the API<br />
|
|
...: How much knowledge do we expect users to have</p>
|
|
|
|
<p class='phone'><cite>matt:</cite> again, we punted this to
|
|
the browser<br />
|
|
... so the google gears plug-in is the editor<br />
|
|
... of the geolocation APIgoogle gears has a lot of work on
|
|
this<br />
|
|
... mozilla's implementation allows users to change this<br />
|
|
... had some JSON specification<br />
|
|
... but not baked into API.</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> Geolocation API =
|
|
assumes that the browser knows where the user is located, and
|
|
provides an API to allow Javascript to access it.</p>
|
|
|
|
<p class='phone'><cite>SimonTenant:</cite> Thanks!</p>
|
|
|
|
<p class='phone'><cite>hhalpin:</cite> long term prospects for
|
|
interoperability, given convergence of browser and mobile</p>
|
|
|
|
<p class='phone'><cite>Simon:</cite> We have a specification to
|
|
get location, and another one to continously sharing</p>
|
|
|
|
<p class='irc'><<cite>tinkster</cite>> To an extent, as
|
|
they each use WGS84, they're already pretty interoperable.</p>
|
|
|
|
<p class='phone'><cite>Simon:</cite> There is nothing to
|
|
prevent Oslo to use geolocation API to get the location, and
|
|
then sharing it via Oslo.</p>
|
|
|
|
<p class='phone'><cite>matt:</cite> we could not have said it
|
|
better<br />
|
|
... they work well together</p>
|
|
|
|
<p class='phone'>thanks!</p>
|
|
|
|
<p class='phone'><cite>DKA:</cite> Thanks for coming on the
|
|
call</p>
|
|
|
|
<p class='irc'><<cite>matt</cite>> Thanks for having
|
|
us!</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> are these speakers
|
|
going to be joining teh SWXG mailing list?</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> the topic of context
|
|
will be increasingly important</p>
|
|
|
|
<p class='irc'><<cite>matt</cite>> <a href=
|
|
"http://lists.w3.org/Archives/Public/public-geolocation/">Geolocation
|
|
WG's mailing list</a></p>
|
|
|
|
<p class='phone'><<cite>hhalpin</cite>> we should definitely get someone on that
|
|
geolocation WG list.</p>
|
|
|
|
<p class='irc'><<cite>mischat</cite>> bye all</p>
|
|
|
|
<p class='irc'><<cite>Adam</cite>> thank you to the
|
|
speakers!</p><a name="action12" id="action12"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> DKA to summarize OSLO and geoLocation
|
|
conversation in order to spread knowledge of these efforts
|
|
among W3C members. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action12">http://www.w3.org/2009/07/15-swxg-minutes.html#action12</a>]</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> 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].</p>
|
|
|
|
|
|
</div>
|
|
|
|
<h2><a name="ActionSummary" id="ActionSummary">Summary of Action
|
|
Items</a></h2><!-- Action Items -->
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> DKA to summarize
|
|
OSLO and geoLocation conversation in order to spread knowledge of
|
|
these efforts among W3C members. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action12">http://www.w3.org/2009/07/15-swxg-minutes.html#action12</a>]<br />
|
|
|
|
<br />
|
|
<strong>[PENDING]</strong> <strong>ACTION:</strong> adam to write
|
|
up the boeing use case for enterprise social networks [recorded
|
|
in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action05">http://www.w3.org/2009/07/15-swxg-minutes.html#action05</a>]<br />
|
|
|
|
<strong>[PENDING]</strong> <strong>ACTION:</strong> danbri to
|
|
write up widget business story. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action09">http://www.w3.org/2009/07/15-swxg-minutes.html#action09</a>]<br />
|
|
|
|
<strong>[PENDING]</strong> <strong>ACTION:</strong> hhalpin to
|
|
write up the social network data exchange story [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action06">http://www.w3.org/2009/07/15-swxg-minutes.html#action06</a>]<br />
|
|
|
|
<strong>[PENDING]</strong> <strong>ACTION:</strong> Mischa to
|
|
describe/implement a report of terms and conditions, and how they
|
|
change between now and the end of the XG. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action03">http://www.w3.org/2009/07/15-swxg-minutes.html#action03</a>]<br />
|
|
|
|
<strong>[PENDING]</strong> <strong>ACTION:</strong> tinkster to
|
|
document danbri's microblogging provenance question as a user
|
|
story. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action11">http://www.w3.org/2009/07/15-swxg-minutes.html#action11</a>]<br />
|
|
|
|
<strong>[PENDING]</strong> <strong>ACTION:</strong> tpa to look
|
|
for similar use cases list to expand ours [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action10">http://www.w3.org/2009/07/15-swxg-minutes.html#action10</a>]<br />
|
|
|
|
<br />
|
|
<strong>[DONE]</strong> <strong>ACTION:</strong> danbri to write
|
|
up widget business story. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action07">http://www.w3.org/2009/07/15-swxg-minutes.html#action07</a>]<br />
|
|
|
|
<strong>[DONE]</strong> <strong>ACTION:</strong> jsalvachua to
|
|
write up business use-case with the company he's been working
|
|
with. [recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action08">http://www.w3.org/2009/07/15-swxg-minutes.html#action08</a>]<br />
|
|
|
|
<strong>[DONE]</strong> <strong>ACTION:</strong> Sören to propose
|
|
addition to the template for user stories for privacy conditions
|
|
[recorded in <a href=
|
|
"http://www.w3.org/2009/07/15-swxg-minutes.html#action04">http://www.w3.org/2009/07/15-swxg-minutes.html#action04</a>]<br />
|
|
|
|
<br />
|
|
[End of minutes]<br />
|
|
<hr />
|
|
|
|
<address>
|
|
Minutes formatted by David Booth's <a href=
|
|
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">
|
|
scribe.perl</a> version 1.135 (<a href=
|
|
"http://dev.w3.org/cvsweb/2002/scribe/">CVS log</a>)<br />
|
|
$Date: 2009/07/15 19:11:05 $
|
|
</address>
|
|
|
|
</body>
|
|
</html>
|