AboutFIBOProd.ttl doesn't import the new ACTUS ontologies.

[jziemer2]

The ACTUS ontologies are missing in AboutFIBOProd.ttl.

Please add imports for
ACTUSContractTerms.ttl
ACTUSTaxonomy.ttl
ACTUSTermApplicabilityMapping.ttl

[ElisaKendall]

@jziemer2 Hi Jurgen, These ontologies / vocabularies are still provisional, not yet released, which is why they are only in the development part of FIBO at the moment. We completed a PoC last month regarding mapping the ACTUS contract types and data dictionary parameters to FIBO, but it's still quite early and very partial. The idea is that we will continue the work this quarter, and will release the pieces that are most stable at the end of the quarter into production. That may still not include all of the applicability rules or mappings, but likely the taxonomy and contract terms (which currently is missing a number of additional controlled vocabularies for valid values). I'm delighted you noticed that they are there, though!

[jziemer2]

Hi @ElisaKendall ,
Thanks for your prompt response.

The ACTUS ontologies are in the FIBO PROD, Turtle download on the EDMC website:
https://spec.edmcouncil.org/fibo/ontology/master/2026Q1/prod.ttl.zip
Directory of D:\Downloads\prod.ttl\fibo\ontology\master\2026Q1\ACTUS
2026-04-23 16:27

..
2026-04-23 16:27 124,808 ACTUSContractTerms.ttl
2026-04-23 16:27 55,465 ACTUSTaxonomy.ttl
2026-04-23 16:27 15,457 ACTUSTermApplicabilityMapping.ttl
2026-04-23 16:27 73,696 catalog-v001.xml
2026-04-23 16:27 6,565 MetadataACTUS.ttl

The quarterly FIBO Data Model (FIB-DM) release derives from FIBO production. The transformation processes all ontologies in the "official" zip file above. It already generated ACTUS entities and relationships.

Can you advise?
a) Use the ACTUS ontologies if the next release is likely only to add to the Taxonomy and Contract terms (unlikely to rename or delete classes and object properties).
b) Remove the ACTUS ontologies. Start over.

Ontologists at FIs using FIBO Prod may have the same confusion.

Thanks and regards
Jurgen

[ElisaKendall]

@jziemer2 Hmmm ... ok. Here is what I would suggest:

1. The Taxonomy and ContractTerms are in decent shape. They will both be extended, but the content that is there now is "close" to where we will land once they are finalized. We haven't changed the Taxonomy very much, for example, since late last year. ContractTerms is newer but is mainly a set of controlled vocabularies that will be augmented with more content over the coming weeks. You can safely use those two. They will be released in the next release.

2. The content in the current applicability ontology is quite volatile, and likely to be moved around, and will take experimentation to work through the gremlins. It's simply something we pulled together for the ACTUS challenge. Don't use that one, which is I think what you were guessing.

Apologies for the confusion -- we will be making more changes with respect to structure to make things clearer this quarter, such as moving all examples into a separate 'EXMP' folder, but with structure showing which domain areas they belong to. There may be a few other changes like that with respect to reference data vs. nominals as well, but not sure it will get in until sometime over the summer / fall. Still discussing that.

Hope that helps,

Elisa

[ElisaKendall]

@jziemer2 I agree that these files appear in the production zip files. They are not included in the about files which determine the contents of the zip files, however, so something is amiss with our publication process. I'll ping Witek to take a look.

But my suggestion, above, holds - you could use the Taxonomy and ContractTerms, though we will be extending both. But I would not use the mapping file since that one will change substantially.

[jziemer2]

Thank you, Elisa.
I already added the missing includes and transformed the FIBO - all set.