Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

F.5:11 - SoTA Decision for Precise, Readable Technical Names

The bounded question is: after the object is recovered, what is the smallest naming result that stays technically precise, readable to a project reader, and explicit about morphology and reuse?

Current lineStrong contributionLimit at comparable one-name effortFPF decision and receiving locus
ISO 704:2022 and ISO 1087:2019Separate objects, concepts, definitions, and designations; make concept relations and term formation inspectable.Terminology work does not itself admit the FPF object, decide a system-role kind, make an assignment obtain, or state the direct use and publication boundaries.Adopt naming after meaning, minimal generality, and inspectable term formation in sections 4.1-4.3 and checks CC-F5-1 to CC-F5-4. Reject a preferred term or definition as object admission.
W3C Ontology-Lexica Community Group, OntoLex-Lemon, 2016 Community ReportSeparates lexical entry, written and morphological form, lexical sense, ontology reference, usage conditions, and sense relations.A full lexical graph and syntax-semantics model is excessive for one local Tech/Plain pair, and its reference relation does not establish FPF object identity or reuse authority.Adapt object-sensitive morphology and the separation of name, sense, and referent in sections 4.1-4.4. Reject mandatory full lexicon modeling; use F.18 only when durable naming needs a card.
ISO 24495-1:2023, current published plain-language standardRequires written information that intended readers can find, understand, and use; it explicitly applies to technical writing and controlled languages.Plain-language quality does not settle ontology, reference, or term identity, and a shorter familiar word can still widen the meaning.Adopt the reader-use check and, when that use needs it, one short Plain designation in section 4.2 and CC-F5-4. Reject simplification that changes the recovered value or removes a live distinction.
W3C SKOS Reference, Recommendation 2009Keeps preferred and alternative labels, notes, concepts, collections, and mapping relations distinct.It is useful lineage for labels and aliases but does not model enough morphology or decide FPF kind, assignment, Work, evidence, or publication claims.Retain as lineage for aliases and cross-local caution in rules 8-9 and CC-F5-6/CC-F5-9; do not treat a shared label or generic mapping as a Bridge or common referent.

Selected contribution. Keep the recovered meaning accessible through the designation and its direct explanation. A bare label is insufficient when the intended reader cannot recover that meaning; a full ontology lexicon may supply detail that one naming decision does not need. F.5 uses one already recovered value and a Tech designation, adding a short Plain explanation for a stated didactic need. Word form follows the kind of object, and the name’s use remains bounded by the recovered meaning.

Source-use boundary: external labels, Concept-Set rows, and citations are evidence for local meaning or common practice, not automatic Tech designations, admission decisions, or Work, result, and provenance identities. A source term becomes selected only after the exact value is admitted and the naming comparison passes; naming changes none of those objects.