19:58:08 RRSAgent has joined #sdwcov 19:58:08 logging to http://www.w3.org/2016/03/09-sdwcov-irc 19:58:13 Zakim has joined #sdwcov 19:58:19 RRSAgent, make logs public 19:58:31 meeting: SDW Coverages Sub Group 19:58:50 present+ dmitrybrizhinev 19:59:18 present+ billroberts 19:59:21 agenda: https://www.w3.org/2015/spatial/wiki/Meetings:Coverage-Telecon20160309 19:59:27 Chair: Bill 19:59:27 present+ sam_t 19:59:34 present+ PhilA 20:00:21 present+ kerry 20:00:50 issue-18? 20:00:50 issue-18 -- Model Reuse -- open 20:00:50 http://www.w3.org/2015/spatial/track/issues/18 20:03:30 https://github.com/Reading-eScience-Centre/coveragejson/ 20:03:36 https://github.com/Reading-eScience-Centre/coveragejson/blob/master/spec.md 20:04:10 scribe: phila 20:04:15 scribeNick: phila 20:04:30 billroberts: No minutes of the previous meeting to worry about 20:04:41 Topic: Patent call 20:04:44 https://www.w3.org/2015/spatial/wiki/Patent_Call 20:04:46 https://www.w3.org/2015/spatial/wiki/Patent_Call 20:05:30 billroberts: Main suggestion for today is to try to go over the scope of the things we're meant to do, set objectives and then get on with it. 20:05:44 ... Maybe a schedule may be too ambitious for today but we can get some ideas. 20:06:02 https://www.w3.org/2015/spatial/charter 20:06:19 billroberts: Points to the charter's wording related to coverages. 20:06:59 ... In Amersfoort it was clear that we're interested in all sorts of coverages and subsets. 20:07:21 ... In the F2F meeting we starting to home in on the CoverageJSON work from Uni Reading as a good starting point 20:07:40 ... We shoujld probabyl check that people think that's a good idea. 20:08:08 ... And what our requiremetns are for a Recommendation - what does it need to do to satisfy the WG, making it Webby enough. 20:08:20 q+ 20:08:21 ... So, comments welcome 20:08:27 ack k 20:08:55 kerry: I'm afraid I wasn't in Amersfoort, and only saw the demo from a distance. I would like to push a bit harder to get he RDF data Cube working with what we do. 20:09:08 ... Which may be a query model rather than a delivery model. 20:09:29 ... I'm keen not to take Coverage JSON at face value, we should try to go a little harder to go on the LD route. 20:09:55 ... There's something from Munster that had more of a data Cube flavour to it, but it dealt with smaller sets 20:10:21 ... But I don't want to deny that what's being done at Reading isn't very good. 20:10:46 billroberts: I think Reading have attempted to come up with a representation that works well with typicl Web tools but it's not the only possible approach. 20:10:59 ... So some way of testing options against criteria would be good. 20:11:11 ... is option A better than option B anad in what respect. 20:11:34 ... That might be a difficult thing to do. What makes something Webby? We can link to it. 20:11:46 +q 20:11:52 ... Shoujld be able to request over HTTP. It would be good if the bits of HTTP like conneg could be used. 20:12:16 ... There's an interesting discussion around conneg around max resolutions, max data size etc. 20:12:26 ... And it needs to play nicely with other common Web approaches. 20:12:43 ... That's what makes it suitable for being on the Web, but that's not a very retsrictive set. 20:13:06 ... But UI'd be happy to have a strand that looks into the CoverageJSON work and one that looks at QB, or an evolution of it. 20:13:30 ... Especially when it comes to subsetting. I think QB has a lot of potential on that. 20:13:39 ... QB is verbose, so if the coverage is small enough, that won't matter. 20:13:40 ack k 20:14:08 kerry: I agree. We do have a list of well developed ideas about what makes data more webby in our own BP doc. 20:14:27 ... And I think we might be making a rod for our own back if we try and deliver everything. 20:14:29 q+ 20:14:51 kerry: Maybve we just need to point to what we think is most important, for a start. Good characteristics etc. 20:14:57 ack phila 20:15:17 q+ 20:16:16 q- 20:16:34 -> https://github.com/Reading-eScience-Centre/coveragejson/blob/master/spec.md Example 1.1 20:17:05 phila: describes what's in this example. In a few lines of JSON, it sets out all the domain details 20:17:41 phila: covers multidimensional grids, not (yet) point clouds 20:18:12 phila: that domain specification could potentially be defined in RDF, either RDF Data Cube or something that maps clearly to it 20:18:57 phila: CSVW WG defined how to define metadata for tabular data that defined how it could be transformed to RDF 20:19:06 phila: some commonality there wtih the things we have to do 20:19:30 phila: Maik from Reading emphasises that CoverageJSON is early experimental work 20:19:58 phila: the opportunity to have the ANU team to look at this in detail and suggest improvements 20:20:04 phila: metadata is easy 20:20:25 phila: providing values within the coverage prob doesn't make sense as triples, which would be too verbose 20:20:47 phila: but defining the domain in a way that draws on data cube looks promising 20:21:04 phila: this needs testing, I may well be talking rubbish 20:21:34 q+ 20:21:35 phila: it would be good to investigate if CoverageJSON and RDF Data Cube can be combined in some way 20:21:40 ack kerry 20:21:54 kerry: That sounds like a good plan. What Chris mentioned in the last meeting... 20:22:11 ... the QB may not be granukar enough. WE need dicing as well as slicing - which makes sense 20:22:30 ... And the other comment was... what do the team here think? 20:22:44 ... This is a student project and they get a lot of say in what they do. It's a fairly open-ended spec 20:22:57 ... the spec is to work with the WG and deliver stuff that the group can use 20:24:00 kerry: The group here is already tied to an infrastructure environment that they're working with. It's different from what the Reading is working on. 20:24:11 .. and they're working with another OGC spec @@@ 20:24:22 ... whichy seems to fit very well. 20:24:41 s/@@@/DGGS/ 20:24:50 q+ 20:24:56 ack d 20:25:21 Duo: Hi... I guess my role as team leader, client application developer. 20:25:35 ... What we've been working on is very rought, just setting up the raw data that we have and playing around with it. 20:25:56 ... So we haven't started looking at what we might use it for, so we're open to what you'd like us to do with it. 20:28:10 phila: the working group can interpret the charter as it sees fit. We don't necessarily have to make a specification 20:28:23 ...there isn't a predefined answer, so it's ok to follow the directions that come up in the research 20:29:37 billroberts: The basic objective is clear - there is this big collection of data from satellites etc. that is not being made best use of in the Web community because it's too difficult sand if we can make it play more nicely with the Web then that's good. 20:30:03 ... One task that I had from a few weeks ago was to go through the existing use cases to see how they look fromn the POV of our coverage work. 20:30:20 -> https://www.w3.org/TR/sdw-ucr Use Case doc 20:30:49 billroberts: What's harder to tell is whether they are sufficient. I;m not sure that the translation from the UCs to the Reqs is helpful enough to head towards a solution. 20:30:54 action-144? 20:30:54 action-144 -- Bill Roberts to Review the use cases from a coverages point of view -- due 2016-02-16 -- OPEN 20:30:54 http://www.w3.org/2015/spatial/track/actions/144 20:31:35 billroberts: I can document what I came up with and make some suggestions for refining those requirements. That would be a starting point, and we have the BPs as a guide too. 20:32:02 phila: Will there be a new version of the UCR? 20:32:23 kerry: Yes. And Frans is expecting the sub groups to come up with new stuff that needs to be incorporated. 20:32:45 s/new stuff/better stuff/ 20:32:55 ... A more refined description of the requirements. 20:33:16 billroberts: The reqs at the moment are very much at the summary level. I think we can probably fill those out in a bit more detail. 20:34:48 billroberts: A suggestion - could the ANU team take a look at the UCR and see how that fits with the GSA data Cube data 20:35:08 ... What kind of applications do you see? etc. 20:35:50 Duo: I think that at this stage, we are still trying to figure out what you guys are doing. We're also working with Kerry and Matt from GSA who might be having different requirements from the SDW WG. 20:35:56 ... We need to work with both teams. 20:35:58 s/GSA/AGDC/ 20:36:07 q+ 20:36:09 ... But it would be good to get clarity on what you want. 20:36:24 s/GSA/AGDC/g 20:36:33 ack k 20:37:32 kerry: Just to support that. The team is not use case driven. They're not working with users of the data. Matt does work with data users though. 20:38:17 ... Matt is looking for something that in his work with GDDS can deliver against the interoperability requiremetn that he has. He's not imposing abything beyond what this group is doing, just to be able to use GDDS. 20:38:37 ... It really is open ended. Taking the advice from this group is the way to get maximum impact from the project. 20:39:04 ... The team is comfortable with it being very experimental. 20:39:14 ... They're well matched for it to be an experimental project. 20:40:04 billroberts: Something I'd find useful, is some good worked examples of you taking some example satellite data of interest and showing what are the steps you have to do to get hold of it, process it, filter it, how it refers to POIs on the ground etc. 20:40:30 Yadu_ has joined #sdwcov 20:40:49 phila: agrees. Running code beats everything. 20:41:59 phila: the Reading work has been a compelling example because it clearly works and we can see that it takes satellite data and makes it usable in a browser 20:42:27 phila: would be great to see similar things from the ANU team 20:43:00 phila: this project is an opportunity for ANU to demonstrate a lot of impact from their work through involvement in the group 20:43:04 q+ 20:43:10 ack d 20:43:37 Duo: I think everyone in the team is super keen. Everyone's inetersted, especially as it is so open ended. 20:43:47 q+ 20:43:54 ack k 20:46:26 +1 to wiki 20:46:50 billroberts: I propose that we spend time on that stuff around use cases and requirements. Looking at the BPs in the context 20:46:59 ... I'll do that on the wiki in the next couple of days. 20:47:13 ... We can use the mailing list to prod people once that's in existence. 20:47:37 ... From there then I guess we want to scope out possible solutions and check them against the requirements. Maybe Maik can do that. 20:48:07 ... Maybe he can look through that in the context of the CoverageJSON stuff, might he need to/want to tune his work etc. 20:48:26 ... Would you, Kerry, be interested in how the Data Cube might relate to that? 20:48:36 ... Exploring and making some working notes? 20:49:00 kerry: I'd live to say yes but honestly I'm not sure I can between now and the next meeting. 20:49:11 ... (I have SSN stuff to work on etc.) 20:49:37 billroberts: I;m happy to do a little on that. I'll at least make a QB for Coverages wiki page and see if we can promot ideas from other people 20:50:34 kerry: I'm intrested and keen on this but I'm not sure how much I can add given other roles in the WG. 20:50:50 billroberts: A procedural thing... 20:51:04 ... Our first milestone is the FPWD. WE have to work out a draft of what? 20:52:38 q+ 20:52:52 billroberts: I think I've got what I was hoping to get today... 20:52:53 ack k 20:53:13 kerry: A question about turnout - is this going to be it for the regulat bi weekly meetings? 20:53:49 billroberts: I don't know. Other people have expressed an interest... Scott was keen. Of course this week is OGC TC week. Robin was interested. 20:53:54 regrets+ scott 20:54:05 ... Peter Baumann said he definitely wanted to take part. 20:54:16 ... The timing of the calls rules out Chinese folks. 20:54:28 ... And Maik Riechert we can hope will join the call. 20:54:37 kerry: So we might get a few more people/ 20:54:46 ... But we do need to have a few more active people in the group. 20:55:13 kerry: If it's just us, we can possibly come up with a better time (for Aus and UK). This time is good for the USA as well 20:55:39 billroberts: If they do join then great. If not then we may look again, especially when the clocks change 20:55:55 RRSAgent, draft minutes] 20:55:55 I'm logging. I don't understand 'draft minutes]', phila. Try /msg RRSAgent help 20:55:57 RRSAgent, draft minutes 20:55:57 I have made the request to generate http://www.w3.org/2016/03/09-sdwcov-minutes.html phila 20:56:28 RRSAgent, make logs public 20:56:33 RRSAgent, draft minutes 20:56:33 I have made the request to generate http://www.w3.org/2016/03/09-sdwcov-minutes.html phila 20:58:14 present+ Duo 20:58:24 present+ Yadu 20:58:55 RRSAgent, draft minutes 20:58:55 I have made the request to generate http://www.w3.org/2016/03/09-sdwcov-minutes.html phila 21:00:02 bye! 21:00:08 thanks, bye all! 21:00:14 dmitrybrizhinev has left #sdwcov 21:02:17 [leaving] 23:20:05 Zakim has left #sdwcov