1) Use Case reminder.
2) Where we are on our road map.
3) Open Action Items
4 ) JIRA Issues Review
5) Todays content discussion.
6) For next week.
20160329 FIBO-BE FCT
DN - Priority for the RTF is ownership and control for Resolutions V and F, and W. W needs quality time with attys and other resources to perform commonality and variability analysis. Begin with US and UK.
EK - The challenge is that OMG needs a 1 to 1 correspondence between the issues raised and resolved on the EDMC side and the OMG side - of JIRA. Need to have a business reason for making the change. Need to add justifications into JIRA. Elisa wants to insure that the words necessary for OMG reports are actually in OMG JIRA. Not able to interpret the current code letters.
Dean understands the requirement. Dean is concerned about Green Field work. How do we deal with new concerns that are not currently documented in JIRA? EK reminds that all on the OMG side must be voted on. Once the spec exists, there is nothing Green field as far as OMG is concerned.
DN walks through FIBO-BE Resolution E that has much detail and explains that this is just a starting point for the new work. The letters are only code for the BE Team to keep on track. EK - need the JIRA resolution #'s and the chapter and verse being modified in the JIRA. The ontology and the words that describe what in the spec text was changed. The changes need to be explained in the OMG resolution language.
Bobbin agrees that we need the text done up front. DN - how to deal with the very labor intensive work required? DA action identify all Wikipedia definitions so that definitions can be reviewed and appropriate sources agreed upon. EK asks that DA run a query that identifies missing definitions.
DN - E and K are short term now priorities.
Discussion on Wikipedia definitions not being acceptable. DN - annotate Wikipedia sources saying why they were chosen. DA - find better sources. DW - action to put the definition source policy into GitHub to make it clear to all who want to use FIBO.
EK - Put jurisdictions in a separate FBC ontology. Do the same for other entities such as registration authorities.
EK asks if DA as done all of the Diffs. Yes, for E and K. DA, all of the metadata submission is right for K. Maybe for E. Can look in GitHub and see what has been done so far. Plan is to work forward on the more simple ones. In sourcetree. This is in DA fork in forward where there are Res E and Res K branches. Dean shows this from GitHub. DA says to never serialize an about file. Dean will demo automation this at April 4th FLT. This will greatly improve our process. This will put the non serialized issues behind us. EK - this is a big step up.
EK - We also don't have the ability to generate the tables. If we could do this, it would save much time. Bobbin to discuss this again with NoMagic. The Wiki has all of the changes and DA has verified that the OWL works. The spec is now only one resolution behind.
EK - build the resolution as a team. Then, show what it takes to load into VOM.
For what currently exists there is the complication of UUIDs. If we had persistent UUIDs everybody’s life would be easier. What do we want in the OWL to correspond to this. EK, if Diffs have been done for these 2, then we are not that far behind. DN - probably no net new content till maybe May.
DN - Do kick off for early adopter program and couple with face to face on SEC. EK - ok if separate meetings. Need to work on a date for this in May. Need to work out how to have FCT face to face meetings. DN agrees. WE ALL AGREE.
DN - Wrap up - E ad K are the targets. Need to think about linkage with LCC in terms of performance. Pellet issues. E is clear cut, but need to walk through all. Question on when to invite RTF people. RTF is us + Richard and Manfred. EK has just checked out the E fork and will diff now.
- Dennis Wisnosky put the definitions policy into GitHub
- Dean Allemang identify all Wikipedia definitions so that definitions can be reviewed and appropriate sources agreed upon. Run a query that identifies missing definitions.
- Dean Allemang Elisa Kendall Put jurisdictions in a separate FBC ontology. Do the same for other entities such as registration authorities.
- Bobbin Teegarden Discuss OMG documentation generation with NoMagic.