20:53:41 RRSAgent has joined #profgui 20:53:41 logging to https://www.w3.org/2019/02/14-profgui-irc 20:53:59 rrsagent, make logs public 20:54:08 meeting: profgui sprint 20:54:12 chair: kcoyle 20:59:45 I'll send you the link on skype 21:03:28 ncar has joined #profgui 21:03:32 hi 21:03:37 https://w3c.github.io/dxwg/profiles/ 21:03:53 https://docs.google.com/document/d/1Y4jP4SGZMnt63EpjTX11-hW6-3mxlaq1i-Lbiw4tx1M/edit# 21:04:00 https://www.w3.org/2017/dxwg/wiki/Meetings:ProfGui-Telecon2019.02.14 21:04:24 roba has joined #profgui 21:07:11 scribenick: antoine 21:08:04 alejandra has joined #profgui 21:08:09 present+ 21:08:12 present+ 21:08:33 https://www.w3.org/2019/01/23-profgui-minutes.html 21:08:46 present+ 21:08:53 kcoyle: we didn't create an action for the resolution for the last resolution 21:08:55 present+ 21:08:59 ... about creating a milestone 21:09:03 present+ 21:09:05 present+ 21:09:16 kcoyle: has anyone changed this milestone? 21:09:38 action: kcoyle to update milestone as per last week's minutes 21:09:38 Sorry, but no Tracker is associated with this channel. 21:09:44 https://github.com/w3c/dxwg/milestone/10 21:11:39 resolved: approve minutes of 1/23 21:11:39 Proposed: that we approve minutes 21:11:49 +1 21:11:54 +1 21:11:55 q+ 21:12:33 antoine: we are approving minutes from 3 wk ago? there were minutes from the one roba scribed. 21:12:51 ... this other was a sprint, but minutes need approval too 21:13:11 https://www.w3.org/2019/02/06-profgui-minutes.html 21:13:46 +1 21:13:50 RESOLVED: approve minutes from 6 Feb 21:14:02 q+ 21:14:23 ack antoine 21:14:44 antoine: section1 - minutes of the last call, action on me to incorporate 21:15:00 ... edits into html master 21:15:13 roba: I looked at it and it was OK 21:15:20 https://w3c.github.io/dxwg/profiles/ 21:16:10 kcoyle: so section 1 shows the results of the last discussion, and there have subsequently been more changes, but we press on 21:16:17 kcoyle: we should rather dive in section 2 now, we can come back to the details of the new suggestions for section 1 21:16:19 ... and return to the more recent changes in due course 21:16:52 [kcoyle goes through the intro of section 2] 21:17:11 q+ 21:17:28 ack antoine 21:17:47 antoine: asking roba what he means in his comments 21:18:05 roba: we are not taking responsibility for every use of the word profile in the outside world 21:18:31 kcoyle: "outside of this document"? 21:18:38 roba: maybe "outside of this context" 21:19:14 PWinstanley: "in other contexts" - we want to claim our context 21:20:39 q+ 21:21:16 ack roba 21:21:39 Discussion on keeping MUST/SHOULD/ETC etc 21:21:52 We agree to keep them 21:22:05 roba: this section is about constraints 21:22:05 q+ 21:22:14 kcoyle: this requirements is not about constraints 21:22:25 ack PWinstanley 21:22:27 (requirement #275) 21:24:09 +1 that the language used actually has no meaning without context.. 21:24:24 alejandra_ has joined #profgui 21:24:37 alejandra__ has joined #profgui 21:24:46 PWinstanley: it's formal, but we should try to have a introduction 21:25:02 q+ 21:25:17 +q 21:25:41 q+ 21:26:11 q? 21:27:12 q? 21:28:18 ack roba 21:28:31 ack alejandra__ 21:28:45 ack antoine 21:29:32 if we are not talking about "named graphs" then we need to define all the connecting words in terms of the agreed definition of a profile - not introduce new terminology 21:30:22 "collection of properties" needs to have a meaning w.r.t. to the definition - and its not obvious or defensible as is 21:30:34 Action: PWinstanley will rewrite the beginning of 2.1 21:30:34 Sorry, but no Tracker is associated with this channel. 21:31:30 q+ 21:31:32 remove "status of Standard" - we are based on the very loose dct:Standard which has no requirement for a formally defined status .. 21:32:18 q+ 21:32:20 kcoyle: discussing the second paragraph with "Distribution: 21:32:22 ack antoine 21:33:09 antoine: I think I was the one writing it - the paragraph was to be a guide to this document - there would be hyperlinks to different sections 21:33:57 https://www.w3.org/TR/skos-primer/#secsimple 21:35:05 +q 21:35:51 q- 21:40:35 q+ 21:40:56 ack roba 21:41:12 kcoyle: ok we move it back up 21:41:46 kcoyle: section 2.2 (multiple) base specifications 21:41:57 roba: specification is strightforward 21:41:57 +q 21:42:07 ... this paragraph is quite RDF: the re-use of elements 21:42:17 kcoyle: it's also XML 21:42:55 roba: ok but it's also more than re-using vocabularies 21:43:14 q+ 21:44:17 +1 21:44:19 alejandra__: yes having first a general wording is good and then we can go into an example like the RDF and XML one 21:44:20 +1 21:44:35 ack antoine 21:44:41 ack alejandra__ 21:45:07 ack roba 21:45:14 Action: alejandra will re-word the intro for 2.2 and issue 268 21:45:14 Sorry, but no Tracker is associated with this channel. 21:45:50 +q 21:45:59 q- 21:46:11 q+ 21:46:14 q+ 21:46:16 q+ 21:46:56 q- 21:47:04 q- 21:47:10 alejandra__: have we kept "base specification"? 21:47:18 ack roba 21:47:34 roba: yes we've removed it as a class in PROF (as it was more a role) but we've kept the wording. 21:47:51 kcoyle: 2.3 profiles or profiles 21:48:02 q+ 21:48:07 q+ 21:48:15 ack roba 21:48:49 roba: we've introduced "level" but there might not be anything as a "level of profile" 21:49:03 ... we could remove the first line 21:49:12 q+ 21:49:26 what is being left open? 21:50:59 q+ 21:51:48 ack roba 21:52:11 q+ 21:52:51 antoine: issue 270 is really about saying that it;'s ok to have several levels 21:53:02 ... the other paragraph is about a more general issue 21:54:24 +q 21:55:17 ack alejandra__ 21:55:38 q+ 21:55:50 q+ 21:56:00 q+ 21:56:06 ack ncar 21:57:18 ack ncar 21:57:55 yes! 21:58:03 ack antoine 21:59:35 ack roba 22:00:11 [discussion on mutliple base specifications and hierarchical profiling. We agree and need a diagram] 22:00:40 +1 to DAG 22:01:21 q+ 22:01:53 ack antoine 22:02:04 antoine: I was volunteering for diagram duty 22:02:15 +1 to add the diagram in the document 22:02:22 +1 to non-technial 22:02:31 Action: Antoine to create diagram(s) for the different possiblilty for profiles, on 2.2 and 2.3 22:02:31 Sorry, but no Tracker is associated with this channel. 22:02:37 https://github.com/w3c/dxwg/issues/641 22:02:37 I need my friends to be able to understand it 22:03:05 s/non-technial/non-technical/ 22:03:33 q+ 22:03:49 kcoyle: profile inheritance (2.4) 22:04:17 ack roba 22:04:21 ... it connects to ODRL 22:05:39 roba: can we say that profile should indicate how formal semantics are inherited? 22:05:48 kcoyle: it comes from external comments. 22:05:50 q+ 22:05:58 ack antoine 22:06:12 q+ 22:06:21 antoine: at this stage let's put it as an open issue and return to it 22:06:31 q+ 22:06:42 q+ 22:06:51 ack roba 22:06:57 I was first! 22:07:38 * no, other relevant comment about procedure of Issues 22:07:50 +1 to roba comment's about inheritance 22:09:49 ack ncar 22:11:18 ncar: the discussion on inheritance relates to a PR for PROF, on examples of inheritance 22:11:48 ack antoine 22:11:58 ... if it's accepted people will see 22:13:03 antoine: reacting to ncar , having been involved in the discussion, the example deserves some improvement, but there should be a proper issue for the requirement [github issue is missing]. I gree wiht roba , and if he can open an issue for the explanation of inheritance it would be great 22:13:21 s/gree wiht/agree with/ 22:13:54 Action: roba to create a requirement issue for inheritance 22:13:54 Sorry, but no Tracker is associated with this channel. 22:14:21 rrsagent, create minutes v2 22:14:21 I have made the request to generate https://www.w3.org/2019/02/14-profgui-minutes.html PWinstanley 22:14:49 Action: Antoine to relate other issues from external comments on inheritance to Rob's requirement, after he has created it 22:14:49 Sorry, but no Tracker is associated with this channel. 22:15:02 Meeting: Profile Guidance doc St Valentines Day Sprint 22:15:07 rrsagent, create minutes v2 22:15:07 I have made the request to generate https://www.w3.org/2019/02/14-profgui-minutes.html PWinstanley 22:15:43 kcoyle: Data publication according to different profiles 22:15:43 dcat 22:15:51 ... my take is that it's conneg 22:15:51 q+ 22:16:11 ack roba 22:16:28 roba: it's a requirement for DCAT expressivity 22:16:35 ... provide a mechanism to express it 22:16:45 q+ 22:17:42 q+ 22:18:09 https://github.com/w3c/dxwg/issues/608 22:18:10 ack antoine 22:19:42 ack roba 22:19:44 antoine: pasting a link to the requirement that indicates that we decided to create it as a general fork of something else, in the profile category. It illustrates the need for expressivity - a mechanism in conneg shows that there can be many satisfying profiles and one can be chosen. We want this to be a general feature 22:20:00 ... and I would prefer that not all examples come from DCAT 22:20:33 roba: the documents are not disjoint, and the guidance can be the place where things are put together 22:20:47 ... so DCAT can be one mechanism, but there can be others. 22:21:02 q+ 22:21:03 +q 22:21:09 nick alejandra 22:21:10 kcoyle: we don't say how data relate to profiles 22:21:15 ack ncar 22:21:22 s/nick alejandra/ 22:21:30 ncar: we had feedback on this from external comments 22:22:11 ... there are examples that we have to align with 22:22:19 ack alejandra 22:22:29 alejandra: I agree it makes sense to put it in the guidance 22:22:37 ... it's about linking profiles to data 22:22:45 kcoyle: 2.5 and 2.6 are very similar 22:23:14 q+ 22:23:16 ... it seems we need to make a single section about data and profiles 22:23:25 ack roba 22:23:31 roba: I can see the difference but not in the wording 22:24:06 ... difference between conformance of the data and the access to the data 22:24:16 q+ 22:25:11 ack antoine 22:25:50 antoine: I'm fine if roba starts it. I'll check that what he writes fits with #274 ... schema.org and DCAT compatibilty 22:26:16 ... data according to two profiles in one distribution 22:28:25 kcoyle: there are notes that can be useful 22:28:39 ... and then a part on validation. We can see where it belongs, in the end. 22:28:57 q+ 22:29:12 ack antoine 22:29:21 antoine: should we try to go to the suggestions for section 1 22:29:24 +q 22:29:25 ...? 22:29:43 ack alejandra 22:29:45 q- 22:31:21 q+ 22:31:30 q+ 22:31:56 ack antoine 22:32:25 antoine: it reads well, but do you want it as an editorial note? Both sentences? or as a regular paragraph? 22:32:39 ack roba 22:32:57 q+ 22:33:33 +q 22:35:13 q+ to discuss the proposed edit of s.2.1 22:35:53 q? 22:35:56 ?q 22:36:01 ack antoine 22:36:21 antoine: no pull requests now please. 22:36:50 ... I agree with roba original comment on a base specification and a profile. 22:38:21 q- 22:38:33 ack PWinstanley 22:39:09 q+ to introduce the Baltimore classification - https://en.wikipedia.org/wiki/Baltimore_classification 22:40:22 * what are we looking at Peter? the edits to section 1? 22:43:16 [discussion on merging 2.2 and 2.3. we agree to wait until next time - and the diagrams] 22:43:32 PWinstanley: [introduces his proposal for 2.1] 22:44:31 PWinstanley: the Baltimore classification https://en.wikipedia.org/wiki/Baltimore_classification could be used as a guide 22:44:39 ... it tells the rules to compose and match DNA 22:44:54 kcoyle: feel free to make suggestions 22:45:58 PWinstanley: it's about patterns/strategies 22:47:24 rrsagent, please draft minutes 22:47:24 I have made the request to generate https://www.w3.org/2019/02/14-profgui-minutes.html antoine 22:49:37 +1 for these edits.. 23:03:22 rrsagent, create minutes v2 23:03:22 I have made the request to generate https://www.w3.org/2019/02/14-profgui-minutes.html PWinstanley