W3C home > Mailing lists > Public > public-xg-webid@w3.org > November 2011

closed 9 issues

From: Henry Story <henry.story@bblfish.net>
Date: Fri, 25 Nov 2011 14:44:50 +0100
Message-Id: <7294A507-C4DD-4843-9B38-8549D276BBDC@bblfish.net>
To: "public-xg-webid@w3.org XG" <public-xg-webid@w3.org>
There are a couple of small todos buried in there. Please verify you are ok with this.


- ISSUE 61 "xsd datatypes" We now have those xsd datatypes
     http://www.w3.org/2005/Incubator/webid/track/issues/61
     There is a follow up issue there for the taking: interact with the SPARQL folks to see if they can add language to bring out that
    xsd:hexBinary and  xsd:base64Binary equivalent datatypes
 
- ISSUE 62: "null certificate_authorities list"
       http://www.w3.org/2005/Incubator/webid/track/issues/62
       text explaining this has been added to the spec in "3.2.3 Requesting the Client Certificate"

- ISSUE 1: Multiple URI entries in the SAN extension
       http://www.w3.org/2005/Incubator/webid/track/issues/1
       Step 5 in the sequence diagram specifies how this works. The language may not be perfect, but that would be another issue.

- ISSUE 14: WebID and Browsers
       http://www.w3.org/2005/Incubator/webid/track/issues/14
       We should add the paper http://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_22/webid.html
       to our wiki with a space where we can add additional things that come up.

- ISSUE 59: Filtering & Versioning WebID Certificates
      this was a duplicate of issue 15, closed (I could never find the name of that other issue)

- ISSUE 33: Add a reference to the X.509 spec in the references sections
     Done

- ISSUE 39: Simplify how public keys are expressed
     I think we have the simplest we can have, allowing for flexibility, simplicity of querying, reduction of namespaces, whilst not taking sides between X509 ASN.1, GPG, or XML-DSIG with which we are compatible.

- ISSUE 31: WebID over SSH?
     the latest spec allows that as the initial connection is only described in terms of TLS, with https as the main example. 
     If people want to add an extra sentence there to make clear that ssh would also work, feel free to propose it.

- ISSUE-65: Add an Attack Scenarios section to the spec
     that is a duplicate of ISSUE-34, Create a security considerations section even if it is more precise

Henry

Social Web Architect
http://bblfish.net/
Received on Friday, 25 November 2011 13:45:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 November 2011 13:45:31 GMT