2017-03-30 Meeting notes

Date

30 Mar 2017

Attendees

Agenda

0) EDW wrt spec.e

1) Where we are on our road map.

2) Open Action Items

3) JIRA Issues Review - https://jira.edmcouncil.org/projects/RDFKIT/issues

4) Todays content discussion.

5) For next week.

Proceedings: Collaborator and FIBO.pptx

20170330 FIBO FPT

Discuss the Elie diagram. For New content use case SME is FCT. Each FCT has an Otologist - need to give guidelines on the use of CCM. Should not distinguish between use cases. Blend the use cases using the FCT - the FCT deals with comments Elie will continue working diagram. Are we getting answers to questions regarding automation between GitHub and TWC in both directions? Jim Logan has explained relationship and MB has some diagrs. MB 4 options were shown last week with one obvious choice. Slides are available and he will send them out. MB is the CCM Ontologist.

ACTION - Jim, Elie and MB to consolidate diagrs into a single operational governance diagr for review and acceptance. MB to present to this group which each option is and have the FPT sign off. Timeline for action - MB will have something for EDW.

New topic - Domain, subdomain. DA why 45 domains we should be using the FIBO top level domains - JG agrees. MB decided to stop using module. JG should be all domains or all modules. How about business domains. MB there are places we may need to redesign the hierarchy. DA/JG Modules would be ontology structure Domains would be business structure and not necessarily one to one. DA Plugins are neither domains or modules. JG plugins could be special case of modules. DA agrees with MB that we should distinguish between Domain as a set of business problems and Module as a design / packaging feature, whether or not we then decide to make them one on one. JG does not see them as one on one. JG says these do not need to be in the Artifact ontology. Thanks MB, there are a lot of ABox things we should not store on the Artifact Onto itself.

ACTION: DA to build that out and push into GitHub. INFRA 146. There is some stuff that is generated, some is curated, some is something else. JG we can load the RSD toolkit file which is RDFtoollkit.ttl file. Then load triples that might come from different places. JG notes that DA using the AI in the root but he has moved it to somewhere different. DA that's where it is in Elie's branch which is the branch DA is using. If this is out of date as need to get EAL branch back in synch with JG branch. DA does need EAL's stuff. Will then need to diff for any conflicts and get all this in one place.

EAL when I did a pull req these conflicts appeared. Can wait for JG to suggest the architecture for these files i.e. which things are in what, then EAL can branch off the most recent Masters that JG has completed and restart rom there, since his work is mostly automated. Whereas if DA builds another thing he would rather work from the merged version. So EAL suggests that DA works off JG's branch. Then EAL can add his stuff after he finished. Not for DA to continue EAL branch.

Which one is JG branch? JG has put everything in the Master. This is on RDFKit. JG is trying to load everything into the thing. Will end up with all ontologies loaded in memory and use SPARQL-DL (with some tweaks) to manipulate a little triple store in memory. Would also start using that as a test language for testing the ontologies. DA how does this differ from ARC? ARC is actually JENA-AIQ. Pronounced "Ark". For every user story you can then have a SPARQL query to see if it still conforms to that user story.

DW: Where did we end up on Elie's diagr? There were some changes to that relating to the role of FCT, which EAL will adjust for. Also there are other parts of the process that MB discussed with the OMG crowd last week, along with additional elements for the process to be discussed with Jim about finer option choices. MB will come up with initial ideas / proposals on that process by next week. Has already uploaded the OMG deck./wiki/spaces/FPT/pages/8918526

DW: Next - what we expect to have for EDW. We still have no Welcome page. This is for initial HTML navigation. BNY were to help with that. JG will ask that person today. JG sees 2 things: 1. ontology versionIRIs - this has to be done first. JG will do this using a thing. 2. when that is done can start beautifying those pages. Also (3) TC can help with, from those, getting to the other serialization formats e.g. JSON-LD.

ACTION: DW to read and review spedc…… and send a new version to JG from this, or ask him to copy it form the wiki once it's updated.

MB will deliver process outline for the CCM side but it is ahead of this group being able to have reviewed. Will possibly extend Elie's slides, possibly Bennett OMG slides from last week (see wiki). RC: this will fulfil the purpose.

EDW next week we have an FLT next Thursday. We need to have the process hammered out. Need a decision from Mike A about how to transfer the permissions from GitHub into EDM Council.51DW did go through many INTFRA JIRA issues yesterday. Where did we get to with Single Sign-on for http://spec.edmcuoncil.org? JL we offered to have a common LDAP server for Teamwork Cloud and Collaborator, but there was a question whether both of those supports Open-ID. The answer was not yet. JG https://www.atlassian.com/software/crowd DA also when you look at the GitHub and other stuff, that's possibly not compatible with LDAP. DW: This was all 6 months ago, has anything changed? See the Atlassian Crowd product per the above link. Might the be able to use this for the EDM Council web permissions side of things as well. DA that does not solve the problem of CCM. DW there are 3 problems. Public path for all EDM Council members, for http://spec.edmcoucil.org - those working with the public side should have a happier path than needing to understand GitHub (to date, we have given GitHub access to all the EDM C members who needed access.) Will still need GitHub for those smaller percentage who would be working with GitHub. Also there is the visibility of the business content per Collaborator, which will be covered on MB new slides. We need to be aware of the range of things need to people know.

Decisions:

Action items

Jim Logan (Unlicensed) Mike Bennett Elie Abi-Lahoud (Unlicensed) to consolidate diagrs into a single operational governance diagr for review and acceptance. MB to present to this group which each option is and have the FPT sign off. Timeline for action - MB will have something for EDW.
Dennis Wisnosky read and review spedc…… and send a new version to JG from this, or ask him to copy it form the wiki once it's updated.
Dean Allemang to build that out and push into GitHub.
Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.