RE: Collected Requirements

Since an application could be an independent business entity in web service
model, the service description would need to communicate not only the
services available and how to invoke these services, but also information
such as charging model, SLA, permissioning, etc.

One use scenario may be that a web service portal aggregates several related
web services each with different charging model, some subscription and
others usage based.  - Jian

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
Behalf Of Jonathan Marsh
Sent: Thursday, February 14, 2002 11:59 AM
To: Jian Zhang; www-ws-desc@w3.org
Subject: RE: Collected Requirements


Can you clarify the usage scenario you are envisioning?  And how it
might affect our requirements?  Especially, where are the boundaries
between the vertical use of WSDL in describing billing procedures, and
the infrastructure within WSDL that might be needed to support this?

> -----Original Message-----
> From: Jian Zhang [mailto:jian@xcerla.com]
> Sent: Thursday, February 14, 2002 10:38 AM
> To: Jonathan Marsh; www-ws-desc@w3.org
> Subject: RE: Collected Requirements
>
>
> I am not sure if accounting related requirements are appropriate to
post
> in
> this list, but I can envision today's enterprise/service provider
centric
> resource accounting and billing would have to be revamped to support
cross
> domain business model.  - Jian
>
>
>
> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
> Behalf Of Jonathan Marsh
> Sent: Wednesday, February 13, 2002 9:10 AM
> To: www-ws-desc@w3.org
> Subject: Collected Requirements
>
>
> Enclosed is a document that collects the requirements posted to this
> list, for the purposes of assigning numbers to each requirement.

Received on Friday, 15 February 2002 10:49:34 UTC