Meeting minutes
Jo: let's kick it off, good afternoon
Admin
<jo_> https://
<discussion about chat disabled>
… there were 3 actions
Resolution: Accept minutes of last meeting
FISD Update
Ben: we're confirmed for the 24th June, I've asked John Chappell and Alistair Kerr if they were up for a panel. They said yes - pending internal approvals
… I would like to get another panelist to make it more interesting
… and we would need a vendor, exchange or data provider to make it fuller. We will kick off with an overview of the standard, by FISD we will have a draft standard and some demos. That's the state of play with FISD at the moment
… I welcome some feedback and suggestions on that.
Jo: what Ben is saying that we will have a final public draft by FISD
Ben: yes
Jo: it is a good opportunity for anyone to make a comment
Timescales
Ben: I promised foolishly my co-chair that by the time of the next meeting I would check the standard, decorate it with some examples and invite members of the community group to comment.
… because by the time of our next meeting I hope it is in a state for development, rather than spelling mistakes.
… the target is to have a document published as a draft by the next meeting. So by the time FISD we have a public draft and we can invite the community for feedback.
Mark: is this different from the ask before? Is this about what's in/out or just analysis?
Ben: this is more about analysis
… it is more about the quality of the definitions
Mark: do we want to sign chunks or let everybody find their favourite parts?
Ilya: is there a summary of changes?
Ben: there is none, I'm afraid.
… I think people might look at the areas they are most interested and look if they work.
Jo: is everyone OK to put their name against sections?
… can we choose some major sections ?
Ben: the key ones are the supplier chain metamodel
… the next is the actions
… there is a section on constrains - very narrow and technical
… I would say those are the main ones
Mark: could break the metamodel into 2
Ben: we could even be more sophisticated than that
… <explains the further subdivisions>
Jo: so, lets see where we get to and how do we get onto the review on the next call
Mark: I'll send a link to the document and hopefully we can get some volunteers to review
Action: MarkB to send out a link to the various parts for people to pick up and review
Jo: what else do we have on timescales? Anyone has any questions?
Editor Update
Jo: ok let us move on
Ben: this will be quite short, which is a good sign that we are moving near the end of the work
… <shares screen>
… < discussion about :systemProvider as a new term >
<jo_> (lengthy discussion about identifier strategy)
<jo_> (whatever we do will be better than free text)
Action: Ben and Caspar to catch up on identifiers and bring to next meeting
Ben: I wanted to cover one other issue before we finish, it is kind of a vendor issue
… I think we're missing a concept
Action: Ben to call a meeting of interested parties about identity
Ben: <goes through examples>
… put the question more widely: are people comfortable with the terms and we can cover all the scenarios in which market data is licensed and billed ? Or are there any weird models this doesn't cover?
<jo_> (no need to add any elaboration as to administrator)
Laura: this is really comprehensive, I only wonder about "licensee"
… <goes through example>
Ben: <explains his interpretation of the contract>
… and it is a sign we're coming to the end of the first iteration
AOB
Ben: Michelle alerted me that ASX has a different licensing model, if anyone on the call it would be great if we could pick it up and discuss it on the next meeting
Mark: any specific use case
Michelle: there's some interesting divergencies from standard parties when you are creating a new original work. They could be a 3rd party or internally and then you have the licensor of the new original work (an index for example) that's a new license. It is a slightly different structure, might be a good example. Whether we have enough to validate that.
Ali: yes it seems like a hybrid/cross of some of the language that covers a service facilitator and vendor, the likes of Deutsche Borse or Euronext
Ben: OK
… we can pick it up in the next meeting
<jo_> thanks to josh for scribing
<jo_> --- meeting closed