Codex Resonance
/
Codex Commons
/
🧬
CC-EXTRACT-ARQUA-01 — Commons Candidate Extraction from Recent Arqua–CR Work v0.1
/
🧪
CC-EXP-C04-01 — Mapping Qualification Envelope — Decomposition & Generality Test v0.1
/
🔎
CC-EXP-C04-02 — QMAP Prior-Art & Relation Vocabulary Reduction v0.1
🔎

CC-EXP-C04-02 — QMAP Prior-Art & Relation Vocabulary Reduction v0.1

Experiment ID: CC-EXP-C04-02

Version: 0.1

Date: 19 September 2026

Candidate: QMAP — Qualified Mapping Assertion Profile

Standing: INTERNAL — PRIOR-ART / RELATION-VOCABULARY REDUCTION. NO ADMISSION OR PUBLICATION AUTHORISED.

Question

Should QMAP define its own relation vocabulary, or qualify established relation semantics from SKOS, OWL and domain vocabularies?

Executive result

PASS WITH STRONG REDUCTION — QMAP SHOULD NOT OWN A UNIVERSAL RELATION VOCABULARY.

QMAP's contribution is the qualified mapping assertion, not proprietary relation predicates.

Reuse the strongest applicable external/domain relation semantics; use QMAP to declare purpose, provenance, scope, standing, version/lens, conflict and lifecycle around the assertion.

CC-C02 therefore changes disposition from candidate Commons relation vocabulary to relation-selection/mapping guidance within QMAP.

SKOS

SKOS already provides mapping relations for concept schemes, including exact, close, broad, narrow and related matches.

Reuse when concept-scheme semantics fit.

Do not use SKOS mapping properties for arbitrary architecture/application/vendor objects merely for convenience.

OWL

OWL provides formal equivalence, identity, subsumption and other logical semantics.

OWL identity/equivalence is much stronger than business “alignment”.

Do not translate ALIGNS_WITH into formal equivalence without semantic justification.

PROV-O

Reuse for mapping assertion provenance, derivation, attribution, generation/use and revision.

QMAP does not need a provenance ontology.

Metadata/domain vocabularies

Reuse generic source/version/date metadata and domain-defined relationships where appropriate.

QMAP should allow:

relation_ref → external/domain predicate

rather than force a Commons predicate.

What remains for QMAP

QMAP supplies cross-domain qualifiers:

  1. why the relation is asserted — mapping purpose;
  2. who/what asserted it — provenance;
  3. applicable source/target versions/lenses;
  4. scope/applicability;
  5. acceptance/standing;
  6. evidence/rationale;
  7. conflict;
  8. effective/supersession/revalidation lifecycle.

Candidate core

Minimum

Required:

  • source_ref
  • target_ref
  • relation_ref
  • mapping_purpose
  • provenance/asserting source

Required when material:

  • source/target version/lens;
  • scope/applicability;
  • effective time.

Optional/linked:

  • evidence/rationale;
  • acceptance/standing;
  • confidence;
  • conflict;
  • supersession;
  • revalidation.

Relation-selection guidance

  1. If exact formal semantics exist, use the established formal predicate.
  2. For concept-scheme mapping, use SKOS where semantics fit.
  3. If a domain vocabulary defines the relation, use it.
  4. If no suitable predicate exists, a local relation may be used only with explicit definition, owner/version and no false equivalence.

CC-C02 disposition

Do not admit ALIGNS_WITH, MAPS_TO, SPECIALISES, REALISES, SUPPORTS, CONSUMES, PRODUCES, IMPLEMENTS, HOSTS, EXPOSES, GOVERNS, EVIDENCES, DEPENDS_ON, OVERLAPS_WITH, CONSTRAINS, CONFLICTS_WITH, SUPERSEDES as universal Commons predicates.

Keep them as candidate categories/examples for relation-selection guidance.

Hostile relation tests

  • Universal identity asserted from identifier correlation → REJECT.
  • Approximate mapping upgraded to exact → BLOCKED by Non-Promotion Rule.
  • Business support relation treated as ontology subsumption → REJECT.
  • Mapping valid only for one purpose → PASS via purpose/applicability.
  • Relation vocabulary changes → PASS via version/revalidation.
  • Local relation replaced by standard predicate → PASS via supersession/new assertion.
  • Mapping generated by inference → PASS with derivation/provenance.
  • Customer accepts mapping but Arqua does not → PASS; standings separate.
  • Framework owner publishes crosswalk → PASS; source authority ≠ customer acceptance.
  • Vendor says compatible → PASS; preserve exact claim, do not translate to conformance/equivalence.

Naming

Qualified Mapping Assertion Profile (QMAP) survives.

“Qualified” means context/provenance is explicit, not that mapping quality has been approved.

Retain as preferred working name.

Interoperability posture

QMAP should be:

  • vocabulary-agnostic;
  • relation-semantic preserving;
  • provenance-aware;
  • purpose-explicit;
  • version/lens-aware;
  • standing-preserving;
  • conflict/supersession capable.

It should not be a universal ontology, relation dictionary, reasoner, conformance engine, authority model or mapping-quality score.

RRAP relationship

RRAP qualifies the role of a representation/evidence entity.

QMAP qualifies the assertion relating source and target resources.

They compose but neither depends on the other.

Non-Promotion relationship

QMAP is a prime application:

  • relation does not promote to stronger relation;
  • public mapping does not promote to accepted mapping;
  • accepted mapping does not promote to conformance;
  • conformance does not promote to authority/admissibility.

Result

Prior-art/relation reduction: PASS.

Universal Commons relation vocabulary: REJECT.

QMAP qualified assertion profile: RETAIN.

CC-C02 standalone vocabulary: DO NOT ADVANCE.

Next

Hard-test QMAP against:

  • changing source/target identity;
  • many-to-many mappings;
  • conditional mappings;
  • temporal mappings;
  • conflicts;
  • mappings of mappings;
  • inferred mappings;
  • probabilistic/approximate mappings;
  • jurisdiction-specific mappings;
  • source-version invalidation;
  • future/nonexistent targets;
  • asymmetric mappings;
  • transformations rather than mappings.

Decision

CC-EXP-C04-02 — PRIOR-ART / RELATION REDUCTION PASS.

QMAP reuses external/domain relation semantics and owns only the qualified assertion envelope.

Linked

🧪CC-EXP-C04-03 — QMAP Semantic Stability & Hard Counterexample Test v0.1