RE: Action vocabulary change request - modify/writeTo/appendTo ...

Hi Ray,

good idea to add that - as there are no agreed rules for making this distinction.
= I support your proposal.

Thanks,
Michael


> -----Original Message-----
> From: Ray Gauss [mailto:ray.gauss@alfresco.com]
> Sent: Friday, November 21, 2014 2:23 PM
> To: Michael Steidl (IPTC)
> Cc: ODRL Community Group
> Subject: Re: Action vocabulary change request - modify/writeTo/appendTo
> ...
> 
> Hi Michael,
> 
> Perhaps a note should be added to modify and derive stressing that the
> notion of whether or not the change is significant enough to qualify as a 'new
> asset' is completely subjective?
> 
> Is there a good spot to express that sort of qualification at the moment?
> 
> Regards,
> 
> Ray Gauss II
> DAM Architect, Alfresco
> 
> 
> On November 21, 2014 at 5:28:20 AM, Michael Steidl (IPTC)
> (mdirector@iptc.org) wrote:
> > 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: www.iptc.org - on Twitter
> > @IPTC
> >
> > Business office address:
> >
> > 25 Southampton Buildings, London WC2A 1AL, United Kingdom
> >
> > Registered in England, company no 101096
> >
> >
> >
> >
> >
> >

Received on Friday, 21 November 2014 19:43:18 UTC