- From: Henry Story <henry.story@bblfish.net>
- Date: Tue, 1 Feb 2011 11:30:59 +0100
- To: WebID Incubator Group WG <public-xg-webid@w3.org>
On 1 Feb 2011, at 11:18, WebID Incubator Group Issue Tracker wrote: > Raised by: Nathan Rixham > On product: WebID Spec > > The WebID Protocol currently defines and constrains the usage of WebID to the HTTP transfer protocol, however TLS is a /transport/ protocol which can be used with multiple /transfer/ and /application/ protocols. > > Other commonly protocols which may be useful and which are TLS compatible include FTP, SMTP, NNTP and XMPP. > > It is suggested that WebID protocol removes the HTTP+TLS constraint such that WebID can be used in multiple different scenarios, and so as not to constrain usage needlessly. That makes sense. We don't want to limit it to HTTP+TLS. Just as we allow multiple representations, one can allow different transfer protocols. For example it would be very useful for ssh access. At the same time, HTTP is going to be the most useful and widely deployed one (IMHO), and we can't try to deal with all protocols that come up, due to lack of time. So if we can make the protocol modular and extensible that will help. Henry Social Web Architect http://bblfish.net/
Received on Tuesday, 1 February 2011 10:31:36 UTC