Re: Requesting Agent too General

Ok, I'll try to rephrase it a bit.

Andrei


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

>
> On 10 Dec 2012, at 15:36, Andrei Sambra <andrei.sambra@gmail.com> wrote:
>
> 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?
>
>
> both I think.
>
> The spec is building up the concept of an Requesting Agent that is very
> general in that it can make requests to anything. ( What is not a
> requesting agent under that definition? ) What it seems to me is that the
> spec only needs to speak of making a request. There is no need to create a
> category of agents that make requests.
>
>
>
> 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/
>>
>>
>
>   Social Web Architect
> http://bblfish.net/
>
>