RE: [wsdm] Draft of response

["Martin Chapman" <martin.chapman@oracle.com>]

Title: Message

I would suggest the following:

 

Change:

 

"The WSDM TC is expecting standard versions of these dependent specifications; therefore the TC will update WSDM specifications to refer to the standard and, if necessary, make changes to WSDM specification to come into compliance."

 

to:

 

"The WSDM TC is expecting standard versions of these dependent specifications; therefore the TC will update WSDM specifications to refer to the standard and, if necessary, make changes to WSDM specification to come into compliance. Any updated versions of  the WSDM specifications will be put though the normal OASIS standardisation process."

 

 

-----Original Message-----
From: Heather Kreger [mailto:kreger@us.ibm.com]
Sent: 04 March 2005 02:45
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Draft of response

Hi Folks, Here is a slightly wordsmithed version of the note we discussed on our call today.  Please respond with suggestions, edits, approvals by close of business (ET time).  Thanks.

"The WSDM TC understands your concerns with the WSDM V1.0 dependency on non standard versions of specifications. However, the TC believes that there is an industry need for standards for management using Web services and management of Web services that are implementable today. WSDM 1.0 is first industry standard that meets this need. The WSDM TC made WDSM 1.0 based on explicit versions of the specification in order to eliminate any ambiguity with regard to what it is dependent on and therefore ensure that WSDM is fully implementable and interoperable.  The TC did ensure that that the references are not in violation of OASIS policy.

The WSDM TC is expecting standard versions of these dependent specifications; therefore the TC will update WSDM specifications to refer to the standard and, if necessary, make changes to WSDM specification to come into compliance. Many companies are implementing and looking forward to the upcoming interoperability activity. "

These specifications are referred to in a normative way.  WSDM can not be implemented without using them.  

Web services Description Language (WSDL) 1.1, W3C Note, March 2001, http://www.w3.org/TR/wsdl

Web services Addressing (WS-Addressing), W3C Member Submission, August 2004, http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/

Web Services Resource Properties 1.2 (WS-ResourceProperties), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-04.pdf

 Web Services Base Notification 1.2 (WS-BaseNotification), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-03.pdf

Web Services Topics 1.2 (WS-Topics), OASIS Working Draft, July 2004, http://docs.oasis-open.org/wsn/2004/06/wsn-WS-Topics-1.2-draft-01.pdf

These specifications are referred to in advisory way.  WSDM can be implemented without using them.

Web Services Service Group 1.2 (WS-ServiceGroup), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.pdf

Web Services Resource Lifetime 1.2 (WS-ResourceLifetime), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-03.pdf

Web Services Resource Metadata 1.0 (WS-ResourceMetadataDescriptor), OASIS Working Draft, October 2004, http://www.oasis-open.org/committees/download.php/9758/wsrf-WS-ResourceMetadataDescriptor-1.0-draft-01.PDF

Heather Kreger
STSM, Web Services Lead Architect for SWG Emerging Technologies
Author of "Java and JMX: Building Manageable Systems"
kreger@us.ibm.com
919-543-3211 (t/l 441)  cell:919-496-9572