Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

13

Attendees

Goals

  • Position to progress the Orchestration Focal Point

Discussion items


 TimeItemWhoNotes
1

2

Agree prior meeting notes #001#002All
  •  AgreedApproved
25AgendaRajiv Garg
  • Review/adjust & Agree on Agenda
33CUEIan Watt
  • CUE setup for Orchestration Focal Point
  • Quick overview sent buy Rajiv to all members last week.
  • Team members to study and review.
43530Setup FP content on CUE
54520Workshop for China Forum

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

  • Presentation slides
  • Handouts
  • Flyers
655Wind-up & next conf callRajiv Garg
  • Call for team members to study collateral at item 3.
  • Agreement of schedule of 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 Capell Revise FP writeup draft for discussion in next meeting
  •  Unknown User (malik) Create Knowledgebase section for FP, post links as provided by Rajiv Garg - Done
  •  David Roff  Provide Data model - Done, link posted on knowledgebase 
  •  Unknown User (malik) Integrate Confluence with GitHub
  •  Rajiv Garg Post draft agenda for next meeting
  •  Rajiv Garg Schedule next meeting on Thursday, July 12 9PM US PT/Friday July 13 6AM Geneva/1400 Melbourne
  •   
  • Rajiv 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.