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.
835 lines
30 KiB
835 lines
30 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 (vers 6 November 2007), see www.w3.org" />
|
|
|
|
<title>Social Web Incubator Group Teleconference -- 03 Mar
|
|
2010</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>- DRAFT -</h1>
|
|
|
|
<h1>Social Web Incubator Group Teleconference</h1>
|
|
|
|
<h2>03 Mar 2010</h2>
|
|
|
|
<p>See also: <a href="http://www.w3.org/2010/03/03-swxg-irc">IRC
|
|
log</a></p>
|
|
|
|
<h2><a name="attendees" id="attendees">Attendees</a></h2>
|
|
|
|
<div class="intro">
|
|
<dl>
|
|
<dt>Present</dt>
|
|
|
|
<dd>+41.79.200.aaaa, MacTed, +049173900aabb, +049173537aacc,
|
|
AnitaD, tpa, oshani, melvster, hhalpin, DKA, yoshiaki,
|
|
Carine, +49.173.537.aadd</dd>
|
|
|
|
<dt>Regrets</dt>
|
|
|
|
<dt>Chair</dt>
|
|
|
|
<dd>hhalpin</dd>
|
|
|
|
<dt>Scribe</dt>
|
|
|
|
<dd>Dan, DKA</dd>
|
|
</dl>
|
|
</div>
|
|
|
|
<h2>Contents</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
<a href="#agenda">Topics</a>
|
|
|
|
<ol>
|
|
<li><a href="#item01">Convene SWXG WG meeting of
|
|
2010-03-03T16:00-17:00GMT</a></li>
|
|
|
|
<li><a href="#item02">Minutes</a></li>
|
|
|
|
<li><a href="#item03">Action reminders.</a></li>
|
|
|
|
<li><a href="#item04">Action Reminders</a></li>
|
|
|
|
<li><a href="#item05">Tim's Pearls of Wisdom</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>trackbot</cite>> Date: 03 March
|
|
2010</p>
|
|
|
|
<p class='phone'>hi</p>
|
|
|
|
<h3 id="item01">Convene SWXG WG meeting of
|
|
2010-03-03T16:00-17:00GMT</h3>
|
|
|
|
<p class='phone'>can you chair actually today?</p>
|
|
|
|
<p class='phone'>I am happy to scribe.</p>
|
|
|
|
<p class='irc'><<cite>scribe</cite>> Scribe: Dan</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> scribe: DKA</p>
|
|
|
|
<p class='irc'><<cite>scribe</cite>> ScribeNick: DKA</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> scribenick: DKA</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> PROPOSED: to
|
|
approve SWXG WG Weekly -- 24 February 2010 as a true record</p>
|
|
|
|
<h3 id="item02">Minutes</h3>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> <a href=
|
|
"http://www.w3.org/2010/02/24-swxg-minutes.html">http://www.w3.org/2010/02/24-swxg-minutes.html</a></p>
|
|
|
|
<p class='phone'>+1</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>tpa</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>yoshiaki</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> APPROVED: SWXG WG
|
|
Weekly -- 24 February 2010 as a true record</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> PROPOSED: to meet
|
|
again Wed. March 10th: Social APIs and Mobile Widgets: Thomas
|
|
Roessler on DAP, Scott Wilson on OpenSocial Shindig, and Robin
|
|
Berjon and Marcos Carecas on W3C Widgets.</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> Next week - interesting
|
|
week - there's been a lot of talk of OpenSocial and its
|
|
connection to w3c widgets.<br />
|
|
... current work in the Apache foundation might [be a
|
|
bridge]</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> 5:00UTC</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> Not 4:00UTC?</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> the issue is - because of
|
|
everyone's schedule, they won't be able to come online until
|
|
5:00 pm UTC, not 4:00 UTC.</p>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> no</p>
|
|
|
|
<p class='irc'><<cite>yoshiaki</cite>> no</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> yes</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> no</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> yes</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> yes</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> are people familiar with
|
|
w3c widgets and open social.</p>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> yes</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> we could do an intro
|
|
session on opensocial and w3c widgets...</p>
|
|
|
|
<p class='phone'><cite>Dan:</cite> maybe we should just do it
|
|
at 5:00 instead next week.</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> So should we have it at a
|
|
special time next week - 17:00 UTC to 18:00 UTC</p>
|
|
|
|
<p class='phone'>+1</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> Assuming 5:00 next
|
|
is fine.</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> +1</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> That should be a
|
|
one-off-move.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> APPROVED: Move
|
|
meeting to 17:00 UTC next week</p>
|
|
|
|
<p class='phone'>I am very much looking forward to this
|
|
call.</p>
|
|
|
|
<h3 id="item03">Action reminders.</h3>
|
|
|
|
<h3 id="item04">Action Reminders</h3>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> not yet</p><a name=
|
|
"action01" id="action01"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[DONE]</strong> mcarvalh to
|
|
look at Contact API and put those in Google Doc [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action01">http://www.w3.org/2010/03/03-swxg-minutes.html#action01</a>]</p>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> we will get
|
|
something by end March</p>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> wasn't it the
|
|
deadline we agreed?</p><a name="action02" id="action02"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[DONE]</strong> Anita to draft
|
|
XMPP and mobile notes and put them on wiki [recorded in
|
|
<a href="http://www.w3.org/2010/03/03-swxg-minutes.html#action02">
|
|
http://www.w3.org/2010/03/03-swxg-minutes.html#action02</a>]</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> Tim, use case stuff?
|
|
Danbri and Dan, coordination proposal, Anita on XMPP,
|
|
etc...</p>
|
|
|
|
<p class='phone'><cite>Dan:</cite> I will work on this.</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> I put the WBS
|
|
questionnaire on there - about the importance of various social
|
|
web standards - would appreciate answers.</p><a name="action03"
|
|
id="action03"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> <strong>[DONE]</strong> hhalpin to
|
|
make WBS survey on ranking future topics to be continued
|
|
afterwards [recorded in <a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action03">http://www.w3.org/2010/03/03-swxg-minutes.html#action03</a>]</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> <a href=
|
|
"http://www.w3.org/2002/09/wbs/43434/SocialWebLastHalfTopics/">http://www.w3.org/2002/09/wbs/43434/SocialWebLastHalfTopics/</a></p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> <a href=
|
|
"http://www.w3.org/2002/09/wbs/43434/SocialWebLastHalfTopics/">http://www.w3.org/2002/09/wbs/43434/SocialWebLastHalfTopics/</a></p>
|
|
|
|
<h3 id="item05">Tim's Pearls of Wisdom</h3>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> oh hey, it's 5pm+
|
|
already</p>
|
|
|
|
<p class='phone'><cite>Dan:</cite> "architecture of social web
|
|
based on linked data" was the headline proposal from Tim at
|
|
Santa Clara f2f.</p>
|
|
|
|
<p class='irc'><<cite>FabGandon</cite>> slide 37 <a href=
|
|
"http://www.slideshare.net/fabien_gandon/semantics-in-social-networks">
|
|
http://www.slideshare.net/fabien_gandon/semantics-in-social-networks</a></p>
|
|
|
|
<p class='phone'><cite>Dan:</cite> and there was a diagram
|
|
(posted by Fabien above).</p>
|
|
|
|
<p class='phone'><cite>Fabien:</cite> rely on linked open data
|
|
infrastructure. Transparent API for any rich client of app to
|
|
access the profile of the user independently of how and where
|
|
they are stored.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> #swxg on irc.w3.org
|
|
port 6665</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> since there is
|
|
nothing written down, we're happy to write it up for you!</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> <a href=
|
|
"http://www.w3.org/2010/Talks/0303-socialcloud-tbl">http://www.w3.org/2010/Talks/0303-socialcloud-tbl</a></p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> I've got a few slides and I
|
|
wrote a "design issues" document...</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> yes</p>
|
|
|
|
<p class='phone'>Yep.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> can hear you</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> <a href=
|
|
"http://www.w3.org/DesignIssues/CloudStorage.html">http://www.w3.org/DesignIssues/CloudStorage.html</a></p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> re <a href=
|
|
"http://www.w3.org/2010/Talks/0303-socialcloud-tbl/">http://www.w3.org/2010/Talks/0303-socialcloud-tbl/</a>
|
|
is there an url for the full no-javascript view?</p>
|
|
|
|
<p class='phone'>Got the slides up.</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> Starting with the
|
|
talks...</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> from a glance, it
|
|
looks like what i've been hoping oauth+atompub will give
|
|
us...</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> Social networks are doing
|
|
well but [disconnected...]<br />
|
|
... e.g. Twitter vs. Identi.ca<br />
|
|
... There are APIs but they are tweet-specific.</p>
|
|
|
|
<p class='phone'>[slide 4]</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> notes that even the
|
|
Tweets now have URIs so they can be forwarded...</p>
|
|
|
|
<p class='phone'>[slide 5]</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> i.e. tweets as
|
|
linked data</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> 'APIs are poor,
|
|
because the hide the nature of the underlying data'</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> APIs are poor because APIs
|
|
hide the nature of the underlying data. This isn't scalable to
|
|
new things. The Linked Data Way is to represent it as data.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> wonders about
|
|
access control and linked data</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> In a sane, clean design, the
|
|
data is linked data and the access control list is linked
|
|
data.</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> hi</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> ...so the data and the
|
|
access control are examples of the same stuff...</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> as in how access
|
|
control can *be* linked data, rather than a policy language
|
|
operating over access control.</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> And the access control for
|
|
the data is controlled by this other access control
|
|
resource...</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> what's the URL?</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> <a href=
|
|
"http://www.w3.org/2010/Talks/0303-socialcloud-tbl/#%285%29">http://www.w3.org/2010/Talks/0303-socialcloud-tbl/#%285%29</a></p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> So keep that architecture
|
|
diagram in one window and follow along.</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> thanks :-)</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> i have them</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> <a href=
|
|
"http://www.w3.org/DesignIssues/CloudStorage.html">http://www.w3.org/DesignIssues/CloudStorage.html</a></p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> So the design of this -
|
|
going on to [slide 6].</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> <a href=
|
|
"http://www.w3.org/DesignIssues/diagrams/social/acl-arch.png">http://www.w3.org/DesignIssues/diagrams/social/acl-arch.png</a></p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> I would like to build on the
|
|
cool things the community has developed. WebID- FOAF+SSL, RDF,
|
|
WebDAV, SPARQL Update, Widget libraries, Application
|
|
Builders.</p>
|
|
|
|
<p class='phone'>[Slide 7]</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> Access control: read, write
|
|
and control...</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> can we get links to
|
|
those apache modules?</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> implementation has been
|
|
written in an apache module[ of this kind of access control on
|
|
top of] WebDAV.</p>
|
|
|
|
<p class='irc'><<cite>FabGandon</cite>> <a href=
|
|
"http://twitpic.com/16eebm">http://twitpic.com/16eebm</a> #w3c
|
|
#tbl #tpac09</p>
|
|
|
|
<p class='irc'><<cite>oshani</cite>> Apache module for
|
|
authentication: <a href=
|
|
"http://dig.csail.mit.edu/2009/mod_authn_webid/">http://dig.csail.mit.edu/2009/mod_authn_webid/</a></p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> MS-Author-Via:
|
|
WevDAV</p>
|
|
|
|
<p class='irc'><<cite>oshani</cite>> Apache module for
|
|
authorization: <a href=
|
|
"http://dig.csail.mit.edu/2009/mod_authz_webid/">http://dig.csail.mit.edu/2009/mod_authz_webid/</a></p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> MS-Author-Via:
|
|
SPARQL</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> I think the access
|
|
control is here: <a href=
|
|
"http://esw.w3.org/topic/WebAccessControl">http://esw.w3.org/topic/WebAccessControl</a></p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> There is a header that MS
|
|
has used to tell their applications not to use front-page
|
|
extensions.</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>>
|
|
header('MS-Author-Via: SPARQL');</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> Idea is to use the HTTP link
|
|
header to point to the access control list.<br />
|
|
... Someone can read it and write it and tweak it using SPARQL
|
|
updates.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> need a SPARQL
|
|
update in C to make the implementation really work</p>
|
|
|
|
<p class='phone'>[Slide 8]</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> Web Groups - how do they
|
|
work? - URIs - if I look up a group name, I get back a document
|
|
which has the URIs of the people in the group.<br />
|
|
... ...or I get back URIs of sub-groups...<br />
|
|
... There's a question of how much RDF processing do you want
|
|
the system to do?</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> RDFsS inference</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> You log on with a WebID -
|
|
WebID tells you who user is pretending to be but can't be
|
|
trusted.<br />
|
|
... You can imagine doing very complicated rule-based systems,
|
|
but there is tremendous advantage on being really simple.<br />
|
|
... This will be an application-independent architecture.<br />
|
|
... So imagine you're designing Twitter. The first thing you
|
|
need to create is a public list of tweets. We need conventions
|
|
of generating URLs that won't clash with other
|
|
applications.<br />
|
|
... you need to have an "incoming drop box" so when someone
|
|
tweets about you, you can [be alerted].<br />
|
|
... in a centralized application all links are automatically
|
|
both ways. When I follow you on Twitter you know that because
|
|
it's the same application.<br />
|
|
... in a distributed way, you need to duplicate this with
|
|
messages.<br />
|
|
... Social networks [are] a partially public, partially
|
|
controlled view of [their activities.]<br />
|
|
... cross-application is valuable. [Allowing other applications
|
|
to access all this data]... creates an app market for this
|
|
data.<br />
|
|
... they should be portable but should not have to each make
|
|
their own data space. This architecture allows them to work in
|
|
a context where they are using data which is being produced and
|
|
managed by other applications.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> increasing
|
|
innovation in apps over open space is a good business case.</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> When we have this open
|
|
system and open linked data architecture, we will see a [jump]
|
|
in innovation in these apps.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> ?</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>>
|
|
_________________________________</p>
|
|
|
|
<p class='irc'><<cite>Zakim</cite>> danbri, you wanted to
|
|
ask about exact definition of webid:, does it assume user
|
|
control of the URI? and to mention foaf:membershipClass re Web
|
|
Groups - defined groups by membership</p>
|
|
|
|
<p class='phone'>[slide talk ends]</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> A WebID is a a URI
|
|
for a person which can be used for single sign-on</p>
|
|
|
|
<p class='phone'><cite>Danbri:</cite> WebID - I have a mixed
|
|
sense of what a WebID is. Is it a euphemism for a URI? Or is it
|
|
a specific technology?</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> using foaf+ssl</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> thought the same ID
|
|
could be both</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> A WebID is specifically a
|
|
FOAF+SSL ID. It's an alternative to an openID.</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> rather the OpenId
|
|
could be the foaf:homepage where the WebId is described</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> I can imagine there will be
|
|
WebID you get because you visit a web site and you have control
|
|
over it and you will have WebIDs for specific reasons - e.g. a
|
|
WebID for W3C or for your business.</p>
|
|
|
|
<p class='phone'><cite>Danbri:</cite> If I copy your FOAF file
|
|
and put it on my website. It still says true things about you -
|
|
is it a webid?</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> No - when you look up a
|
|
WebID it gives you a public key. And when you look up that
|
|
[FOAF] file it will give you the wrong public key.</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> The certificate and
|
|
the FOAF file are cross-linked</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> It's a WebId from
|
|
the users point of view because a ID selector will pop up asing
|
|
him which ID he wants to choose. This is what users will
|
|
remember</p>
|
|
|
|
<p class='phone'><cite>Danbri:</cite> Second question - one of
|
|
your slides you talk about groups. In FOAF we have [a
|
|
mechanism] for this.</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> Is a group a class?</p>
|
|
|
|
<p class='phone'><cite>Danbri:</cite> No it's related to a
|
|
class...</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> That's a design issue.</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> Keep it simple -->
|
|
the group is the class</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> The question of whether you
|
|
want a group to have a class or be a class...</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> :-)</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> A class is not
|
|
set</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> so I think it's
|
|
ok</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> apache code url?</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> I think the url is
|
|
on foaf+ssl wiki</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> did you want the
|
|
apache_mod URIs?</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> oshani++</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> <#ThisGroup> is
|
|
rdf:type of Joe, Fred, Albert.</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> oshani++</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> 2 quick questions. I think
|
|
the concept is good and I want to make it part of the final
|
|
report. But 2 critiques from some working on the open
|
|
stack.</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> You can have as
|
|
many certificates as you want</p>
|
|
|
|
<p class='irc'><<cite>pchampin</cite>> yes, but how do
|
|
you conveniently create one when you need it?</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> first problem with
|
|
certificates - they vary between machines, different devices,
|
|
if I go to an Internet cafe how can I use my certificate... So
|
|
this is in support of the username/password.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> (ben laurie)</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> you have a password
|
|
or one time password on the Identity Provider site</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> so a one-time
|
|
password would be the way to go here?</p>
|
|
|
|
<p class='phone'><cite>BBlfish:</cite> You have an identity
|
|
provider site - your openID home page - you have a password or
|
|
you have it able to send you a one-time password to your mobile
|
|
phone - and then you can create a new certificate which you can
|
|
set the TTL for -</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> so a one-time
|
|
OpenID-style login would create the certificate...could we just
|
|
have the certificate then automatically put through to other
|
|
apps with minimal user-intervention?</p>
|
|
|
|
<p class='phone'><cite>BBlfish:</cite> so if you're in an
|
|
Internet cafe you can set up a new certificate for only an
|
|
hour... You can have as many certs as you want and you can
|
|
disable certs just by removing the public key from your
|
|
profile.</p>
|
|
|
|
<p class='irc'><<cite>pchampin</cite>> a little hard to
|
|
explain to my mother, but technically sound, yes :)</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> If the thing is set up to
|
|
use public-key cryptography then it's easier to down-grade it
|
|
to openID like systems and you can cross-link OpenID and
|
|
WebIDs.<br />
|
|
... of course going into an Internet cafe and logging into your
|
|
common provider is [low security].</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> so Google says,
|
|
single-sign on us with us and trust us :)</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> SSO means you can do a lot
|
|
of damage with just one login.<br />
|
|
... When you're at the bank, typlically you can look at your
|
|
statement but then [an extra level of security is requried]
|
|
when you want to make a payement.<br />
|
|
... "These are two versions of Harry - the strong and the weak
|
|
one."</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> openid has some
|
|
specs in this direction - <a href=
|
|
"http://openid.net/specs/openid-assertion-quality-extension-1_0-03.html">
|
|
http://openid.net/specs/openid-assertion-quality-extension-1_0-03.html</a></p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> 2nd question - about APIs
|
|
and data formats -<br />
|
|
... we need to have a good answer.</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> yes, one could have
|
|
some interesting reasoning engines that work out the level of
|
|
security someone has, given how they have logged in, if their
|
|
webid is http, or https...</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> I agree it's better if you
|
|
want control of your data and have infinite descriptive power a
|
|
URI is as good as it gets. On the other hand, some developers
|
|
just want a string name - a first name<br />
|
|
... and "you're forcing me to do all this work."</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> RDFHTTPRequest and a
|
|
great RDF API</p>
|
|
|
|
<p class='phone'><cite>Harry:</cite> If you start mixing up the
|
|
cloud with linked data then it starts getting out of hand for
|
|
developers. The linked data community needs to answer these
|
|
questions...</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> no definitely
|
|
doesn't devalue it</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> there is a cloud - web
|
|
services - that people are using - but it doesn't devalue the
|
|
linked data cloud.</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> <a href=
|
|
"http://www.oreillynet.com/pub/wlg/3005">http://www.oreillynet.com/pub/wlg/3005</a>
|
|
'Amazon has both SOAP and REST interfaces to their web
|
|
services, and 85% of their usage is of the REST interface.'</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> we just need to
|
|
make it as easy-to-use Linked Data as possible</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> (let's not get
|
|
bogged down on soap vs rest)</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> (ah, good pointer
|
|
danbri!)</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> (maybe back to API
|
|
vs. Linked Data format issue)</p>
|
|
|
|
<p class='phone'><cite>Tim:</cite> You should just be able to
|
|
ask a question by a very simple query in javascript ...</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> user = weblogin();
|
|
name=user.foaf:name</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> ldQuery</p>
|
|
|
|
<p class='phone'>Sorry but I actually have to leave the call
|
|
right now... :(</p>
|
|
|
|
<p class='phone'>Hope someone else can take over
|
|
scribing...</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> any more
|
|
questions?</p>
|
|
|
|
<p class='phone'>Thanks Tim!</p>
|
|
|
|
<p class='phone'>Very highly enriched information.</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> Ok, thanks for coming
|
|
... sprry the note isn't finished yet</p>
|
|
|
|
<p class='phone'>Also wonder how this interoperates with
|
|
OneSocialWeb XMPP-based architecture...</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> thanks</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> thanks!</p>
|
|
|
|
<p class='irc'><<cite>petef</cite>> thanks timbl</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> thanks!</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> thanks!</p>
|
|
|
|
<p class='phone'>But this is too big a quetion for today.</p>
|
|
|
|
<p class='irc'><<cite>cperey</cite>> bye for now!</p>
|
|
|
|
<p class='irc'><<cite>AnitaD</cite>> thanks</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> we normally ask aout
|
|
role of w3c</p>
|
|
|
|
<p class='irc'><<cite>yoshiaki</cite>> thanks!!</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> Yes, that would
|
|
have been a good question...</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> oh, good point!</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> TimBL, if you can
|
|
answer this one :)</p>
|
|
|
|
<p class='irc'><<cite>yoshiaki</cite>> TimBL: W3C is
|
|
engaging community in general.</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> we've invited them
|
|
to calls and TPAC :)</p>
|
|
|
|
<p class='irc'><<cite>yoshiaki</cite>> ... and invite
|
|
them to TPAC.</p>
|
|
|
|
<p class='irc'><<cite>danbri</cite>> <a href=
|
|
"http://www.w3.org/News/2009#entry-8674">http://www.w3.org/News/2009#entry-8674</a>
|
|
fits in?</p>
|
|
|
|
<p class='irc'><<cite>timbl</cite>> It isn't ready yet,
|
|
don't review it until we have it more finishde</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> but the problem is
|
|
that with most of these Social APIs, and even W3C DAP API, we
|
|
have these descriptive features mied in</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> good point</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> makes sense</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> big deal</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> take care
|
|
timbl!</p><a name="action04" id="action04"></a>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>>
|
|
<strong>ACTION:</strong> hhalpin to send Team a simple e-mail
|
|
overview for Social Web API [recorded in <a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action04">http://www.w3.org/2010/03/03-swxg-minutes.html#action04</a>]</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-132
|
|
- Send Team a simple e-mail overview for Social Web XG [on
|
|
Harry Halpin - due 2010-03-10].</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> great</p>
|
|
|
|
<p class='irc'><<cite>bblfish</cite>> bye</p>
|
|
|
|
<p class='irc'><<cite>petef</cite>> bye all</p>
|
|
|
|
<p class='irc'><<cite>melvster</cite>> thanks</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> bye all!</p>
|
|
|
|
<p class='irc'><<cite>yoshiaki</cite>> bye</p>
|
|
|
|
<p class='irc'><<cite>hhalpin</cite>> trackbot, end
|
|
meeting</p>
|
|
</div>
|
|
|
|
<h2><a name="ActionSummary" id="ActionSummary">Summary of Action
|
|
Items</a></h2><!-- Action Items -->
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> hhalpin to send
|
|
Team a simple e-mail overview for Social Web API [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action04">http://www.w3.org/2010/03/03-swxg-minutes.html#action04</a>]<br />
|
|
|
|
<br />
|
|
<strong>[DONE]</strong> <strong>ACTION:</strong> Anita to draft
|
|
XMPP and mobile notes and put them on wiki [recorded in <a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action02">http://www.w3.org/2010/03/03-swxg-minutes.html#action02</a>]<br />
|
|
|
|
<strong>[DONE]</strong> <strong>ACTION:</strong> hhalpin to make
|
|
WBS survey on ranking future topics to be continued afterwards
|
|
[recorded in <a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action03">http://www.w3.org/2010/03/03-swxg-minutes.html#action03</a>]<br />
|
|
|
|
<strong>[DONE]</strong> <strong>ACTION:</strong> mcarvalh to look
|
|
at Contact API and put those in Google Doc [recorded in <a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html#action01">http://www.w3.org/2010/03/03-swxg-minutes.html#action01</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: 2010/03/03 17:16:32 $
|
|
</address>
|
|
|
|
<div class="diagnostics">
|
|
<hr />
|
|
|
|
<h2>Scribe.perl diagnostic output</h2>[Delete this section
|
|
before finalizing the minutes.]<br />
|
|
<pre>
|
|
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20
|
|
Check for newer version at <a href=
|
|
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/">http://dev.w3.org/cvsweb/~checkout~/2002/scribe/</a>
|
|
|
|
Guessing input format: RRSAgent_Text_Format (score 1.00)
|
|
|
|
Succeeded: s/RDF/RDFs/
|
|
Succeeded: s/API/XG/
|
|
Found Scribe: Dan
|
|
Found Scribe: DKA
|
|
Inferring ScribeNick: DKA
|
|
Found ScribeNick: DKA
|
|
Found ScribeNick: DKA
|
|
Scribes: Dan, DKA
|
|
Default Present: +41.79.200.aaaa, MacTed, +049173900aabb, +049173537aacc, AnitaD, tpa, oshani, melvster, hhalpin, DKA, yoshiaki, Carine, +49.173.537.aadd
|
|
Present: +41.79.200.aaaa MacTed +049173900aabb +049173537aacc AnitaD tpa oshani melvster hhalpin DKA yoshiaki Carine +49.173.537.aadd
|
|
Found Date: 03 Mar 2010
|
|
Guessing minutes URL: <a href=
|
|
"http://www.w3.org/2010/03/03-swxg-minutes.html">http://www.w3.org/2010/03/03-swxg-minutes.html</a>
|
|
People with action items: hhalpin
|
|
|
|
</pre>[End of <a href=
|
|
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">
|
|
scribe.perl</a> diagnostic output]
|
|
</div>
|
|
</body>
|
|
</html>
|