19:56:52 RRSAgent has joined #sdwcov 19:56:52 logging to http://www.w3.org/2016/12/07-sdwcov-irc 19:56:53 billroberts has joined #sdwcov 19:56:54 RRSAgent, make logs world 19:56:54 Zakim has joined #sdwcov 19:56:56 Zakim, this will be SDW 19:56:56 ok, trackbot 19:56:57 Meeting: Spatial Data on the Web Working Group Teleconference 19:56:57 Date: 07 December 2016 19:56:59 dmitrybrizhinev has joined #sdwcov 19:57:09 s/Working Group/Coverages Sub Group/ 19:57:13 chair: Bill 19:57:29 roba has joined #sdwcov 19:57:40 agenda: https://www.w3.org/2015/spatial/wiki/Meetings:Coverage-Telecon20161207 19:58:17 hello everyone 19:58:44 looks like webex not started yet - is that right Phil? 20:00:27 kerry_ has joined #sdwcov 20:01:09 Kerry has joined #sdwcov 20:01:57 present+ billroberts 20:02:02 regrets+ Jon Blower 20:02:20 present+ Dimitry 20:02:23 present+ Kerry 20:02:41 morning... 20:04:37 present+ 20:05:20 scribe: kerry 20:05:26 scribenick: kerry 20:05:46 q+ 20:06:16 ack k] 20:06:24 Topic: Approval of earlier minutes 20:06:45 Meeting 2 weeks ago was informal. So... 20:06:47 q- 20:06:48 https://www.w3.org/2016/11/09-sdwcov-minutes 20:07:41 +1 20:07:55 +1 20:07:57 +1 to approve minutes 20:08:02 resolve: approve minutes https://www.w3.org/2016/11/09-sdwcov-minutes notuc 20:08:40 topic: https://www.w3.org/2016/11/09-sdwcov-minutes 20:08:59 topic: Progress towards the 3 FPWD - EO-QB, QB4ST, CovJSON. How close are we to candidate FWPD on each of these? 20:09:27 bill" covjson plan to fill in a lot of the gaps 20:09:44 ...call with Jon Friday and exepct to meet monday morning stabe doc 20:09:50 as to plan 20:09:55 ....but have some questions... 20:09:55 http://w3c.github.io/sdw/coverage-json/ 20:10:21 billroberts: couiple of sections that I am asking about 20:10:34 ....section 6 use cases and requirements 20:10:50 ....thinking of exaplining how covjson maps to requirements 20:11:03 q+ 20:11:04 ... saw that other docs have not done it in a lot of detail 20:11:09 .... is this appropriate? 20:11:16 ack me 20:11:18 ack phil 20:11:22 ... necessary? useful? 20:11:23 q+ 20:11:33 phila: yes it is necessary 20:11:42 ....you must show you have met requirements 20:11:54 .... a section in each document to do this is useful 20:12:02 .... it needs to be in all 20:12:17 billroberts: will do 20:12:19 ack roba 20:12:37 roba: was planning to do same for qb4st 20:13:29 .... but question about style ...OGC provides more rationale of technology where W3C is terse.. what do we do? 20:14:03 q+ 20:14:06 q- 20:14:06 billroberts: also for covjson --- we need to say "why we are making another standard for coverages" 20:14:08 ack phila 20:14:27 phila: would include some verbage around motivation 20:14:33 q+ 20:14:51 ...also relationship to previous work would be good 20:15:07 ...like time --- why it is different to before 20:15:14 ...beyond that entirely up to you 20:15:40 ... no rule that yo cannot include explanation --- you should do it if you think so especially if expected of OGC papers 20:16:08 roba: qb4st will retain why you need anything at all 20:16:38 phila: inapprop to write non-normative in docs as whole doc is non-normative 20:17:09 dmitrybrizhinev: non-normative comes by defualt -- cannot remove it -- is there another one? 20:17:49 phila: yes ... you should not use informative class so ... dont' sue section class = informative 20:17:52 q+ 20:18:02 s/sue/use/ 20:18:50 billroberts: covjson may have an appendix that contains [missed] so that the same doc has everything in it and not externally referenced 20:18:55 ack k 20:20:33 https://covjson.org/spec/ 20:20:46 phila: billroberts question it is odd to have covjson standard body with an appensix that is the specification 20:20:53 s.appensix/apendix/ 20:21:02 s/appensix/appendix/ 20:21:15 phila: will look inot ithis 20:21:42 billroberts: will talk to jon about how much the covjson spec might change -- it does not look tremendously final right now 20:22:06 roba: suggests you copy the spec in in full status 20:22:40 billroberts: but how close to final is it? in final version of note this could be the definitive version of spec 20:23:45 phila: leave this to editors draft link.... their doc does not have ipr committments, so that repo spec could be implemented with royalties lurking 20:24:09 ...so I am reluctant to give that doc credit, but we could incluide a link somewhere... 20:24:23 roba: previous version link? 20:25:15 phila: no but something in the status of the repo doc to point to our Note that points it as a static version and that this version may be an update 20:25:21 ... legal stuff matters a lot 20:25:50 ... a link to that one is the best you can do -- there are places you can link but it will not go through process and IPR 20:26:20 billroberts: will work through that with Jon, seems like we should wrap up that spec and put it in this note 20:26:33 phila: yes, if the full content goes in our note 20:26:55 ...must give full credit in our note but IPR constrains us 20:27:15 s/credit/endorsement/ 20:27:17 roba: could transcribe the bulk of it directly into our Note 20:27:43 s/ but we could include a link somewhere/ but we could certainly include links somewhere.../ 20:27:55 billroberts: respec references: if we need a ref that is not elsewhere whre do I put it? 20:28:07 phila: in local biblio = config.js 20:28:27 -> https://github.com/w3c/sdw/blob/gh-pages/coverage-json/config.js This file, bill 20:29:34 phila: it shows how to do it there -- an ssn one is thre 20:29:50 billroberts: are we sharing a common biblio? 20:30:04 phila: just copy and paste between config.js 20:30:12 billroberts: doc number? 20:30:36 roba: offers to check on OGC doc number 20:31:18 Topcic: eo-qb? 20:31:29 topic: eo-qb 20:31:36 16-125 Publishing and Using Earth Observation Data with the RDF DataCube and the Discrete Global Grid System 20:32:09 but i dont see covjson yet.. 20:32:13 dmitrybrizhinev: pretty good shape, includes refs to use cases and requirements, we have description to rdf on example, als some new detail with implementation, has updated qb-4st 20:32:30 billroberts: what do we have to do in a formal sense? 20:33:13 phila: day 1 of f2f will be vote -- it ha become the norm that the group is given a week to review it 20:33:22 shall I generate one then? 20:33:29 eo-qb lokks ready for review to me 20:34:00 billroberts: if there isn't one and you can make one --- can you pls? for covjson 20:34:24 roba: title is currently "coveragejson" but it can be changed 20:34:43 ...usually more descriptive than that -- what do you want? 20:35:10 The CoverageJSON Format Specification 20:35:26 roba: [suggested a name] and bill agreed 20:35:37 phila: asks about geojson's name 20:35:59 phila: likes "coveragejson" name 20:36:17 phila: dmitry 20:37:07 phila: could this end up a rec -- could there be another implementation for rec? 20:37:30 dmitrybrizhinev: but is more of guidance -- a wroked example -- than it is for a standard 20:37:49 You have successfully reserved 16-145 for The CoverageJSON Format Specification. 20:37:58 billroberts: on eo-qb will send round an email to draw attention 20:38:00 q+ 20:38:06 ack k 20:39:26 roba: minor changes around qb4st 20:39:33 Kerry: will do 20:40:14 roba: other comment is if using rdfdatacube --- statment about using for data and metadata should be higher up 20:40:29 ...is more significant than where it is 20:40:29 q+ to ask about the namespace http://resources.opengeospatial.org/def/qbcomponents/qb4st/ 20:40:57 ack me 20:40:57 phila, you wanted to ask about the namespace http://resources.opengeospatial.org/def/qbcomponents/qb4st/ 20:40:59 ack p 20:41:01 phila: 20:41:31 .... 2 things -- the namespace is very long... can it be shorter ... when I refernce it I get an error 20:42:06 I can offer you http://www.w3.org/ns/qb4st 20:42:10 roba: namespace is not fixed yet.... currently mutable... what should they be .. can be changed to a target 20:42:17 phila: can give you one 20:42:40 roba: will adopt what you give me 20:43:00 phila: want to see the final name space in the FPWD 20:43:19 q+ to ask a realted question about ssn 20:43:38 roba: happy eith that 20:43:54 ack kerry 20:43:54 Kerry, you wanted to ask a realted question about ssn 20:46:18 billroberts: so when will qb4st be ready 20:46:52 roba: wanting some more review 20:47:59 billroberts: will leave to you to mail the list 20:48:44 roba: there has been close review of the concept by dmitry, chris, kerry etc but would like a closer look at the ontlogy itself 20:49:08 ....but can throw it out as public draft and see 20:49:27 phila: we should contact Cyganiak and Reynolds to review 20:49:58 roba: did talk with reynolds again about the concept but not the detailed design 20:50:17 ...would welcome a closer inspection 20:51:03 billroberts: any other thing to agree for next meeting? 20:52:02 ....rob would you lie to see someone lese summarise and present for you? 20:52:18 roba: I might make it (am on holiday) 20:53:04 billroberts: beterrn Kerry and I we can muddle through witout you 20:53:28 s/beterrrn/between/ 20:53:35 topic: next meeting 20:53:56 billroberts: propose skip 21 Dec 20:56:44 billroberts: propose next meeting is 18th Jan 20:57:01 +1 20:57:09 billroberts: aob? 20:57:44 roba: will also correct namesspace update for eo-qb if you accept the pr 20:58:02 RRSAgent, draft minutes 20:58:02 I have made the request to generate http://www.w3.org/2016/12/07-sdwcov-minutes.html phila 20:58:15 billroberts: happy Christmas! and good hoidays1 20:58:26 rrsagent, make logs public 20:58:34 rrsagent draft minutes 20:58:36 bye all 20:58:38 RRSAgent, draft minutes 20:58:38 I have made the request to generate http://www.w3.org/2016/12/07-sdwcov-minutes.html phila 20:58:49 bye! 21:08:59 RRSAgent, bye 21:08:59 I see no action items