13:00:19 RRSAgent has joined #sdwcov 13:00:19 logging to http://www.w3.org/2016/08/10-sdwcov-irc 13:00:21 RRSAgent, make logs world 13:00:21 Zakim has joined #sdwcov 13:00:23 Zakim, this will be SDW 13:00:23 ok, trackbot 13:00:24 Meeting: Spatial Data on the Web Working Group Teleconference 13:00:24 Date: 10 August 2016 13:00:27 present+ kerry 13:00:39 present+ billroberts 13:00:40 chair: bill roberts 13:00:51 regrets+ scottsimmons 13:01:21 present+ dmitrybrizhinev 13:09:08 roba has joined #sdwcov 13:09:11 sam has joined #sdwcov 13:10:34 https://www.w3.org/2016/07/27-sdwcov-minutes 13:11:18 PROPOSED:approve minutes of last meeting 13:11:21 scribenick roba 13:11:26 +1 13:11:36 +1 13:11:36 +1 13:11:41 scribenick: roba 13:11:51 scribe: Rob Atkinson 13:12:03 +1 13:12:11 https://www.w3.org/2015/spatial/wiki/Patent_Call 13:12:24 RESOLVED: minutes approved 13:12:40 https://www.w3.org/2015/spatial/wiki/Meetings:Coverage-Telecon20160810 13:14:12 https://github.com/ANU-Linked-Earth-Data/ontology/blob/master/ANU-LED.owl 13:14:18 sam - we can see you are nearly on webex - dmitry will go first on his part of the work 13:14:18 https://github.com/ANU-Linked-Earth-Data/ontology/blob/master/ANU-LED-example.owl 13:17:16 dmitrybrizhinev: most of the work of defining a coverage compatible with way datacube works. 13:17:45 ...have defined subProperties of geo:location etc for cells 13:18:06 ...explained another DGGS example 13:18:29 ...support SPARQL queries over image metadata 13:18:36 q+ 13:18:52 q+ 13:19:48 roba: has also been looking at an ontology that builds on QB for spatial concepts 13:20:10 roba asks about qb dimensions for basic geospatial concepts -- no problem with you defining lat/long in your own namespace and a broader one might be better 13:20:27 dmitry: yes 13:20:54 roba: a subproperty of WGS 84 CRS may not be a useful coord system 13:21:18 dmitry: yes when there is a tem as advised by BP gropu we should subclass that 13:21:25 roba; will suggest something tomorrow 13:21:28 ack r 13:21:32 ack b 13:22:16 billroberts: this is and rdf approach top tiliing, with metadata in rdf, is a way towards metadata discovery. 13:22:17 bill: is an RDF approach to tiling 13:22:29 ...are you looking for a rdf version of what is in the image? 13:22:37 kerry cant help scribing :-) 13:23:57 q? 13:24:02 q+ 13:24:09 dmitrybrizhinev: SSN has capabilities? 13:24:11 ack k 13:25:26 kerry: featureofinterest missing in example - what is it for coverage 13:28:30 kerry: we should ask Peter Baumann 13:29:31 roba: feature of interest is the thing that has a property whose value is the coverage range (i think) 13:30:17 kerry: deployment metadata would be useful 13:30:50 ...use PROV to talk about processing 13:31:07 what is on coverage BP scope/ 13:32:36 roba: feels that current practices for describing coverage metadata is not good enough 13:36:48 q+ 13:37:01 roba: suggests we focus primarily on describing the spatio-temporal aspects of coverages 13:37:20 ack sam 13:37:20 ...including the "range envelope" 13:38:16 sam: RDF QB not designed for serialising dense grids - but useful for description 13:38:40 ...materialising subset over the wire may be useful though 13:39:41 sam: experience/experiment? is storing data in HDF 13:40:14 ...serving in RDF 13:40:43 use case is also describing any access method - e.g. WCS 13:42:54 roba: have you done anything reasoning over descriptions? 13:43:05 sam: not yet 13:43:31 q+ 13:43:37 ack q 13:43:40 qxk k 13:43:46 ack kerry 13:48:21 q+ 13:48:40 ack k 13:51:53 roba: is it reasonable to ask the user "figure out on your own how to write the query that will give you the metadata you want?" 13:52:39 What I want is give me the entire graph of your metadata, but without the metadata, as a thing 13:52:56 roba: What I want is give me the entire graph of your metadata, but without the data, as a thing 13:53:36 kerry: "something like select * ?" 13:53:56 roba: You might be able to find a best practice, but there needs to be a shortcut, a best practice 13:54:07 roba: You might be able to find a pattern, but there needs to be a shortcut, a best practice 13:54:34 billroberts: This is why we need a well defined data model 13:54:46 billroberts: ... so the common tasks for the user are simple 13:55:37 roba: it's nice having a data model with both data and metadata, but it makes it harder to say "give me all the metadata without the data" 13:55:53 roba: so we need a best practice to say that the metadata on its own should be easily accessible 13:56:14 roba: have a data model that can support both description and serialisation 13:56:38 q+ 13:57:03 roba: have a look at the existing working group requirements, maybe we need to define a new one 13:57:14 sorry, I keep making errors 13:57:22 billroberts: have a look at the existing working group requirements, maybe we need to define a new one 13:58:29 roba: I'll take an action to write up a usecase for rdf metadata description 13:58:43 ack k 13:59:05 roba: I want prov, I want SSN, I want that extensible description 13:59:20 kerry: one of my favourite things about rdf is it doesn't distinguish between data and metadata 13:59:29 kerry: you can treat it as a view of the data 13:59:43 roba: yes I would treat it as a view of the data, but the way to do this is not yet standard 14:00:09 billroberts: please write up examples of some of the things you would want to retrieve 14:01:43 maybe - maybe thats an implementation detail ? 14:02:13 +1 and me too 14:04:09 RRSAgent, draft minutes 14:04:09 I have made the request to generate http://www.w3.org/2016/08/10-sdwcov-minutes.html billroberts 14:04:18 thanks bye 16:11:13 Zakim has left #sdwcov