<CarolineB> * whats the webex password?

<victor> Hi! how are you?

<victor> renato, can I get the password for the WebEx? Last Monday I was traveling and could not connect...

<victor> thanks Simon

<benws_> Hi guys - what is the PW?

<scribe> scribe: michaelS

<scribe> scribenick: michaelS

<renato> https://www.w3.org/2017/07/03-poe-minutes

Approving last meetings minutes

<benws_> Thanks!

RESOLUTION: last minutes were approved

<renato> https://github.com/w3c/poe/issues/206

deliverables/constraints

renato: pointed at the issue and summarized the discussion

<victor> (See agenda here: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20170710)

renato: suggested to have two independant classes Constraint and LogicalConstraint
... and each class will specific properties and operators
... asked for comments
... this is not a big change, more covering the narrative
... the LogicalConstraint can have multiplie operands
... how to deal with odrl:andSequence

<victor> If it helps, I would just say that in MPEG-21 Media Contract Ontology, we opted for a very similar approach. See informally here: http://vroddon.sdf-eu.org/mco/mco-core/#FactComposition

michaelS: andSequence leans more toward the Constraint with only two operands

benws_: the sequence fits better with the Constraint

<benws_> +1

michaelS: gave an update on the changes of terms Atomic Constraint -> Constraint

benws_: we do this because RDF sequence are ugly

renato: yes, in JSON-LD this would be no drama
... conclusion: we use andSequence with (Atomic) Constraint

<simonstey> +q

benws_: we need a different name for ODRL's xor

<simonstey> -q

<simonstey> odrl:oneOf ?

benws_: the ODRL xor has a different truth table than the logical xor

<simonstey> odrl:xone ?

(discussion about the name)

<victor> :)

renato: do we have to deprecate xor?

simonstey: nobody has implemented it yet

<victor> as non-official

IM OUT FOR 1 MINUTE

renato: we add odrl:xone as sub-property of operator

sim

simonstey: no, sub-property of operand

renato: this is accepted

<renato> https://github.com/w3c/poe/issues/162

Github issue 162

<renato> https://w3c.github.io/poe/model/#duty

<benws_> Didn't we say we'd give Sabrina and Simon another week to make their suggestions around this?

renato: outlined his actions: the Duty section of the Information Model was revised

<benws_> OK ...

renato: any questions?

<benws_> +1

renato: next week we talk about the Consquence issue

Test Cases

<renato> https://github.com/w3c/poe/blob/gh-pages/test/cr-exit.md

renato: having successfully completed test cases is essential for the CR

<renato> https://github.com/w3c/poe/blob/gh-pages/test/implementors.md

renato: we should approach implementers and invite to do the tests

<renato> https://w3c.github.io/poe/model/#odre

renato: unfortunately Phil, who has worked on the test cases, is not with the group anymore

<simonstey> +q

renato: any comments on Phil's outline?

simonstey: this shows what we have agreed on.
... he is not sure about this Natural Language thingy
... as the processing of a Policy will get more complex by that

benws_: tends to agree with simonstey
... the evaluator should not look into details of constraints etc

<simonstey> +q

benws_: we need a kind of truth table
... will an evaluator ever run over something else than an agreement

renato: agress to this assumption

simonstey: disagreed: what about combined offer - an evaluator would be essential
... to find out if the two (or more) Policies are conflicting.
... if we limit the effect of a rule to Agreements only we would have to rewrite the Information Model

<benws_> I think Simon is right

<Sabrina> It would also be relevant for checking the best offer

simonstey: we could define that an Agreement and an Offer have to cover different rules.

renato: how to move forward on the test cases?

<victor> (a) Phil's work has to be completed (b) Implementors must start implementing features

<simonstey> +q

benws_: he will have a look at that and pass this to developers at TR

simonstey: the test cases should test all the essential features of the ODRL Information Model
... a test case doesn't have to be a real-world case.

renato: agreed - who will write the test cases testing the features?

<victor> ideally, implementors should not mess with the test cases definition

renato: the test cases should define the input and the expected output/result

simonstey: inheritance is a good example: policy C interits from B and B inherits from A
... what are the effective rules in C?

<simonstey> sounds good

benws_: he meant he will share abstract definitions with developers

<victor> i think they should be different persons

<victor> sure :)

simonstey: implementors should have the right to issue new test cases

<benws_> Will do

renato: any further test case issues?
... if you are an implementer pleasea add your name to the list of implementers

<renato> https://github.com/w3c/poe/projects/1

Kanban Project Status

renato: went over the issues in the Project Status

<renato> https://github.com/w3c/poe/issues/158

We should consider adding Creative Commons terms to the Common Vocab

simonstey: why including CC - there are other similar vocabularies too?
... why not other/all too?

<victor> (a) creative commons's vocab is used out there (at least the property cc:license) (b) this vocab has been used by other (c) everybody knows cc

simonstey: doesn't not like to prefer CC over other vocabularies.

benws_: CC is only relevant is some businesses

victor: CC is a widely used and quite flat vocabulary

<victor> A very beatiful example: the OGL license (open government license)

renato: invited to add comments to Github issue #158

<victor> please go to to RDF distiller here: https://www.w3.org/2012/pyRdfa/Overview.html and try with the beautiful OGL license: http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/

renato: At the next call: we need to close the open issues

<victor> thanks have a nice week!

michaelS: regret for the next 3 weeks

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/pwd=webexpoe//
Succeeded: s/use/test/
Present: renato benws_ victor simonstey Sabrina
Regrets: Ivan
Found Scribe: michaelS
Inferring ScribeNick: michaelS
Found ScribeNick: michaelS
Agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20170710
Found Date: 10 Jul 2017
Guessing minutes URL: http://www.w3.org/2017/07/10-poe-minutes.html
People with action items: