Re: “Content protection” vs. “DRM” (was: Re: Letter on DRM in HTML from the Civil Society Internet Governance Caucus)

> So even before being able to encrypt the data, it would be useful to
carry with the resource (media file, text, etc.) the associated rights.
This can be useful in many contexts, broader than just encrypted media,
such as creativecommons document, ways of paying an artist through
donations, etc. etc.
>
While reading this I was thinking on the CreativeCommons example since it
would be a super-set of this rights (also including expiration date, for
example), and this "associated rights" API just as an info layer would be a
great idea, not only for web but also for stored files, so computer would
warn to the user about he is not suposed to do something but there's
nothing to prevent him to do it.

+1

Received on Tuesday, 18 June 2013 10:04:34 UTC