12:12:30 RRSAgent has joined #poe 12:12:30 logging to http://www.w3.org/2017/02/13-poe-irc 12:12:32 RRSAgent, make logs public 12:12:32 Zakim has joined #poe 12:12:34 Zakim, this will be 12:12:34 I don't understand 'this will be', trackbot 12:12:35 Meeting: Permissions and Obligations Expression Working Group Teleconference 12:12:35 Date: 13 February 2017 12:12:39 RRSAgent, make logs public 12:12:46 present+ renato 12:12:57 Chair: renato 12:13:06 Regrets: Serena, Stuart, Ben 12:14:43 simonstey has joined #poe 12:28:29 agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20170213 12:28:37 michaelS has joined #poe 12:30:36 present+ 12:30:50 present+ 12:30:50 present+ 12:31:27 Plenty of snow - just the 40 degree heat melts it on entry to our atmosphere :-) 12:32:41 scribe: simonstey 12:32:43 victor has joined #poe 12:33:24 chair: renato 12:33:27 TOPIC: approval of last week's minutes 12:33:42 https://www.w3.org/2017/02/06-poe-minutes.html 12:33:51 present+ michaelS 12:34:05 renato: hearing no objections -> minutes approved 12:34:28 present+ victor 12:34:30 TOPIC: 2 rec track documents 12:34:36 CarolineB has joined #poe 12:34:58 Sabrina has joined #poe 12:35:08 present+ Sabrina 12:35:11 renato: comments from simonstey regarding introduction of attributes 12:35:13 https://github.com/w3c/poe/issues/ 12:36:06 ... another issue discussed last week was json-ld context 12:36:33 ... got some advise/comments from gregg kellogg 12:37:10 ... has anyone any further questions/comments regarding the info model? 12:37:44 https://github.com/w3c/poe/issues/105 12:37:51 ... we plan to publish both documents as WD 12:39:14 simonstey: There are issues in the PDF that are implementation specific, they don't provide general info 12:39:34 simon: undefined actions section - http://w3c.github.io/poe/model/#undefined 12:39:56 simon: what is an undefined action? too vague? 12:40:52 ...implementation specific 12:41:46 renato: this feature was added way back 12:42:31 q+ 12:42:32 ... when ODRL was used more in closed environments, rather than open world scenarios 12:42:40 ... I propose to mark it as "at risk" 12:43:11 phila: the phrase "at risk" has a specific conotation 12:43:25 ... I would mark it as issue 12:43:55 Sounds sensible to me 12:44:10 phila: Maybe also add a sentence to the Status of the Document 12:44:23 present+ CarolineB 12:44:44 Proposal: mark section 3.1.4 as an issue - the feature maybe removed in future version 12:44:53 +1 12:44:58 +1 12:45:00 +1 12:45:04 +1 12:45:05 +1 12:45:06 +1 12:45:31 Resolved: mark section 3.1.4 as an issue - the feature maybe removed in future version 12:45:41 RRSAgent, draft minutes 12:45:41 I have made the request to generate http://www.w3.org/2017/02/13-poe-minutes.html phila 12:46:05 renato: anyone has any other questions/comments reg. the info model? 12:46:41 phila: is that the only open issue? 12:47:05 renato: yes, other than that only editorial ones left 12:47:20 TOPIC: vocab document 12:47:44 http://w3c.github.io/poe/vocab/ODRL22.jsonld 12:48:01 renato: we now know how a json-ld context should actually look like 12:48:36 ... the only other issues for the vocab (apart from the json-ld) are a few little ones 12:48:43 ... 1) issue 101 12:48:44 https://github.com/w3c/poe/issues/101 12:49:14 ... there are 4 actions that all end with "to an audience" 12:50:02 ... I would like to propose removing the phrase "to an audience" from all 4 12:50:16 q+ 12:50:22 ack phila 12:50:29 q+ 12:50:34 ack michaelS 12:51:22 michaelS: adding this phrase was highly recommended by a big german law firm back then 12:51:35 q+ 12:52:25 michaelS: there's a difference between "playing" for a small audience or a big one 12:52:26 q- later 12:53:11 renato: you might be giving away too much permission by having this phrase 12:53:13 regrets+ Brian 12:54:01 ... plus, we won't be able to have a "private" use version of play 12:54:16 michaelS: what would be a use case for that? 12:54:28 renato: [explaining a use case] 12:55:25 michaelS: maybe we need a new action? 12:55:36 q? 12:55:59 ack s 12:56:06 q- 12:57:13 michaelS: the assignee isn't necessarily the beneficiary of a permission 12:57:41 ... we could require the definition of a recipient 12:59:57 renato: if you explicitly mention "to an audience", it implies that you have the right to publicly play it to an audience 13:00:41 michaelS: there should be a distinction between private&public use 13:01:06 renato: most of the action can only be performed by the assignee 13:02:07 ... maybe a profile could implement such a feature 13:02:50 michaelS: looking at the old version of the vocab, present is defined as parent action of display 13:03:31 ... presenting something implies (imo) presenting to someone 13:03:38 ... rather than only to yourself 13:03:51 q? 13:04:24 phila: there's def. a distinction between presenting something to yourself and presenting something to a stadium 13:04:44 Proposal: remove "to an audience" from Present terms, display, play, text2speech 13:04:55 ... (a stadium with people in it) 13:04:58 +1 13:05:00 +1 13:05:00 0 13:05:04 +1 13:05:05 +1 13:05:58 +1 13:06:06 Resolution: remove "to an audience" from Present terms, display, play, text2speech 13:06:41 +q 13:06:41 https://github.com/w3c/poe/issues/103 13:07:27 The actions present, display, play and textToSpeech should include a note requiring to add a receipient party as a private or open audience. 13:08:57 simonstey: mentions different semantics of action "stream" for data community 13:09:13 ... streaming data vs streaming movies/audio/... 13:10:23 proposal: Add "stream" to action vocab - broad definition - not as a narrower term of Present 13:10:43 +1 13:10:45 +1 13:10:49 +1 13:10:51 0 13:10:52 +1 13:11:00 0 13:11:01 +1 although, again, I don't like enumerated lists in a vocab 13:11:08 renato: will work on the specific def. of stream 13:11:16 Resolved: Add "stream" to action vocab - broad definition - not as a narrower term of Present 13:11:20 +1 to phil's comment 13:11:20 0 13:11:33 q 13:11:37 q- 13:11:42 ack simonstey 13:12:00 victor: I opened a new issue few minutes ago 13:12:13 ... the ontology isn't OWL-DL 13:12:21 Victor's issue: https://github.com/w3c/poe/issues/106 13:13:12 ... by removing rdfs:range we could make it OWL-DL 13:13:44 ... I could enrich this issue and propose changes 13:13:47 yes 13:14:41 ... the specs can still change after next week right? 13:14:46 renato: you bet 13:14:55 q+ 13:15:03 q+ 13:15:38 phila: just for clarification -> the diagrams in both vocabs are slightly different.. why's that? 13:16:23 renato: [explains diff.] 13:16:59 phila: e.g., "status" in constraints isn't part of the figure in the vocab spec.. why? 13:18:01 phila: maybe worth considering adding an explanatory sentence to the figure in the vocab 13:18:13 q- 13:18:18 ack m 13:18:21 ... basically reiterating what you just said renatio 13:19:01 michaelS: status is "non-normative" what does that mean? 13:19:14 ... what's the difference in relevance? 13:19:40 ... we have two main actions -> use & transfer 13:19:49 ... where transfer now seems to be non-normative 13:20:44 renato: based on the implementation survey we did last year, we derived this distinction 13:21:29 q+ 13:21:29 ... we have to have a number of implementations that implement the whole spec 13:22:58 michaelS: my concern is that someone who's not familiar with the W3C process might be inclined to reinterpret "non-normative" terms 13:23:36 phila: the distinction between normative<->non-normative might have to be recast 13:24:16 ... and we may want to consider change that to core/extension 13:24:47 ... will give both specs a more thorough readthrough until next week 13:25:59 q- 13:30:28 q+ 13:31:14 *me - sorry have to go now 13:32:54 q+ 13:34:09 [discussing generalities] 13:34:44 q- 13:34:48 ack i 13:35:29 ivan: instead of discussing generalities, the question is whether there are at least two different groups that implement e.g. display 13:36:01 ... if this can be proven, there is no point in not having it normative 13:36:07 q+ 13:36:50 ... at this point we could also have certain terms being "at risk" 13:37:16 ... [relevant for CR] 13:38:30 michaelS: I would like to have an equal opportunity for all actions, as people may tend to avoid actions that are denoted as being "non-normative" 13:39:40 RRSAgent, draft minutes 13:39:40 I have made the request to generate http://www.w3.org/2017/02/13-poe-minutes.html phila 13:40:20 renato: plan for next week -> vote on both documents 13:40:22 ... AOB= 13:40:37 RRSAgent, draft minutes 13:40:37 I have made the request to generate http://www.w3.org/2017/02/13-poe-minutes.html phila 15:48:29 Zakim has left #poe