CMS-WS Meeting Minutes 2019-01-21

Table of Contents

Date/Time


Attendees

NameOrganisation
Leo PapadopoulosCloud9
Byne
Oliver KemmiscomitFS & Globility Ltd.

Outstanding Action Items

  • Leo Papadopoulos to look into  ODP-52 - Repository for proposed standards for FDC3 and FOS programs RESOLVED  and what FDC3 WG's are doing.
  • Leo Papadopoulos to address Rob's comments on concrete timelines.

Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call


Noted that it is a US bank holiday today. Agreed to put out notes and ask the team if they want to have an extra meeting this month.
10 minReview action items from previous meetings 


Leo Papadopoulos cleaned up repo. Delivered draft spec to be cleaned up some more and delivered this week. Comments by Vitor Espindola to also be merged in my end of this week.

Status, Questions, and Next steps

Leo Papadopoulos Spoke about merged cleaned up repo.

Leo Papadopoulos Spoke about a goal of putting out a draft specification by end of March. Then a roadmap for the rest of the year.

Vitor Espindola was confused as to whether the comments should be again the YAML or the JSON file. The answer is YAML. Leo Papadopoulos to clarify this in the readme for the project.

Leo Papadopoulos clarified questions from Vitor Espindola that there should be one specification that covers all call types. (Dialtone, DID, Shoutdown, Ringdown, Intercom, etc)

Oliver Kemmis agree to contact schema.org one more time to see if there is a better way to auto-generate documentation for the JSON spec for call metdata. Vitor Espindola also agreed to think about any suggestions he have have on this topic.

The group agreed that after this week when Leo Papadopoulos merges in Vitors PR and performs final clean up then we will begin working on incorporating ideas form other team members to work towards a specification.


5 minAOB & adjourn



Decisions Made

  • See above.

Action Items

  • Also see above


Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.