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: WSDM 10/27 Call minutes



WSDM Call minutes

1. Roll - 68%
2. Reopened attendance ballot (vote till tomorrow)
3. Namespace naming convention
        - moved to have resolveable namespaces
        - explain new naming convention for namespaces on webpage (decoupled spec version from XML/WSDM doc versions)
        - website with pointers to 'latest'
        - add back in 'WS' to names so have 'muws' and 'mows'.
        - standardize prefixes in specs
4. F2F Agenda Theme: closing spec content/issues for WSDM 1.1 and Primer
        Mon - noon - MUWS
        Tues - MUWS  am;  MOWS pm
        Wed -  Primer review
        Thurs till noon - planning
5. Metrics

1.        Proposal by Kirk Wilson to include Max/Last Request/ResponseSize metrics. [1]
a.        Should these properties be included in both service level and operation level metric capabilities? [2]
Resolution: adding service and operation level to MOWS
 
2.        Extensions to other capabilities:
a.        Proposal by KW to include the operation-level attributes introduced by Fred in the OperationMetrics capability proposal, operationName & portType, in the Request Processing state elements [3]
b.        Proposal by Dave Cox/Tony Gullotta to extend OperationalStatus to operations  (as well as State, perhaps) [4] [5]

Discussion: Dave: 2 and 3 are the same, was trying ot start the discussion on if other manageablility apply to operation level: ability to understand if an operation is available and if can block access to an operation... sort of OperationalStatus for operations (OperationOperationalStatus :-) ).  Discussed scenarios where this sort of granularity would be important. Per operation status capability should be supportable by some operations, but not required to be on all or none of the operations. Reuse Operation Status values?

        - Kirk will draft a writeup
 
3.        Proposal by DC to treat operations as manageable resources in their own right [4]
a.        This proposal has been opposed by Bryan Murray and Dave Snelling. [6]  [7]
b.        This editor’s opinion: The extensions in #2 do not require making operations manageable resources.  There would be additional model issues to handle the relationship between a web service and its associated operations that only serve to complicate the representation of a web service.
 
             Discussion: The same kinds of discussion can be had around relationships between operations.  Should we look at extending all the capabilities down the operations access. They do apply.  Do we get too much detail?  It is a lot, but you should be able to look for very specific properties, not really 'get all' all the time.  Operations are what managers work with, not so much at the service level. This bears futher investigation.

            Do we need to qualify per request state change events with what operation it was invoking. Does our infrastructure know what operation is being invoked? Will it be expensive to figure out at that time. Leave open item at this time.  

            Per operation configuration: no compelling scenarios at this time.

        Add AI's for WSDM ++
            Relationships between operations: need to investigate, but not do for 1.1.  
            More general approach for operation level management

4.        Proposal by KW to replace the word “Operation” with “Request” in the operation-level capabilities, e.g., RequestMetric capability, RequestNumberofRequests (hmm, perhaps not too good), RequestOperationalStatus (but more preferable than OperationOperationalStatus).  This would keep the vocabulary consistent with “RequestProcessingState”. [3]
                Discussion: Today, request is msg flying thru system, a directed message
                Operation is  group of msgs that has meaning to managee.
                We'll leave naming as Operation.

6. Review document changes made this week
        MUWS - Vaughn: changed namespaces, and standard namespaces, clarifications made, resource def clarifications made, working on relationship types and wsa:actions.  Need to go over part 2 metrics section for readability at F2F. On target for Nov F2F.
        MOWS - Kirk: new version this week w/ inclusion of operation metric section and will add additional metrics from today. found technical contradiction in text wrt UP state fixed.   ? eliminating complex types from WSDL for capabilities, allow cut/paste of property elements by developers. Bryan/Heather to review to see if done right.
        Primer MUWS - version 20 of MUWS ready to go w/ changes accepted from 19 and changes for moving relationships section to separate main heading and formatted text following WSDL, Kirk will post 20 today
        Primer MOWS - new version 2.0, 2 important changes, 1. incorporated editing from Mark Ellison, 2. started building appendix A containing all XML snippets in XML document form

End call

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]