OASIS WSDM TC Face To Face Agenda

1. OASIS WSDM TC Face To Face Agenda August, 2004 BEA, San Jose, CA

2. Agenda, Monday August 16th Afternoon Session 12:00pm – 01:00pm Arrivals, Lunch, Roll, Agenda adjusting, Minute taker, Laison Status DMTF: Utility WG, State WG, Interop CIM-SOAP GGF: OGSA CMM OASIS: Security TC 01:00pm - 04:00pm Relationships – Igor/William 04:00pm – 05:30pm Metadata

3. Agenda, Tuesday August 17th Morning Session • 8:30am – Relationship issues review • 9:30 - Notifications mechanism and Notification requirements from WSDM • 10:30 am - Metadata • 11am - Taxonomies • noon - lunch

4. Agenda, Tuesday August 17th Afternoon Session • 12:30 pm - MOWS Request Processing • 02:30 pm - Resurrecting Metrics and State • 03:00 Scope of relationships • 04:00 pm - Discovery - Hibernated issues • 06:00 pm - End of Day • 07:00 pm - Dinner!

5. AgendaWednesday, August 18 Morning Session 08:30 Discovery hibernated issues collections and registries 10:30 Review WS-RF requirement from WSDM - email 11:00 Scheduling • State – Karl/Nick Drive subteam meetings • Metrics – Richard to lead subteam meetings • Base event format – Heather to set up subteam meetings • Action Items – HK to publish to email/next call • Next F2F – oct (Rf/rn 26-29/ca), (19-20/boston), WSDM- 20-22 • Next Interop – • Spec levels for platforms – Nov (w/ Spec) • Scenario – end year • Ongoing external endpoints w/ virtual interops? • Internal Date – 1.0 Mid Feb • External Date – March? • Gartner – do 0.5 spec? No. Can we talk there and get some visibility w/o demo? • Ongoing document of interactions that should be testable and should work – Mike Clements? • Specifications – committee draft due end November • Subteams – call for membership on email, Separate calls 12:30 Done for lunch and travel to GGF site

6. Discovery issues/resolution • ?Disc01 – epr-wsdl: accepted by RF; interim sol’n for 1.0?: wsdlLocation type uri in EPR as attribute of PortType element.?alternative to ws-mdx; do we need to indicate mdx vs location; • P.Disc02 – wsdl-epr: submit req to RF – close today • P.Disc03 – getEPRs – Relationship.getRelated or aquire Service Group of • P.Disc04 – find all MEndpoints for a MResource – Relationships, new relationship type, ‘works on same resource’?, (AI: issue.to.relationships work?) P: do thru registry/SG w/ Identity content &/or correlatable names model • P.Disc05 – are MEndpoints for same resource, - Identity/Correlatable names, done • Disc06 – find capabilities of a MResource – interface/portType search, issue, wsdl1.1 loses interface/portType inheritence, follow RF solution?; Spec: AI: Open discussion on finding by capability to be closed; Primer: use of. • Disc07 – find mgmt portTypes – Is acapabilities issue; understand qname and extensions of portTypes. Dup of Disc06 • P.Disc08 – find related resources – Relationships, done, Primer • P. Disc09 – find in a MResource repository/registry: uddi: technote for mapping wsdm into uddi, find MR resource reg, find MR; You can get EPRs from registries just like you can get WSDLs. Issue: do we need standard registry/collection? • Disc10 – broadcast type discovery - drop requirement for 1.0; doesn’t preclude use of or registries use of. Closed. • Disc11 – subscribe to MResource lifecycle events – Notification provides subscribe. Need to address creation/deletion event definition. Issue: where to subscribe to create. Have cr/del on relationship as one way to see if one of those participants is new, WSRF has a destroy event. Issue: who do you subscribe to for create? If a registry in system, like SG, you could subscribe to ‘adds’. Define a create event/topic that ‘things that create things’ can/should emit. ‘creation capability’ independent of ‘factory’. Creation capability might advertise that it sends creation events and for what kinds of things. Should we do the same for Destruction capability, i.e. something that destroys things and issues events that its destroyed. ? Advertising? I found/lost something and I’m telling you vs I actually personally created/destroyed it. AI: William will write up a capability that emits create/destroy events. Primer? What out of this is normative? Is it all ‘advice’? – Bryan Murray will lead (william will help)

7. Registry/Collections • Do we define Registry/Repository note ? • Is it different from a registry? • Do we define a collection? Yes. Can we depend on Service Group. • Is a collection different from a relationship? • SG today has a ‘memberEntry’ WS-resource w/ pointer to SG and member (which looks like a relationship). • Collections offer scaleability – operate on all resources in collection • Issue which resources returned what values operations returned • collection of responses • Is this a generic ‘OperableCollection’? responseCollection = operableServiceGroup.invoke(‘stop’, parameters). • Is this model specific extensions? responseCollection = allStoppableAppsServiceGroup.stop(parameters). Relationship between one thing and a collection of things Options: 1. SG and Relationship are 2 things in 1.0 till resolved in RF in WSDM 2.0 2. Don’t use SG and use Collection relationship 3. Do something in middle, use SG as it exists but require SG to expose collection relationships to its members. Issue on Relationships – what is the relationship between service groups and relationships and is it messy When we need a collection of things, we’ll use service groups unless it fails Registry Capability in WSDM 1.0 -

8. AgendaWednesday, August 18 Afternoon Session3:00-6:00pm Joint Global Grid Forum (1) OGSA and WSDM taxonomies fit? - Start with comparison of what OGSA expects and what WSDM defines. (2) OGSA usecase/scenario - Extract EMS and data service usecase/scenario from v1 doc which utilizes WSDM as its management interface. (3) Naming: Might want to have unique identifiers that are unique across domains. - To some extent uniqueness is addressed (identity comparison). But different identities do not preclude that it is the same resource.; No rules to define unique identities; Work on data management might be relevant here (4) Operational state diagram - OGSA expects to define some state diagrams (e.g., job). Not sure how good a fit exists between OGSA and WSDM. (5) Event format - WSDM is defining common event format and Grid would also need some common event format; and we have to discuss whether requirements match. (6) Policy and Negotiation - less sure about negotiation and relationships to WS-Agreement (7) CMM and WSDM

9. GGF OGSA / WSDM F2F Joint SessionLogistics • Venue: Intel facility in Santa Clara Address: 2200, Mission College Blvd., Santa Clara, CA 95052 Directions to Intel: http://tinyurl.com/644su Meeting room is at the main lobby of the main building (RNB), next to the Intel museum. Out of BEA, (leftish) North 1st street to Montague (left) to Mission College Blvd (right). • Entrance Procedure: All visitors will need to sign-in in at a security desk, show a picture Id and obtain a visitor badge before entering the meeting room. All visitor will also be subject to bag searches during sign-in. • Dial in information: Domestic - 1-888-452-0308 International 1-484-644-0505 Pass code for both is 13729

10. Laisons • DMTF: • Utility WG – prioritizing use cases, not just server oriented, next week at f2f, this will drive profiles to tie together sets of cim classes for a use. These use cases should be valuable to us as well. AI: review use cases from Utility WG when they are ready AI: relationship between CIM Profiles and WSDM Capabilities proposal;Andrea will try to post a pointer to a overview in DMTF • State WG – state model, transition encoding; determine state based on model, research group in France w/ concrete proposal, a language alongside cim to describe semantics behind a state, how it is transitioned/determined, based on UML state work. New use cases from server management wg. AI: pointer to requirements document for WSDM? Andrea • Interop CIM-SOAP & WS-CIM – CIM-SOAP phase 3 + Server Mgt structure protocol; WMX possible proposed solution from MS, Rejustifying early decision to be WSDM based. Revisiting requirements. • GGF: • OGSA • OASIS: Security TC

11. Relationships • Specification Review • Issues Review and resolution • Dialects • Multiple Dialects • Simple query operations • Directionality • Standard relationship types? • CIM Associations? UML?

12. Relationship Issues • Scope of relationships: to non WS represented resources? To Any Resource? WS only (manageable or not)? Only manageable resources? • Do we need to allow multiple references for a participant • Do we define the relationship related interface for a participant in the participant definition • Name: Is ‘name’ metadata?, if keep it change its ‘tag’, • Identity of a relationship – is the identity the whole relationship? • Finish definition of ‘Type’ • Internationalization of ‘name’ • Rename ‘ControlEndpoint’ tag to something less prescriptive • Content of Particpant • Do we need to reference enclosure • Do we need multiple references • Dialects – (if not just manageable resources) do we do this, what are the mandatory ones? • Create a relationship for MR w/ relationship registry for it? • Queries – • Ability to get relationship data without endpoints • Ability to get EPR for a known relationship • Get relationshipByType – expand to get by relationship type and role type • Get related resources by type and role • Give me all relationships for participant (passing in EPR) • Coordinate Properties for resource relationship WS-Resource as each own properties vs. one giant property. What is the intended use • Are RelationshipControlEndpoints to be a ‘Manageable Resource’ – implementing Identity? • Can a Resource ALSO BE the relationship… can it BE MULTIPLE relationships… property collision? Action Items: Continue Relationships calls – 4 calls – 2 hrs 1-3est – Fridays, Editor: Igor

13. Hibernated Issues • Relationship type markup and declaration independent of relationship instance • Allow a resource to declare the relationships it may participate in or must be a participant in • GetRelationshipControlGroup – give me all managealbe relationships of this type – Service group w/ relationship markup and all relatoinships with eprs. • Create a relationship for MR w/ relationship registry for it?

14. Relatoinship Conclusions • Will support n-ary • Be able to represent anything uml can model • All roles in a relationship are unique • Directionality is part of metadata on a relationship • Instead of ‘supported types’ its ‘CurrentTypes’ property and then move to operation ‘are you involved in relationships of this type’ returning # of relationships of that type • Relationships between • EPRs for any WS • Identity: MUWS:Identy • Name: xsd:any Reference – wsa:endpointReference Is MUWS:identity inside of ‘name’ ‘Name’ isn’t liked by Igor Issue: value of Name tag (igor does n’t like

15. MetaData • WSDM requirements • Associate information with Properties, Operations, Notifications. • WSDM 0.5 tactical • See metrics: Schema element attribute • WSRF requirement? • Scope? • Timing? • WSDM 1.0 • What do WE do? • Add metadata content to specification – Heather/Homayoun/William/Warren/Andrea • Type • Instance • Rendering • Interim general • Interim capability specific/baked into schema • None for 1.0 • Revisit rendering decision when there’s a ws-rf metadata doc if its by Sept something • ActionItem: Heather run a few calls to add proposed metadata content thru existing MUWS capabilities • Hal: r/w – changeable, constant • Metadata models in the world for properties – cim metric models w/ metadata as input • Tom will send url of position paper when there is one in WS-RF

16. Notifications • Requirements to WS-Notification • Selecting notification technology for WSDM to be dependent on • WS-Notification – OASIS TC with messaging and mgmt industry participants • WS-Eventing – MS/partners specification • Other candidates? • AI: Requirement on WS-N to define a content filter on the returned event (only subset of information in message). • Put a note about get all data of messages performance impact, don’t do something in WSDM in the interim

17. Event Formats • CBE as a starting point? • Proposing a slightly re-factored CBE to start with • Adding CBE semantics to CIM • Continuing this work…subgroup?

18. Taxonomies • Igor’s Proposal • Issues • Forest: No sharing, no cycles • Some categories may be a graph w/o cycles (multiple inheritance) • Relationships to owl and rdf? (requires new parser) • Warren looked at OWL and RDF – probably too heavy to do this • Is this a general problem or a management problem • Like UML Stereotype • Pick one? #5 • Any alternatives/objections by next TC call (next week)

19. Request Processing State • Issues • Message content selection for events • AI: Operational state change will need a State Change Event; which OperatoinalStateChagne can extend and RequestProcessingState change can extend • AI: Investigate adding provider context in request processing notification

20. Resurrections • Metrics • Types • Groups • Meta information • Notifications • State • State model(s) • Meta information • Notifications

21. Discovery • Discovery – • Status on Disc01-Disc09 • Wrap up outstanding hibernated discovery discussions – William • Correlateable names – Igor/Andrea (Disc05) • Manageability capabilities – Heather (Disc06/Disc07) • Registries – William (Disc09)

22. WSDM Requirement to WS-RF • Finding the EPR of a WS-Resource from WSDL Current proposed wording:

23. Planning • Action Items • Pre-existing • From this meeting • Outstanding work items • What needs to be accomplished for our specification • Any new subgroups? • Specification Planning • Dates? • Next F2F Planning • When and where • Early Oct in ? Europe?

24. Action Items – Last F2F • Use cases, Profiles from Utility WG • Capabilities – HK writeup, done • Scenario – HK • Taxonomy/portTypes - Igor • CBE-CIM mapping – Andrea, done • Registry – Fred writeup, done • Conceptual model followup with WS-Addressing in IBM –Heather, done • WSDM requirements for WS-RF and WS-Notification – Warren, done • WSDM discovery requirements for WS-RF – Warren, done • Correlatable properties write up – Igor, done • Relationships – concept model – Igor, done • Security Questions – Andreas,?

25. Action Items This F2F • WS-RF requirement • WS-Notification requirement –content filter • Progressing Event format • Relationships issues resolution • Internationalization of ‘Names’ • Normative description of Name and Identity (Heather) • MetaData proposals in MUWS (hk+group)

26. Outstanding Work: MUWS and MOWS Champion, assign #calls they have to work in, scope of items (w/ some scope perhaps not in 1.0). • Finish discovery - IP • Meta information • Relationships - IP • Notifications mechanism – document decisions and how to use • Event Formats • Collections • Finishing capabilities: • Identity (version/) • State • Metrics • New Capabilities • Configuration • Correlatable Properties - IP • MOWS Request processing model -IP • MOWS managing per operation • Security • ?Change Management