2020-08-10 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/SEC/issues/SEC-7?filter=allopenissues
5) Todays content discussion.
SMIF OWL-UML
SKOS
RDF/S
6) For next week.
Proceedings:
w.r.t. hasGracePeriod for preferred dividend - may want to move this up in the hierarchy
Do we keep track of who the custodian is for shares? Check to see if we have that with respect to portfolio or account ... need to see if we have custodial account, or some property with respect to the position as to who the custodian is. We should look at corporate actions – how custodians handle payment of dividends, etc., based on position, where do we track that information in FIBO?
w.r.t equity redemption provisions - there may be a redemption cycle in addition to a specific date on or after which you can redeem something, but there may also be a provision that says that you can only redeem it semi-annually or quarterly or something like that, some frequency to allow for managing investments... might be relevant to funds or REITs ...
For Listings - hasListingDate and hasDelistingDate should be combined date time rather than explicit date based on use cases... and hasLastTradingDateTime should be a combined date time rather than DateTime.
Remove the restriction on Listing for isProvidedBy (keep isTradedOn), isTradedOn should be a subproperty of isProvidedBy.
The restriction on mid price for the security it applies to should be moved up to security price, and possibly use appliesTo instead of refersTo.
Note that for a high price, there may be multiple times in the same day that the high occurs, so we should be able to handle that. For further analysis, someone would need to look at the 'tape' of how the price moved during the day, the time series of what happened during the day, via the pattern of trades.
The use case Pete is looking at is for a given stock on a given exchange, to display the summary details including high, low, open, close, which would be extracted from the broader series. So we may want to be able to have a 'daily snapshot', to track just the summary details, per day, rather than tracking the individual trade details. We may need a separate, more specific collection for that, rather than the collection of security prices.
For tracking prices on an exchange, may also need some other structure to show how prices have changed to include splits, etc. - whether it has been normalized or historical (the actual price on that date on that exchange for that share). If normalized, there may be some ratio you have to apply due to mergers/splits. Yet another adjustment might have to do with normalization for CPI/inflation. We would also likely need trading volume stats, etc. That work might need to be done in another ontology or in the market data domain, rather than in the core equities module.