20:03:02 RRSAgent has joined #profgui 20:03:02 logging to https://www.w3.org/2019/01/23-profgui-irc 20:03:10 Zakim has joined #profgui 20:03:37 @alejandra: do you need connection details? 20:03:56 * present+ 20:03:59 https://www.w3.org/2017/dxwg/wiki/Meetings:ProfGui-Telecon2019.01.23 20:04:48 present+ 20:04:49 present+ 20:05:18 present+ 20:05:54 present+ 20:06:21 rrsagent, create minutes v2 20:06:21 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html PWinstanley 20:06:27 scribenick: alejandra 20:06:45 topic: action items 20:06:55 s/topic: action items/ 20:07:04 topic: minutes from last meeting 20:07:12 rrsagent, create minutes v2 20:07:12 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html alejandra 20:07:18 https://www.w3.org/2017/dxwg/wiki/Meetings:ProfGui-Telecon2019.01.09 20:08:33 https://www.w3.org/2019/01/09-profgui-minutes.html 20:08:53 +0 (not present) 20:09:14 proposed: accept minutes from last meeting 20:09:17 +1 20:09:19 +1 20:09:19 +1 20:09:19 +0 (not present) 20:09:22 +1 20:09:32 resolved: accept minutes from last meeting 20:09:54 regrets+ Antoine 20:09:57 topic: action items 20:10:14 rrsagent, create minutes v2 20:10:14 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html PWinstanley 20:10:19 https://www.w3.org/2017/dxwg/track/products/3 20:11:00 rrsagent, make logs public 20:11:28 synbcing UCR and profgui requitrements 20:11:31 ncar: action item 272 - analyse profile requirements against the guideline 20:11:39 kcoyle: I think we can close that one 20:11:46 ... moving the requirements into the UCR did it 20:11:51 +1 20:11:53 ncar: ok, let's close it 20:12:04 rrsagent, create minutes v2 20:12:04 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html alejandra 20:12:07 close action-272 20:12:07 Sorry, but no Tracker is associated with this channel. 20:12:15 close: action-272 20:12:17 chair: ncar 20:12:51 meeting: ProfGui Subgroup 20:12:51 topic: ESWC paper review 20:12:57 q+ 20:13:24 kcoyle: we have to make the reviews public 20:13:31 ... even if copied from somewhere 20:13:35 q+ 20:13:37 ncar: yes, we are ready for that 20:13:47 ... we've got 4 reviews, we've got the in a document 20:13:56 ... we're tidying them up 20:14:05 kcoyle: the paper is about the profiles ontology? 20:14:14 ... and this is the profile guidance group 20:14:24 ... maybe there is subset that relates to profile guidance 20:14:37 ncar: we've got a couple of comments about background and information 20:14:57 ... we want to indicate what belongs to the ontology and what we think belongs to the guidance document 20:15:30 ... we don't have to spend this meeting to discuss the comments fully 20:15:47 roba: we need to outline the guidelines ; are the comments confidential? 20:16:04 ... feedback is related to the paper and is less important to the substance of the ontology 20:16:13 q+ 20:16:20 ... and I think the feedback is mainly about the paper rather than the ontology 20:16:44 ncar: yes, I read through the comments again and the majority are about the paper itself 20:16:57 ... maybe two comments about the ontology 20:17:27 ... the reviews are open reviews 20:17:44 +q to say that the reviews are published at notification time 20:17:58 ... we can include them in the public comments list 20:18:03 q? 20:18:10 ok cite them and reflect in the substantive matters 20:18:20 ack kcoyle 20:18:24 ack roba 20:18:41 ack PWinstanley 20:18:48 PWinstanley: three things: 1- I haven't seen this paper and I'd like to if possible 20:19:11 ... 2- are there things in the paper that would help us complete this document ? 20:19:41 ... 3- in the plenary, we were talking about doing the sprints and this is one of the areas that seriously needs a sprint and wanted to make sure that we discuss that today 20:19:47 +1 20:19:53 re 2 - as ncar said it gives us some insight into guidance needs 20:20:02 ncar: it is a sideshow w.r.t. the profile guidance document 20:20:15 ack PWinstanley 20:20:25 PWinstanley: there is a big difference between writing a paper for a meeting and getting the guidance thing pushed ahead 20:20:29 ... we need to move on 20:20:30 q? 20:20:39 ack alejandra 20:20:39 alejandra, you wanted to say that the reviews are published at notification time 20:20:54 alejandra: reviews will be public when notifications are out 20:21:17 ncar: there is a small number of comments related to the profile guidance, so we will refer to the reviews in the comments list 20:21:55 ncar: I'll send the paper to PWinstanley after this meeting 20:21:58 q+ 20:22:06 ack roba 20:22:13 ... we could organise a workshop 20:22:30 roba: the milestone for the prof guidance FPWD is broadly discussed 20:22:42 ... we need a couple of specific milestones and discuss when those can be done 20:22:57 ... identifying things in the UCR is important 20:23:07 ... things to discuss 20:23:33 ... there are lots of issues that are controversial or complicated because we have to cite evidence 20:23:37 topic: plans for Prof Guidance workshop 20:23:59 ... a milestone that is the requirements and the mapping to conneg 20:24:10 ... would be a substantial initial piece 20:24:22 ... and it is a different milestone to what is currently described 20:24:34 ncar: was that milestone produced a long time ago? 20:24:39 roba: yes 20:24:57 "A definition of what is meant by an application profile and an explanation of one or more methods for publishing and sharing them." 20:25:05 ncar: having a mini-workshop asap, could this be item number 1 of that workshop? 20:25:22 q? 20:25:38 ncar: comments on that proposal? 20:25:54 kcoyle: since we do have conneg and ontology in progress, it would make sense to integrate them into this document 20:26:04 ... it will leave a whole bunch that isn't covered 20:26:11 q+ 20:26:12 ... but there is no reason not to include them 20:26:20 ... and will help us to see what is remaining 20:26:28 ack PWinstanley 20:26:30 PWinstanley: we need to sort out this definition 20:26:34 we can choose a second milestone for FPWD 20:26:44 ... the discussion is still going, e.g. with base specification 20:27:00 -1 for changing the defintion - it would without defining BaseSpecification as a class 20:27:23 ncar: we don't have any substantial discussion about the ontology 20:27:27 s/would/works/ 20:27:34 ... the discussion about base specification has been resolved 20:27:41 which document are you speaking about? 20:27:43 q+ 20:27:43 its a change to the ontology - but not the definiton 20:27:58 ack kcoyle 20:28:01 definition is common to all documents (please!) 20:28:07 kcoyle: what document are you referring to? the ontology document? 20:28:14 ... that is not what PWinstanley is talking about 20:28:24 ... he is talking about the profgui document 20:28:27 q+ 20:28:28 PWinstanley: exactly 20:28:33 https://w3c.github.io/dxwg/profiles/ 20:29:01 PWinstanley: we had Annette, me, Antoine, we've been doing different versions of it and we need to move on from that 20:29:20 ... and come back to the introduction and the abstract after the sections and subsections have been completed 20:29:38 ... the definition will be more clear after that 20:30:06 ncar: the proposal at the moment is to do away with the phrase base specification 20:30:14 ack roba 20:30:27 ... when we complete this action, we can think of the use of base spec in the guidance doc 20:30:44 roba: the definition that we agreed that would be common to all documents is still fine 20:30:49 ... base spec defines a role 20:31:03 ... and the change in the ontology is independent 20:31:13 ... still seems to meet the requirements in the UCR 20:31:21 ... if we have evidence of something that breaks it, fine 20:31:41 ... if we need to clarify saying that base spec is whatever the standard is referring to 20:31:57 ... we can write a piece of text extending the explanation 20:32:00 +1 to roba suggesting we move on 20:32:10 ... but I'm reluctant on changing the definition 20:32:20 ncar: shall we define what to do in a workshop? 20:32:26 q+ 20:32:28 ... and then see when this could happen 20:32:41 ack kcoyle 20:33:26 kcoyle: the key thing is not whether or when we will have it, but how 20:33:29 ... let's define actions 20:33:49 ok next week 20:33:51 +1 20:33:52 ncar: are people on this call available on the first 3 days of next week for instance? 20:34:01 yes, in principle 20:34:19 * prefer not within 12am-6am window :-) 20:35:02 q+ to talk about duration 20:35:04 ncar: not easy to find a time slot with a mix of North America / Europe / Australia 20:35:12 ack roba 20:35:12 roba, you wanted to talk about duration 20:35:23 roba: we talked about 3 hours sprints 20:35:43 ... we can make substantive comments in 1 1/2 h 20:35:54 ... if we know what we are doing 20:35:58 +1 to roba 20:36:13 ncar: suggestion is to propose a series of times 20:36:46 action ncar to send out doodle poll 20:36:46 Sorry, but no Tracker is associated with this channel. 20:37:05 ncar: so, as discussed, let's come up with an agenda 20:37:23 ... we had some discussion about base spec, and roba mention about triaging the issues 20:37:29 q+ 20:37:32 q+ 20:37:33 ... can someone else suggest more topics? 20:37:34 ack roba 20:37:52 roba: one of the things we want to do is come up with a standard wording when referring to other documents 20:38:02 ack PWinstanley 20:38:06 ... this is probably a little bit tricky but it's something we need to prioritise 20:38:25 PWinstanley: going to the documents, it's completely scattered with pink boxes relating to the issues 20:38:35 ... and going to the google doc and things like that 20:38:57 ... going all the way through sections 2.1 and 2.6 and replacing the pink boxes 20:39:05 +1 for removing all google docs and putting in even placeholder text 20:39:10 ... would be helpful 20:39:24 +1 to writing - we need some writing 20:39:38 PWinstanley: I see these meetings being collaborative writing of text rather than discussing something and going away to write it 20:39:44 ... maybe we can work on a google doc 20:39:53 +1 collaborative writing. We could use a google doc as long as we transcribe when agreement made in the meting 20:40:03 +1 to above 20:40:16 ... we can move quickly through the red boxes and replace them with some proper narrative 20:40:20 q+ 20:40:33 +1 to collaborative writing 20:40:55 ack kcoyle 20:40:59 kcoyle: I'd drop the base specification one 20:41:08 ... we agreed that we're going to leave it until we have more 20:41:21 ... there are some issues that we have, where we have quite a bit written 20:41:40 ... my question is: should we go ahead and put those in here or should we look at the issues first? 20:41:51 i think triage that issues are referenced 20:42:04 ncar: if we took the google doc, why don't we say that people will find the summary of the issues and put them in the google doc? 20:42:11 kcoyle: we kind of have them on this document 20:42:32 ncar: we need to include what we have in the document 20:42:34 i think use google doc only during meetings and dont allow it to persist... 20:42:42 kcoyle: someone has done a google doc to respec translate 20:42:46 q+ 20:43:04 ... we can get this structure as something we can write into without having to go through github 20:43:32 ncar: if we are only addressing a subset of the document, I can include it into a google doc and then put it back 20:43:32 ack roba 20:43:56 roba: my view is that google doc is great for collaborative writing and terrible for persistence and tracking changes 20:44:08 ... so we can use a google doc for collaborative writing and then move it to github 20:44:12 +1 to the mixed approach roba suggests 20:44:24 +1 to approach 20:44:31 ... the google doc should be thrown away 20:44:35 ... after a session 20:45:33 ncar: happy to treat this as set up and tear down thing 20:45:57 ... prepare google doc before the workshop and transfer it over after the workshop 20:46:23 roba: we could do it as we go along, rather than leave it to transcribe at the end 20:46:27 q+ 20:46:47 ack kcoyle 20:46:52 ncar: we have a couple of topics that would be suitable for a couple of sections 20:47:17 kcoyle: either ncar or roba feel that they can fill the conneg work and profile ontology work between now and then? 20:47:20 ok - i will do a triage for the ontology references 20:47:21 ncar: I think that's possible 20:47:54 ... the semi-urgent things we need to deal are some responses related to the paper on the ontology 20:48:00 ... but no other thing too urgent 20:48:00 rrsagent, create minutes v2 20:48:00 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html PWinstanley 20:48:10 ... so I think that's possible 20:48:25 q+ 20:48:30 ack roba 20:48:32 action ncar address as many issues for conneg and profile ontology doc before guidance workshop 20:48:32 Sorry, but no Tracker is associated with this channel. 20:48:51 s/action ncar address as many issues for conneg and profile ontology doc before guidance workshop/ 20:49:25 action ncar address as many issues for conneg before guidance workshop 20:49:25 Sorry, but no Tracker is associated with this channel. 20:49:36 action roba address as many issues for profiles ontology before guidance workshop 20:49:36 Sorry, but no Tracker is associated with this channel. 20:49:44 rrsagent, create minutes v2 20:49:44 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html alejandra 20:50:20 summarising suggested agenda for workshop: 1. Create a referal wording for Guidance doc to other Profile docs, 2. Triage Issues - handoff to other docs, 3. Issues in Sections 2.1 - 2.6 20:50:25 q+ 20:50:31 ack kcoyle 20:50:47 kcoyle: could the issue about how to link from one to the other become a github issue? 20:51:01 ... this would leave more time for us to write 20:51:05 roba: yes 20:51:08 ncar: ok 20:51:12 proposed: rewrite FWPD milestone to be "Have all requirements in UCR represented and cross referenced, and addressed with a cross reference, agreed text or an open issue" 20:51:35 "Have all requirements in UCR represented and addressed with a cross reference, agreed text or an open issue" 20:51:54 q+ 20:52:33 proposed: rewrite FWPD milestone as "Have all requirements in UCR represented and addressed with a cross reference, agreed text or an open issue" 20:52:43 summarising suggested agenda for workshop: 1. Review outcome from an Issue discussiong doc referal text, 2. Triage Issues - handoff to other docs, 3. Issues in Sections 2.1 - 2.6 20:52:47 ack roba 20:53:25 proposed: rewrite FWPD milestone as "Have all requirements in UCR represented and addressed with a cross reference, agreed text or an open issue" 20:53:25 q+ 20:53:36 topic: reform Milestone for Guidance doc 20:53:39 proposed: rewrite FWPD milestone as "Have all requirements in UCR represented and addressed with a cross reference, agreed text or an open issue" 20:53:50 ack kcoyle 20:54:08 action ncar to create the google doc 20:54:08 Sorry, but no Tracker is associated with this channel. 20:54:51 +1 20:54:52 +1 20:54:52 +1 to milestone 20:54:59 +1 20:55:12 +1 20:55:23 resolved: rewrite FWPD milestone as "Have all requirements in UCR represented and addressed with a cross reference, agreed text or an open issue" 20:55:44 rrsagent, create minutes v2 20:55:44 I have made the request to generate https://www.w3.org/2019/01/23-profgui-minutes.html kcoyle 20:58:02 PWinstanley has left #profgui