[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsdm] Draft of response
Reworded to add emphasis by employing active voice and shortening the text; 2 sentence clauses added to improve readability. One sentence shifted to (what I hope is) a more logical spot. One typo corrected ("non-standard" for "non standard"). Accept, reject, or wordsmith this as you prefer. The WSDM TC understands your concern that WSDM 1.0 depends on non-standard versions of other specifications; nevertheless, the TC has requested OASIS to approve WSDM 1.0 as a standard. The TC believes the industry has an immediate need for standards for management using Web services and management of Web services. WSDM 1.0 is the first industry standard to meet this need; many companies will test their WSDM implementations during the upcoming interoperability activity. The TC does not consider the dependencies a problem because WDSM 1.0 refers to explicit versions of the specifications it depends on, ensuring that WSDM can be implemented fully and interoperably. The TC has been assured that such references do not violate OASIS policy. As standard versions of these dependent specifications receive approval from their respective standards bodies, the WSDM TC will update the WSDM specifications to refer to and comply with these standards. Hope that's of some use, Mark Peel Web Services Infrastructure Novell, Inc. >>> Heather Kreger <kreger@us.ibm.com> 3/3/05 8:44 PM >>> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]