F.7:11 - Worked example and application sketches
Section 11.1 supplies exact source bases for one contrast row. Sections 11.2–11.5 show further applications; complete their source-local claims, relations and evidence before treating them as finished tables.
F.7:11.1 - Actor wording across BPMN and PROV
| Comparison or use | Exact entries | Relation | Boundary | Basis | Conclusion |
|---|---|---|---|---|---|
| Choose a plain-language heading for a teaching paragraph | BPMN 2.0.2 §9.3.1 Participant: a Collaboration element representing a PartnerEntity, PartnerRole, or both. PROV-O, 30 April 2013, §3.1 prov:Agent: something responsible for an activity, an entity’s existence, or another agent’s activity. | None asserted; this is a contrast row. | BPMN’s representation within a Collaboration and PROV’s responsibility meaning remain distinct. | BPMN 2.0.2 §9.3.1, p. 113; PROV-O §3.1; each term is interpreted within that cited source scheme. | Use Parties in the comparison as this paragraph’s heading, then retain the two source-specific sentences. This explanatory heading asserts no common kind, identity or substitutability. |
F.7:11.2 - Runtime occurrence comparison
| Comparison or use | Exact entries | Relation | Boundary | Basis | Conclusion |
|---|---|---|---|---|---|
| Report selected PLC task runs as provenance activities | IEC task-execution claim; PROV Activity claim | A stated source-local semantic or representation relation, direction IEC → PROV, when established for those entries | PROV omits scan-cycle and scheduling semantics | F.9 or the direct representation pattern plus evidence | Report only the covered occurrence facts; do not infer that every PROV Activity is an IEC task run. |
Performed-Work attribution remains an A.15.1 and F.6 claim about actual Work and system-role assignment. The table supplies neither.
F.7:11.3 - Measured value and target
| Comparison or use | Exact entries | Relation | Boundary | Basis | Conclusion |
|---|---|---|---|---|---|
| Judge an observed service characteristic against a target | SOSA observation and its result; ISO quantity value if used; ITIL service target | Measurement, scale, and unit relations; F.9 only for a relation between source-local meanings | Composite KPI, sampling, and unit limits | C.16, A.10, B.3, and F.12 | Compare only the named characteristic, population, and window with adequate evidence. |
F.7:11.4 - Class inclusion and FCA order
A contrast row may show OWL class inclusion, FPF U.SubkindOf, and FCA concept order together. FCA orders formal concepts by inclusion of their extents, equivalently reverse inclusion of their intents, within a selected formal context (Rudolph, Săcărea and Troancă, 2015, §2.1). That order does not by itself establish an OWL class axiom or an FPF subkind fact. A positive correspondence requires an explicit interpretation and grounds for the chosen domain and membership criteria.
F.7:11.5 - Role trigger word
Show NIST RBAC role as a permission grouping. Beside it, show the local claim that identifies a system-role kind whose members are Systems. Mark them distinct subjects. Use E.10.ROLE to recover other uses such as relation participation or signature position. Shared spelling alone gives no basis for assigning one senseFamily.