Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:45:03 UTC

F.6:13 - SoTA-Echoing and Source Use

Internal basis, not an external SoTA claim. A.2.1 and A.6.5 supply the declaration-local slot, domain, and participant-value discipline. A.2.5 keeps assignment state distinct from the assignment occurrence. A.6.REL supplies relation obtaining and occurrence identity. A.15.1 supplies dated Work and the actual-performer basis. F.6 uses these as its governing FPF neighbours; they do not replace comparison with external work.

Source and statusDecision for F.6What F.6 uses and does not importAffected loci and smallest source-driven revisit
Almeida, Guizzardi, Sales, and Fonseca, gUFO, 2026 preprint — current ontology comparator for this narrow questionAdapt. Use its separation of classification, relational aspects, and relation occurrences to test whether F.6 keeps a system-role kind, an assignment species, an assignment occurrence, and Work–assignment attribution distinct.Keep the distinctions. Do not import gUFO’s category hierarchy, OWL commitments, reified-aspect design, or a direct identity between a gUFO category and an FPF kind.§§4.1–4.3 and the assignment examples. Revisit them if this source materially changes the distinctions used here or a better direct Work–assignment account preserves more of FPF’s identity and use requirements without greater practitioner burden.
W3C PROV-O, 2013 Recommendation — representation lineageAdapt as a representation contrast. Its qualified association keeps activity, agent, role, and plan separately addressable.Use the separation when checking reports and provenance. Do not treat a PROV association as an FPF assignment occurrence, its role as a system-role kind, its activity as dated Work, or a provenance record as proof that attribution obtains.§§4.2, 4.5, and §7.3. Revisit only if the qualified-association meaning used in this contrast changes materially.
OCEL 2.0 Specification, 2023 — event-log stress testAdapt as a logging stress test. Its separate events, objects, and qualified relations test whether an exported log can preserve the identities F.6 needs.Use the separation, not the log’s identities as the world-side ontology. An event is not thereby FPF Work, a qualifier is not thereby an assignment or system-role kind, and a row does not establish that attribution obtains.§§4.2, 7.2, and 7.3. Revisit only if the event/object/qualified-relation structure used by this test changes materially.

The comparison is qualified on 2026-08-15 for this question and these source editions. gUFO is the current comparator because it directly addresses the classification–relational-aspect–occurrence separation at issue; PROV-O and OCEL answer narrower representation and logging questions and therefore serve as lineage and stress tests. A new edition number, publication status, or harmless wording change does not reopen the comparison. A material change to a distinction used above, or a competitor that offers a better direct Work–assignment attribution solution with at least the same exactness, readability, and use cost, reopens only the affected row and F.6 loci.

Refresh by meaning, not by publication. If A.2.1 or A.6.5 changes how an assignment species declares slot domains or how an occurrence supplies participant values, revisit §§4.3, 5, 7.1, and 9. If A.6.REL changes relation obtaining or occurrence identity, revisit §§4.1–4.2, 5, 7, and 9. If A.15.1 changes the actual-performer or covering-assignment basis, revisit §§4.4–4.6, 7, and 9. If a better direct Work–assignment solution changes the source decision, revisit §13 and only the solution or examples that depend on it. Wording or publication changes that leave these meanings intact require no refresh.