voice-metadata-standard

voice-metadata-standard copied to clipboard

pinczo

System Object

1

new System Object moved audioInterface into event required changs member sUserID, pUserId

pinczo

Support call transcription

2

Add support for call transcription in the standard. Multiple formats should be supported(eg. VTT, SRT).

vitorespindola

Add example files to the repository and documentation, to clarify the usage of the standard in distinct recording types.

vitorespindola

Use JSON Schema [definitions](https://json-schema.org/understanding-json-schema/structuring.html#reuse) and [combining](https://json-schema.org/understanding-json-schema/reference/combining.html#combining) features to improve standard readability and reusability. The schema root should not allow additionalProperties and should not have properties on it. We'd define if...

vitorespindola

all IDs should be UUIDs

1

Having non-UUID ids in the examples doesn't scale as well.

tschady

Define required fields on the JSON Schema

1

We should add required fields on JSON Schema file to determined minimum required fields to be compliant with the standard. Eg. ```"required": ["fileName", "md5Checksum"] ```

vitorespindola

app specific fields should be removed

3

e.g. `buttonName` refers to the invoking application, and not the actual call metadata, and should be removed. Vendors should be able to extend the format to include optional payloads.

tschady