Re: Hotel video rentals and Duty Classes

If it is part of an Agreement policy, then the commitment (to pay later) has been recorded?

R

> On 3 Jul 2024, at 22:04, Joshua Cornejo <josh@marketdata.md> wrote:
> 
> But wouldn’t that still leave the state of the Duty as “unfulfilled” (“all constraints are satisfied”) because the hotel:checkOut hasn’t happened?
>  
> IMHO (as I tried to explain during that call):
>  
> I will think that all rules in an agreement are “agreed” and there is no way around them, as such Duties are either:
> pre-fulfilled (like paying for the hotel room in advance) or
> a deferred commitment (like paying for the movies and minibar).
>  
> What I am trying to ascertain is the sequence of events for pre-fulfilled and what is the sequence of messages that an evaluator has to interact with the agents (for deferred commitment) (still hard for the implementors 😃).
>  
> Regards,
> ___________________________________
> Joshua Cornejo
> marketdata <https://www.marketdata.md/>
> embed open standards 
> across your supply chain
>  
> From: Renato Iannella <r@iannel.la <mailto:r@iannel.la>>
> Date: Wednesday 3 July 2024 at 12:53
> To: "public-odrl@w3.org <mailto:public-odrl@w3.org> Group" <public-odrl@w3.org <mailto:public-odrl@w3.org>>
> Subject: Re: Hotel video rentals and Duty Classes
> Resent-From: <public-odrl@w3.org <mailto:public-odrl@w3.org>>
> Resent-Date: Wed, 03 Jul 2024 11:53:50 +0000
>  
> It is possible to infer that “Fulfill” has temporal aspects…that is…the word may mean that the duty has been actioned/completed (eg the amount payed before playing the video).
>  
> But I think policies like the Hotel Movie rental should be very explicit and state that the compensation is due at the end of the hotel stay.
> (yes, this makes it harder for implementors!)
>  
> So, Example 22 https://www.w3.org/TR/odrl-model/#duty-perm
> could be updated with operator “eq” and rightOperand of the constraint being “hotel:checkOut” 
>  
> R
>  
> 
> 
>> On 3 Jul 2024, at 20:52, Joshua Cornejo <josh@marketdata.md> wrote:
>>  
>> During one of the conversations about Semantics a couple of months ago, I tried badly to explain this:
>>  
>> 2.6.1 Permission Class
>> A Permission allows an action, with all refinements satisfied, to be exercised on an Asset if all constraints are satisfied and if all duties are fulfilled.
>> 
>> 2.6.3 Duty Class
>> 
>>  
>> A Duty is the obligation to exercise an action, with all refinements satisfied. A Duty is fulfilled if all constraints are satisfied and if its action, with all refinements satisfied, has been exercised.
>>  
>> Use case:
>> odrl:TouristAssignee visits a hotel, sits in his room and browses the movies’ catalogue – finds Dune 2 at a rental charge of €5. He clicks “rent” and watches the movie.
>>  
>> They haven’t paid (duty fulfilment for all rentals and the mini-bar at the end of the stay), and any consequences for unfulfilled duties will trigger after this point as well.
>>  
>> Is ‘fulfil’ the right word, what about using “committed”?
>>  
>> Regards,
>>  
>> ___________________________________
>> Joshua Cornejo
>> marketdata <https://www.marketdata.md/>
>> embed open standards 
>> across your supply chain

Received on Friday, 5 July 2024 04:25:26 UTC