FIBO Build and Publish Process Dennis E. Wisnosky Senior Consultant, EDM Council Founder, Wizdom Systems, Inc. CTO-CA (ret), DoD Business Mission Area Tools Pathologist

FIBO Tools Path FIBO is tools agnostic Tools based on standards Read/write W3 OWL – Machine Readable Read/Write OMG SIMF (not yet a standard) ‘UML’ People readable The 4 Products FIBO-V RDF/S SKOS FIBO.Schema.org FIBO-NL

FIBO Core SIMF Diagrams FIBO Tools Path FIBO Published Spec.edmcouncil.org/FIBO/ GitHub FIBO SoR Repo OMG/SIMF Based Visualization Tools and W3C/OWL tools Detailed FIBO Axioms FIBO Core OWL Ontologies FIBO Core SIMF Diagrams Content Management Automation (GitHub/Jenkins-JIRA)

SIMF for FIBO - semantic mediation We need to understand What are the common concepts How do the various information syntaxes represent those concepts What are the rules for translating between them in various context Information Syntax Represents Common Concepts Information Syntax Represents Represents Information Syntax Ontology(<http://example.com/SIMF/LegalCapacities> Import(<http://example.com/SIMF/Agents#>) Import(<http://example.com/SIMF/Relations#>) >) ) UML Model OWL Model Mapping Rules Information Model

SIMF Status in OMG Usable NOW Needed as a foundation for both threat/risk and FIBO, which also provide examples of use Focused on the requirements demonstrated by these initiatives Submission in September included: Formalization of the kernel More Robust OWL mapping Refinement of terminology Mapping prototype Better support for OntoUML

FIBO Vocabulary RDF/S SKOS Red FIBO’s are all in compliant OWL in a ‘Baby Pink’ Repo. Pink FIBO’s are in the testing/validating process and will be published by EDMC as all in sync with the SoR. The OMG process documents and approves EDMC FIBO’s through yellow and green. 2016 and beyond FIBO Developments FIBO OWL FIBO SIMF FIBO.Schema.org FIBO NL Glossary FIBO Vocabulary RDF/S SKOS spec.edmcoucil.org/ FIBO/// EDMC GitHub FIBO SoR Repo Validate Test EDMC-OMG FIBO Spec Approving Documenting OMG Specification Process A Little More Detail!

2016 and beyond FIBO Developments FIBO in OWL and UML FIBO.Schema.org FIBO Natural Language Glossary FIBO Vocabulary RDF/S SKOS EDMC/FIBO Releases Website Feedback FIBO- OWL FIBO-SIMF property for sale o the fox river GitHub FIBO SoR Repo Published FIBO Core OWL Ontologies Published Detailed FIBO Documentation FIBO.Schema.org Aligned Generated FIBO-NL Glossary Computer Aided Generated FIBO Core SIMF Diagrams Feedback FIBO-Vocabulary RDF/S SKOS Feedback https://spec.edmcouncil.org/FIBO/ Feedback All Flavors Follow the Standard FIBO Process!

Standard FIBO Process Public Report Issues Commit messages attached to JIRA issues EDM Council JIRA JIRA Service Desk Curation HTTP Notification of Failed jobs Email Notification of Failed jobs Ontologist SME Run Serializer Notification of Failed jobs per related JIRA issue FIBO User FIBO Team Push Commit Internal Test Trigger EDM Council Jenkins Master Publish Spec.edmcouncil.org/FIBO/ Pull, Fetch zip, View report, etc. FIBO-OWL FIBO-UML FIBO-Vocabulary FIBO.Schema.org FIBO-NL Publish Trigger GitHub What changes were made in response to my issue? Results Per job Jenkins Slave 1..N RDF Store or other Vendor product Test Job? pass YES! NO! Vendors Public Current Pink is the Pink because it has been tested and verified in the RDF/OWL and UML/ODM and is the stable internal version. Baby Pink is all of the FIBO’s including refactored old Reds now integrated in a single repo with the old pinks and yellows and greens. GitHub/JIRA integration matches actions to issues

Feedback from all parties FIBO untested and tested Domains Vocabulary UML FND, FBC, IND, LCC, BE, SEC, Loans, Debt/Bonds, DER in SIMF/OWL-UML NL Glossary FIBO untested and tested Domains Published Quarterly as content is added to existing ontologies and new FIBO Domains are fleshed out and tested FND, FBC, IND, LCC, BE, SEC, Loans, Debt/Bonds, DER in SIMF/OWL-UML Schema.org GitHub FIBO- Master FND, FBC, IND, LCC, BE, SEC, Loans, Debt/Bonds, DER Vocabulary FIBO-Work in Process Developed -Tested by FIBO Content Teams daily. Maintained as the SoR in SIMF/OWL-UML. This is the beginnings of a picture that will show the process that publishes FIBO Master and FIBO Working within spec.edmcouncil.org/FIBO SIMF/OWL-UML NL Glossary Schema.org FIBO- Release Spec.edmcouncil.org

Offline FIBO Version Control System Flow Update JIRA Issue with Job Completion Info JIRA Start Create JIRA Issue and obtain Issue Key for Git Finish Git Commit with JIRA Issue Key (+optional JIRA Smart Commit) Clone Source RDF for Tag into Jenkins workspace Git Notify Jenkins of Git when Pull request occurs Tag Assemble Job Completion Info For JIRA containing Issue Key (+optional JIRA Smart Commit) RDF Source Jenkins Tag Job Pull from Git with Tag Create Named Graph in Stardog with tagged Source Tag Stardog VCS Tag Stardog Revision Coffee Mug

Subject Matter Experts Ontologists FIBO Team and Ontologists decide on comments that require FIBO modifications FCT Manager GitHub EDM Council JIRA OWL Collaborator propagates comments to EDMC Confluence Confluence CCM FIBO-Staff Create CCM Diagrams and Glossary (Magic Draw) FIBO-Team responds to review in Collaborator UML/SIMF Model Collaborator Comments Subject Matter Experts FIBO-Staff and No-Magic load this content in Collaborator FIBO-Team assigns batches of concepts for reviews SME enters review of FIBO artifact* in CCM Collaborator Collaborator notifies FIBO-Team of review FIBO Artifact: Diagram or Glossary Entry (Class or Object Property)

FIBO GitHub/Jenkins/JIRA Process 1. Gets the number of a JIRA issue. Together determine If an existing FCT can manage this issue OR there is a need for new eyes. FIBO process owner Ontologist SME JIRA 7. Jenkins adds URL to job results to corresponding issues, JIRA will then notify any subscribers 2. Ontologist commits changes with the JIRA issue number in the commit description, then pushes all commits to GitHub 3. GitHub adds each commit-description to the corresponding JIRA issue. 10. Move corresponding issues to next state (like “Released”) 8. Process Owner Presses the Release Button in Jenkins when all jobs ran successfully and all issues are resolved. GitHub Jenkins 9. Jenkins sets the version-tag (also called Release in GitHub) (optionally before or after running various release-jobs for packaging, renaming namespaces and so forth) 5. Schedule Jobs where each Job execution report “knows” which JIRA issues and which GitHub commits caused the job to be scheduled. 4. GitHub triggers Jenkins with the URL of the repository, Jenkins will then figure out which jobs refer to that URL and therefore need to be scheduled. Jenkins Executor (either on the Jenkins master itself or on any of the (vendor) slaves) 6. Write execution report back to Jenkins master and publish any artifacts.

Thank you! 13