This module binds schema-field classification review to one canonical field/use meaning and exact executed program frame. Provider revision, domain, range, parent, model and path remain visible with use purpose, direction, input policy and candidate category/sensitivity. A classification confirmation supplies no observed-payload assertion, consent or current provider-access authority.

This is the unofficial 0.1.0 module specification. Source review and executable correctness are separate standings. Full generation, runtime and publication verification are pending configured GitHub CI; this draft supplies no release, native write or client-adoption qualification.

Scope and intended use

This module binds schema-field classification review to one canonical field/use meaning and exact executed program frame. Provider revision, domain, range, parent, model and path remain visible with use purpose, direction, input policy and candidate category/sensitivity. A classification confirmation supplies no observed-payload assertion, consent or current provider-access authority.

Agents can inspect the selected retained evidence, ask for missing scope or review, and keep unresolved answers visible. A successful inspection remains separate from permission to act on a live account.

Competency questions

  1. Which exact field/use meaning and program frame did an offer review?
  2. Which applicable registry entry and supersession lineage qualify current standing?
  3. Which historical, conflicting or unanchored offers still require review?

Namespace

https://ontology.inferal.com/modules/classification-review-context/

The prefix rc names the existing vocabulary. Term identity and the original RDF types remain stable. Shared advertising and commerce concepts supply scope; captured provider terms retain their provider-specific meaning.

Conceptual model

CurrentContext identifies canonical semantic and program digests. A version2 offer retains context, decision, target, reviewer, timestamp and explicit supersession lineage. Version 1 decisions remain historical claims. ReviewAssessment derives current standing from applicable independently anchored registry evidence. Active conflicting offers remain visible and cannot be reduced to a favorable decision.

Independent evidence axes
EvidenceWhat the consumer can conclude
Retained sourceThe selected bytes and represented claims remain inspectable.
Scoped interpretationThe named contract supplies a result with its own qualification and coverage.
Current action authorityLive permission, native applicability and client adoption require separately qualified evidence.

Current confirmation or rejection requires admission by an independently anchored approval registry. A self-refreshed local hash or reviewer name cannot update that authority. Same-field/provider/purpose supersession must be valid and acyclic. Equivalent RDF ordering, prefix spelling and formatting preserve canonical meaning; cyclic or ambiguously shared blank-node contexts and unsupported bounds leave current review unqualified.

RDF permits incomplete descriptions. A conforming execution profile must enforce its declared closed-world input and output constraints. Unknown or conflicting business evidence must keep its explicit standing and cannot be converted into a favorable value.

Validation and interpretation

Carrier and result constraints validate context, immutable offer/history and exact supersession-target digest before standing is emitted. Current reports and indexes require one coherent postpublication source frame, while prepublication custody remains separate. Saving an unanchored offer preserves history and does not confirm a field. Retained schema review leaves payload, ownership, consent and native action axes independently unassessed. Human activity, client adoption and a native sender require their own evidence.

Validation establishes conformance to a selected profile. Retained scope, reported evidence and operational success keep their separate meanings. Runtime and generation evidence for this source repair remain pending GitHub CI.

Worked example and boundary

The example retains an email-category candidate under exact semantic/program digests and NoApplicableReview standing. requiresReview remains true; category and sensitivity remain visible while consent, ownership, authorization and observed-payload standing stay Unassessed.

Inspect the declared roles and independent standings before using this evidence. Omitted source data or an unresolved qualification must remain visible. This example does not attest a live provider request or complete merchant history.

Term reference

Classes, properties and existing controlled evidence values retain their authored labels and definitions. Listing a controlled value here does not change its RDF type or grant execution authority.

rc:ApplicableConsentEvidence — ApplicableConsentEvidence
Applicable consent evidence is needed; privacy category confirmation cannot supply it.
rc:ApprovedOfferBinding — ApprovedOfferBinding
Externally anchored approval binding for exact offer and program bytes; a locally refreshed hash alone does not supply authority.
rc:CanonicalContextUnqualified — CanonicalContextUnqualified
The finite canonicalizer cannot safely bind this field context, so current confirmation/rejection remains unqualified.
rc:Confirm — Confirm
Recorded confirmation offer for the retained schema context.
rc:ConflictingReviewOffers — ConflictingReviewOffers
Active context offers conflict; no favorable matching offer is selected.
rc:ContextDriftRequiresReview — ContextDriftRequiresReview
Meaning or executed artifact context changes and the old review cannot qualify the current field.
rc:CurrentAnchoredConfirmation — CurrentAnchoredConfirmation
Applicable externally anchored confirmation of this retained schema-field context; no dispatch authority follows.
rc:CurrentAnchoredRejection — CurrentAnchoredRejection
Applicable externally anchored rejection of this retained schema-field context; no authorization or payload truth follows.
rc:CurrentContext — CurrentContext
One captured canonical schema-field meaning and program frame for this interpretation; not current upstream or runtime authorization evidence.
rc:CurrentProviderAuthorizationEvidence — CurrentProviderAuthorizationEvidence
Source-qualified current provider/account access evidence at the actual dispatch decision is needed.
rc:HistoricalReview — HistoricalReview
A retained prior review claim with its original decision and lineage; no current applicability is inferred.
rc:HistoricalUnanchoredReview — HistoricalUnanchoredReview
A prior review claim is retained without binding current field/program meaning.
rc:NoApplicableReview — NoApplicableReview
No independently approved applicable current review exists.
rc:ObservedPayloadEvidence — ObservedPayloadEvidence
Applicable observed payload evidence is needed before asserting every value contains personal data.
rc:ReferencedEntityOwnershipEvidence — ReferencedEntityOwnershipEvidence
Applicable provider/account/reference existence and ownership evidence is needed.
rc:Reject — Reject
Recorded rejection offer for the retained schema context.
rc:RetainedSchemaClassificationOnly — RetainedSchemaClassificationOnly
Retained schema-field review scope; actual observed payload and current native dispatch remain separate.
rc:ReviewAssessment — ReviewAssessment
SPARQL assessment of applicable retained schema review, preserving missing state, drift and conflicts.
rc:ReviewOffer — ReviewOffer
An immutable context-bound review offer; external approval and current applicability are separately assessed.
rc:Unassessed — Unassessed
No applicable evidence assesses this distinct payload/owner/access/consent axis.
rc:approvalMatched — approvalMatched
Whether the exact offer and program frame match the independently anchored approval registry.
rc:authorizationStanding — authorizationStanding
Current provider dispatch authorization standing, independent of privacy schema review.
rc:candidateCategory — candidateCategory
Current candidate privacy category from the retained actual detector.
rc:candidateSensitivity — candidateSensitivity
Current candidate sensitivity from the retained actual detector.
rc:canonicalContext — canonicalContext
Lossless canonical JSON of the finite current retained field interpretation; it is transport evidence and not a replacement for the executable standing queries.
rc:category — category
Schema privacy target category of this current assessment.
rc:classificationStatus — classificationStatus
Candidate, Confirmed or Rejected schema classification from the current review assessment.
rc:consentStanding — consentStanding
Consent standing, independent of schema category and source custody.
rc:context — context
Current retained field context assessed by this result.
rc:contextSupported — contextSupported
Whether this finite canonicalizer can represent the captured field meaning without ambiguous or cyclic blank structure.
rc:decision — decision
Recorded confirm or reject offer; it is not self-authenticating current approval.
rc:evidenceNeeded — evidenceNeeded
Evidence needed before extending schema review to a distinct action or applicability claim.
rc:historicalReview — historicalReview
Retained historical review claim separate from current dcls:reviewedBy provenance.
rc:offer — offer
Exact immutable review offer retained in the current assessment or history.
rc:offerDigest — offerDigest
Digest of exact immutable offer contents including context, decision, target, reviewer, timestamp and lineage.
rc:ownershipStanding — ownershipStanding
Referenced native entity/account ownership standing, independent of field or lexical identity.
rc:payloadStanding — payloadStanding
Observed payload personal-data standing, independent of a schema field classification.
rc:predicate — predicate
Exact scoped native field predicate; local-name equality across providers cannot identify the field.
rc:programDigest — programDigest
Digest of exact loaded program/query/vocabulary/shape bytes and physical executable modes.
rc:provider — provider
Provider identifier scoped to the captured source namespace and API artifact.
rc:reader — reader
Fixed read service for current context, pending review or independent action evidence.
rc:readerName — readerName
Closed ordinary read service name.
rc:requiresReview — requiresReview
Whether the retained current field still requires review.
rc:retainedRecord — retainedRecord
Lossless original review-offer or historical-record JSON retained independently of current standing.
rc:reviewedAt — reviewedAt
Original review timestamp retained without claiming present upstream truth or access.
rc:reviewedProgramDigest — reviewedProgramDigest
Exact executed artifact context reviewed by this offer.
rc:reviewedSemanticDigest — reviewedSemanticDigest
Exact semantic context reviewed by this offer.
rc:reviewerName — reviewerName
Retained reviewer identity claim, authenticated only within separately anchored evidence.
rc:scope — scope
Declared retained schema-review scope; no observed-payload or native dispatch claim follows.
rc:semanticDigest — semanticDigest
Digest of the complete canonical field meaning/use tuple, independently of exact raw artifact bytes.
rc:sensitivity — sensitivity
Schema sensitivity target of this current assessment.
rc:sourceFrameDigest — sourceFrameDigest
Digest of the full physical captured artifact frame, independent of semantic canonicalization.
rc:standing — standing
Current review applicability derived through captured SPARQL.
rc:supersedes — supersedes
Explicit immutable prior offer replaced by an approved successor, preserving historical lineage.
rc:supersedesDigest — supersedesDigest
Exact immutable digest of the targeted prior offer, retained with the supersession edge; changing either identity invalidates admission.