W3C

- DRAFT -

Permissions and Obligations Expression Working Group Teleconference

05 Sep 2016

Agenda

See also: IRC log

Attendees

Present
Serena, michaelS, renato, victor, james, Ivan, phila, benws, CarolineB
Regrets
Chair
SV_MEETING_CHAIR
Scribe
CarolineB, Caroline

Contents


<ivan> scribenick: CarolineB

<ivan> scribe Carline

<phila> scribe: CarolineB

<ivan> scribe: Caroline

<phila> scribeNick: CarolineB

<renato> Proposed to approve last week's minutes https://www.w3.org/2016/08/29-poe-minutes

<benws116> Hmmm - when I try to join the webex I get: The meeting has been cancelled or ended!

<benws116> Is there something I missed while away?

<renato> Click on the webex link here:

<renato> https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160905

last weeks minutes approved

Use Cases

UC17

<benws116> Many thanks

<renato> UC.17 http://w3c.github.io/poe/ucr/#assetInSet

UC 17 concerns groups of assets that are all subject to the same offer

scribe: wants to link offer to the set with contstraint saying "applies to 1"

james: offer would point to set rather than single assets
... and you'd choose one

benws116: TR shares this one. Can we borrow terminology from elsewhere?

<victor> The requirement derived from UC17 is also supported by one of the five requirements from UC1, which claims the same. The idea of saying "this policy applies to EACH of the assets in this group" is equivalent to the semantics of the Group, where an equivalent idea is convey ("each party in this group is an assignee")

phila: is leaving in 15mins. puffs up powder but nobody uses it

<phila> POWDER Grouping

phila: but it provides good mechainism for grouping things and listing exceptions. Its based on idetnifier patterns

renato: yes this ties to UC1 as victor says and there is a definite need

<renato> US.22 https://www.w3.org/2016/poe/wiki/Use_Cases#Deletions_Must_be_Propagated

<renato> UC.22

UC.22

<james_> .. apologies, my connection is a bit flakey

benws116: its where changes in master set must be reflected in related data

renato: its a duty then? yes

benws116: re personal data - this will be needed in EU from 2018

<renato> UC.23 https://www.w3.org/2016/poe/wiki/Use_Cases#Synchronization_in_a_multilayer_music_description_environment

UC.23

renato: relates to packaging up music and score etc together. Needs a new action around permission and prohibition around sync. Its about coleections of resources and being able to refer to ndividuals
... or individuals that is
... when play audio and there are graphical notes, to follow notes- keep music and notes synched

benws116: can we all think about other examples of sync in this way?

<victor> Within the Media Value Chain Ontology (ISO/IEC 21000:19), we also defined Synchronization as a first class action that was needed.

<victor> NON official spec http://dmag.ac.upc.edu/ontologies/mvco/

victor: for mpeg21 is was one of the main actions along with "distribute" etc

renato: next week 12th is last call before F2F lets finish off the current use cases

<michaelS> https://www.w3.org/2016/poe/wiki/Requirements

renato: we need to prep use cases for discussion at F2F. By putting requirements on a wiki?

benws116: happy to work on this

michaelS: some reqs have open issues. will I filter these out? yes
... asks question about style. Would we propose solution? Not yet

victor: will original ODRL requirements be in the list?

renato: not those that are already in 2.1. just starting from the base line and moving forward from there

<renato> https://www.w3.org/2012/09/odrl/archive/odrl.net/2.0/WD-v2req-20050213.html

Admin

Serena: Done action 19 this morning

<renato> https://www.w3.org/2016/poe/track/issues/raised

renato: we still need to talk about ODRL profiles
... issue 8. heading towards this: from UCR document the group will decide whcih will be accepted and implemented
... issue 9. potential note about best practice

AOB

<ivan> trackbot, end telcon

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/09/05 12:41:11 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Approve:/Proposed to approve last week's minutes /
Found ScribeNick: CarolineB
Found Scribe: CarolineB
Found Scribe: Caroline
Found ScribeNick: CarolineB
Scribes: CarolineB, Caroline
Default Present: Serena, michaelS, renato, victor, james, Ivan, phila, benws
Present: Serena michaelS renato victor james Ivan phila benws CarolineB
Agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160905

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 05 Sep 2016
Guessing minutes URL: http://www.w3.org/2016/09/05-poe-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]