Re: Things we're not doing

Let me comment on three items:

1. Privacy. 
To the man on the street privacy and security may be the two biggest 
problems with the Web.
OASIS is starting a TC on a privacy model.  Charter is at 
http://www.oasis-open.org/committees/process-2009-07-30.php#formation
This is a strong model where everytime a website wants some personal 
information it has
to indicate why it wants the information and request permission.  Some 
feel this is too onerous and
recommend an alternate model where you indicate your privacy preferences 
(what data, who can see it, how long)
and the privacy preferences are carried along with the data.  If they 
are violated, there are legal recourses.

2. Identity
Anyone can get an OpenId ... I have 3!  But there is no way to verify 
if, indeed, what/who I claim to be is
accurate.  This kind of Id is useful for single-sign on but it is not 
verified identity.  The Social Security Office
will not accept it.  So, should we try and start an agency that that 
provides verified identity?  This should be
voluntary, so there is a means to verify your identity if you choose to 
provide it.  The agency should keep
track of who requests your identity.  The eGoverment folks may be 
interested.  My take the fun out of online dating :-)

3. Cloud Computing
Cloud computing uses URIs to identify Cloud artifacts and uses REST 
protocols but other than that there is
little connection with the Web.  The concerns in Cloud computing have to 
do with managing artifacts in the
cloud and managing applications in the Cloud.  Not clear what W3C can 
contribute to this.

All the best, Ashok


Philippe Le Hegaret wrote:
> There are plenty of things that we're doing and some individuals believe
> we should tackle or might become interesting. I'd like us to think about
> which of those (feel to extend this raw list) things we believe we need
> to go after.
>
> Privacy
>   W3C Workshop on Privacy for Advanced Web APIs 
>     http://www.w3.org/2010/api-privacy-ws/
>     papers at http://www.w3.org/2010/api-privacy-ws/papers.html
>
> Access Control and Policy
>
> Data and Query server discovery
>   With RDF data and SparQL servers out there, how do an application know
> where to find them and what to find in them?
>
> Federated query servers
>   Combining SparQL queries across servers.
>
> Web Identity
>   Open ID, Facebook Connect, Infocard, OAuth, XAuth, Web ID (foaf+ssl),
> Web finger, european ID system, Higgins, Kantara
>
> Trust
>
> Read-Write Web
>
> HTTP and P2P
>
> Cross browser bookmarking
>  With users having several devices, they're managing their bookmarks in
> the cloud. This seems a special case of Web Identity and Cloud
> Computing.
>
> Browser extensions
>   Mozilla and Chrome have browser extensions. Should we try to unify
> them?
>
> Cloud computing
>  Besides making the Web a platform for data, document, and application,
> are there other uses in cloud computing we should look into? Cloud
> management seems to be handle using the SOAP stack, which seems to get
> outside our Core area imho. Data exchange between clouds seems vertical.
>
> Social Networking
>  Besides making the Web a platform for data, document, and application,
> are there other uses in cloud computing we should look into?
>
> Adaptative HTTP Streaming
>  Apple is moving in this area at the IETF. Not clear if they're looking
> to standardize anything.
>   http://tools.ietf.org/html/draft-pantos-http-live-streaming-04
>
>
> Philippe
>
>
>
>

Received on Friday, 23 July 2010 15:19:08 UTC