Re: Requesting Agent too General

So..what exactly is your question? Do we need to define what a Requesting
Agent is? Or, if we should mention HTTP(S) in the definition?

Andrei


On Mon, Dec 10, 2012 at 8:34 AM, Henry Story <henry.story@bblfish.net>wrote:

> In the WebID spec it says
>
> http://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html
> [[
> The Requesting Agent initiates a request to a Service listening on a
> specific port using a given protocol on a given Server.
> ]]
>
> That is too general. I suppose it means the protocol is the HTTP or https
> protocol protocol.
> But do we really need to define this concept?
>
> In the WebID Authentication spec ( http://webid.info/spec )
> this type of agnosticism on the protocol is appropriate, because we are
> dealing
> with client authentication using the TLS stack, and there it does not
> matter
> what type of underlying protocol the client uses when connecting to a
> server. The
> WebID verification in any case is then done by the Relying Party.
>
> Henry
>
> Social Web Architect
> http://bblfish.net/
>
>