FPF Reference

    Service and access separation pressure

    Preface node heading:service-and-access-separation-pressure:16241

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    These sources constrain the recovery of service or access wording; they do not define a service ontology for FPF.

    Source lineSeparation pressureFPF adoption, adaptation, and rejection
    S-OPL: Service Ontology Pattern Language, specification v1.7Offering, agreement, participants, and delivery are related but different modeling problems.Adopt the separation; adapt it as exits to the existing promise-content, commitment, speech-act, role-assignment, Work, evidence, and evaluation owners. Reject the imported process ontology and service ontology, participant taxonomy, and any common service-situation carrier or service bundle.
    NIST SP 800-207, Zero Trust ArchitectureRequester, resource, policy decision, and enforcement functions must remain distinguishable in an access decision.Adopt the demand to name the exact requester, requested use, resource, policy or grant, and enforcement facts; adapt grants through A.2.8.PER and performed enforcement through a system, assignment, and dated Work when those facts are current. Reject the component diagram as FPF ontology and infer neither U.Access nor AccessRelation.
    The Open Group ArchiMate 3.2 specificationService, interface or point of access, and realization system are not interchangeable.Retain as a comparison only. Distinguish a service provision, access description or Method, exact access point, and realization bearer; invoke A.1 only for a separate system-dependent claim. Reject imported ArchiMate elements and relations, source-word-induced systemhood, and addressability as a classification rule.

    Earlier public service lineage also cited ITIL 4, ISO 24617-2 speech-act practice, and SRE literature. They remain bounded examples rather than ontological governors: ITIL offer and service-level wording can cue A.2.3 or A.6.C; a communicative act is separated from its content and any enduring binding by A.2.9, A.2.3, and A.2.8; SRE interface, SLO, deployment, telemetry, and incident distinctions can help name separate claims. None licenses an always-unpack word rule, a mandatory facet family, every deontic phrase becoming a commitment, every performative phrase becoming a speech act, or actuals becoming Work and evidence automatically.

    Across these sources, FPF adopts separation pressure and adapts it to the direct-owner routes in 4.11a. It explicitly rejects U.Access, AccessRelation, a service bundle, word-induced systemhood, and blanket actuals-to-Work.

    The first table governs the general ontological moves. The second checks representability only after those moves have been selected. The service-and-access table constrains one recurring recovery branch without importing a service ontology. The physical, clinical, episteme, work, and formal cases test that the resulting method is not specialized to information systems.

    Reopen the smallest affected passage. Start with the one claim, case, exit, or source row that uses the changed fact. Reopen it when its governing pattern changes who participates, when the relation obtains, or how an occurrence is reidentified; when newer source evidence overturns or narrows the construction or reification distinction used there; or when an actual use can no longer reach the practical result or stopping boundary promised by that passage. Do not reopen the whole pattern unless the same change reaches several passages. If an exit no longer matches its owner's entry and result, stop using that exit until it is repaired.

    Last Updated: 2026-07-30 — upstream FPF commit 308edacf (github.com/ailev/FPF)