From 09151795671e9794acf81c5f314e99650c1da4fc Mon Sep 17 00:00:00 2001 From: arnoweiss Date: Tue, 19 Nov 2024 19:47:39 +0100 Subject: [PATCH 1/3] fix(dt): adjust policy example --- .../page_software-development-view.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md b/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md index c0329a33ba3..afa60464e0c 100644 --- a/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md +++ b/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md @@ -480,14 +480,14 @@ differences are the changed typization. `proxyPath` parameter should be set `"tr ### Usage Policies For Digital Twin Registries, Data Providers are encouraged to only extend Data Offers that make no explicit checks to -use-case frameworks (formerly known as `FrameworkAgreements`. The DTR is an Enablement Service that should only be +use-case frameworks (formerly known as `FrameworkAgreement`s). The DTR is an Enablement Service that should only be visible once to every Data Consumer in the DSP-Catalog because it is a meta-data broker for data from multiple use-cases. Registering it with a Constraint that's specific to a particular use-case would restrict it only to a small subset of the dataspace. Of course, the DTR could be registered once per use-case but that's not recommended as it bloats the catalog and requires a lot of consumer-side processing. That's why Offers for a DTR should always be extended to the dataspace using the at least two Constraints: -1. Check for an active `Membership` credential. This is agnostic to use-cases but still ensures that a Consumer's VP +1. Check for an active `DataExchangeGovernanceCredential` credential. This is agnostic to use-cases but still ensures that a Consumer's VP is valid and issued by a common trust-anchor. 2. using the DTR as a roadsign in the discovery process is legitimate but requires a set of predefined behavior which is why there's a `purpose` for the DTR. @@ -497,10 +497,7 @@ Here's an example ````json { "@context": [ - "https://www.w3.org/ns/odrl.jsonld", - { - "cx-policy": "https://w3id.org/catenax/policy/" - } + "https://www.w3.org/ns/odrl.jsonld" ], "@type": "Policy", "permission": [ @@ -509,9 +506,9 @@ Here's an example "constraint": { "and": [ { - "leftOperand": "cx-policy:Membership", + "leftOperand": "https://w3id.org/catenax/policy/Framework", "operator": "eq", - "rightOperand": "active" + "rightOperand": "DataExchangeGovernance:1.0" }, { "leftOperand": "cx-policy:UsagePurpose", From 03ff23fb9df3c8fb6014094b0c2e376f0c1b3bbc Mon Sep 17 00:00:00 2001 From: arnoweiss Date: Tue, 19 Nov 2024 19:51:09 +0100 Subject: [PATCH 2/3] chore: dependencies --- DEPENDENCIES | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DEPENDENCIES b/DEPENDENCIES index 37fe425a765..74fc085ec63 100644 --- a/DEPENDENCIES +++ b/DEPENDENCIES @@ -144,7 +144,7 @@ npm/npmjs/-/cose-base/2.2.0, MIT, approved, clearlydefined npm/npmjs/-/cosmiconfig/6.0.0, MIT, approved, clearlydefined npm/npmjs/-/cosmiconfig/7.1.0, MIT, approved, #4975 npm/npmjs/-/cross-fetch/3.1.5, MIT, approved, clearlydefined -npm/npmjs/-/cross-spawn/7.0.3, MIT, approved, clearlydefined +npm/npmjs/-/cross-spawn/7.0.3, MIT, approved, #17146 npm/npmjs/-/crypto-js/4.1.1, MIT AND BSD-2-Clause, approved, #6630 npm/npmjs/-/crypto-random-string/2.0.0, MIT, approved, clearlydefined npm/npmjs/-/css-declaration-sorter/6.3.1, ISC, approved, clearlydefined From d541523d47759c531fbc3d93214394c610e0f7ae Mon Sep 17 00:00:00 2001 From: arnoweiss Date: Wed, 20 Nov 2024 19:48:02 +0100 Subject: [PATCH 3/3] fix: use usage purpose fully qualified IRI --- .../Software Development View/page_software-development-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md b/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md index afa60464e0c..0d9b47a1798 100644 --- a/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md +++ b/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md @@ -511,7 +511,7 @@ Here's an example "rightOperand": "DataExchangeGovernance:1.0" }, { - "leftOperand": "cx-policy:UsagePurpose", + "leftOperand": "https://w3id.org/catenax/policy/UsagePurpose", "operator": "eq", "rightOperand": "cx.core.digitalTwinRegistry:1" }