W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > February 2009

Re: "Final review" of FPWG candidates

From: Doug Davis <dug@us.ibm.com>
Date: Mon, 23 Feb 2009 12:57:14 -0500
To: Bob Freund <bob@freunds.com>
Cc: public-ws-resource-access@w3.org, public-ws-resource-access-request@w3.org
Message-ID: <OFEB1F621B.5D46B80F-ON85257566.00628BA4-85257566.00629FD3@us.ibm.com>
I believe Katy left for the day so before someone else tries to make fix 
it.... she updated the bad mailto link in #1.

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com



Bob Freund <bob@freunds.com> 
Sent by: public-ws-resource-access-request@w3.org
02/23/2009 08:50 AM

To
public-ws-resource-access@w3.org
cc

Subject
"Final review" of FPWG candidates






I did a fairly mechanical review of the FPWG candidates and came up 
with the following.
I understand that many of these will be corrected at the time of 
publication, however, I thought that sending the list might be useful.
thanks
-bob

FPWG "final" review
I think that the following comments are common to all of the five specs:
1) public-ws-resource-access-comments@w3.org mailto link contains 
incorrect uri, (contains public-resource-access-request@w3.org)
2) http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/ 

  (archive) does not exist
3) Section  Acknowledgements Section is empty.  Fill it with list of 
members or ex-members who have attended at least one meeting:

In WS-Transfer
4) http://www.w3.org/2009/02/ws-tra cannot be de-referenced
5) http://www.w3.org/2009/02/ws-tra/transfer.wsdl cannot be de- 
referenced
6) http://www.w3.org/2009/02/ws-tra/fault cannot be de-referenced

In WS-Resource-Transfer
7) http://www.w3.org/2009/02/ws-rst cannot be de-referenced
8) http://www.w3.org/2009/02/ws-rst/Dialect/QName cannot be de- 
referenced
9) http://www.w3.org/2009/02/ws-rst/Dialect/XPath-Level-1 cannot be de- 
referenced

In WS-MEX
10) http://www.w3.org/2009/02/ws-mex cannot be de-referenced
11) http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd cannot be de- 
referenced
12) http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl cannot be 
de-referenced

In WS-Eventing
13) http://www.w3.org/2009/02/ws-evt cannot be de-referenced
14) http://www.w3.org/2009/02/ws-evt/DeliveryFailure cannot be de- 
referenced
15) http://www.w3.org/2009/02/ws-evt/SourceShuttingDown cannot be de- 
reference
16) http://www.w3.org/2009/02/ws-evt/SourceCancelling cannot be de- 
referenced
17) http://www.w3.org/2009/02/ws-evt/eventing.wsdl cannot be de- 
referenced

In WS-Enumeration
18) http://www.w3.org/2009/02/ws-enu cannot be de-referenced
19) http://www.w3.org/2009/02/ws-enu/SourceShuttingDown cannot be de- 
referenced
20) http://www.w3.org/2009/02/ws-enu/SourceCancelling cannot be de- 
referenced
21) http://www.w3.org/2009/02/ws-enu/enumeration.wsdl cannot be de- 
referenced


And in addition,
Several of the specs note that the schema is retrievable at the 
namespace location, which it is not.
Received on Monday, 23 February 2009 17:57:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:17:45 GMT