Convene & roll call

Mao

1. Composition of initiative into separate work streams
2. What is object hierarchy
3. Review website pages & how data is shown

Tosha

• Helped explain structure & that it is representative of assets already defined.  
• Conceptually giving an idea, but by no means complete.  
• Reiterated this is just first pass of representing in a different way what was in the wiki.

Hammad feedback:

• Representing this way is very powerful and having the visual representation so people don’t get lost in network of data.  
• Should be intuitive and agrees early days.  
• Is there horizontal and vertical representation?  
• Sees great value and continue to think through and build out.
• For every object that gets build out, see how to add it to this visual model

Rob explained 3 discrete requirements

1. Set of macro requirement of documentation discoverability
2. Language bindings & distribute in different code sets
3. Modeling tool - how biz and product analysts would model this

Mao 

• Spirit of the demo is what Hamad describe
• Build something that allows navigation through objects, clickable, etc.
• Will change depending on how objects are structured.

Rob -

• Reminded this is very preliminary working model
• For this meeting, get feedback only on how FINOS team conceptualized to present to developers.  
• Later separate meeting around details

Gab input to group:

• What you are seeing is how to automate
• How to make available to developers
• Visual editing requirements not addressed yet
• FINOS fully aware conversations about typescript, etc.  
• But this has not been currently implemented yet which is why the source they are seeing is code

Hammad:

• Overall sight looks good, clean
• Browsing capabilities, etc. can be further explored  
• Will there be some type of interface?

Gab:

Yes, but that’s sizeable effort and having side conversations with one members who contributes full blown modeling environment which can be easily integratable with advanced editing capabilities, the framework that’s being built can be easily changed.

Rather get something already workable from a member rather than build from scratch.  

First wanted to show initial progress so decomposed the visual editing.  But also having separate conversations that is professional and ready. But that’s a bit down the line

Hammad:

Great to hear something might be available “off the shelf”

Gab:

• FINOS does have a way of editing objects right now which is the wiki.  
• Not great but currently available.
• That said, first order of biz get the 1.0 release which is baked enough and then do visual editing version in next 1.1.   
• Either the group cares about visual editing or they care about code format.  
• Right now must be either/or, can’t be both.  
• FINOS needs some kind of direction.

Hammad:

• Heading down right path.
• Accessibility of site looks good, as long as can enter content.
• Let’s not try to organize all FO, build objects up and build up rather than top down

Johan:

Since we now have basic objects ratified as standard, maybe use those to add to this website platform.  Don’t worry about what’s not available yet, use the ones that are ratified

Hammad: 

Agrees,  continue to build out and get community input.  But start with what already exists.

Johan: 

Anything in the website now that can be used for flagging.

Mao:

Use branches.  Useful, quick way to count different efforts. Also forking.  Good way to submit changes. Github suite useful to use

Gab:

• Provides context - advantage of having objects & documentation in GitHub, can then use standard pull requests.  
• Suggested w get CCLA w/ UBS so Tony is enabled.
• Website gets updated automatically when there is a release
• Master where releases are cut out of, then branches.  All contributions will go into branch and then merged into master and then new bindings will be published into website.  
• Different versions of standard can be viewed (probably drop down).
• GitHub is already an established collaboration pattern

Mao:

Technology used is the same that FDC3 is using for their website.  They have support for different API versions. Definitely doable

Gab:

expects a)there is a way to selecting version &  b) More links that can simply download so consumption is easy.  Downloadable in different code languages.

Hammad:

Haven’t been focused on codification side as of now. So Gab’s input is helpful.

Hammad Akbar