- From: Víctor Rodríguez-Doncel via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 May 2017 08:54:51 +0000
- To: public-poe-archives@w3.org
Partially implemented in Revision: 28689e1b1a19cf165a3233f206cbec8a71a19248 Please note that these points have not been implemented: - Obtain Consent (4.14.9): the definition should outline how the consent should be obtained, the current definition could be interpreted as wide open but then it is also unclear and could be interpreted differently easily. **NOTE DONE - UNCLEAR** - Watermark (4.14.12) - Note: embed a link to what - and how?? **NOT DONE. What should we do then?** - Semantics of Distribute (4.12.11), Move (4.12.18) and Reproduce (4.12.23): quite clear is Move: the (only) copy of the asset goes from A to B, nothing remains at A. Reproduce covers only making a copy of the asset but nothing about the use of this copy. If the use of the copy should be defined by another constraint we would tell that in a Note. (Practical note: is a realistic to define a constraint for such a common action like creating a copy? I guess not Assignee can guarantee that the provided digital asset will only be moved and never copied.) And what exactly is Distribute? Something like moving a reproduced copy from A to B (or many Bs)? These three actions need reconciled semantics. **NOT DONE - UNCLEAR** -- GitHub Notification of comment by vroddon Please view or discuss this issue at https://github.com/w3c/poe/issues/178#issuecomment-301718627 using your GitHub account
Received on Tuesday, 16 May 2017 08:54:58 UTC