kidehen at openlinksw.com
Fri Nov 18 13:28:33 CET 2011
On 11/18/11 4:14 AM, Henry Story wrote:
> Section 2.1 Terminology http://webid.info/spec#terminology
> As we discussed during this week's teleconference, the terminology in the spec seems a bit heavy. We have
> - Verification Agent
> Performs authentication on provided WebID credentials and determines if an Identification Agent can have access to a particular resource. A Verification Agent is typically a Web server, but may also be a peer on a peer-to-peer network.
> - Identification Agent
> Provides identification credentials to a Verification Agent. The Identification Agent is typically also a User Agent.
> - Identification Certificate
> An X.509 [X509V3] Certificate that must contain a Subject Alternative Name extension with at least one URI entry identifying the Identification Agent. This URI should be dereference-able and result in a document containing RDF data. For example, a certificate identifying the WebID URI http://example.org/webid#public would contain the following:
> X509v3 extensions:
> X509v3 Subject Alternative Name:
> When these are used in the sequence diagram it makes for very heavy language. In a TLS authentication process, both sides are "Identification Agents" in any case (which may be ok for future uses, but it makes the explanation a bit difficult) Also it would be better english to say "Identifying Agents". And somehow the notion of an "Identification Certificate" seems like a pleonasm.
> TLS uses the words Client and Server, "Client Certificate" and "Server Certificate" . We could use those too.
Yes! Please use Client-Server terminology since its familiar to a vast
audience technology users and developers that extend way beyond the Web.
> Social Web Architect
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1625 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20111118/ba7ad545/attachment.bin
More information about the foaf-protocols