2020-04-07 Meeting notes
- Elisa Kendall
Date
Attendees
Agenda
1) Use Case reminder
2) Where we are on our road map.
3) Open Action Items
4) JIRA Issues Review - https://jira.edmcouncil.org/projects/DER/issues/DER-10?filter=allopenissues
5) Todays content discussion.
6) For next week.
Proceedings:
Discussed the potential of a demonstration based on the current work we have been doing on interest rate swaps, as well as training based on that content.
We also discussed whether or not our architecture for representing individuals should change, and the fact that we should at least document it for users. Currently we have:
Nominals - these are typically encoded in the ontology where they are needed, such as the day count conventions
Reference Data - this includes currency codes, jurisdictions for the US and Canada (and small EU/UK jurisdictions that are incomplete), MIC codes, FpML interest rates, some of the US and Canadian regulatory agencies, etc.
Examples - these include certain business entities, their LEI data, the stocks that they issue, the DJIA basket that includes those stocks, the Mizuho interest rate swaps, etc.
And we should also have test data, possibly in the fibo/etc/testing/data directory structure, which would be data that may not be very pretty but would support regression testing, as well as a place for much broader examples, such as fully worked use cases.
No conclusion was reached, but we at least wanted to put it on the table for further discussion. We also talked about issues with scalability, since running protege and reviewing the derivatives data causes Elisa's laptop screen to lock up for a considerable amount of time while in GTM. Perhaps we are at a point where we need to use Stardog for this sort of testing rather than Protege, so David is going to reach out to Robert to discuss it. Another option would be to update TROWL to support Protege 5 and perhaps data property reasoning. Yet another option would be to see what happens with other meeting tools, such as webex or zoom. Again no conclusion was reached, but we should try some of these things and test further as time and resources permit.