[Odrl-version2] Durations

[Myles, Stuart]

Hi Renato,

 

Ø  For clarification - what is the difference then between meteredTime and elapsedTime?

Ø   

Ø  EG, a meteredTime of P5H allows the video to be played for a total of 5 hours (at any time, with unlimited stopping and starting...)

 

The elapsedTime concept is to express a period of time during which it is OK to perform the action.  In the case of the video on the website, it means that the website is permitted to play the video for - say - 24 hours.  But there is not a limit on how often the video can be played or for how long (at least, not implied by the elapsedTime value).  It also means that, once the elapsed time is up, the permission cannot be exercised (i.e. even if no one watched the video in that elapsed time period, then the permission is no longer in place).

 

The other way to express this type of concept, of course, would be to instead specify a precise start and stop time.  This would be an option.  It would require us to decide whether to account for any delay between publishing the asset and the associated rights.  Or to simply calculate "now" + 24 hours and just deprive the recipient of whatever the time it takes from when we calculate "now" and when they receive the asset.  Specifying the duration via elapsedTime would push that calculation to the recipient and would therefore allow for a more flexible definition of elapsedTime:  you are allowed to exercise the permission (display the video) for up to 24 hours from when you start.

 

Regards,

Stuart

 

P.S.  Welcome back Renato!

 

 

 

From: odrl-version2-bounces at odrl.net [mailto:odrl-version2-bounces at odrl.net] On Behalf Of ri at odrl.net
Sent: Tuesday, February 01, 2011 7:33 AM
To: ODRL-Version2
Subject: Re: [Odrl-version2] Durations

 

 

On 11 Jan 2011, at 05:09, Francis Cave wrote:





Sometimes the duration of a permission is constrained not by specific start and end dates/times, but by a fixed period from whatever time the action is initiated. This could apply, for example, to playing a video: it may be played (any number of times) for a specific period from whenever the user first starts playing it. It therefore makes sense to have a constraint term that is distinct from both 'meteredTime' (the cumulative usage time) and 'timeInterval' (a recurring period of usage). Would 'elapsedTime' be appropriate? We are considering adding this to the ACAP profile, but it might make sense to add it to the Common Vocabulary.

 

For clarification - what is the difference then between meteredTime and elapsedTime?

 

EG, a meteredTime of P5H allows the video to be played for a total of 5 hours (at any time, with unlimited stopping and starting...)

 

Cheers

 

Renato Iannella

ODRL Initiative

http://odrl.net





 



The information contained in this communication is intended for the use
of the designated recipients named above. If the reader of this 
communication is not the intended recipient, you are hereby notified
that you have received this communication in error, and that any review,
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please 
notify The Associated Press immediately by telephone at +1-212-621-1898 
and delete this e-mail. Thank you.
[IP_US_DISC]
msk dccc60c6d2c3a6438f0cf467d9a4938
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://odrl.net/pipermail/odrl-version2_odrl.net/attachments/20110201/6c1e8eba/attachment-0001.html>