Date/Time

Wednesday, 2019-01-16, 12am ET

Attendees

Name	Organisation	Role	Present

Name	Organisation	Role
@Brian Ingenito (Unlicensed)	Morgan Stanley	Chair
@Jamie Jones	GitHub	Participant
@Diane Mueller-Klingspor	Red Hat	Participant
@Maurizio Pillitu	FINOS	Participant
@Gabriele Columbro	FINOS	Facilitator
@Rob Underwood (Deactivated)	FINOS	Facilitator
@Adam Batkin	AQR	Guest
@Espen Overbye	OpenFin	Guest
Riko Eksteen	Adaptive	Guest
Rich Linnell	JPMC	Guest
Tristan Ratchford	Wellington	Guest

Outstanding Action Items

Plan report on removing frictions, ie once a month, to this group from @Maurizio Pillitu

@Maurizio Pillitu - clear way to validate ODP activities and report back to the group

Agenda

Time	Item	Who	Notes from the Meeting

Time	Item	Who	Notes from the Meeting
5 mins	Convene & Roll Call	@Former user (Deleted)	Who is the secretary?
15 mins	Update group on FINOS priorities and resourcing after strategic offsite	@Maurizio Pillitu @Gabriele Columbro	Decisions: Reduce number of backlogs - removing frictions is part of ODP backlog Priorities: Program Support → FO and FDC3 requests for standard documentation / release process (https://finosfoundation.atlassian.net/browse/ODP-61,https://finosfoundation.atlassian.net/browse/ODP-62) Fix email → move to a different system <add issue here @Maurizio Pillitu> Fix wiki → move to Github for new programs and then define a transition plan <add issue here @Maurizio Pillitu> Ongoing: present progress this group every two weeks (sprint end)
15 mins	Review approach for FINOS recommended object library (project) definition https://finosfoundation.atlassian.net/browse/ODP-62	@Maurizio Pillitu @Adam Batkin	@Adam Batkin has provided very good input to @Maurizio Pillitu and the work required to support a standard type definition and documentation. Objective is to validate approach and make sure appropriate task and stories are added to the backlog. Mao: open conversation around JSON Schema VS ProtoBuf as language for object definition discuss protobuf extensibility; based on what implemented on proto-test, how can objects be extended? see com.factset.symbology.entity in the latest FOS proposed object definition.
10 mins	Final Scrubbing and start sprint	Group	Review ODP backlog and start sprint
10 mins	Roadmap update	Group	Who can take the action to update the roadmap for this group in 2019?
5	AOB & adjourn	Group

Notes

We heard a lot of good feedback in favour of using JSON Schema - instead of ProtoBuf - as a language to define object definitions within the FOS working group.

The language have some indisputable advantages compared to ProtoBuf, such as the flexibility, the features (inheritance, optional/mandatory fields, validations, etc), which is where the group agreed upon; however, there have been different opinions whether this tool would be "accessible" enough for business analysts.

On the downside, JSON Schema does not provide - as ProtoBuf does - a consolidate set of tools for static code and docs generation, which requires custom configuration and setup.

A couple of other interesting/recurring considerations:

ProtoBuf is conceived as a wire protocol format, which also affects the language syntax (ie properties must be numbered) and user experience
It is unclear who is leading the "JSON Schema" initiative and how it is governed (couldn't find much info on the web), though it looks healthy as open source project, though still in an incubation phase (see version 0.7)

Action Items

@Maurizio Pillitu updates the the ODP Roadmap published in the Wiki page

Open for volunteers to build a spike - similar to the one built with ProtoBuf - to present to the FOS Working Group as a solution to adopt

2019-01-16 ODP WG Meeting notes

Table of Contents