[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm][UPlat] "How"s for several sections of the Uplat document
Here is my to-do on the "how" for transactions (Section 2.1.12): <transaction-how> There are several existing specifications addressing web services transactions. These are: - Committee Specs from the OASIS Business Transactions http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=business-tran saction See "Documents" - WS-Transaction Management submitted to the OASIS Web Services Composite Application Framework http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-caf See also http://developers.sun.com/techtopics/webservices/wscaf/wstxm.pdf - WS-Transaction http://www-106.ibm.com/developerworks/webservices/library/ws-transpec/ <\transaction-how> Also, I would like to add to the "how" for several sections: - 2.1.4 Meta-data Additional text: "One of the strong points of the Distributed Management Task Force's Common Information Model (CIM) is the concept of qualifiers. Qualifiers are meta-data concerning a class, property, method, notification or method parameter. The CIM qualifiers may be mined for useful information for web services meta-data." - 2.1.7 Relationships Additional text: "The standard UML relationships and refinements of those described by the DMTF CIM Schema may be consulted for additional semantics." - 2.1.10 Policy: Additional text: "Policy is also of prime concern in various industry standards - GGF's Policy Research Group (https://forge.gridforum.org/projects/policy-rg/), IETF's Policy Framework Working Group (http://www.ietf.org/html.charters/policy-charter.html) and DMTF's Policy Working Group (http://www.dmtf.org/about/committees/slaWGCharter.pdf). Existing standards should be built upon, for the web services work. Also, policy languages such as Imperial College's Ponder (http://www-dse.doc.ic.ac.uk/Research/policies/index.shtml) may be useful." - 2.1.11 Collection Additional text: "DMTF CIM's Core Model Collection class and its associations, MemberOfCollection and OrderedMemberOfCollection" Andrea -----Original Message----- From: Andreas Dharmawan [mailto:andreas@westbridgetech.com] Sent: Wednesday, November 26, 2003 12:01 PM To: wsdm@lists.oasis-open.org Subject: [wsdm][UPlat] TO DOs: ------- Transaction: - Need confirmation regarding the how from Andrea W. Notification: - Waiting for an update from Igor. Name Resolution: - Heather needs to clarify relationship between Name resolutin and Discovery and Registration General: - Andreas need to add priority on each item. I am waiting for confirmation from the group on the latest email containing the agreed priority. Changes made in this revision: ------------------------------ Identification: - moved some part of what to how section Version: - fixed the example - echo concerns: <There is an argument for WSDM-UPlat to specify the format of manageable webservice component's versioning. This will be resolved in F2F meeting.> Flow: - Added new What, Why, and How sections Meta-Data: - Added how: Possibly add some short-term meta data schema by WSDM if OGSI specs not available Addressing: - Added Addressing note from William's 11/19/2003 Attributes: - Added how: follow OGSI specs on the mechanism to implment attributes Relationship: - Updated with latest write up from Heather - Added Igor's recommendation on how Security: - Added WS-Security on how section Resource State Model: - Removed duplicated section Collection: - Updated base Hoamyoun email Transaction: - Inserted picture - How: Leverage other Webservice standards on transaction Registration and Discovery: - How: In the mean time come up with simplistic solution and will grow to future more sophisticated solution such as UDDI Policy: - How: Leverage existing Webservice standards that can implement various policies. General: - added Homayoun's and Igor's reommendation on how on the following items: co-relatable names, versioning, attributes, meta data, notification, relationship, security, collection, negotiation
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]