The Relay Data Classification Profiles annotate current Inferal Relay RDF schema predicates as data elements and classify likely personal data using the Inferal Data Classification ontology and DPV-PD. Each Relay source has its own profile ontology.
This is an unofficial 0.1 Editor's Draft maintained in the Inferal ontology repository.
These profiles cover the current merged Relay ontologies for Amadeus,
Hyros, Inferal Relay, Pinterest, Shopify, Triple Whale, and WooCommerce.
They do not modify generated Relay RDF. Instead, each relevant Relay
predicate is represented in the provider-specific profile namespace as
a dcls:DataElement with a dcls:dataPredicate
link back to the original term.
The profile classifies schema fields, not observed payload values. A confirmed classification means the field name and upstream description clearly identify a personal-data category. A candidate classification means the field is linkable, derived, unstructured, or context-sensitive and requires review before it is treated as asserted personal data.
Each annotation consists of a data element and a classification record. The data element names the source Relay ontology, local field path, and RDF predicate. The classification record carries a DPV-PD category, confidence, sensitivity, status, review flag, policy measures, and provenance.
Each provider profile also includes a generated
dcls:ClassificationRuleSet named
relay-pii-rule-set-v1. The rule set contains the concrete
exclusion and classification rules used by the generator. Every
generated dcls:DataClassification links to the rule branch
that produced it with dcls:classifiedByRule.
The Relay profiles expose the generator's deterministic rule branches as RDF resources for audit. Exclusion rules document fields that are intentionally suppressed, such as aggregate metrics, monetary metrics, business/product names, and generic configuration flags. Classification rules document the branches that assign DPV-PD categories, status, sensitivity, confidence, and review requirements.
Provider-specific branches are kept in the provider profile where they
apply. For example, the Pinterest profile contains separate enhanced
match rules for em, fn, ph, and
related fields, while the Inferal Relay profile contains the endpoint
metadata rule for hostname and node.
A catalog viewer can show the relevant provider profile on each Relay
ontology and as incoming references on individual Relay terms such as
shopifyprop:email or woocommerce:customerIpAddress.
A governance process can run the confirmed-fields query to seed access
controls, and the review-required query to route ambiguous identifiers,
URLs, headers, and derived status fields to a human reviewer.
Integrators should treat candidate classifications as prompts for review rather than as personal-data entailments. If a candidate is confirmed in a deployment, a local profile can add an asserted classification without editing this base profile or the Relay source RDF.
The profile ships query examples for listing confirmed personal-data fields and candidate classifications that require review.