W3C home > Mailing lists > Public > www-ws-arch@w3.org > June 2002

Re: Peer to Peer Goal

From: Hugo Haas <hugo@w3.org>
Date: Fri, 28 Jun 2002 13:54:02 -0400
To: www-ws-arch@w3.org
Message-ID: <20020628175402.GE17582@jibboom.w3.org>

Hi Franck.

It seems to me that what this CSF calls for is support for a wide
range of MEPs.

Here are a few more specific comments. 

* Francis McCabe <fgm@fla.fujitsu.com> [2002-06-25 17:00-0700]
> D-AC023
>   Web services and clients must support modes of interaction where both 
> have a permanent presence

This is not clear to me what that means.

> D-AR023.1
>   Clients and servers must support asynchronous messaging, such as event 
> notification. I.e., a supplier must be able to notify a customer of an 
> event.
> D-AC024
>   Web services such be able to support N party interactions, such as 
> auctions, escrow services, proxy services, broker services.

Requesting that all services support asynchronous messaging seems
unreasonable. Having the architecture enable such modes of
communications is important though.

> D-AC024.1
>   It must be possible to quote, verbatim and modified, messages within 
> top-level messages, to an arbitrary depth.

Hmmm... while I don't question that this is useful, I am not sure that
we need to have this in the requirements document.

Moreover, message here is very vague. What about a simple HTTP GET

> D-AC024.2
>   It must be possible to `anonymize' (sic) messages to elide the 
> intended recipient

This looks to me like a privacy requirement.

> D-AC024.3
>   It must be possible to express multiple receivers and to express 
> `wait' points in service orchestration

This seems to be more related to your service composition proposal.



Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092
Received on Friday, 28 June 2002 13:54:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:34 UTC