Leo Papadopoulos

Cloud9 Technologies LLC

Zeno Lee

Cloud9 Technologies LLC

Kapil Mohindra

Cloud9 Technologies LLC

Jim Miller

Cloud9 Technologies LLC

Oliver Kemmis

comitFS

Tom Schady

Greenkey Technologies

Mark Erdtmann

Tradeweb

Justin Peterson

Tradeweb

Rob Underwood

FINOS

5 min

Convene & roll call

@Leo Papadopoulos

5 min

Review WG Links

@Leo Papadopoulos

WG Home Page with meeting info:

- https://finosfoundation.atlassian.net/wiki/spaces/VOICE/pages/154632282/Call+Metadata+Standardization+Working+Group

Mailing Lists:

- voice@finos.org - Join here: https://groups.google.com/a/finos.org/forum/#!forum/voice - this is for all FINOS Voice Program activity.

- voice-call-metadata-standardization@finos.org - Join here: https://groups.google.com/a/finos.org/forum/#!forum/voice-call-metadata-standardization

GitHub: https://github.com/finos-voice/voice-metadata-standard

5 min

Review Charter

@Leo Papadopoulos

The group will define and agreed upon format for call metadata. This includes call details, voice recordings, and transcribed voice. The goal being that consumers can design to one interface and always be able to consume data from any voice provider.

Leo: Walked the group though the charter and explained the value prop if both vendors/producers and consumers use the same standard.
Leo: We are not defining the transport layer; our purpose is the data format (currently being done in JSON)

Leo: No questions on the charter and therefore no changes for now.

5 min

Review Initial Check-In

Zeno Lee

- Review present integrations to this standard (NICE, Verint, Redbox, etc)

- Review what is presently there and how to standardize as broadly as possible. https://github.com/finos-voice/voice-metadata-standard

5 min

Review anticipated next standard proposal

@Leo Papadopoulos

Leo: Our first standard is what C9 calls the "analytics API". The first standard was for voice recording. 

Three use cases – the data may be differ

TWO POST CALL USE CASES:

Data for the purpose of call logging. Each record include the call recording and all the call records associated with it. ← This is the first check in to GIT shown below by Zeno

Data for the purpose of call activity. Support putting call records only regardless of recording. ←  A draft will be put  out before the next meeting.

ONE REALTIME USE CASES:

• Real time call activity. These are not call records per se, but the events of a call sent out in realtime. It is expected that the data format will be similar to the above.

Zeno introduced himself and the trader API: 

Goal of this group is to make sure everyone is OK with this. 

Tom: Asked a question about a multi-way call (e.g., a conference call, a three way call). 

Leo: The specification will make it clear how multi-way calls are handled.

Tom: As we develop a spec, we need figure out

Tom: What use cases?

Tom: What data types?

Tom: Will we support whispering? 

Leo: Cloud9 to put out a specification that describes fields. Then that will be something we can collaborate on.

5 min

Agree on method of collaboration on this standard

@Leo Papadopoulos

Brainstorm with the group on how to best collaborate between meetings on this standard.

5 min

Next steps

@Leo Papadopoulos

See below and above.