2017-12-14 Meeting notes

Table of Contents

Date

Actions items

Task report

Looking good, no incomplete tasks.

Add new action items here.

Agenda

TimeItemWhoNotes
5 minConvene & roll call

10 minReview action items from previous meetings

See above

10 minCountry ObjectAll

org.symphonyoss.country [A]

20 minSecurity ObjectJohan Sandersson

org.symphonyoss.fin.security [E]

5 minAOB & adjourn
Next meeting?

Meeting notes

BS: No value in defining an entity, because you’re just… What’s useful for us to agree upon is what format we’ll use. Otherwise we’re just bloating the standard. I recommend we standardize on the 2-letter ISO code.

JS: Any objections from anyone, or should we move this up to proposed standards? Ok, I’ll take that as a yes. Ok, moving into the security object. I had suggested the possibility of including some form of name in the object so that the Symphony platform could display a hovercard that’s useful for the security. But by then having a name and country reference in the object itself, the interface could display it in a nice way, and users could decide how they wanted them displayed. Have people had a chance to think further about that? Should country be put in with the country ID type?

BS: I understand the desire to present useful information to a user without having to lookup what the identifiers actually mean, but that’s what the PresentationML is for. If I send you an object that contains the Microsoft ticker and the Symphony name, I could trick you into buying the wrong thing. I think a better approach would be to make an agreement with some provider of financial data to be able to look up some standard code. So FactSet could offer some basic level of free service, allowing Symphony to lookup the security, and get a link to buy enhanced service from the service provider. The alternative makes the object more complicated and harder to understand. At the very least, we’d need to identify the real data and the stuff that’s informational, so it’s clear that if they conflict, the latter should be discarded.

What are the use cases here? There’s one where the user has an app installed that can look up the security based on the ticker symbol. There’s another where the user has no app installed and Symphony will render the PresentationML. If you want to be able to construct a hovercard without access to market data, even if you identify something as a ticker, you can’t do anything with it.

JS: You have more information there than I do, but I haven’t seen any apps that change the presentation of just a basic security. Like if I want to, say, buy 100 AAPL, users still want to see that it’s an Apple security and send that to their news provider, etc.

BS: Yes, but if they have a charting app installed, it will be able to tell the user that AAPL is Apple, Inc. If there’s not an app, you should just display the PresentationML. The solution to the problem you’re talking about is to extend PresentationML so that you can define hovercards.

JS: Yes, that is correct. My main focus for the security object is that it will provide enough information so that any app in Symphony would be able to present the same Hovercard and with maintained data so that you can pass the object on to another application.

BS: That sounds more like something you should discuss with Platform Product Management.

JS: Fair point - i'll try to bring it up with them. Maybe we should table this discussion for now. My proposed structure is on the confluence page for people to consider - let's see if we get some further feedback or interest on the next call.

JS: On another item, I have had some offline feedback regarding the name spaces and that they are unnecessarily long. For each security id we have eg both "type:org.symphonyoss.fin.security.id.isin" and "value:AB12345678". Given the JSON schemas - would it make sense to just shorten it to "ISIN:AB123456. Unfortunately the person who suggested this is not on the call and I don't have enough technical knowledge so just throwing it out for discussion.

BS: I don't believe that to be an issue at all. 

JS: OK

JS: Time to end - please note that next meeting on the 28 Dec will be cancel due to the holidays - so see you all in the next year. Happy Holidays!

Attendees

NameOrganisationPresent?

Johan Sandersson (co-chair)

FactSetY
Hammad AkbarCiti

Afsheen Afshar

JP Morgan Chase
Matthew BastianS&P Capital IQ
Hamish BrookermanS&P Global Market Intelligence
Brett CampbellCitiY
Anjana DasuSymphony LLC
Prashant DesaiIpreo
Doug EsanbockDow Jones
Anthony FabbricinoBNY Mellon
Blackrock
Symphony LLC
Dave HunterS&P Global
Richard KleterDeutsche Bank
Nick KolbaOpenFin
Samuel KrasnikGoldman Sachs
Former user (Deleted)Deutsche Bank
BNY Mellon
S&P Capital IQ
Dow Jones
Jiten MehtaCapital
Symphony LLCY
Credit Suisse
Linus PetrenSymphony LLC
Scott PreissS&P Capital IQ
FactSet
Former user (Deleted)IHS Markit
Symphony LLCY
Peter SmulovicsMorgan StanleyY
Jeff SternbergIpreo
TradeWeb
Kevin SwansonCUSIP
Markit
Credit Suisse
Gavin WhiteTradition
HSBC
Symphony Software Foundation
Symphony Software FoundationY
Symphony Software FoundationY

Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.