E.24.UK:4.4 - Source Ontology Conversion Guide
Use this short conversion guide when a source ontology, schema, standard, class hierarchy, or top-level ontology uses words such as type, class, category, object type, entity type, kind, or subtype. BFO-style, ISO-style, OWL/RDF, database-schema, programming-language, and discipline-local type systems are source ontologies or representation regimes; they do not become FPF U.* names by translation.
First recover the source construct by value:
- source name and source ontology or schema;
- source identity rule, membership rule, extent rule, or recognition rule;
- source relations such as is-a, part-of, realizes, participates-in, depends-on, or equivalent local relations;
- intended source use: classification, query, modeling, exchange, validation, reasoning, implementation, or documentation.
Then select the FPF object:
| Source construct use | FPF recovery |
|---|---|
| claim quantification, membership, extent, subkind, kind bridge, or bounded local classification | C.3 U.Kind, C.3.1 U.SubkindOf, and typed-reasoning rules; record local-kind only through one exact current C.3.2 declaration referenced by LocalKindDeclarationRef |
| public durable FPF kind needed across patterns | use E.24.UK with the shared E.24:4.0a decision; admit the kind on its direct membership/identity grounds and record whether a needed ontic is reused, both new outputs are independently needed, or direct rules suffice without an additional durable ontic |
| a reusable coordination of one primary governed subject kind, its identity rule, minimal independently governed relation set, optional identity-bearing direct relation selected by the exact subject predicate and occurrence-identity rule, declarations actually reused, and dependent-use reliance | use the E.24:4.0a ontic settlement; do not invent a universal core relation or a relation whose participants are kinds, patterns, declarations, or the ontic |
| imported formal symbol or declared range in a signature or mechanism | A.6 U.Signature identified by <content, EntityOfConcernRef, effectiveReferenceScheme> with direct SubjectKind and RangedValueKind declarations, a symbol bound by that signature, a Concept-Set row, or an admitted durable U-kind |
| source-name alignment between exact F.17 cells | F.9 Bridge, F.17 term row, F.18 naming, and explicit loss notes |
| quoted source construct with no current FPF classificatory, ontic, naming-alignment, or implementation use | retain source wording with its exact local sense and quote-only or reduced-use boundary under E.10 and E.10.ARCH |
| implementation or serialization category | representation, publication form, record field, schema field, or direct implementation artifact handled under the rule that defines or tests its use |
A source “type” may become an FPF kind and may require an ontic, but only after these tests. If the source construct only supplies local classification or exchange syntax, keep it as C.3 typed reasoning, bridge material, representation material, or source wording. Do not create a rival FPF type layer beside durable U-kind governance and E.24 ontic settlement.