ncar: there may be more issues in the shex comments than we have captured
kcoyle: best if issues are "atomistic"
can close #963 because poll came to conclusion
Action: kcoyle close #963 with link to poll - check if appears in minutes - add text to closure
<trackbot> Sorry, but no Tracker is associated with this channel.
ncar: reviewing all issues; responding to feedback
… next divide editorial v features
… we have a label for 'editorial' that can be used
ncar: we would like to have translations
kcoyle: translations are notes? know that they are not normative
<ncar> A suggested order of processing the Issues is:
<ncar> 1. get up-to-speed for all Issues initially
<ncar> 2. directly address all feedback
<ncar> 3. mark Issues editorial v. substantive v. out-of-scope
<ncar> 4. prioritise substantive Issues
ncar: and will tag them appropriately
ncar: out of scope, comment from shacl; has been responded
kcoyle: time to get review by working group; they'll need 2 weeks since they haven't seen it for a while
ncar: can do by plenary next week
<ncar> Here is the current working branch: https://raw.githack.com/w3c/dxwg/prof-3PWD-candidate/prof/
ncar: going through related work
… section 6.4 has VOAF
… it may be that some of these can be used
… if the domains and ranges are friendly
kcoyle: seems like a good source for roles to add to prof if these can't be used directly
ncar: what can we learn from voaf?
kcoyle: need to find ways to get more engagement from group
ncar: there are folks who have contributed to issues - maybe ping them for interaction
kcoyle: create resolutions in issue and ask people to give up/down
kcoyle: other meeting times better for other folks?
… to get this done one meeting a week is not enough - may need sprints
ncar: will ping Antoine and Rob for another meeting
kcoyle: if you hold a meeting do minutes, in anything, and post to the email list if not via rrsagent
Succeeded: s/branche/branch