Re: constraining parties and leftOperands

Great read – a few months ago I thought about something similar to SIoTRx but concluded that it would introduce unnecessary security risks and extra latency due to the necessary parsing/etc and followed a different direction.

 

Regarding the problem described in the document around ‘accessing only during dispatch’, I would address it with polymorphism, simplifying the evaluation: 

 

ex:Prohibition1                 a odrl:Prohibition ;
                      odrl:target ex:SignedAgreement ;

                      odrl:action odrl:use ;
                 odrl:leftOperand odrl:event ;
                    odrl:operator odrl:gteq ;
                odrl:rightOperand ex:delivery ;
                terms:description "can only be evaluated until delivery"

.

ex:SignedAgreement              a odrl:Agreement, odrl:Asset ;
                 odrl:prohibition ex:Prohibition1

.

 

Regards,

 

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: Renato Iannella <r@iannel.la>
Date: Sunday 16 June 2024 at 02:00
To: "public-odrl@w3.org Group" <public-odrl@w3.org>
Subject: Re: constraining parties and leftOperands
Resent-From: <public-odrl@w3.org>
Resent-Date: Sun, 16 Jun 2024 01:00:24 +0000

 

This paper is related to the current discussion:

 

  https://ceur-ws.org/Vol-3705/paper10.pdf

 

Cheers - R