FIBO is published in a way that allows users from financial institutions, regulators, or even research groups to download and use a variety of artifacts. But people who plan to contribute to FIBO will have to deal with the FIBO source, and will need to know how to edit it. They will also need to know their way around GitHub and understand how to carry out actions such as fork, pull request.
A FIBO Metadata specification document has been developed. This document sets out the FIBO metadata for ontologies, modules and the overall FIBO specification. Its purpose is both to serve as information for FIBO content developers and as the specification for how FIBO content can be offered to OMG with no rework in the OMG specification process.
Fibo is developed using a familiar process from software engineering, in which a product is developed using source code which is compiled into a product. In most software settings, source code is written in a programming language (e.g., java, C, or Cobol) which is compiled into executable code for the product. FIBO is developed in the same way, but the product code is not 'executable' in any normal sense of the word. In fact, the FIBO products can be published in the same language as the source (i.e., OWL), so it is easy to be confused when looking at any particular file, whether you are looking at source or product. Management of the FIBO development process follows conventional software engineering practices, so the difference between source and product is clear when you think about the process.
The FIBO sources are kept in a repository on GitHub, https://github.com/edmcouncil. As is customary with GitHub, changes to FIBO are made in a fork of the EDMC repository, and these changes are proposed to the FIBO Leadership Team through a pull request. All FIBO Content and Tools are here. Some of it is open and some is private to FIBO team members (you will need to be granted access). In either case you will need a GitHub user name to participate in the development process.
FIBO is published in two release levels - a Production level, where every model has passed serious scrutiny for consistency, completeness and documentation, and a Development level,
FIBO publications are built out of
Informative ontologies are ones that have been considered by a development team, but have been explicitly rejected. They are included in FIBO sources because they contain the target of references from Provisional ontologies, without which FIBO would fail the basic referential consistency tests. Developers should consider these for information only, to determine the detailed meaning of the things that reference them. One aim of development is to replace references to elements in Provisional ontologies to those in Provisional or Release ontologies.
Provisional ontologies were developed in the early days of FIBO, and have not undergone the complete review required to be considered Release. There is a wide range of maturity that fits into Provisional; some have barely been reviewed, others have had considerable review and are on their way to being Release.
Release models have undergone extensive unit and integration testing, and have passed the most rigorous tests for completeness, consistency and correctness.
The FIBO publications are built from sources through a process that involves re-writing URIs to match publication conventions, converting files into multiple standard formats, and triggering derivative products such as the glossary and FIBO-V.
The two FIBO publication products are built by combining models from the source maturity levels as follows:
Production is made up of the Release sources only.
Development is made up of sources from Release, Provisional and Informative levels, all combined together.
FIBO developers are working to move ontologies up the maturity ladder. Specifically, to develop Provisional ontologies to become part of the Release, and to remove reliance on Informative models so that they can be removed entirely.
Indication of Maturity Levels in FIBO sources
FIBO maturity levels are indicated on an ontology basis; that is, an ontology has a level (Informative, Provisional, Release), not a class or a property (classes and properties have the maturity level of their containing ontology). The maturity level of an ontology is indicated in the ontology file itself, with a triple in RDF, e.g.,
fibo-bp-iss-doc: fibo-fnd-utl-av:hasMaturityLevel fibo-fnd-utl-av:Provisional .
The development process could go as follows:
If you want to contribute to FIBO, you'll need to do the following things:
You only have to do steps 1-6 once; once you have begun contributing, you just repeat steps 7 and 8.
When you cloned your fork to your local repository, you chose a directory in which FIBO resides. This is your fibo installation directory. In order to use the FIBO Serialization tools you will need two files, a pre-commmit hook file and a Java application file called RDF Toolkit. These need to reside in a directory called /hooks under yor local Git working directory, called .git; the instructions below shuold be followed in order to ensure that you have the latest versions of these files in their intended locations.
Once you have installed these two files, every commit you do will re-write your RDF/OWL files in a consistent way that can be compared and merged with work done by other FIBO collaborators.
FIBO developers are accustomed to using desktop tools like Protege, TopBraid Composer, VOM, and MagicDraw/CCM. These tools include a variety of tests that experienced users rely on to determine the correctness of their models. In order to satisfy themselves that the ontologies are correct, they need to be able to test the same configuration of ontologies that will be published (i.e., Production and Development, see above).
In order to make this possible on their local machine, developers need to be able to load just the Release ontologies (from their current testbed).
Some tools (e.g., Protege and CCM) use catalog files to manage the file loading. These can also be automatically created.
reateCatalog.sh(optional, for use with Protege or CCM only)
reateAbout.sh (this can take a while)
Step 3 needs to be done again whenever you create a new file or change the base URI of a file.
Step 4 needs to be done again whenever you change the maturity level or base URI of a file, add a new file, or delete a file.
When a pull request results in a new version of FIBO in the EDMC repository, a series of publication processes are performed according to the FIBO publication policy.