Integrate ENTITY without pretending another standard means the same thing
ENTITY's adoption layer uses explicit translation/crosswalk envelopes. Existing standards remain external standards; mappings are evidence of an intended relationship, not silent semantic identity or automatic authority.
1. Import an ODRL policy as mapped rights
mapping = StandardsAdapters.import_odrl(odrl_policy) rights = mapping["mapped_rights"]
The adapter maps supported ODRL permissions/prohibitions into explicit ENTITY-style rights rules and records silent_semantic_equivalence=false.
2. Export rights back to ODRL where useful
odrl = StandardsAdapters.export_odrl(
passport["rights"],
target_uid=object_id,
)Only mapped ALLOW/PROHIBIT semantics are exported. The translation should be reviewed in the target domain rather than assumed to preserve every legal nuance.
3. Treat external credentials as evidence
vc_evidence = StandardsAdapters.credential_evidence(verifiable_credential) did_evidence = StandardsAdapters.did_evidence(did_document)
A W3C Verifiable Credential or DID document can provide external evidence/identifier material, but the adapter explicitly states that the external credential/identifier is not ENTITY authority.
4. Map data-space standards explicitly
gaia = StandardsAdapters.dataspace_mapping(
"GAIA_X",
gaia_document,
policy_refs=[policy_ref],
semantic_crosswalk_refs=[crosswalk_ref],
)The same approach applies to IDS. The crosswalk records source hashes and references and preserves the distinction between the external data-space model and ENTITY's authority/right semantics.
5. Install/select an industry profile
Built-in profiles include:
| Profile | Mapped standards |
|---|---|
| Healthcare | HL7 FHIR, DICOM |
| Finance | ISO 20022, FIX, LEI |
| Manufacturing | OPC-UA, Asset Administration Shell |
| AI | NIST AI RMF, SPDX 3, CycloneDX |
| Robotics | ROS 2, Open-RMF |
| Public/unclassified defence | Public-data governance and originator-control mappings |
The profile registry carries the explicit rule technical_interoperability_not_regulatory_compliance=true. A healthcare profile does not declare HIPAA/PIPEDA compliance; a finance profile does not declare regulatory approval.
6. Bind profiles into a global passport
Use a global passport to carry the applicable profile stack, standards mappings, evidence refs, jurisdiction refs, rights passport and economic/BTDU context together. The resulting envelope remains verifiable without making the adapter or profile the authority root.
7. Qualification test
- Change a standards mapping hash and confirm verification fails.
- Attempt to set
normative_equivalence_claimed=true; the global passport path must reject it. - Confirm an external credential can be recorded as evidence without being able to mint a new ENTITY right.