ohdrl

Hi Paul,

 

I had a look at your repository.

 

"ovc:leftOperand": "$.credentialSubject.gx:vatID",

 

I opened the two files you include:

 

                "gx": "https://registry.lab.gaia-x.eu/development/api/trusted-shape-registry/v1/shapes/jsonld/trustframework#"

                "ovc": "https://w3id.org/gaia-x/ovc/1/"

 

And unless the further files included do some magic behind:

 
I can’t see gx:vatID defined as a odrl:LeftOperand
gx:vatID seems to be part of “gx:ParticipantShape” which looks like it should be a odrl:Party or odrl:Asset (or both, I can’t tell from your specific example)
I would also point out that there’s a gap between the relationship of the policy and the ovc:leftOperand (I don’t see how you know that the value of the LeftOperand comes from a VC that is not mentioned anywhere in the policy, “ovc:credentialSubjectType” is not doing it if that’s the intention).
Looking at how custom, this likely needs a profile (unless ovc-1 will cover this, but it doesn’t now).
 

I would also put some verbiage around the use case, from the example, I can’t tell if you are evaluating:
“authorised to distribute” (the right use case for ODRL, authorisation) 
or 
“Is this assignee someone that can distribute” (attempting to “merge” authentication and authorisation)
 
If you are looking at the former, you probably should go with a refinement to the assignee (since the target is the document?).
If you are looking at the latter, that’s going to give the system a lot of headaches (authentication should already have happened).
 

You mentioned that your parsing took 89% of your time. Looking at “gx” (not your issue, but), It is an ontology with all the “taxonomies” inside – so if you have to download that file and process it in “one go”, it is probably serialised parsing (and not parallel if you had taxonomies as separate references). 

 

It also (for awareness):
Redefines some terms rather than “reuse and extend” from other ontologies – likely creating friction for adoption and ‘extra’ hurdles for integrations,
Seems to reference standards that are sunset (line 3598 - "GPS in ISO 6709:2008/Cor 1:2009 format.")  (https://www.iso.org/standard/39242.html) – not sure why.
 

Regards,

 

___________________________________

Joshua Cornejo

marketdata

smart authorisation management for the AI-era