FIBO Business Entities / Documentation coverage

GraphArch Documentation Preview

Documentation coverage

GraphArch Documentation Preview

A. Documentation coverage§

48 ontologies; 942 documented named resources. 34 resources have no English source definition.

Missing annotations are shown explicitly and recorded as KG diagnostics. No inferred definitions or external imports are added.

OntologyResourcesMissing definitions
All Business Entities (BE) Domain00
Corporations Ontology1111
Metadata about the EDMC-FIBO Business Entities (BE) Corporations Module11
Functional Entities Ontology120
Metadata about the EDMC-FIBO Business Entities (BE) Functional Entities Module11
Publishers Ontology140
Canadian Government Entities and Jurisdictions Ontology420
Central Asia Government Entities and Jurisdictions Ontology150
Caribbean Government Entities and Jurisdictions Ontology450
Central American Government Entities and Jurisdictions Ontology210
Eastern Asia Government Entities and Jurisdictions Ontology240
Eastern Europe Government Entities and Jurisdictions Ontology300
European Government Entities and Jurisdictions Ontology80
Government Entities Ontology320
Metadata about the EDMC-FIBO Business Entities (BE) Government Entities Module11
Mexican Government Entities and Jurisdictions Ontology30
Northern Europe Government Entities and Jurisdictions Ontology300
South American Government Entities and Jurisdictions Ontology360
Southern Asia Government Entities and Jurisdictions Ontology270
Southeastern Asia Government Entities and Jurisdictions Ontology330
Southern Europe Government Entities and Jurisdictions Ontology450
Government Entities and Jurisdictions for the United Kingdom of Great Britain and Northern Ireland Ontology210
US Government Entities and Jurisdictions Ontology1710
Western Asia Government Entities and Jurisdictions Ontology540
Western Europe Government Entities and Jurisdictions Ontology270
Corporate Bodies Ontology210
Formal Business Organizations Ontology110
Legal Entity Identifier (LEI) Entities Ontology330
Legal Persons Ontology130
Metadata about the EDMC-FIBO Business Entities (BE) Legal Entities Module11
Metadata about the FIBO Business Entities (BE) Domain11
Corporate Control Ontology210
Corporate Ownership Ontology90
Control Parties Ontology220
Executives Ontology4813
Metadata about the EDMC-FIBO Business Entities (BE) Ownership and Control Module11
Ownership Parties Ontology170
Metadata about the EDMC-FIBO Business Entities (BE) Private Limited Companies Module11
Private Limited Companies Ontology90
Metadata about the EDMC-FIBO Business Entities (BE) Partnerships Module11
Partnerships Ontology130
Metadata about the EDMC-FIBO Business Entities (BE) Sole Proprietorships Module11
Sole Proprietorships Ontology20
Metadata about the EDMC-FIBO Business Entities (BE) Trusts Module11
Trusts Ontology120
Business Entities Domain, European Extension00
Business Entities Domain, North American Extension00
Business Entities Domain, Reference Individuals00

Quality issues

Document provenance

Diagram interpretation

Class diagrams use UML shorthand for asserted OWL facts and declared SHACL constraints, without inference or a claim that validation passed. RDF properties remain independent resources even when drawn as class members or labelled associations. Domain/range declarations alone do not impose requiredness or cardinality. A property with a declared domain and range is a labelled association from the domain to the range; a datatype property, or one without a specific range, is an attribute of its domain. Multiple domains or ranges apply conjunctively, not as alternatives: each declared domain-range pair is drawn and holds for every use of the property. An explicitly declared union domain is drawn as one source box whose class alternatives are joined by or. A dotted rdfs:Resource source box is a presentation placeholder when no specific domain is declared in the selected inputs, not an asserted domain or a claim that none can be entailed. OWL class restrictions on the documented class and on neighbouring classes use UML notation instead of expression boxes, scoped to the restricted class and never declaring a global range or count. A datatype restriction is an attribute, name : type [multiplicity]; an object restriction is an association to its filler class with the multiplicity at the target end (a neighbouring class shows it as a typed attribute instead). An unqualified count uses the declared property range. someValuesFrom gives 1..* {qualified}; allValuesFrom gives * {all values}, narrowing the value type; a qualified count counts only values in the named filler and adds {qualified}; hasValue adds {= value}. Multiplicities follow one convention: equal bounds show one number such as 1, an unconstrained range shows *, and otherwise lower..upper such as 0..1 or 1..*. A maximum or exact count of zero, in OWL or SHACL, is a prohibition rather than a multiplicity: it appears as a class constraint row after the attributes, {no p}, or {no p in C} when only values in C are excluded. A zero minimum imposes no restriction and is omitted. {redefines} marks a restriction on a property whose declared domain is an asserted superclass, redefining the inherited property of the same name. An existential with a simple zero-minimum filler still requires a value; a positive count on the same class and property already guarantees that existence. Boolean class expressions, nested restrictions, inverse properties and property chains remain explicit boxes named after their form, such as Anonymous OWL intersection 1. Types and counts from simple property shapes enrich the UML notation. Identical qualifiers are shown once; where declaring shapes disagree, the disputed type or multiplicity is omitted from the drawing and remains in the dedicated shape documentation. No shape is chosen arbitrarily and conflicting counts are not silently intersected. An absent count imposes no lower or upper bound beyond zero or unbounded, respectively. Complex constraints require the linked full shape definition. Original OWL facts and shape provenance remain in the published source graph. Some diagrams show at most five complete OWL relationship groups within an eighteen-fact budget, selected in deterministic IRI order; omitted groups remain in the published source graph. These views are not exhaustive. Names from the same ontology as the documented class are shown by label; names from another ontology add their prefixed name in parentheses, and unlabelled names show their prefixed name.

Search this specification