W3C home > Mailing lists > Public > public-webid@w3.org > February 2013

Re: Formal WebID Teleconf Friday February 1 2013 15:00UTC

From: Henry Story <henry.story@bblfish.net>
Date: Fri, 1 Feb 2013 11:33:06 +0100
Cc: "public-webid@w3.org Group" <public-webid@w3.org>
Message-Id: <5D1D2E7E-BA8E-4506-ACD3-680CE0E5755B@bblfish.net>
To: Henry Story <henry.story@bblfish.net>

On 31 Jan 2013, at 10:30, Henry Story <henry.story@bblfish.net> wrote:

> Meeting Time:
> Friday 1 February, 15:00 UTC, 16:00 Paris, 10:00 New York
> full time zone information:  http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130201T15&ah=1
> tel: +1-617-761-6200
> sip: zakim@voip.w3.org
> irc: irc://irc.w3.org:6665/%23webid
> Agenda:
> Meeting Minutes from last time
> ------------------------------
> http://www.w3.org/2013/01/25-webid-minutes.html
> Actions
> -------
> Let's close some actions: 
> I propose doing this in Bulk. Closing
> - "Cross reference SocialWeb XG stories with WebID XG. There will be a handful of intersections that make sense to further develop"
>  http://www.w3.org/2005/Incubator/webid/track/actions/17 
>  close:  way overdue 
> - "Write a small wiki page on ldap protocol answering the questions: what is the schema for publc key in ldap, what dereferencing methods are there + section of links to implementations and small explanation."  
>  http://www.w3.org/2005/Incubator/webid/track/actions/33 
>  close: ldp is no longer in scope for the group 
> - "J├╝rgen Jakobitsch to put up thesaurus wiki available to team"
> http://www.w3.org/2005/Incubator/webid/track/actions/48
> close: I think it may have been done, but I am not sure we need it, though it is a nice demo
> - "Fix respec.js errors in the spec"
>  http://www.w3.org/2005/Incubator/webid/track/actions/50
>  Done.
> - "Explain on the wiki how to configure WebID on Apache Tomcat"
>   http://www.w3.org/2005/Incubator/webid/track/actions/51


We can also close or move issues. Most of the issue below are either 
of the following:
  - things that have been done -> we can close
  - things that are out of scope. We can do a number of things with them
     * we can close 
     * move to a different section, such as
         - a future spec section
         - identity interoperability section

- Issue 5: Follow work in publishing keys in DNSSEC-DANE
  These are now specs. 
  Perhaps these need to be added to the Auth-TLS spec?

- Issue 17: Add UML Sequence diagram to spec
  That was done long ago.

- ISSUE 18: Transfer Protocol Independence
  I think the spec actually does this as far as connecting to a TLS server goes.
  So I think this can be closed as accomplished.
  ( please check the latest HG version of https://webid.info/spec/ )

- ISSUE 10: x509v3 Independence and TLS Extensions

  This is too much work for our group as is, and not useful enough. So I suggest 
  making it out of scope, even though it is really interesting theoretically. 
  To be looked at if we get sponsors that put money into this.

 - ISSUE-26: take account of client_certificate_url extension in spec

   Too complicated for our current group, and I don't see a huge need for it.
   Out of scope until we get sponsors that put serious money into this.

 - ISSUE-37: Should WebFinger be mentioned in the spec?

   No we limit ourselves to http URIs for WebID. This could be moved to
   the Identity-Interopertability section. So we need a new 
   Identity-Interoperability product ( though this is not one we as this
   group will be likely to be able to finish )

 - ISSUE 43: Replace email verification with WebId
   An identity-interoperability issue it seems to me, so we should move it there.

 - ISSUE 57: Salmon and WebID
   Move to Identity Interoperability spec 

 - ISSUE-61: xsd datatypes
   I think we settled the xsd data types question. To close.

> WebID Definition
> ----------------
> Current results of vote. Discussion of where to go from there 
> Security & Privacy Section
> --------------------------
> Trust?
> - To add: some form of explanation that the information in a WebID profile is
> only as trustworthy as the trust one puts in that URL. 
> btw. this means that tools like MyProfile need to think about how to guard
> against someone putting up a fake profile of me. Anyone could do that at
> present. So the importance of understanding the way someone is related in the
> social network becomes paramount. 
> Use Case and Requirements Document
> ----------------------------------
> we have the following two pages up:
> - http://www.w3.org/2005/Incubator/webid/wiki/User_Stories_and_Use_Cases
> - http://www.w3.org/2005/Incubator/webid/wiki/Use_Cases_and_Requirements  
> We are still looking at how to proceed here.
> Please mention ISSUE-41 in your mail, so we can find it quickly from the
> issue-tracker.
> https://www.w3.org/2005/Incubator/webid/track/issues/41
> I have opened ISSUE-41.
> Web Access Control
> ------------------
> Report from Andrei on the situation.
> Henry
> Social Web Architect
> http://bblfish.net/
> Social Web Architect
> http://bblfish.net/

Social Web Architect

Received on Friday, 1 February 2013 10:33:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:49 UTC