[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] Uploaded and updated MUWS 05-20040216
Andreas, Figure 2.4-1 is a replica of the figure 2.3-1. We should remove the 2.4-1 or discuss why is it needed if there is someone to defend it. -- Igor Sedukhin .. (igor.sedukhin@ca.com) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 -----Original Message----- From: Andreas Dharmawan [mailto:andreas@westbridgetech.com] Sent: Tuesday, February 17, 2004 12:50 PM To: Sedukhin, Igor S; wsdm@lists.oasis-open.org Subject: RE: [wsdm] Uploaded and updated MUWS 05-20040216 Igor: Thank you for the feedback. I will incorporate all feedback before our conf call this week (Wed night. I am expecting more items and feedback.) and upload the new revision. Regards, Andreas -----Original Message----- From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] Sent: Tuesday, February 17, 2004 9:24 AM To: Andreas Dharmawan; wsdm@lists.oasis-open.org Subject: RE: [wsdm] Uploaded and updated MUWS 05-20040216 Andreas, Great document. Following are my comments. 2.5 belongs to 2.1 or immediately after. This is the context and not concepts. This is the way we discussed it at the F2F. I believe you can use "composability" as a word. It has been used, for example [We use the term composability to describe independent specifications that can be combined to provide more powerful capabilities.] from http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwssec ur/html/securitywhitepaper.asp 4.1.4: It may be a better idea to have all properties in one document at the beginning. That way it is easier to understand the actual schema. Other XML specs sucessfully followed this approach. The text descriptions follow the combined XML instance example (just like in the metrics ot state docs). You do not need 4.1.5 and 4.1.6. I suggest that they are removed. I suggest that 4.1.2 becomes 4.1 and everything else follows starting from 4.2. That way you don't need to repeat same set of namespaces for MUWS for every capability definition. 4.1.3 is not Data Types. In fact, there are no reusable data types in Identity. If we want to have any, then that has to be XML Schema and not UML there. I suggest that UML goes right on top after 4.1 without any subsection headings. -- Igor Sedukhin .. (igor.sedukhin@ca.com) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 -----Original Message----- From: Andreas Dharmawan [mailto:andreas@westbridgetech.com] Sent: Monday, February 16, 2004 10:01 PM To: wsdm@lists.oasis-open.org Subject: [wsdm] Uploaded and updated MUWS 05-20040216 Hi team: The URL is: http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/5497/wd-w sdm-muws-0.5-20040216.doc In this revision: - Added Abstract and Introduction - Incorporated compose-ability note from Igor's email under architecture section - Incorporated Metrics draft from F2F, and State draft from F2F - Modify Identity section format to conform with the rest of capabilities For those who have action items due on Feb 18th, if you forward the deliverables by the 17th to William and me, we will incorporate them for the conf call. Regards, Andreas To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou p.php. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou p.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]