[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
-----Original Message----- From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] Sent: Monday, October 27, 2003 10:21 AM To: ECKERT,ZULAH (HP-Cupertino,ex1); wsdm@lists.oasis-open.org Subject: RE: [wsdm] [OMod] minutes of Oct 21th 2003 call Zulah, Thank you for correcting the minutes. Those were important points I forgot to capture. About the metric/performance, do you want the group to discuss it as an issue or was it just a note? Currently it says Metrics on slide 17. And immediately I have this use case. If, say, request counters are used for security audits, then are those counters performance information or security information or audit information or are they simply metrics? Are all known "metrics" performance only? Can anyone guarantee that? If a metric is a number of autentication failures on the resource, is that related to performance as well? -- Igor Sedukhin .. (igor.sedukhin@ca.com) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 _____ From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com] Sent: Monday, October 27, 2003 12:36 PM To: Sedukhin, Igor S; wsdm@lists.oasis-open.org Subject: RE: [wsdm] [OMod] minutes of Oct 21th 2003 call For issue #1 I have a few clarifications. We did agree to the capabilities listed in the first bullet of slide 17, however the following discussion took place: * This is the model for capabilities - not the mapping to an interface. As a model, it represents the kinds of manageability capabilities that we expect Web services to have. The mapping to an interface might be based on a different set of categories (perhaps based on access control requirements). So, the information model and the interface mapping are different things and will be based on different requirements. * The term "atomic manageability capability" was not agreeable to the group because the capabilities are not atomic. I also would like to call out my preference for the term "performance" over "metric" as many of the things that will fall into this category (based on MTF discussions) are counters from which metrics might be taken. What everything in this group has in common is that it relates to the performance of the resource under management. Zulah -----Original Message----- From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] Sent: Tuesday, October 21, 2003 11:46 AM To: wsdm@lists.oasis-open.org Subject: [wsdm] [OMod] minutes of Oct 21th 2003 call Roll: Igor, BrianC, DanF, William, Zulah, Heather, Alexandro, Fred, Andrea Approval of minutes http://lists.oasis-open.org/archives/wsdm/200310/msg00075.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00075.html> approved Agenda ISSUE 1: identifying one atomic manageability capability which we can model with props/ops/events/metadata, can we just stick to slide 17? In other words: do we lump all operations/props/events into one UML piece (class) or do we split classes as indicated on slide 17. [long discussion not recorded] DECISION: we will start defining a UML model componentized according to categories (concerns, capabilities) expressed on the slide 17 subbulets of the first bullet. Igor: will send empty UML model with those components ISSUE 2: manageability of a web service: inferred from manageable endpoints or do we need to define manageable service separately The former means that an endpoint's manageability information is sufficient to infer manageability of a service. The manager can do it and may represent the manageable service which we may define later, but not now. The later means that we define manageable service as a separate concept and associate manageability capabilities and information with it and not with an endpoint. [long discussion on the culprits of the web service concepts, not recorded] DECISION: we will not define separate model for a manageable service ACTION: William to provide text on inferring manageability of a service from manageable endpoints (generally, no specifics of how) William's concern about manageability information to capture relationship of endpoints and services separately from WSDL/UDDI, etc. was postponed until we get to discuss the actual manageability model with concete properties, etc. William will propose and justify concrete elements of the model at that point. ISSUE 3: aggregation of manageability to the endpoint level is a responsibility of the provider of manageability (need text for the concepts section) This is clear, but needs an action item on someone to provide the text. BrianC's input: http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html> Igor's answer: http://lists.oasis-open.org/archives/wsdm/200310/msg00081.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00081.html> ACTION: Fred to provide text for the ISSUE 3. ISSUE 4 (by BrianC): concepts of versioning have to be applied to the MOWS Concepts diagram Igor: yes, but may be as details of the concepts diagram: pick elements that are necessary to express the versioning/revision concepts and draw a diagram complimentary to the main diagram ACTION: BrianC to provide a versioning concepts diagram BrianC's input http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html> BrianC presented the UML diagram on the page 3 of the <http://lists.oasis-open.org/archives/wsdm/200310/doc00006.doc> http://lists.oasis-open.org/archives/wsdm/200310/doc00006.doc - revisions are infromation about the an element - change descriptions are information about transitions between revisions [Andrea's comments?? sorry, didn't capture them] BrianC: question to the group: should revision concepts be part of the main diagram or a detail diagram that compliments the main diagram? Andrea, DanF, Igor: complimentary detail diagram DanF&Igor had a concern that version has to be expressed as well. For example a versioned service "is a" service with version as an attribution. Revisions are written against versioned elements (associated to). This applies to all other elements that can be versioned. BrianC agreed. ACTION: BrianC to align the versioning/revision/change detail UML diagram with the MOWS Concepts diagram and incorporate "versioned X is an X" elements. CALL CLOSED ISSUE 5: using http://lists.oasis-open.org/archives/wsdm/200310/msg00067.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00067.html> UML approach ACTION: BrianC to attempt to express ManageableEndpointState UML information model linked directly to the web service endpoint state diagrams designed by the W3C Arch MTF. Igor's simplified proposal: http://lists.oasis-open.org/archives/wsdm/200310/msg00082.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00082.html> and other possible choices http://lists.oasis-open.org/archives/wsdm/200310/msg00083.html <http://lists.oasis-open.org/archives/wsdm/200310/msg00083.html> NOT DISCUSSED ISSUE 6: There is a need for another diagram to display the "locus of implementation" concepts. Essentially the diagram to depict relationships between manageable endpoint in MOWS Concepts and manageability endpoint in MUWS. ACTION: Igor to provide "locus of implementation" concepts diagram for MOWS. See http://www.oasis-open.org/archives/wsdm/200310/msg00076.html <http://www.oasis-open.org/archives/wsdm/200310/msg00076.html> NOT DISCUSSED ISSUE 7: another diagram that shows relationships of MUWS and MOWS concepts (possibly aggregation/composition of manageability capabilities). NOT DISCUSSED -- Igor Sedukhin .. (igor.sedukhin@ca.com) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 ------_=_NextPart_001_01C39CD0.36165B12 Content-Type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <TITLE>Message</TITLE> <META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2>I think it is very restrictive to interpret performance only through the angle of throughput. Performance is about how the resource is performing its task. If the tasks of the resource include processing (or requesting) authentication tasks, then yes, the number of authentication failures is part of the performance of the resource.</FONT></SPAN></DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2>For a sport car fan, performance of a car is limited to max speed and acceleration, but for a real user or a manager (mechanic) of a car it contains a lot more than this, including how often the electric sunroof failed to close properly and the driver got rained on. Performance is just how the resource executes the tasks it is designed to execute.</FONT></SPAN></DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2>From Webster.com:</FONT></SPAN></DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=365061321-27102003>Main Entry: <B>per·for·mance</B><BR>Pronunciation: <TT>p&(r)-'for-m&n(t)s</TT><BR>Function: <I>noun</I><BR>Date: 15th century<BR><B>1 a</B> <B>:</B> the execution of an action <B>b</B> <B>:</B> something accomplished <B>: <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=deed"><FONT size=-1>DEED</FONT></A>, <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=feat"><FONT size=-1>FEAT</FONT></A></B><BR><B>2</B> <B>:</B> the fulfillment of a claim, promise, or request <B>: <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=implementation"><FONT size=-1>IMPLEMENTATION</FONT></A></B><BR><B>3 a</B> <B>:</B> the action of representing a character in a play <B>b</B> <B>:</B> a public presentation or exhibition <a benefit <I>performance</I>><BR><B>4 a</B> <B>:</B> the ability to <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=perform">perform</A> <B>: <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=efficiency"><FONT size=-1>EFFICIENCY</FONT></A></B> <B>b</B> <B>:</B> the manner in which a mechanism <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=performs">performs</A> <engine <I>performance</I>><BR><B>5</B> <B>:</B> the manner of reacting to stimuli <B>: <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=behavior"><FONT size=-1>BEHAVIOR</FONT></A></B><BR><B>6</B> <B>:</B> the linguistic behavior of an individual <B>: <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=parole"><FONT size=-1>PAROLE</FONT></A></B>; <I>also</I> <B>:</B> the ability to speak a certain language -- compare <A href="http://webster.com/cgi-bin/dictionary?book=Dictionary&va=competence+"><FONT size=-1>COMPETENCE </FONT></A>3 </SPAN></DIV> <DIV><SPAN class=365061321-27102003></SPAN> </DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2>Regards,</FONT></SPAN></DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=365061321-27102003><FONT face="Courier New" color=#0000ff size=2>William</FONT></SPAN></DIV> <BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] <BR><B>Sent:</B> Monday, October 27, 2003 10:21 AM<BR><B>To:</B> ECKERT,ZULAH (HP-Cupertino,ex1); wsdm@lists.oasis-open.org<BR><B>Subject:</B> RE: [wsdm] [OMod] minutes of Oct 21th 2003 call<BR><BR></FONT></DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2>Zulah,</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2>Thank you for correcting the minutes. Those were important points I forgot to capture.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2>About the metric/performance, do you want the group to discuss it as an issue or was it just a note? Currently it says Metrics on slide 17.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2>And immediately I have this use case. If, say, request counters are used for security audits, then are those counters performance information or security information or audit information or are they simply metrics? Are all known "metrics" performance only? Can anyone guarantee that?</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=345561118-27102003><FONT face=Arial color=#0000ff size=2>If a metric is a number of autentication failures on the resource, is that related to performance as well?</FONT></SPAN></DIV> <DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><!-- Converted from text/rtf format --> <P><SPAN lang=en-us><FONT face="Arial Black" color=#800080 size=2>--</FONT><FONT face=Arial size=2><B> </B></FONT><B><FONT face=Arial color=#000080 size=2>Igor Sedukhin</FONT></B><FONT face=Arial size=2></FONT> <FONT face="Arial Black" color=#c0c0c0 size=2>..</FONT><FONT face=Arial size=2> </FONT><FONT face=Arial color=#800080 size=2>(</FONT><FONT face=Arial size=2>igor.sedukhin@ca.com</FONT><FONT face=Arial color=#800080 size=2>)</FONT></SPAN> <BR><SPAN lang=en-us><FONT face="Arial Black" color=#800080 size=2>--</FONT><FONT face=Arial size=2></FONT><B> <FONT face=Arial color=#808080 size=2>(631) 342-4325</FONT></B><FONT face=Arial size=2></FONT> <FONT face="Arial Black" color=#c0c0c0 size=2>..</FONT><FONT face=Arial size=2> </FONT><FONT face=Arial color=#008080 size=2>1 CA Plaza, Islandia, NY 11788</FONT></SPAN><SPAN lang=ru></SPAN><SPAN lang=ru></SPAN> </P> <DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><FONT face=Arial color=#008080 size=2></FONT><BR> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> <FONT face=Tahoma size=2><B>From:</B> ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com] <BR><B>Sent:</B> Monday, October 27, 2003 12:36 PM<BR><B>To:</B> Sedukhin, Igor S; wsdm@lists.oasis-open.org<BR><B>Subject:</B> RE: [wsdm] [OMod] minutes of Oct 21th 2003 call<BR></FONT><BR></DIV> <DIV></DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2>For issue #1 I have a few clarifications. We did agree to the capabilities listed in the first bullet of slide 17, however the following discussion took place:</FONT></SPAN></DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2>* This is the model for capabilities - not the mapping to an interface. As a model, it represents the kinds of manageability capabilities that we expect Web services to have. The mapping to an interface might be based on a different set of categories (perhaps based on access control requirements). So, the information model and the interface mapping are different things and will be based on different requirements.</FONT></SPAN></DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2>* The term "atomic manageability capability" was not agreeable to the group because the capabilities are not atomic.</FONT></SPAN></DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2>I also would like to call out my preference for the term "performance" over "metric" as many of the things that will fall into this category (based on MTF discussions) are counters from which metrics might be taken. What everything in this group has in common is that it relates to the performance of the resource under management.</FONT></SPAN></DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=296252617-27102003><FONT face=Arial color=#0000ff size=2>Zulah</FONT></SPAN></DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] <BR><B>Sent:</B> Tuesday, October 21, 2003 11:46 AM<BR><B>To:</B> wsdm@lists.oasis-open.org<BR><B>Subject:</B> [wsdm] [OMod] minutes of Oct 21th 2003 call<BR><BR></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#ff0000 size=2><SPAN class=732020819-17102003><SPAN class=432123516-21102003>Roll: Igor, BrianC, DanF, William, Zulah, Heather, Alexandro, Fred, Andrea</SPAN></SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003><SPAN class=432123516-21102003></SPAN></SPAN></FONT> </DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003><SPAN class=432123516-21102003>Approval of minutes <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00075.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00075.html</A></SPAN></SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#ff0000 size=2><SPAN class=732020819-17102003><SPAN class=432123516-21102003>approved</SPAN></SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003></SPAN></FONT> </DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003><SPAN class=432123516-21102003>Agenda</SPAN></SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003></SPAN></FONT> </DIV> <DIV dir=ltr align=left> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003><STRONG>ISSUE<SPAN class=654185116-20102003> 1</SPAN></STRONG>: identifying one atomic manageability capability which we can model with props/ops/events/metadata, can we just stick to slide 17?</SPAN></FONT></DIV></DIV> <DIV><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2>In other words: do we lump all operations/props/events into one UML piece (class) or do we split classes as indicated on slide 17.</FONT></SPAN></DIV> <DIV><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=654185116-20102003><FONT face=Arial color=#ff0000 size=2><SPAN class=432123516-21102003>[long discussion not recorded]</SPAN></FONT></SPAN></DIV> <DIV><SPAN class=654185116-20102003><FONT face=Arial color=#ff0000 size=2><SPAN class=432123516-21102003>DECISION: we will start defining a UML model componentized according to categories (concerns, capabilities) expressed on the slide 17 subbulets of the first bullet.</SPAN></FONT></SPAN></DIV> <DIV><SPAN class=654185116-20102003><FONT face=Arial color=#ff0000 size=2><SPAN class=432123516-21102003>Igor: will send empty UML model with those components</SPAN></FONT></SPAN></DIV> <DIV><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=654185116-20102003> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><STRONG>ISSUE<SPAN class=654185116-20102003> 2</SPAN></STRONG>: manageability of a web service: inferred from manageable endpoints or <SPAN class=654185116-20102003>do </SPAN>we need to define manageable service separately</FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2>The former means that an endpoint's manageability information is sufficient to infer manageability of a service. The manager can do it and may represent the manageable service which we may define later, but not now. The later means that we define manageable service as a separate concept and associate manageability capabilities and information with it and not with an endpoint.</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>[long discussion on the culprits of the web service concepts, not recorded]</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>DECISION: we will not define separate model for a manageable service</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>ACTION: William to provide text on inferring manageability of a service from manageable endpoints (generally, no specifics of how)</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>William's concern about manageability information to capture relationship of endpoints and services separately from WSDL/UDDI, etc. was postponed until we get to discuss the actual manageability model with concete properties, etc. William will propose and justify concrete elements of the model at that point.</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><STRONG>ISSUE<SPAN class=654185116-20102003> 3</SPAN></STRONG>: aggregation of manageability to the endpoint level is a responsibility of the provider of manageability (need text for the concepts section)</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2>This is clear, but needs an action item on someone to provide the text.</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><SPAN class=432123516-21102003>BrianC's input: <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html</A></SPAN></FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><SPAN class=432123516-21102003>Igor's answer: <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00081.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00081.html</A></SPAN></FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><SPAN class=432123516-21102003></SPAN></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#ff0000 size=2><SPAN class=432123516-21102003>ACTION: Fred to provide text for the ISSUE 3.</SPAN></FONT></SPAN></DIV></FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><STRONG>ISSUE<SPAN class=654185116-20102003> 4</SPAN></STRONG> (by BrianC): concepts of versioning have to be applied to the MOWS Concepts diagram</FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2>Igor: yes, but may be as details of the concepts diagram: pick elements that are necessary to express the versioning/revision concepts and draw a diagram complimentary to the main diagram</FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial><FONT color=#0000ff><FONT size=2>ACTION: BrianC to provide a versioning concepts diagram<SPAN class=432123516-21102003> </SPAN></FONT></FONT></FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=432123516-21102003></SPAN></FONT></FONT></FONT></SPAN> </DIV></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><SPAN class=432123516-21102003>BrianC's input <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00080.html</A></SPAN></FONT></SPAN></FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial size=2><FONT color=#ff0000>BrianC presented the UML diagram on the page 3 of the </FONT><A href="http://lists.oasis-open.org/archives/wsdm/200310/doc00006.doc"><FONT color=#ff0000>http://lists.oasis-open.org/archives/wsdm/200310/doc00006.doc</FONT></A></FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>- revisions are infromation about the an element</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>- change descriptions are information about transitions between revisions</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>[Andrea's comments?? sorry, didn't capture them]</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>BrianC: question to the group: should revision concepts be part of the main diagram or a detail diagram that compliments the main diagram?</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>Andrea, DanF, Igor: complimentary detail diagram</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>DanF&Igor had a concern that version has to be expressed as well. For example a versioned service "is a" service with version as an attribution. Revisions are written against versioned elements (associated to). This applies to all other elements that can be versioned.</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>BrianC agreed.</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#ff0000 size=2>ACTION: BrianC to align the versioning/revision/change detail UML diagram with the MOWS Concepts diagram and incorporate "versioned X is an X" elements.</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN></SPAN></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#0000ff size=2>CALL CLOSED</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2><STRONG>ISSUE 5</STRONG>: using <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00067.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00067.html</A> UML approach</FONT></SPAN></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=732020819-17102003> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2>ACTION: BrianC to attempt to express ManageableEndpointState UML information model linked directly to the web service endpoint state diagrams designed by the W3C Arch MTF.</FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#0000ff size=2>Igor's simplified proposal: <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00082.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00082.html</A> and other possible choices <A href="http://lists.oasis-open.org/archives/wsdm/200310/msg00083.html">http://lists.oasis-open.org/archives/wsdm/200310/msg00083.html</A></FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><SPAN class=432123516-21102003><FONT face=Arial color=#0000ff size=2>NOT DISCUSSED</FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><STRONG>ISSUE<SPAN class=654185116-20102003> 6</SPAN></STRONG>: There is a need for another diagram to display the "locus of implementation" concepts.</FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=654185116-20102003>E</SPAN>ssentially the diagram to depict relationships between manageable endpoint in MOWS Concepts and manageability endpoint in MUWS.</FONT></FONT></FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2>ACTION: Igor to provide "locus of implementation" concepts diagram for MOWS.</FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><SPAN class=654185116-20102003><FONT face=Arial color=#0000ff size=2>See <A href="http://www.oasis-open.org/archives/wsdm/200310/msg00076.html">http://www.oasis-open.org/archives/wsdm/200310/msg00076.html</A></FONT></SPAN></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2><SPAN class=432123516-21102003>NOT DISCUSSED</SPAN></FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003> <DIV><SPAN class=732020819-17102003><FONT face=Arial><FONT color=#0000ff><FONT size=2><STRONG>ISSUE<SPAN class=654185116-20102003> 7</SPAN></STRONG>: another diagram that shows relationships of MUWS and MOWS concepts (possibly aggregation/composition of manageability capabilities).<SPAN class=432123516-21102003> </SPAN></FONT></FONT></FONT></SPAN></DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=432123516-21102003></SPAN></FONT></FONT></FONT></SPAN> </DIV> <DIV><SPAN class=732020819-17102003><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=432123516-21102003>NOT DISCUSSED</SPAN></FONT></FONT></FONT></SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></SPAN></DIV></SPAN></DIV><!-- Converted from text/rtf format --> <P><SPAN lang=en-us><FONT face="Arial Black" color=#800080 size=2>--</FONT><FONT face=Arial size=2><B> </B></FONT><B><FONT face=Arial color=#000080 size=2>Igor Sedukhin</FONT></B><FONT face=Arial size=2></FONT> <FONT face="Arial Black" color=#c0c0c0 size=2>..</FONT><FONT face=Arial size=2> </FONT><FONT face=Arial color=#800080 size=2>(</FONT><FONT face=Arial size=2>igor.sedukhin@ca.com</FONT><FONT face=Arial color=#800080 size=2>)</FONT></SPAN> <BR><SPAN lang=en-us><FONT face="Arial Black" color=#800080 size=2>--</FONT><FONT face=Arial size=2></FONT><B> <FONT face=Arial color=#808080 size=2>(631) 342-4325</FONT></B><FONT face=Arial size=2></FONT> <FONT face="Arial Black" color=#c0c0c0 size=2>..</FONT><FONT face=Arial size=2> </FONT><FONT face=Arial color=#008080 size=2>1 CA Plaza, Islandia, NY 11788</FONT></SPAN><SPAN lang=ru></SPAN><SPAN lang=ru></SPAN> </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C39CD0.36165B12--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]