13:55:02 RRSAgent has joined #dxwg 13:55:02 logging to http://www.w3.org/2017/06/26-dxwg-irc 13:55:04 RRSAgent, make logs public 13:55:04 Zakim has joined #dxwg 13:55:06 Zakim, this will be 13:55:06 I don't understand 'this will be', trackbot 13:55:07 Meeting: Dataset Exchange Working Group Teleconference 13:55:07 Date: 26 June 2017 13:55:29 regrets+ Ruben, Peter_Winstanley, Antoine, Colleen_Fallaw, Eric_Stephan 13:55:43 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2017.06.26 13:55:50 chair: Karen 13:55:52 present+ 13:56:04 RRSAgent, draft minutes 13:56:04 I have made the request to generate http://www.w3.org/2017/06/26-dxwg-minutes.html phila 13:56:11 RRSAgent, make logs public 13:56:35 present+ Dave_Browning 13:56:52 present+ 13:56:53 alejandra has joined #dxwg 13:56:56 LarsG has joined #dxwg 13:57:08 present+ 13:57:21 Chair: Karen Coyle 13:57:49 present+ 13:58:58 SimonCox has joined #dxwg 13:59:10 the password has not been shared yet I think? 13:59:20 for webex, I mean 14:00:05 mdaquin has joined #dxwg 14:00:53 Roba has joined #Dxwg 14:01:15 present+ 14:01:31 Thomas has joined #dxwg 14:01:35 present 14:01:39 present+ mathieu 14:01:44 present+ 14:01:46 regrets+ Luiz, Newton 14:01:46 Am in ogc meeting and cant currently dial in but will watch the irc 14:02:14 What's the webex pw? 14:02:35 thx 14:02:44 phila has changed the topic to: Dataset Exchange Weekly Call. See below for new PW 14:02:54 present+ 14:03:28 Present__Ixchel has joined #dxwg 14:03:34 achille_zappa has joined #dxwg 14:04:10 * i think i lay be the only temporary newfoundlander 14:04:53 annette_g has joined #dxwg 14:04:58 MJ_Han has joined #dxwg 14:05:14 Caroline_ has joined #DXWG 14:05:32 Present+ 14:06:09 scribe: LarsG 14:06:13 ScribeNick: LarsG 14:06:25 Topic: Preliminaries 14:06:31 Topic: Approve last week's meeting minutes 14:06:54 Resolved: approved last weeks minutes (NOTUC) 14:07:08 Topic: new attendees? 14:07:11 present+ annette_g 14:07:20 No new attendees 14:07:31 RiccardoAlbertoni has joined #DXWG 14:07:33 Caroline_: new password is webexdxwg 14:07:40 Topic: Reports from sub-groups 14:07:47 s/Caroline_: new password is webexdxwg// 14:07:59 present+ MJ_Han 14:08:21 No reports from sub-groups 14:08:40 kcoyle: wants to know if DCAT group has met 14:09:10 alejandra: DCAT has exchanged a few emails but hasn't met yet. 14:09:11 present+ nandana 14:09:14 q+ 14:09:16 ... will keep us posted 14:09:30 present+ RiccardoAlbertoni 14:09:35 kcoyle: so far we have approved three use cases 14:09:38 q- 14:09:48 ... today we discuss are modelling temporal coverage, 14:09:58 ... modelling spatial coverage 14:10:07 ... and data access restrictions. 14:10:15 https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_temporal_coverage 14:10:49 temporal coverage submitted by Andrea (who isn't here) 14:10:50 Make sure to use https://www.w3.org/TR/owl-time/ :-) 14:11:13 ... DCAT say to use dct:temporal 14:11:23 q? 14:11:26 ... SimonCox proposes owl-time 14:11:36 q+ 14:11:38 Can we add to the links the following ones: http://github.com/biocaddie/WG3-MetadataSpecifications 14:11:46 present+ achille_zappa 14:11:46 and https://developers.google.com/search/docs/data-types/datasets 14:11:53 q? 14:11:56 https://www.w3.org/TR/owl-time/#time:hasEnd etc 14:12:03 where also temporal coverage have been considered 14:12:11 kcoyle: If people have more links, they can add that to the wiki page 14:12:16 q+ 14:12:25 ack m 14:12:28 roba_ has joined #dxwg 14:12:41 present+ Rob Atkinson 14:12:56 Makx: reacting to Andrea ADMS and DCAT-AP use schema:start and schema:end since owl-time looked too complicated 14:13:01 ack m 14:13:05 ack a 14:13:06 ack a 14:13:08 ... many European data portals use that, too 14:13:14 * online for next 30 mins 14:13:26 alejandra: Question about process: When I have comments or links 14:13:36 q+ 14:13:53 ... can I modify the UC directly in the Wiki or should it go through the UC editors? 14:14:02 Jaroslav_Pullmann has joined #dxwg 14:14:02 owl-time seems complicated but there can be more complex things to represent than just start and end dates 14:14:10 present+ 14:14:32 I am sorry for being late, could you please pass me the new pwd? 14:14:43 +1 to put to working use cases document. 14:14:45 Present__Ixchel: If it's something that hasn't been discussed yet, just add it so that it's there for the meeting. Otherwise send an email to the editors 14:14:51 thanks! 14:14:53 ... and they'll add it 14:14:55 q? 14:15:03 s/I am sorry for being late, could you please pass me the new pwd?// 14:15:10 alejandra: Agrees with that process. 14:15:41 kcoyle: From XXX there is a link to the working space 14:16:14 kcoyle: there is no way to see which UCs we have discussed just by looking at the list 14:16:29 regrets+ Martin 14:16:44 Roba: plans to put a link to the consolidate use case 14:16:51 ... status is more complicated 14:17:02 ... some things may be solved, others not 14:17:17 q+ 14:17:26 ... e. g. profile might be discussed but discovery of profiles not 14:17:45 kcoyle: You can split the UCs to have more atomic parts. 14:17:52 ack ma 14:17:52 ack M 14:17:57 ... important for people to see what is resolved 14:18:37 I think that is good 14:18:46 to add things to use cases that have not been discussed 14:18:55 Makx: has put something in alejandra's UC. Has marked with his name but wants to know if that's OK 14:19:08 Present__Ixchel: Good idea. 14:19:22 q? 14:19:23 I agree on pinging the original author 14:19:25 ... If you want the orig author to look at it again, send a mail to the author 14:19:34 ... and the list 14:19:47 Jaroslav_Pullmann: Finds Makx's approach a good idea. 14:19:56 ... People can use the comment section 14:20:18 ... Status intended to be used as a progress indicator 14:20:32 ... has started to create a mind map for the UC (has lost overview) 14:20:45 ... prepares a graphical view of the UCs 14:20:50 ... will share the URL 14:20:55 q? 14:21:01 ack 14:21:18 ack J 14:21:35 kcoyle: should we mark this UC as good, can we vote? 14:21:42 -> https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_temporal_coverage 14:21:48 q+ 14:22:01 -> https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_temporal_coverage Modelling Temporal Coverage 14:22:14 https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_temporal_coverage 14:22:21 q+ 14:22:35 ... question is: Is it a valid UC that reflects requirements? 14:22:41 q+ 14:22:42 q+ 14:22:46 q+ 14:22:52 q- 14:22:53 ack annette_g 14:22:59 annette_g: There are more complicated cases 14:23:08 q- 14:23:28 ack alejandra 14:23:46 ... they should be expanded through discussion 14:23:48 ack SimonCox 14:24:00 alejandra: Edge cases not so important 14:24:16 q+ 14:24:32 SimonCox: Title is wrong. More about serialisation (how to serialise beginning and end) 14:24:41 modelling is covered by scope of http://w3c.github.io/sdw/qb4st/ 14:25:25 ... the description points out that in DCAT a URI is used to describe the time. That is considered cumbersome 14:25:27 q+ 14:25:39 ... it's about the representation, not the content 14:25:46 ... per se 14:26:05 ... that is an old problem, when the issue is about modelling and when about syntax/representation 14:26:19 kcoyle: Suggests to change the title 14:26:29 ack roba_ 14:26:48 q- 14:27:00 roba_: It's neither syntax nor modelling, but more about a summary: DCAT proposes simplified view. Author might 14:27:14 ... be simple, but provenance more deeply modelled 14:27:45 q+ 14:27:49 ack J 14:27:52 ... spatio-temporal extent can be done through QB4ST as begun in SDW 14:28:22 Jaroslav_Pullmann: agrees. This is more about representation (date format) and might break down into simple properties 14:28:32 ... part of an overall modelling context 14:29:01 q? 14:29:03 +q 14:29:08 ... and that way put into a bigger relation 14:29:55 Present__Ixchel: speaking from the user perspective. It's about understanding the different kind of temporal coverage. E. g. start and end of 14:30:30 q? 14:30:31 q+ 14:30:34 ... data acquisition. It's about bringing data together using their temporal contexts 14:30:39 ack Present__Ixchel 14:31:20 q- 14:31:25 ack a 14:31:27 q+ 14:31:38 alejandra: Agrees. We also need to discuss the capabilities of DCAT. Obvious cases are dataset creation and modification. But also acceptance on DataCite. 14:31:40 +1 to alejandra I was going to same something similar 14:31:42 q+ 14:31:54 ... We need a very flexible way to handle different kinds of dates 14:32:01 ack Makx 14:32:58 Makx: Wonders if it's useful to change the scope of a UC. The UC builds on a real need and is a simple requirement. 14:33:14 ... There are also a wider issue of modelling temporal aspects 14:33:15 q? 14:33:19 ... but not in this UC 14:33:23 Agreed, Makx 14:33:38 ack J 14:33:45 Jaroslav_Pullmann: relevance of the data is also important when searching for data in a catalogue. 14:33:58 ... Some dates are fixed (distribution etc.). 14:34:16 ... DCAT already has the catalogue record element for such things. 14:34:37 ... Makx's focus is the temporal data itself, not of the dataset 14:34:47 kcoyle: Do we need another UC? 14:34:55 types of dates - will it be a closed list? 14:34:56 Jaroslav_Pullmann: Yes, maybe a meta-UC 14:35:05 q+ 14:35:27 q+ 14:35:33 kcoyle: There is a problem putting too much into a single UC 14:35:41 ... better to have simple specific UCs 14:35:47 ... Who can do that? 14:36:16 alejandra: DataCite has specific types of dates. 14:36:21 q+ 14:36:34 ... that's an existing approach we can follow 14:36:50 ... E. g. when the data was collected. That goes into processes 14:37:05 q? 14:37:06 keep this one as it is, please 14:37:13 riccardoAlbertoni has joined #dxwg 14:38:06 q- 14:38:13 ack roba_ 14:38:21 roba_: This UC is about what we want to put into simple properties in DCAT. Should have a simple model. 14:38:31 ... We probably don't need another UC for that 14:38:51 ... but should have one simple UC (as a meta-UC) and one more deeply into modelling 14:39:17 q? 14:39:22 ... We can add another UC to the working space and map that to the existing 14:39:26 +1 to kcoyle "adding further use cases on time issues" and keep this uc simple. 14:39:40 Jaroslav_Pullmann: Would this be a UC like "temporal aspects in DCAT"? 14:39:59 ... and then bring everything temporal into that 14:40:12 kcoyle: we shouldn't be too abstract 14:40:28 +1 to keeping things practical 14:40:31 ... when we look at UCs at a high level they have much in common 14:40:41 ... but we need to keep it practical 14:41:18 Jaroslav_Pullmann: thought we could have one for all temporal dimensions in DCAT (API availability) all rooted in one meta-UC 14:41:42 kcoyle: Jaroslav_Pullmann shouldn't hesitate to create one if needed 14:42:00 q+ 14:42:02 I vote for keeping it 14:42:03 kcoyle: shall we edit the UC first or can we vote directly? 14:42:09 q+ 14:42:17 +1 for keeping it but adding what's missing 14:42:21 ack Jaroslav_Pullmann 14:42:29 Jaroslav_Pullmann: agrees with Makx that we should edit the UC first 14:42:34 what is missing? 14:42:47 agree with keeping it but rename it - its not modelling.. 14:43:04 q- 14:43:08 PROPOSE: accept ID29 and edit it to be specifically about start and end dates; and modify title to remove modeling 14:43:09 q+ 14:43:33 SimonCox: does that mean start and end date of the data set (the record)? 14:43:52 this is the data itself 14:44:11 no this is not want the UC is about 14:44:18 record is overloaded term.. be careful 14:44:27 Jaroslav_Pullmann: it's about the adding to the catalogue (the record) not the contents of the data set. 14:45:05 q+ 14:45:13 i think we are talking about the temporal coverage of the data - but we need to narrow down the semantics - observation time or phenomemon time 14:45:17 SimonCox: the date of an observation is not always the same as what we are interested in (e. g. geological discovery vs. geological event) 14:45:44 q? 14:45:46 ... there are properties for that 14:45:56 acvk SimonCox 14:46:01 ack SimonCox 14:46:05 ack m 14:46:42 PROPOSE: accept ID29 and edit it to be specifically about start and end dates of the dataset; and modify title to remove modeling 14:46:43 +1 14:46:46 Makx: wants to clarify: it's about the year the (budget) data applies to, not about when the dataset was created 14:46:52 q+ 14:47:11 q+ 14:47:17 ack j 14:47:19 +q 14:47:30 s/PROPOSE:/PROPOSED:/ 14:47:42 ack annette_g 14:47:42 Jaroslav_Pullmann: So it's about the temporal context of the data (phenomenon time), not about observation time 14:47:45 SimonCox: Yes 14:48:16 q+ 14:48:17 q+ 14:48:29 annette_g: Thought this would be more about deep thoughts about start and end dates. We shouldn't remove those from the UC or the discussion 14:48:43 ack alejandra 14:48:50 disagree with extending use cases too much 14:49:18 alejandra: the UC talks about start and end date. But when you work with time series you want intermediate points, too. That's also part of temporal coverage 14:49:24 intermittent periods is covered because dct:coverage is repeatable 14:49:31 ... similar things in other UCs 14:49:39 kcoyle: we need more UCs on that topic 14:49:45 ack Sim 14:50:12 SimonCox: we need to be more clear about specific requirements vs cross-domain reqs 14:50:30 ... [other WG had 13 different kinds of dates] 14:50:47 ... that was a very specialised application (weather forecasting) 14:50:57 ... and there might be scientific cases in the future 14:51:10 ... which leaves us with the dilemma that DCAT is 14:51:28 ... general purpose which needs to be applicable in several 14:51:50 ... domains but also needs to be applied to specific communities' needs 14:52:18 q+ 14:52:47 ... We need to find the right balance 14:52:49 ack Thomas 14:53:23 Thomas: doesn't think we can capture all semantics in one simple model 14:53:41 ... the dataset describer needs to use what works for them 14:54:11 ack annette_g 14:54:17 ... In specialist datasets there are dates that care for phenomenon time 14:55:04 annette_g: we shouldn't try to make DCAT work for all scientific communities, but it should be easier to use if for the scientific community (uptake has been slow) 14:55:27 PROPOSED: accept ID29 and edit it to be specifically about start and end dates of the dataset; and modify title to remove modeling 14:55:40 +1 14:55:45 +1 14:55:45 +1 14:55:46 +1 14:55:46 +1 14:55:47 +1 14:55:48 +1 14:55:50 +1 14:55:51 +1 14:55:51 +1 14:55:54 +1 14:55:57 +1 14:56:00 +1 14:56:11 +1 14:56:13 it's ID27 14:56:15 q+ 14:56:19 +1 14:56:30 s/29/27 14:56:34 +1 14:57:04 alejandra: if we remove modelling, does that mean that we only talk about start and end dates? 14:57:20 +1 14:57:24 Can we review UC1 to see if it covers general modelling of aspects, including time and suggest improvements please 14:57:30 kcoyle: we can add modelling back again if necessary, but for now, yes 14:57:30 review offline 14:57:58 In Requirements, spatial should be temporal. 14:58:03 kcoyle: yes, roba_ , we can do that on the list or at the Oxford F2F 14:58:40 Topic: Research Data 14:59:23 phila: Talked to WG chairs of RDA and then with people at CODATA (umbrella body for science unions) 14:59:40 ... much potential interest in this WG but also in the general 14:59:58 ... idea of research data as shared information on the web 15:00:10 ... phila plans to continue with this 15:00:32 ... RDA und CODATA watch this WG in order to make the web 15:00:42 ... a large information space 15:00:43 +1 exciting stuff! 15:00:48 As phila mentioned, I'm involved with RDA and CODATA so will keep links intact 15:01:02 kcoyle: next week we'll discuss more UCs 15:01:36 phila: If we discuss the outputs of this group in a subgroup, keep the mailing list in the loop to have it public 15:01:40 +1 to discuss in public :) 15:01:46 bye! thank you! 15:01:50 bye all 15:01:52 bye! 15:01:57 bye... 15:01:57 good night 15:01:58 bye 15:02:01 bye 15:02:08 RRSAgent, draft minutes v2 15:02:08 I have made the request to generate http://www.w3.org/2017/06/26-dxwg-minutes.html phila 15:02:34 present- 15:02:46 Thanks Lars for scribing!! 15:02:54 RRSAgent, draft minutes v2 15:02:54 I have made the request to generate http://www.w3.org/2017/06/26-dxwg-minutes.html phila 15:45:02 RRSAgent, bye 15:45:02 I see no action items