W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

improvement to step 5 of sequence diagram

From: Henry Story <henry.story@bblfish.net>
Date: Tue, 10 Jan 2012 13:53:39 +0100
Message-Id: <7EAC79C4-7F8B-4D5C-8D6C-D5CE91CB53DF@bblfish.net>
To: "public-xg-webid@w3.org XG" <public-xg-webid@w3.org>
The introduction was a bit odd in part 5, it started with how to verify a WebId then went on to how to extract it from the cert, so the order was wrong.

Diff here:

https://dvcs.w3.org/hg/WebID/rev/6da4ac1999d6

It reads like this now:




The Verification Agent must extract the Public Key and all the URI entries contained in the Subject Alternative Name extension of the WebID Certificate. A WebID Certificate may contain multiple URI entries which are considered Claimed WebIDs at this point, since they have not been verified. The Verification Agent may verify as many or as few WebIDs it has time for. It may do it in parallel and asynchronously. However that is done, a Claimed WebID can only be considered verified if the following steps have been accomplished successfully:
If the WebID Verifier does not have an up to date version of the WebID profile in the cache, then it must dereference the WebID using the canonical method for dereferencing a URL of that scheme. For an https://... WebID this would be done using the [HTTP-TLS] protocol.
The returned representation is then transformed into an RDF graph as specified in Processing the WebID Profile
That graph is then queried as explained in Querying the Graph. If the query is answered positively, then that WebID is verified.
Henry

Social Web Architect
http://bblfish.net/
Received on Tuesday, 10 January 2012 12:54:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 January 2012 12:54:10 GMT