Edit comment LC-2988 for ODRL Community Group

Quick access to LC-2988

Comment LC-2988

Comment Shortname:

Commenter: Michael Steidl (IPTC) <mdirector@iptc.org>

Message-id:

Section of the document concerned:

[Free text description]Document as a whole1. Overview 2. ODRL Common Vocabulary 2.1 Policy Types 2.2 Actions 2.2.1 Actions for Permission or Prohibition aggregate BT: use annotate BT: use anonymize BT: use appendTo BT: writeTo archive BT: use concurrentUse BT: use derive BT: use digitize BT: use display BT: present distribute BT: use execute BT: use extract BT: reproduce give BT: transfer grantUse BT: use index BT: use install BT: use move BT: use play BT: present present BT: use print BT: present read BT: use reproduce BT: use sell BT: transfer textToSpeech BT: present transfer transform BT: use translate BT: use use writeTo BT: use 2.2.2 Actions for Duty acceptTracking attribute compensate delete ensureExclusivity include inform nextPolicy obtainConsent reviewPolicy uninstall watermark 2.3 Constraints 2.3.1 Names for Constraint 2.3.2 Operators for Constraints 2.4 Role of a Party 2.4.1 Functions of the Role of a Party 2.4.2 Scopes of the Role of a Party 2.5 Relation of an Asset Change History Acknowledgements References
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Abdel-Rahman, Hassan Ai, Lu Arnab, Alapan Becker, Stefan Beynet, Yannick Birmingham, James Cave, Francis Chaney, Dennis CHOUKRI, Khalid Clark, Sheena Colin, Jean-Noel Compton, Dave Delgado, Jaime Desmontils, Emmanuel Earley, Jim Fornara, Nicoletta Gauss II, Ray Großer, Katharina Guth-Orlowski, Susanne Guth-Orlowski, Susanne Hickson, William holborn, timothy Howard, Roger Hück, Benjamin Iannella, Renato Isaac, Antoine Jafari, Mohammad Kapoor, Amit Kasten, Andreas Kirrane, Sabrina Knygar, Ya Lewis, David Lewis, Lucinda Llorente, Silvia McRoberts, Mo Mihindukulasooriya, Nandana Myles, Stuart Öberg, Jonas Pähler, Daniel Paschke, Adrian Perego, Andrea Polleres, Axel Quinn, Brendan Rodríguez-Doncel, Víctor Schumacher, Greg Sedlik, Jeff Steyskal, Simon Suarez-Figueroa, Mari Carmen Tournié, Stéphane ukadike, kemi Villata, Serena Vowles, Graham Wenning, Rigo White, Ben Wilkinson, Simon

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

ODRL Community,



a comment on the Action vocabulary in the 2.1 draft -
http://www.w3.org/community/odrl/work/2-0-common-vocabulary-constraint-draft
-changes/



Since the first publication of this draft in summer we've received comments
on the actions regarding changing/modifying existing assets and
deriving/extracting from existing assets and creating new ones.



Based on that I propose these changes:



** Adding a new action as child of "use":

- Identifier: modify

- Semantics: The Assigner permits/prohibits the Assignee(s) to
update existing content of the Asset. A new asset is not created by this
action.

- Comment: This action will modify an asset which is typically
updated from time to time without creating a new asset like a database. If
the result from modifying the asset should be a new asset the actions derive
or extract should be used.



** Drop or deprecate the actions writeTo and appendTo and recommend using
the action modify



* Note on the proposed changes above:

- writeTo and appendTo are only about adding something to an asset
but not about modifying it .

- . a modify action is missing

- It would be very hard to distinguish precisely modify, writeTo
and appendTo therefore it is better to go ahead with the wider term. (E.g.
is it realistic to permit modifying an asset but to prohibit that something
is added by the modification?)



** Change the Action "derive" by more precise semantics:

- Semantics: The Assigner permits/prohibits the Assignee(s) to
create a new derivative Asset from this Asset and to edit or modify the
derivative.

- Comment: A new asset is created and may have significant overlaps
with the original Asset. To the derived Asset a next policy may be applied.



** Change the Action "extract" by more precise semantics:

- Semantics: The Assigner permits/prohibits the Assignee(s) to
extract parts of the Asset and to use it as a new Asset.

- Comment: A new asset is created and may have very little in
common with the original Asset. To the extracted Asset a next policy may be
applied.





Thanks for considering this change,



Michael



Michael Steidl

Managing Director of the IPTC [mdirector@iptc.org]

International Press Telecommunications Council
Web: <http://www.iptc.org/> www.iptc.org - on Twitter
<http://www.twitter.com/IPTC> @IPTC

Business office address:

25 Southampton Buildings, London WC2A 1AL, United Kingdom

Registered in England, company no 101096

Related issues: (space separated ids)

WG Notes:

Resolution: The proposal is accepted

(Please make sure the resolution is adapted for public consumption)