20:17:03 RRSAgent has joined #profgui 20:17:03 logging to https://www.w3.org/2018/08/22-profgui-irc 20:17:12 rrsagent, make logs public 20:17:24 rrsagent, create minutes v2 20:17:24 I have made the request to generate https://www.w3.org/2018/08/22-profgui-minutes.html kcoyle 20:18:40 present+ 20:18:49 present+ 20:18:54 Agenda for this meeting is https://www.w3.org/2017/dxwg/wiki/Meetings:ProfGui-Telecon2018.08.21 20:18:58 present+ 20:19:08 present+ 20:20:13 scribenick: kcoyle 20:20:47 topic: admin 20:21:01 regrets+ antoine, Lars 20:21:16 rrsagent, create minutes v2 20:21:16 I have made the request to generate https://www.w3.org/2018/08/22-profgui-minutes.html kcoyle 20:21:28 topic: confirm agenda 20:21:41 topic: topics 20:21:49 ncar: discuss scope of the group 20:21:57 ... how will group procede 20:22:19 ... how to deal with requirements? list in the document? 20:22:33 +q 20:22:35 ... address them in the document 20:22:50 ack alejandra 20:23:27 q+ 20:23:29 alejandra: question about scope - we are not supposed to do profiles; odd to produce document without some examples 20:23:42 ... need to provide some idea of how it would be implemented 20:23:52 q+ 20:24:01 ack kcoyle 20:24:03 ncar: I do profiling in my work 20:24:55 https://www.w3.org/2017/dxwg/charter 20:25:46 kcoyle: charter says creating profiles is out of scope 20:25:49 ack roba 20:26:03 q? 20:27:00 roba: there are ranges of communities of practice for creating profiles 20:27:21 ... guidance should be how to do it better; so we can look at existing examples 20:27:31 ... geo-dcat, etc. 20:27:50 from the charter: "A definition of what is meant by an application profile and an explanation of one or more methods for publishing and sharing them." 20:28:09 ... an analysis of what is happening in profile land and how we can support that process 20:28:34 ... defining profile itself is idiosyncratic around community practices 20:29:03 ... general process is not a DCAT profile 20:29:19 ... look for best practices and requirements 20:30:06 ... but not generic profiling language, but support discoverability, conneg, etc. and tying profile to resources 20:30:22 ... some requirements will not have a best practice 20:30:55 ncar: have done profiles of ISO standards; we followed actions that we knew from before, but we had no guidance 20:30:59 +q 20:31:07 ack alejandra 20:31:20 alejandra: we already have a list of DCAT profiles 20:31:23 q+ 20:31:32 ... we should reference existing practice 20:31:51 ncar: have profiles for iso standards as used in Australia 20:32:14 alejandra: I was proposing to collect a list of existing profiles, which nicar has already been compiling 20:32:24 ... rob could gather igc profiles 20:32:51 ack kcoyle 20:33:50 where is the outline? 20:33:56 and in the use cases : DCAT and europeana at least 20:34:16 q+ 20:34:19 https://w3c.github.io/dxwg/profiles/ 20:34:22 kcoyle: need a wide range of profiles; e.g. from many communities 20:34:24 ack roba 20:34:36 +1 to put them directly in the document 20:34:38 https://www.w3.org/2017/dxwg/wiki/ProfileRoundup 20:35:15 roba: if you list these then you have to show how they relate to each other 20:35:29 ... need to describe them formally 20:35:52 Profiledesc profiles examples: https://github.com/w3c/dxwg/tree/gh-pages/profiledesc/examples 20:35:55 https://github.com/w3c/dxwg/issues/242 for a variety of outline 20:36:11 roba: could be included in document 20:37:13 ncar: has pull request , kcoyle doesn't agree 20:39:28 ncar: listing of profiles; have a mechanism to describe profiles; and populated already 20:39:47 action: ncar list other profiles in profileDesc space 20:42:43 q+ 20:43:55 ack roba 20:45:46 roba: there are no perfect profiling languages, but still need to say what profiles exist 20:46:01 ... what the profiles describe may come out of the requirements 20:46:21 ... but not saying dataqube 20:46:24 q+ 20:47:55 ... we have a metamodel for profiles; but we have to catalog the profiles first 20:48:03 ack kcoyle 20:48:41 q+ 20:49:08 asck ncar 20:49:14 ack ncar 20:49:44 kcoyle: we have requirements that are about the functionality of profiles 20:50:31 q+ 20:51:13 ncar: in general, when you do profiles, this is what you can do (this would be the document) 20:51:39 ... then you describe the environment 20:53:16 ack roba 20:54:31 roba: some misconceptions; profdesc should not be in the guidance document? but we need to highlight best practices 20:54:39 q+ 20:55:07 ... we will refer to shacl and shex; we can't give a recommendation to use those and ignore the rest of our requirement 20:55:28 ... we can publish it saying this requirement will need to be met with an ontology 20:56:10 ... nature of guidance doc is to tease out best practices 20:56:23 ... do we leave it at that, or do we publish an ontology? 20:56:37 ack kcoyle 20:58:33 +q 20:58:55 ack alejandra 20:59:24 alejandra: what I'm hearing is that the charter gives us something very generic; guidance could just be a description, or it could go deeper 20:59:48 ... or it could speak of ontologies 21:03:02 https://www.w3.org/2017/dxwg/wiki/ProfileRoundup 21:03:09 https://www.w3.org/2017/dxwg/wiki/ProfileRoundup 21:04:00 +q 21:04:27 ack alejandra 21:06:55 action: ncar do examples for the plenary of options for profileDesc 21:07:51 rrsagent, create minutes v2 21:07:51 I have made the request to generate https://www.w3.org/2018/08/22-profgui-minutes.html kcoyle 21:08:03 present-