OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: MUWS platform recommendations


Dear WSDM TC Colleagues,

Heather (TC Member hat on) and Homayoun were responsible for the outstanding recommendations on determining the Web services platform for WSDM's specifications. The immediate and urgent specifications/technologies that needed to be recommended were for:
  • Addressing
  • Notification
  • Properties/Attributes
  • Metadata (descriptive information about the manageability interface)
We would like to recommend the Web Services Resource Framework as the specification solution for 3 of 4 of these urgent needs. Metadata is yet to be addressed. So specifically, we would like to recommend:
  • WS-Addressing for Addressing
  • WS-Notifications for Notification
  • WS-ResourceProperties for Properties/Attributes
We feel that in order to achieve our aggressive March 0.5 specification dates, we need to leverage specifications already written, which are targeted for standardization, and supported by multiple vendors.

We would like the TC to read these specifications in detail for the February F2F and be prepared to discuss them during the WS-Resource Framework session and vote to approve/disapprove use of them by our specifications.

Heather (Chair hat on) and Winston propose that we navigate the the pre-submission state of the specifications as follows:

  1. WSDM 0.5 specifications - subset of functionality, identity, metrics, state, and simple notification. Since this is a draft specification, it is more acceptable for us to reference/require specifications which are not yet standards, or submitted to standards. For expedience, we can reference to 1.0 pre-submission versions of these specifications.
  2. WSDM 1.0 specifications - complete functionality of WSDM, including operations, configuration, security, Relationships, tbd. This is a final version of the specification and should not be dependent on specifications that are not yet submitted (although not finished going through standardization) to a standards body. All specifications we depend upon would need to be submitted by that time. If any of these specifications are not submitted for standardization by the time we start the 1.0 work, an alternative approach will be selected. Realistically, I think the TC is looking (Heather's best guess) at a July delivery based on the outstanding work and hard questions to be worked through. 
  3. WSDM 2.0 specifications - revised specification to accommodate and leverage the final, standardized versions of WS-Addressing, WS-Notifications, WS-Resource Properties, WSDL 2.0, and other specifications we feel are relevant (possibly Policy, etc.).

We would like the TC to consider this delivery plan and accommodation of specification dependencies and standardization and be prepared to discuss and approve/disapprove it at our February F2F.   The WSRF specifications can be located under:
http://www.devresource.hp.com/drc/specifications/wsrf/index.jsp

Heather Kreger, Winston Bumpus, Homayoun Pourheidari
-- 
M. Homayoun Pourheidari
Management Services Organization
408.447.5012
homayoun@hp.com


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]