1. OASIS WSDM TC Face To Face Agenda January, 2005 IBM, Boulder, CO

2. Agenda, Wendsday January 19th 9:00 Roll, Dinner Arrangements, Agenda Review, WSDM 1.0 Status, Comment reaction, errata 9:30 Tiny WSDM Demo - Heather 10:00 DMTF WS-CIM meeting results - Heather 10:30 Interop Scenario preparation - Igor 12:00 Lunch 01:00 Interop Scenario preparation - Igor 05:00 Done!

3. Agenda, Thursday January 20 9:00a Interop prep including use cases - Igor 12:00 lunch (discuss Interop logistics ) 01:00 Primer - Bryan Outline Best way to leverage scenario work Schedules for delivery 3:30p Standard operations 4:00p WSDM V2 planning – 2hrs – late Thurs afternoon WSDM 2.0 line items review ITUT – Mark Ellison Going forward Next F2F and OASIS Symposium

4. Laisons DMTF: –Utility WG – 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 – AI: pointer to requirements document for WSDM? Andrea –Interop WS-CIM – OGSA OASIS: Security TC

5. TinyWSDM Demo Motivation - Heather Demo – Barry Atkins

6. WS-CIM Meeting Report WS-CIM charter WS-CIM requirements WS-CIM WSDM Mapping WS-Management

7. Interop Scenario Preparation Managers Devices –Server – Dell –Web Service – CA –Blackberry – IBM –Printer – HP WSRF interop scenario

8. Interop Planning Internal - March External commitment (discuss once internal works) AI: Scenario development –Draft by? –Develop in Jan F2F –Extend WSDM.5 interop –Who? Igor Sedukhin?

9. Primer Review AIs –Restructure on 3 examples Incremental build up of function –Add platform section from MUWS (updated) Issues Publication Plan –After 1.0 release in 1Q05, Try to time with moving from Committee Draft to OASIS specification –Input to Primer Use interop scenario EMW presentations

10. WSDM V2 Planning Fujitsu, Standard Operations WSDM 2.0 line items review ITUT – Mark Ellison Going forward Next F2F

11. WSDM Planning Interim Draft? V2 Document deliverables –Primer –Profiles?

12. MUWS Publication Planning AIs and Issues Schedule? OASIS Process

13. MOWS Publication Planning AIs –Managing per operation Issues MUWS Dependencies Schedule

14. V2 Items starter list Standard versions of WS-RF and WS-N Use cases, Profiles from Utility WG Security Questions Progressing Event format Normative description of Name and Identity (Heather), proposed Operable Collections Hibernated Relationship Issues Relationships and Service Group alignment

15. V2 Starter Items Policy based mgmt Resource Type Post Condition Change Management Progressing MetaData proposals in MUWS

16. Hibernated Relationship 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 manageable relationships of this type – Service group w/ relationship markup and all relatoinships with eprs. Create a relationship for MR w/ relationship registry for it? Constrain relationship with interface requirements Directionality Queries Complex Capabilities

17. F2F Planning March? – Internal Interop –WSDM V2 work

18. WSDM Requirement to WS-RF Finding the EPR of a WS-Resource from WSDL (Submitted) Current proposed wording:

19. WSDM Requirement to WS-N Requirement on WS-N to define a content filter on the returned event (only subset of information in message). (Submitted) Raise Issue to WS-Notification TC; Currently subscribers set one message for every topic that a message is published to that they subscribe to. For scaleability subscribers should get 1 message even if subscribe on multiple topics. Raise issue to WS-Notification TC: Notify only allows one topic per message, so have to publish a message/topic pair, so if need to publish on 3 topics, send 3 messages. Can’t publish one message & n topics in one message and we need to