[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: MUWS Requirements Edits from last week.
Here are the edits I had from last week for the WSA Compliance Requirement. These have not been integrated by the editors yet. 1.1.1 WSA Compliance [FR001] The management protocol MUST use existing Internet infrastructure and be compliant to Web Services Architecture developed by W3C WSA Working Group. (Source: IBM, HP, MPTC). {#1, #45, #96} The standards included for the purpose of this section: · XML · HTTP, HTTPS · SOAP · WSDL (1.1 or 1.2?) · WS-I Basic Profile (as a goal for interoperability) · WS-Security [FR001.1] MUST involve exchange of XML infoset messages. <HK: not must, messages expressable in XML. > (attachments, http, binary compression) [FR001.2] MUST allow discovery of manageable resources through Web services discovery mechanisms. These mechanisms could be based on a central registry like UDDI and/or decentralized, out-of-band gathering of WSDL documents (such as retrieving WSDL documents through a crawler). (Source: IBM, HP, MPTC) {#6} < Winston: Make separate high level requirement, look at discovery mechanism to see if sufficient (i.e. email, asking one resource for other resources. May need normative method for interop. > [FR001.3] MUST require description of management capabilities of a manageable resource using WSDL. (align and ref w/ 122) WSDL should be used for capabilities – ref 122 interface - props and ops that represent the management capabilities access – description binding of interface to wire format (including message packaging) addressability description – info necessary to send a message to invoke the interface described using the access described. ( Source: IBM, HP, MPTC) {#2, #3, #4, #15} [FR001.4] Goal: Leverage, does not invent, non-management specific Web services infrastructure. If non-management specific services/infrastructure is required then it is placed as a requirement on the Web services community. This TC may need to assist in the development of the infrastructure services. Required infrastructure include: notifications, relationships, registry etc. {#1, #11, #22, #39, #57, #125, #128} [FR001.5] Delete>> Should follow the principles of Web Services – Loose Coupling {#48}, Discoverable {#6, #76 – to new section}, Internet friendly (already have from top part) (need to define loose coupling, architectural? Msg? [FR001.6] Outline an architecture for Management Using Web Services. {#28, #57}, management patterns, how a mgmt app uses, how a mgd resource uses, how to self manage. < move to specification requirements > [FR001.7] Interoperability between vendors. Goal: WS-I basic profile conformance.{#71} <delete> [FR001.8] Use HTTPS for security on the wire. {#25}, Should also leverage WS-Security as well. {#25} < Delete, covered by FR001 and security section) 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]