Date

Attendees

Goals

  • Position to progress the Orchestration Focal Point

Discussion items


TimeItemWhoNotes
1

2

Agree prior meeting notes #002All
  •  Approved
25AgendaRajiv Garg
  • Review/adjust & Agree on Agenda
330Setup FP content on CUE
420Workshop for China Forum

Prepare for 4 hour workshop at China Forum - Topic is approved by Bureau

  • Presentation slides
  • Handouts
  • Flyers
55Wind-up & next conf callRajiv Garg
  • Agreement of schedule for conf calls every 2 weeks for now. To accommodate everyone it was agreed to have them rotate at Geneva Time 10PM, 6AM and 4PM.
  • Can we have next conf call on Thursday Aug 2 - 7AM USA PT/4PM Geneva/Friday Aug 3 Midnight Melbourne - Proposed?
  • Advise all interested parties & Call for engagement and acceptance of roles

Action items for Meeting #003

  • Ian Watt, Steven CapellRajiv Garg and Everyone - 
    1. Establish dictionary of terms before the 30/7 next Bureau call
      1. Fast data
      2. Snippets
      3. API’s
      4. Restful
      5. JSON
      6. Way point
      7. State transition changes
      8. Etc.
    2. Amend the wording on the proposal for the CUE page to ensure it is clear that the ORCH FP is more about developing and sharing methodology, certainly not encroaching on projects run by PDA’s/Domains
    3. Pass comment that the proposed work by the ORCH FP has been considered v the Mandate,  Strategy and POW   - considered aligned with the Mandate & Strategy – will contribute to the revision 2019-2021 of the PoW
    4. Start to promote the 0.5 day workshop at the next forum as being about methodology, framework, and providing guidance for the consistent development of API’s regardless if related to API’s with  ERP’s  etc,  API’s G2B API’s B2B or API’s IoT2B  etc
    5. Proper tidy version of the above which will change as the framework idea progresses – but is a start.
    6. Ensure Rec-24 is studied by all on the ORCH FP.