19:47:28 RRSAgent has joined #sdw 19:47:28 logging to http://www.w3.org/2016/01/06-sdw-irc 19:47:30 RRSAgent, make logs world 19:47:30 Zakim has joined #sdw 19:47:32 Zakim, this will be SDW 19:47:32 I do not see a conference matching that name scheduled within the next hour, trackbot 19:47:33 Meeting: Spatial Data on the Web Working Group Teleconference 19:47:33 Date: 06 January 2016 19:47:44 RRSAgent, make logs public 19:47:59 Agenda: https://www.w3.org/2015/spatial/wiki/Meetings:Telecon20160106 19:48:10 Chair: Ed 19:48:20 Chair: eparsons 19:49:14 kerry has joined #sdw 19:55:39 BartvanLeeuwen has joined #sdw 19:55:53 ssimmons has joined #sdw 19:56:17 present+ Scott Simmons 19:56:35 presen+ BartvanLeeuwen 19:57:04 phila has joined #sdw 19:57:21 present+ eparsons 19:57:30 trackbot, start meeting 19:57:32 RRSAgent, make logs world 19:57:34 Zakim, this will be SDW 19:57:35 I do not see a conference matching that name scheduled within the next hour, trackbot 19:57:35 Meeting: Spatial Data on the Web Working Group Teleconference 19:57:36 Date: 06 January 2016 19:57:36 robin has joined #sdw 19:57:37 Payam has joined #sdw 19:57:44 present+ kerry 19:58:08 regrets+ Rachel Alejandro Linda Andrea 19:58:24 regrets+ Bill 19:58:28 present+ phila 19:59:15 jtandy has joined #sdw 19:59:19 present+ Payam 19:59:35 jtandy has joined #sdw 20:00:16 frans has joined #sdw 20:01:14 ClemensPortele has joined #sdw 20:01:29 present+ jtandy 20:01:43 present+ frans 20:02:00 ChrisLirrle has joined #sdw 20:02:00 present+ robin 20:02:05 present+ ClemensPortele 20:02:36 present+ ChrisLittle 20:02:38 -1 20:03:15 -> https://www.w3.org/2015/spatial/wiki/Meetings#Teleconference_Agendas_and_minutes 20:03:56 scribe: Kerry 20:03:58 ChrisLittle has joined #sdw 20:04:04 scribenick: Kerry 20:04:11 scribe+ kerry 20:04:13 Topic : Approve last week's minutes 20:04:21 Last meeting's minutes http://www.w3.org/2015/12/16-sdw-minutes 20:04:24 http://www.w3.org/2015/12/16-sdw-minutes 20:04:30 KJanowicz has joined #sdw 20:04:41 +1 20:04:44 MattPerry has joined #sdw 20:04:44 +1 20:04:45 What is the Webex password please? 20:04:45 +1 20:04:49 +0 (wasn't there) 20:04:59 Proposed : Approve last week's minutes 20:05:04 +1 minute but not there 20:05:07 Resolved : Approve last week's minutes 20:05:08 +1 20:05:09 RESOLVED: appove last weeks minutes http://www.w3.org/2015/12/16-sdw-minutes 20:05:09 present+ MattPerry 20:05:19 +0 20:06:03 ED: robin requested to intro 20:06:20 .... no answer from robin 20:06:26 Hi, I am a student from University of Calgary 20:06:56 Robin: PhD student from U Calgary 20:07:13 .... works with Steve Liang of sesnor things API 20:07:36 eparsons: welcome 20:07:44 Topic : Patent Call 20:07:59 https://www.w3.org/2015/spatial/wiki/Patent_Call 20:08:18 eparsons: no comments wrt patent call 20:08:35 Topic : Best Practice - Progress to date 20:08:35 Topic: best practice deliverable 20:09:05 jtandy: I will do most of discussion, payam pls jump in 20:09:26 .... linda is holidaying in the sun 20:09:48 +1 phila 20:09:56 ... .... question to phila re new style change 20:10:05 q? 20:10:25 ... almost signed off, easy change for a Note, just a respec tweak 20:10:40 phila: yes, starts from 1 feb 20:10:54 ... cannot use before then 20:11:23 present+ ChrisLittle 20:11:46 jtandy: so it will have a sidebar with ToC, but we will beat the new style adn will use the existing style for our fpwd 20:12:40 phila: asking Scott about 3 week ucr process that took 8 days second time -- for this new fpwd will it be 1 week or 3? 20:13:03 ssimmons: 3 weeks review plus 8 day vote 20:13:17 phila: so will be feb 20:13:26 jtandy: questions the 3 weeks 20:14:05 ssimmons: if only for review can skip the 3 weeks wait, could be zero wait -- you can approve now 20:14:20 +1 to release doc for public review 20:14:30 jtandy: this is a stable snapshot of unfinished work so does not need a TC vote 20:14:34 ssimmons: confirmed 20:15:03 ssimmons: this gropu can approve it. it only needs to go to geosemantics group in final release 20:15:14 SimonCox has joined #sdw 20:15:43 jtandy: our plan was to provide stable snapshot today and vote in meeting next week -- but that vote may be subject to changes being made 20:15:45 rrsagent, draft minutes 20:15:45 I have made the request to generate http://www.w3.org/2016/01/06-sdw-minutes.html eparsons 20:16:27 phila: yes, depending on content -- the tues or thurs after the next meeting is k with review over next 7 days 20:16:30 present+ SimonCox 20:16:34 s/k/ok/ 20:16:54 http://w3c.github.io/sdw/bp/ 20:16:59 phila: that means tuesday 19 Jan for publication, all being straightforward 20:17:41 jtandy: BP doc review -- I will cover from the top in summary 20:18:04 .... please mail changes to public mail list this week 20:18:08 chair: eparsons 20:18:20 ... for direct text changes that you provide we will apply them 20:18:24 agenda: https://www.w3.org/2015/spatial/wiki/Meetings:Telecon20160106 20:18:39 ....for something without the text we will record an issue but not make the change 20:19:16 q+ 20:19:23 ack next 20:19:26 ....for difficult things that are drastically wrong and you could not support in vote please attend call and disccuss next week 20:19:39 s/disccuss/discuss/ 20:20:37 phila: this is important --- in another group we had some approval subject to changes but we ended up with public doc with a no vote against it 20:21:03 ... please ensure that you are indeed happy before we publish as we want to get this right 20:21:26 -> http://w3c.github.io/sdw/bp/ The Current Ed Draft of the BP doc 20:21:29 jtandy: abstract is a short para for press release that will bring people to see it 20:22:24 q+ 20:22:43 .... next is status of doc trying to resolve a number of things raised in last meeting ... focus on concerns raised in last meeting, evidence needed 20:23:02 q- 20:23:05 q+ 20:23:09 eparsons: i think t his is what we needed -- perhaps should go in press release too 20:23:22 q- 20:23:44 jtandy: eparsons can write the press release to do thius! 20:23:52 s/thius/this/ 20:24:04 q+ 20:24:17 jtandy: ... at the bottom of intro is issue-81 (reads out) 20:24:19 ack next 20:25:24 frans: Q about intro: what is the realtionship between this doc and the charter deliverable for next practice? restful API and spatial ontology? 20:25:37 s/next/best/ 20:25:49 s/real/rel/ 20:26:03 BP deliverable in the charter: http://www.w3.org/2015/spatial/charter#bp 20:26:19 jtandy: i picked out charter things to include in abstract as here (sumarises abstract) 20:26:39 ... are you saying there are BP deliverables from charter that are not in this note? 20:26:49 frans: yes 20:28:19 frans: (reads from charter) ... an ontology is not a document -- what do we do with this? 20:28:20 I agree with Ed 20:28:38 eparsons: we have not got to finding we need this yet 20:29:11 jtandy: we plan at this point to review whate there is and to say what to use and when, we may not need to make a new one 20:29:38 +1 franz! 20:29:42 frans: there is a need for harmonisation of existing standards we need to do this 20:29:48 IMHO, there is a need for such an ontology 20:29:54 (and related ontologies) 20:30:48 rrsagent, draft minutes 20:30:48 I have made the request to generate http://www.w3.org/2016/01/06-sdw-minutes.html eparsons 20:31:15 jtandy: frans please write down a note for this and I will include a comment in our intro about this -- that we might make something new but our first attempt is to review an recommend existing 20:31:32 frans: also needd for API deliverable 20:31:45 +q 20:32:01 jtandy: I beleive we are offering advice on APIs and not defining one -- this looks the right approach 20:32:03 ack next 20:32:32 frans: agrees that APi may not be neccessary but we need to leave this option open where requirements are not met by existing solutions 20:32:56 Payam: part of what Frans is looking for may arise from examples as we get to those 20:33:37 q+ 20:33:40 eparsons: agrees , also a broader point is that we will identify gaps we may not be able to fill but just identify these due to lack of resources 20:33:43 ack next 20:34:00 SimonCox: exercise becomes a meta-exercies if e do not address the gaps 20:34:36 eparsons: points out that we do have limited time -- we need to be realistic 20:35:15 jtandy: in some places we have expert opinions amongst us and we can answer those gaps. e.g. issue-81 20:35:39 ... simon says just cataloguing is insufficient 20:36:08 SimonCox: a list of gaps is not a useful list of best practices 20:36:34 jtandy: we might have to identify what is needed that we cannot do 20:36:39 q+ 20:36:51 q+ 20:36:56 ack next 20:37:06 eparsons: best practice must be practice -- if we see a gap our solution we design in a short time is not best practice 20:37:45 W3C doesn't have a definition of Best Practice - WGs are sovereign! 20:37:55 ClemensPortele: both views are valid --- one option could be to create a new document type or additional deliverables to close the gaps? 20:38:49 jtandy: acking Phil's comment , it is what we want to make it. we can make additional deliverables as we see fit but resourcing is an issue 20:39:23 ack next 20:39:31 an agreed spatial ontology conformant to the ISO 19107 abstract model and based on existing available ontologies such as GeoSPARQL, NeoGeo and the ISA Core Location vocabulary 20:39:34 jtandy: lets see how this goes as we identify the gaps 20:40:20 frans: charter says based on existing ontologies -- suggesting it does not exist yet 20:41:03 jtandy: too much choice at moment -- do we really need another choice? 20:41:06 +q 20:41:07 (and there are also cases where we have not suitable vocabulary/ontology) 20:41:16 -> http://www.w3.org/2014/03/lgd/report#conclusion LGD Report conclusion 20:42:21 phila: this arose from the workshop in the final panel session, stuart williams said "where do i pour the concrete" 20:43:12 +q 20:43:44 ...so charter says we have all these things already but what is someone to do? workshop said do we pick one and forget all the rest or advise what is needed in the right situation, or should we just change something existing a bit? 20:44:07 I like the option of picking the best ontology and try to improve it 20:44:20 ....charter aims to not predefine the decision of the working group about how to deal with this 20:44:23 q+ 20:44:52 ... you can do, if you choose, a comply or explain model -- it really is this group's decision how we solve this. 20:44:59 ack next 20:45:42 frans: I like the 3rd option, not developing and not picking but improving the best one a little 20:46:00 IMHO, we should work on the interface level and there is actually tons of work left to be done there 20:46:01 In case anyone hasn't seen it... http://xkcd.com/927/ 20:46:02 ... we could empower other working groups to help us 20:46:45 q+ 20:46:46 ack next 20:47:20 kerry: our use cases to identify some missing things and we may need a core vocab 20:47:46 Yes. A simple core ontology that is extensible would be a great achievement 20:48:16 KJanowicz: e.g moving objects and trajectories is a common task that has specific requirements... types of measurements is another one.. common guidance at least could be provided 20:48:22 ack next 20:49:11 ack next 20:49:18 rrsagent, draft minutes 20:49:18 I have made the request to generate http://www.w3.org/2016/01/06-sdw-minutes.html eparsons 20:49:24 ChrisLittle: Being blunt, we should not be scared to point to bad practices such as using WGS84 for highly precise locations 20:49:51 IMHO, our work should be about finding and defining the common cores underlying the solutions that exist out there and enabling these common core vocabularies to become the minimal interoperability layer used to translate between the more application oriented vocabularies. 20:49:56 phila: Denise or Bart has mentioned that if we advise geosparql 1.1 then we will. 20:50:39 agreed, but this is about striking the right balance 20:50:42 ...iso core location vocab aimed to identify hight level core stuff but it turns out not to be useful on its own and then you start developing application profiles vey fast 20:51:26 .... to make interoperability to practically work you really need someone to tell you what to do -- this is a difficult balance between theory and practice 20:51:39 +1 20:51:41 eparsons: this doc should be aimed at practitioners 20:52:19 Agreed but somebody needs to explain what ways are out there to deal, for instance, with measurement types, what the pros&cons of these approaches are, and which one should be used if you need guidance. 20:52:27 jtandy: i will update intro and some other section about helping people choose the right one and make a new one if we need to 20:52:38 .... now talking about how we deal with issues 20:53:12 ... e.g see the issue box -- not the order in doc is order of creationg in github 20:53:12 https://github.com/w3c/sdw/issues/81 20:53:42 ... to repond to issues please click on link in doc and leave your comments there in github 20:53:51 please work on issues this way -- is that ok? 20:54:09 frans: are github acounts needed? 20:54:38 jtandy... comments are public, but you need to be signed in 20:54:53 +1 to issue managment 20:55:02 ... this is good for eds to track issues using github 20:55:19 .... now issue-79 about sdis 20:55:49 http://w3c.github.io/sdw/bp/#bp-summary 20:55:49 ...sections on audience, scope, best practices template, summary with all bps listd 20:56:12 .... summary is auto-generated 20:56:30 ... top level sections after that should be no surprise -- there are 30 20:56:33 http://w3c.github.io/sdw/bp/#bp-exposing-via-api 20:56:43 ... please discuss this section now 20:57:08 ... may not need resolution prior to fpwd? 20:57:47 ... but how much of this is about spatial data in particular? is this in the right place or does it belong in a borader document than ours? 20:58:04 s/borader/broader/ 20:58:42 ...will sek to merge those tables as we go on, also ross ref requirements, also appendix b, incomplete glossary, set of references, 20:59:14 ... pls provide feedback on mailing list ideally resolved before next week -- anything outstanding to be discussed in meting next week. 20:59:20 W3C Draft = OGC draft Discussion Paper 20:59:24 ...not not finished -- only FPWD 20:59:33 Payam: all covered 20:59:38 https://www.w3.org/2015/spatial/wiki/Meetings#Amsterdam 20:59:59 eparsons: reminder for f2f only a month away hosted by geonovum 21:00:02 +q 21:00:09 ack next 21:00:42 bye 21:00:48 RRSAgent, draft minutes 21:00:48 I have made the request to generate http://www.w3.org/2016/01/06-sdw-minutes.html phila 21:00:58 .... please read the doc and make your comments well before next meeting 21:01:04 Bye, have a great year 21:01:04 bye and thanks 21:01:05 bye 21:01:05 ... and come to meeting to vote!!!!! 21:01:06 thanks - bye! 21:01:09 bye 21:01:09 RRSAgent, draft minutes 21:01:09 I have made the request to generate http://www.w3.org/2016/01/06-sdw-minutes.html phila 21:01:12 bye 21:01:15 rrsagent, draft minutes 21:01:15 I have made the request to generate http://www.w3.org/2016/01/06-sdw-minutes.html kerry 21:01:21 thanks kerry !!! 21:01:26 rrsagent, make logs public 21:01:34 quit 21:01:41 thanks bye 21:01:43 robin has left #sdw 21:02:33 bye all! 21:36:09 eparsons has joined #sdw 23:40:08 Zakim has left #sdw