W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > June 2010

Re: WSRA Spec abstracts

From: David Snelling <David.Snelling@UK.Fujitsu.com>
Date: Mon, 28 Jun 2010 14:27:33 +0100
CC: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <023DAB20-9D06-480C-AA23-ED3AC12AE433@UK.Fujitsu.com>
To: Doug Davis <dug@us.ibm.com>

On 28 Jun 2010, at 13:16, Doug Davis wrote:

> Per my AI [1], here's a first pass at some abstracts for our specs.   
> I really didn't do anything except copy the abstract from each spec  
> - it seemed sufficient.
> WS-Transfer:
> This specification describes a general SOAP-based protocol for  
> accessing XML representations of Web service-based resources.

Looks fine.

> WS-Eventing:
> This specification describes a protocol that allows Web services to  
> subscribe to or accept subscriptions for notification messages


> WS-EventDescriptions:
> This specification describes a mechanism by which an endpoint can  
> advertise the structure and contents of the events it might generate.


> WS-MetadataExchange:
> This specification defines how metadata associated with a Web  
> service endpoint can be represented as resources, how metadata can  
> be embedded in endpoint references, how metadata could be retrieved  
> from a metadata resource, and how metadata associated with implicit  
> features can be advertised.

This one needs simplifying. It is possible that the spec is actually  
too complicated. I would say something more general and leave the  
details for the spec itself. How about:

This specification defines mechanisms for accessing metadata  
associated with a Web service-based resource.

> WS-SOAPAssertions:
> This specification defines two WS-Policy assertions that can be used  
> to advertise the requirement to use a certain version of SOAP in  
> message exchanges.


> WS-Enumeration:
> This specification describes a general SOAP-based protocol for  
> enumerating a sequence of XML elements that is suitable for  
> traversing logs, message queues, or other linear information models.

I think the application specifics are not necessary. I would simplify  
it to:

This specification describes a general SOP-based protocol for  
enumerating a sequence of XML elements from a SOAP enabled information  

> [1] http://www.w3.org/2002/ws/ra/tracker/actions/166
> thanks
> -Doug
> ______________________________________________________
> STSM |  Standards Architect  |  IBM Software Group
> (919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
> The more I'm around some people, the more I like my dog.
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________

Take care:

     Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
     Fujitsu Laboratories of Europe Limited
     Hayes Park Central
     Hayes End Road
     Hayes, Middlesex  UB4 8FE
     Reg. No. 4153469

     +44-7590-293439 (Mobile)

 Fujitsu Laboratories of Europe Limited
 Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
 Registered No. 4153469
 This e-mail and any attachments are for the sole use of addressee(s) and
 may contain information which is privileged and confidential. Unauthorised
 use or copying for disclosure is strictly prohibited. The fact that this
 e-mail has been scanned by Trendmicro Interscan does not guarantee that 
 it has not been intercepted or amended nor that it is virus-free.
Received on Monday, 28 June 2010 13:28:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:56 UTC