Permissions and Obligations Expression Working Group Teleconference

<renato> scribe: CarolineB

<michaelS> present

<renato> https://www.w3.org/2018/02/05-poe-minutes

minutes approved

Best practices note

<renato> http://w3c.github.io/poe/bp/

best practices

benws_ has lots to integrate and plans a session with Victor to do this

s/stih/sith

scribe: planned for tomorrow or next day
... asks for examples of things people want to express

michaelS: can share from RightsML

lindab: can also supply a magazine use case

benws_: asking for publishing examples
... will supply real time himself

renato: send them in before the next call?
... whats our end date for the working group?

ivan: first or last day of April - looking it up...
... its the 30th April and we can publish up to them
... we should have a near finished document in the first week of April

renato: agree to meet next week to review what we have after stuff has been pulled together

<renato> https://www.w3.org/TR/ld-bp/

renato: victor was asking what exactly are best practices
... will we have this as well as examples?

benws_: could call it a primer
... when I first read the standard it was dense and took a while to understand
... so examples get you up to speed quicker
... the title of the doc isn't so important just now. We can revisit

Current use cases note

<renato> http://w3c.github.io/poe/ucr/

renato: has been updated with stuff from wide review and from Simon
... should we reissue as a wg note?

ivan: a note is something thats worthwhile reading. its ok to leave it if theres a link

AOB

michaelS: if a duty has consequences and both have to be fulfilled, how do we deal with time?
... the rightsML working group is discussing just now

<lindab> +

michaelS: this topic has come up with a question - what happens if the duty isn't fulfilled but consequence is
... currently says basic duty AND consequence has to be fulfilled

benws_: could model is in two ways - either subclass duty
... or say it has to be fulfilled rather than the duty itself

lindab: its catch22.

michaelS: it doesn't allow a new subproperty
... we read it that the profile can't define a new subproperty

<victor> hi

renato: you could create a subproperty of failure
... could add to best practices guide to outline the process

michaelS: a new property would fit but can we do this?

renato: did we forget to put failure in the profile?

<victor> (just realized the time was not 13.30GMT but 13.00GMT :(

<renato> https://www.w3.org/TR/odrl-model/#rule

lindab: remembers conversation earlier there was some issue

renato: think its allowable but we haven't explicitly listed it. Could treat as errata and update
... michaelS approach is correct. We already have stuff in the narrative and just left it out of the table

michaelS: will raise the errata

Community Group and Errata

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

renato: idea is to get community group to review these
... i.e. raise them and decide if typo, or a mistake to note

ivan: even editorial changes need to be recorded as errata
... the new W3C process the W3C team has the right to reissue a doc for purely editorial changes
... current change (adding failure - see above) is probably not a simple editorial change
... but would be if e.g. a wrong term is used
... for editorial things you can change the doc and summarize at the end of the doc

i... you edit the editors draft in Git. In a year from now, we may decide to republish as an edited recommendation

scribe: and that refreshes it

ivan: but we don't need a new working group for that purpose. It can be the cg

renato: so, when cg accept a group of updates do we update something?

ivan: no need, its the one we use for the wg its in the repo and its just editing that

<victor> ...so no need to create "git branch" etc.

ivan: I froze a version from when the rec was published. That won't be changed

renato: there is also a new ODRL area in Git for the CG

ivan: and the CG can do what it likes there
... will we be able to run the tool that converts to html if renato is suddenly removed?

renato: probably... I'll check that there is a readme
... updating victor on the earlier meeting especially re best practices guide

ivan: suggests we don't edit the html doc directly or we might lose changes when we remake the doc

renato: bye ad thanks