[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: WSDM v1.1 Submitted for OASIS Standard
OASIS Members: The OASIS Web Services Distributed Management (WSDM) Technical Committee has submitted the following specification set, which is an approved Committee Specification, to be considered as an OASIS Standard: Web Services Distributed Management: Management Using Web Services (WSDM-MUWS) v1.1 Web Services Distributed Management: Management Using Web Services (WSDM-MUWS) v1.1, Part 2 Web Services Distributed Management: Management of Web Services (WSDM-MOWS) v1.1 The text of the TC submission is appended. You now have until 15 July to familiarize yourself with the submission and provide input to your organization's voting representative. On 16 July, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have until the last day of July, inclusive, to cast their ballots on whether this Committee Specification should be approved as an OASIS Standard or not. Members who wish to discuss this ballot may do so through email@example.com. In accordance with the OASIS Technical Committee Process, this Committee Specification has already completed the necessary 60-day public review period as noted in the submission below. The normative TC Process for approval of Committee Specifications as OASIS Standards is found at http://www.oasis-open.org/committees/process.php#3.4 Any statements related to the IPR of this specification are posted at: http://www.oasis-open.org/committees/wsdm/ipr.php Your participation in the review and balloting process is greatly appreciated. Mary Mary P McRae Manager of TC Administration, OASIS email: firstname.lastname@example.org phone: 603.232.9090 ----------------------- In accordance with OASIS Technical Committee Process for Member Approval (http://www.oasis-open.org/committees/process.php#3.4), the WSDM TC recommends that the Committee Specification of WSDM 1.1 be made an OASIS Standard. WSDM TC has approved a resolution to move the specification forward; therefore, the chair of the WSDM TC submits the following items to OASIS TC Administration: a. Links to the approved Committee Specification in the TC's document repository, and any appropriate supplemental documentation for the specification, both of which must be written using the OASIS templates. The specification may not have been changed between its approval as a Committee Specification and its submission to OASIS for consideration as an OASIS Standard, except for the changes on the title page and running footer noting the approval status and date. Zip file containing all specifications and documents is at: http://www.oasis-open.org/committees/download.php/18756/wsdm-1.1-cs-01.zip Specifications: MUWS 1.0 Part 1 Specification: http://www.oasis-open.org/committees/download.php/18755/wsdm-muws1-1.1-spec-cs-01.pdf MUWS 1.0 Part 2 Specification: http://www.oasis-open.org/committees/download.php/18754/wsdm-muws2-1.1-spec-cs-01.pdf MOWS 1.0 Specification: http://www.oasis-open.org/committees/download.php/18753/wsdm-mows-1.1-spec-cs-01.pdf XML Schema and WSDL documents are available in the Zip file and at: http://www.oasis-open.org/committees/download.php/18756/wsdm-1.1-cs-01.zip or individually below: WSDM MUWS 1.1 Part 1 XML Schema - http://www.oasis-open.org/committees/download.php/18681/muws1-2.xsd WSDM MUWS 1.1 Part 2 XML Schema - http://www.oasis-open.org/committees/download.php/18682/muws2-2.xsd WSDM MUWS 1.1 Part 2 WSDL - http://www.oasis-open.org/committees/download.php/18683/muws2-2.wsdl WSDM MUWS 1.1 Part 2 Topics Document - http://www.oasis-open.org/committees/download.php/18684/muwse2-2.xml WSDM MUWS 1.1 Part 2 PBM Schema - http://www.oasis-open.org/committees/download.php/18686/pbm.xsd WSDM MOWS 1.1 XML Schema - http://www.oasis-open.org/committees/download.php/18687/mows-2.xsd WSDM MOWS 1.1 WSDL - http://www.oasis-open.org/committees/download.php/18688/mows-2.wsdl WSDM MOWS 1.1 Topics Document - http://www.oasis-open.org/committees/download.php/18689/mowse-2.xml b. The editable version of all files that are part of the Committee Specification; WSDM MUWS 1.1 Part 1: http://www.oasis-open.org/committees/download.php/18724/wsdm-muws1-1.1-spec-cs-01.doc WSDM MUWS 1.1 Part 2: http://www.oasis-open.org/committees/download.php/18725/wsdm-muws2-1.1-spec-cs-01.doc WSDM MOWS 1.1: http://www.oasis-open.org/committees/download.php/18726/wsdm-mows-1.1-spec-cs-01.doc c. Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or reference including fragments of such, are well formed, and that all expressions are valid; I, Heather Kreger, certify that the schema and instances are well formed and valid. d. A clear English-language summary of the specification; Web Services Distributed Management: Management Using Web Services (MUWS) 1.1 defines how to represent and access the manageability interfaces of resources as Web services. It is the foundation of enabling management applications to be built using Web services and allows resources to be managed by many managers with one set of instrumentation. This specification provides interoperable, base manageability for monitoring and control managers using Web services. WSDM MUWS 1.1 has been defined in two specifications, MUWS Part 1, which defines the base architectural concepts and required components, and MUWS Part 2 which defines standard composeable support for manageability capabilities. The MUWS 1.1 specifications define how to express the following manageability capabilities: identity, metrics, resource state, status, configuration, name correlation, and relationships. It defines standard descriptive techniques for each of these including required base properties, operations, and notifications, as well as required metadata for each of these to aid introspection. MUWS 1.1 also defines standard management event formats to enhance interoperability and correlateability. It defines how to provide secure management. In addition MUWS 1.1 defines recommendations and interfaces for advertising and discovering resources. MUWS 1.1 adds dependencies on the standardized versions of all dependent specifications. It also clarifies the relationships capabilities, added the ability to declare self in a relationship, and in MOWS, operational status and metrics were added for Web services Web Services Distributed Management: Management Of Web Services (MOWS) 1.1 specification defines the how to manage Web services as resources and how to describe and access that manageability using MUWS. It provides mechanisms and methodologies that enable manageable Web services applications to interoperate across enterprise and organizational boundaries. The MOWS specification allows integration of management with Web services-based business applications and processes. e. A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations; WSDM is related to the following OASIS TCs: The MUWS and MOWS standards are based upon other OASIS standards that are currently under development within OASIS. Most importantly, the WSDM TC has defined manageable resources as resources in a Web Services Resource Framework (WSRF) based context. Thus, the WSDM specification will rely on the following OASIS standards (some of which will be under development at the time WSDM 1.0 is produced). WSDM 1.1 depends on the Standard version of these specifications. • WS-Resource Framework TC: WS-ResourceProperties http://docs.oasis-open.org/wsrf/wsrf-ws_resource_lifetime-1.2-spec-os.pdf • WS-Resource Framework TC: WS-ResourceLifetime http://docs.oasis-open.org/wsrf/wsrf-ws_resource_lifetime-1.2-spec-os.pdf • WS-Resource Framework TC: WS-ServiceGroup http://docs.oasis-open.org/wsrf/wsrf-ws_service_group-1.2-spec-os.pdf • WS-Notifications TC: Base Notification http://www.oasis-open.org/committees/wsn-ws_base_notification-1.3-spec-pr-03.pdf • WS-Notifications TC: Topics http://www.oasis-open.org/committees/wsn-ws_topics-1.3-spec-pr-02.pdf WSDM is related to the following external standards work: WS-I: WSDM has a requirement that WSDM implementation may be WS-I Basic Profile compliant. W3C: The WSDM TC's work has been influence by the W3C Web Service Architecture and Web Service Description working groups. WSDM is also dependent on the following W3C recommendations: • XML http://www.w3.org/TR/REC-xml • XML Schema http://www.w3.org/TR/xmlschema-1 • SOAP http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ • WSDL http://www.w3.org/TR/wsdl • WS-Addressing http://www.w3.org/TR/ws-addr-core Global Grid Forum: The WSDM TC has been working to ensure that the needs of the Global Grid Forum (GGF), Open Grid Services Architecture Working Group are incorporated in the developing standard which has announced intent to use the WSDM specifications to express and access the manageability of Grid resources. DMTF: The WSDM TC has established a liaison with the DMTF (link to DMTF Work Register: http://www.oasis-open.org/committees/download.php/5414/WSDM-DMTFWorkRegister_v2.doc to ensure that the models produced by these groups can be represented using the WSDM standards. The DMTF W BEM Interoperability Protocol Work Group WSDM Subgroup is currently chartered to develop Web services protocol for accessing CIM modeled resources using the WSDM 1.1 specification. f. Certification by at least three OASIS member organizations that they are successfully using the specification consistently with the OASIS IPR Policy are posted here: 1. International Business Machines: http://lists.oasis-open.org/archives/wsdm/200606/msg00021.html IBM Corporation certifies that they are successfully using the WSDM 1.1 specification consistently with the OASIS IPR Policy. 2. Amberpoint, Inc.: http://lists.oasis-open.org/archives/wsdm/200606/msg00024.html AmberPoint, Inc. certifies that we are successfully using the WSDM 1.1 specifications. 3. Cisco Systems Inc., http://lists.oasis-open.org/archives/wsdm/200606/msg00033.html Cisco Systems Inc. certifies that they are successfully using the WSDM 1.1 specification consistently with the OASIS IPR Policy. g. The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a pointer to an account of each of the comments/issues raised during the public review period(s), along with its resolution; Public review began on March 20, 2006 with the announcement posted at: http://lists.oasis-open.org/archives/tc-announce/200603/msg00006.html Two sets of comments were raised during the public review period, its details and resolutions are at: http://www.oasis-open.org/committees/download.php/18562/WSDM%20Public%20Review%20Comments%20and%20Resolution.05312006.doc. The comments are corrected in the Committee Specification and Schemas that have been submitted for OASIS Member Vote. h. An account of and results of the voting to approve the specification as a Committee Specification, including the date of the ballot and a pointer to the ballot; Committee Draft voting record for ballot running from May 26, 2005 8pm ET to June 2, 2005 23:45 ET with 100% voting and approval at http://www.oasis-open.org/committees/ballot.php?id=1028 i. An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the same specification, together with the originating TC's response to each comment; WSDM 1.0 is the first successful standardization of essentially the same specification. This is the first standardization of WSDM 1.1 specifications. j. A pointer to the publicly visible comments archive for the originating TC The archive for WSDM TC email is at: http://lists.oasis-open.org/archives/wsdm/. The archive for WSDM TC public comment list email is at: http://lists.oasis-open.org/archives/wsdm-comment/ k. A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the Committee Specification, which report may include statements regarding why the member voted against the specification or that the member believes that Substantive Changes were made which have not gone through public review; or certification by the Chair that no minority reports exist. I certify that there were no minority reports who did not vote in favor of approving the Committee Draft.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]