W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2004

Crossreferencing the spec list with Apache's

From: Michael Champion <mc@xegesis.org>
Date: Sun, 1 Feb 2004 10:25:31 -0500
Message-Id: <DF75A46D-54CA-11D8-BE7A-000A95CCC59E@xegesis.org>
To: 'www-ws-arch@w3.org ' <www-ws-arch@w3.org>

I did a quick crosscheck between the list of specs now at  
http://lists.w3.org/Archives/Public/www-ws-arch/2003Dec/0058.html and 
that at 

Anyway, the ones I find the the Apache list that aren't in ours include:

[WS-ActiveProfile]: The WS-Federation specification defines an 
integrated model for federating identity, authentication and 
authorization across different trust realms. This specification defines 
how the federation model is applied to active requestors such as SOAP 

[WS-Inspection]: is an XML format for assisting in the inspection of a 
site for available services.

[WS-PassiveProfile] describes how the cross trust realm identity, 
authentication and authorization federation mechanisms defined in 
WS-Federation can be utilized used by passive requestors such as Web 
browsers to provide Identity Services. Passive requesters of this 
profile are limited to the HTTP protocol.

[WS-EndpointResolution]: A set of Web service mechanisms that support 
selecting a specific endpoint for an operation or message from a set of 
allowed candidates. This is particularly useful in server farms and 
mobile environments.

[WS-Manageability]: introduces the general concepts of a manageability 
model in terms of manageability topics and the aspects used to define 

[WS-Privacy] : will describe a model for how Web services and 
requesters state privacy preferences and organizational privacy 
practice statements.

[WS-Referral]: is a SOAP-based, stateless protocol for inserting, 
deleting, and querying routing entries in a SOAP router.

OK, enough of this!  The bottom line is that even people who spend more 
or less full time trying to track this stuff can't keep up (ahem, which 
was the reason the W3C chartered WSA in the first place).   Maybe the 
best way forward is to link to the Apache list along with ours (in the 
Appendix?). Since that is a Wiki and presumably editable (and there is 
an owner one can ping for updates), perhaps someone might synch the 
Roger/Paul list to Apache's.  Whether someone here does it, someone 
seeing the Appendix with both our lists and the link to Apache's does 
it, or whatever,  is not important.

Thoughts on this, especially from Roger and Paul, would be appreciated. 
  I wouldn't object if someone updated our list and we asked David to 
link to the update, but I'm not sure if this would serve any useful 
purpose.  I do think we should revise Appendix A to add a link to 
along with our list, because ours will quickly be obsolete and that 
will presumably be maintained.
Received on Sunday, 1 February 2004 10:25:59 UTC

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