| How should a requirement status stay attached to an exact clause and evaluation use? | ISO/IEC/IEEE 29148:2018, confirmed current in 2024, is a current standard reference for requirements-engineering processes and information items. It does not supply F.10’s status algebra. | Adapt. RequirementStatus targets one requirement or clause under explicit scope, conditions, window, and a direct evaluation result. Reject compliant without the clause, applicable rule, and result; neither a requirement document nor its lifecycle label proves satisfaction or waiver. | Reopen when 29148 is revised or a stronger cross-domain requirements source changes which clause, applicability, evaluation, or result distinctions must remain visible. |
| How should a standard’s edition and lifecycle standing remain distinct from approval of a method or configuration? | ISO’s international harmonized stage codes and standards-development stages are current primary ISO process references for publication, review, confirmation, revision, and withdrawal states. | Adapt only the separation between an edition and its status. StandardStatus names the exact source edition, target, scheme, window, and use. Reject the inference from a source’s publication or confirmation state to enactment, runtime satisfaction, permission, compliance, or project approval. | Reopen when ISO changes the stage model or when another governing source family used by FPF needs a materially different distinction between edition and currentness. |
| What does provenance establish, and what does it not establish about evidence standing? | W3C PROV-O (2013) is a stable Recommendation retained as provenance lineage and reference; it distinguishes entities, activities, agents, and qualified provenance relations. | Adapt the separation, not a truth claim. Recover the exact observation or result, source, provenance relation, and evidence-use relation before assigning EvidenceStatus. Reject provenance presence as target truth, corroboration, assurance, or sufficient evidence by itself. | Reopen if W3C supersedes PROV or a current evidence standard changes the provenance-to-evidence-use boundary consumed by F.10. |
| How should cross-local status words remain local rather than becoming global synonyms? | ISO 704:2022 is a current terminology standard linking objects, concepts, definitions, and designations; F.9 supplies FPF’s current relation between exact local senses. | Adapt. Recover each local value cell and use the separate interpretation rule for the receiving question; add an obtaining F.9 Bridge, bounded-use claim and current reliance only when that use needs semantic correspondence between different local-sense projections. Reject shared spelling, a family edge, or a mapping card as explanation, evaluation, substitution, or global identity. | Reopen when ISO 704 or the F.9 relation model changes the distinction between designations and concepts or the cross-local mapping used here. |
| Why are a credential or dashboard view, its status, and a relying decision different objects? | W3C Verifiable Credentials Data Model v2.0 (2025) is a current W3C Recommendation that separates issuer, subject, holder, verifier, credential, presentation, and credential-status information, and leaves authorization decisions outside the data model. | Adapt. A visible credential, register row, or dashboard cell is a cue or presentation. Recover the source assertion, target, status value, currentness, and actual receiving use separately. Reject display, verification, or credential status as permission, gate passage, assurance, system-role assignment, or relying decision. | Reopen when the VC Recommendation or its status standards change the boundaries among issuer, status information, presentation, and verifier that this example uses. |