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/FND/issues/FND-48?filter=allopenissues
5) Todays content discussion.
6) For next week.
Teamwork Cloud and Migration
Use of TWC versus Offline Files
Choice for some time in the near future (after the 19.0 upgrade): Whether to put future FIBO-Master as a stand-alone (offline) project file in GitHub, versus using the TWC merge facility for collaborative working.
We should also seek guidance from JL about collaborative working versus offline working
PR: If we do the GitHub route, we can save them as MDXML so that you can do textual diffs in GitHub. This MDXML saves as XMI plus the diagrams as well the XMI - is a complete rendition of the file. In contrast, MDZIP is pre-compressed.
Q: Can we then do merges, in GitHub?
PR: Probably can't do merges safely. We should not rely on that. Talk to the MD experts. Depends on how predictable the sequencing is; also the contents of a diagram may be a challenge.
do we have v19 licenses?
MB: Not clear.
PR: able to download a 19.0 license on the MD site. May be related to an existing Adaptive license so we don't know.
MB: We will find out tomorrow.
Deprecation of Legacy Content
Some of the references to eg. TimeExt are from other FND ontologies so we can address these directly in this group. PR has done a list of these. References are from AccountingExt, MathExt and InformationExt
MB: these 4 specifically are also slated for removal. There are corresponding replacement terms in other ontologies. These could all be removed as a set. So we can aim to isolate these from each other.
Cross-reference Details (from Pete)
AccountingExt only has one reference (ref to datePeriod) so these would be easy to swap out.
InformationExt has only 3 references to TimeExt, to the tense class. Easy to remove.
MathExt only has a few references to TemporalUnit, Tense and its sub classes Past / Present / Future. So these can easily be isolated.
Can we get a list of these? These can easily be identified using grep on tim-tim. So MB is happy to find these himself using grep.
FND-224 Offer and Acceptance
MB: if we were working at the conceptual level this would entail representations of temporal / lifecycle concepts. However we looked at this JIRA in the last Homework call and identified that there are simple concepts at the level described here, that can be implemented with reference to the links that PR put in the JIRA note.
PR: May just put Offer and Acceptance into the textual definition for what makes a Contract. We do not need the additional classes unless there are competency questions for them.
FND-223 Negotiation (Agreements and Contracts)
FND-223 securities are negotiated, that is the essence of the Issuance process. But in the secondary market these are sold on by one of the counterparties. The deal negotiated in that case is that of the buyer and seller of the instrument. PR points to the part of the note where he already explained this.
MB isn’t negotiation synonymous with Offer and Acceptance, which in the previous JIRA we said to add?
PR: Negotiation as intended here involves a large number of to and fro offers and counter-offers not simple offer and acceptance.
We should tighten up what we mean by negotiation. Also Agreement is more general than Contract.
MB whether or not something is negotiated is orthogonal to whether or not it is contractual, so it should be able to apply to Contact and to Agreement.
Proposal: remove the word Negotiated from the definition.
FND-211 Out of Date Currency Codes
We should not be maintaining currency codes.
MG: Original ontology approach was to model the concepts of kinds of identifier and their details (schemes etc,), not to include them. Just put in a pointer to the authoritative agency. Can be a URI.
2 possible approaches:
1. Raise an FDTF RFP for someone to submit an OWL Ontology for Currency Codes themselves.
2. Remove it from FND anyway.
- Mike Bennett contact BE about possible use cases for the Capacity related concepts.