Add adalbert-contracts: ODRL 2.2 profile for data governance#160
Open
matthiasautrata wants to merge 1 commit intoEKGF:developfrom
Open
Add adalbert-contracts: ODRL 2.2 profile for data governance#160matthiasautrata wants to merge 1 commit intoEKGF:developfrom
matthiasautrata wants to merge 1 commit intoEKGF:developfrom
Conversation
Contributes Adalbert as a complementary approach to dprod-contracts, using standard ODRL Permission/Duty/Prohibition types with extensions for lifecycle management, bilateral duties, recurrence, and formal evaluation semantics. Includes data-use policies (odrl:Set) for organizational access control alongside bilateral data contracts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
matthiasautrata
requested review from
FroehlichMarcel,
andrea-gioia,
jgeluk,
joshcornejo,
nvar,
rivettp and
tonyseale
as code owners
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dprod-contracts, using standard ODRL 2.2Permission,Duty, andProhibitiontypes (no custom Rule subclasses)odrl:Set) for organizational access control — role-based permissions, purpose restrictions, classification constraints — alongside bilateral data contractsdprod-contractsexamples into Adalbert syntax (examples/dprod-translated.ttl), demonstrating compatibilitydocs/DPROD-Adalbert-Comparison.md) with class/property/action mapping tablesWhat's included
adalbert-core.ttladalbert-shacl.ttladalbert-prof.ttladalbert-due.ttlexamples/data-contract.ttlexamples/data-use-policy.ttlexamples/baseline.ttlexamples/dprod-translated.ttldocs/SPECIFICATION.mddocs/SEMANTICS.mddocs/DATA-CONTRACTS.mddocs/DATA-USE-POLICIES.mddocs/DPROD-Adalbert-Comparison.mdKey architectural difference
dprod-contracts introduces
dprod:Promiseas a newodrl:Rulesubclass. Adalbert uses standardodrl:Dutyfor all obligations, distinguishing provider from consumer duties viaadalbert:subject. Every Adalbert policy is a valid ODRL 2.2 policy that any ODRL processor can partially understand.Scope note
Adalbert intentionally does not address pricing (dprod-contracts has
dprod:hasPricing). Adalbert focuses on rights, obligations, and constraints.🤖 Generated with Claude Code