15:59:14 RRSAgent has joined #sdwbp 15:59:14 logging to http://www.w3.org/2017/03/01-sdwbp-irc 15:59:16 ScottSimmons has joined #sdwbp 15:59:19 RRSAgent, make logs public 15:59:39 Meeting: Spatial Data on the Web Best Practices Sub Group Teleconference 15:59:46 Agenda: https://www.w3.org/2015/spatial/wiki/Meetings:BP-Telecon20170301 15:59:51 Linda has joined #sdwbp 15:59:54 Chair: Jeremy 15:59:59 BartvanLeeuwen has joined #sdwbp 16:00:35 jtandy has joined #sdwbp 16:00:44 Regrets: Phil, Lars 16:01:50 present+ jtandy 16:01:59 regrets+ BillRoberts 16:02:31 eparsons has joined #sdwbp 16:02:46 present+ ScottSimmons 16:03:05 Present+ Francois 16:03:12 ByronCinNZ has joined #sdwbp 16:03:58 present+ ByronCinNZ 16:04:07 AndreaPerego has joined #sdwbp 16:04:16 present+ AndreaPerego 16:04:44 present+ eparsons 16:05:13 present+ BartvanLeeuwen 16:05:13 present+ Linda 16:05:17 ClemensPortele has joined #sdwbp 16:05:24 present+ ClemensPortele 16:05:44 joshlieberman has joined #sdwbp 16:05:47 MattPerry has joined #sdwbp 16:05:51 scribe: Linda 16:05:54 present+ joshlieberman 16:05:58 present+ MattPerry 16:06:06 Zakim has joined #sdwbp 16:06:16 topic: approving the minutes 16:06:22 https://www.w3.org/2017/02/15-sdwbp-minutes 16:06:40 +1 16:06:41 +1 16:06:41 +1 16:06:42 +1 16:06:47 +1 16:06:48 +1 16:06:48 +1 16:06:53 +1 16:07:07 Topic: patent call 16:07:23 https://www.w3.org/2015/spatial/wiki/Patent_Call 16:07:24 eparsons: reads out patent call 16:07:37 [silence] 16:07:48 topic: sprint plan 16:07:51 https://www.w3.org/2015/spatial/wiki/Detailed_planning_BP_document#February_-_mid_March_2017: 16:08:09 jtandy: sprint plan is on the wiki. 16:08:21 ... josh, you're on BP1, do you recognize that? 16:08:26 joshlieberman: yes, with Andrea 16:08:32 jtandy: Andrea: you're on 8 16:08:46 ... 9 is addressed to joshlieberman 16:08:53 joshlieberman: working on that with Christine Perey 16:09:04 jtandy: content of that may be merged with bp10 or 14 16:09:23 ... I spoke with Bill, he knows he's on BP10 16:09:36 .. I'm on 14, 16 will be merged 16:09:53 ... section 11 will be based on work we're doing now 16:10:06 ... bp11 is Clemens with support from Bart 16:10:09 ClemensPortele: yes 16:10:17 BartvanLeeuwen: aware 16:10:55 jtandy: continues going through sprint plan 16:11:12 BP12 ? 16:11:15 ...payam is creating a list of comments we need to go through 16:11:20 q? 16:11:37 ... a lot of work but nothing stopping us from meeting the Delft target 16:12:03 ... Clemens will address BP12 later in this call 16:12:27 topic: Decision: are non-geographic CRS out of scope 16:13:56 Agreed afraid so... lack expertise 16:13:59 q? 16:14:03 q+ 16:14:21 q+ 16:14:22 RESOLUTION: meeting minutes approved 16:14:35 A little too much keyboard noise. 16:14:55 RRSAgent, draft minutes 16:14:55 I have made the request to generate http://www.w3.org/2017/03/01-sdwbp-minutes.html AndreaPerego 16:14:55 jtandy: there is no expertise in the WG on non-geographic CRS, therefore add to our scope section that this is out 16:14:56 q? 16:15:00 ack joshlieberman 16:15:04 eparsons: agrees, unfortunately 16:15:45 joshlieberman: engineering coordinate systems can be tied into geographic CRS but often just relative to some structure. 16:16:07 ... also note the egocentric perspective which comes from AR 16:16:38 ... it's worth mentioning that this is a perspective, without offering a BP 16:16:40 q? 16:16:48 ack ByronCinNZ 16:17:07 ByronCinNZ: leans towards exclusion of non-geo 16:17:37 ... the doc is primarily geospatial so people from other domains will not look for info here 16:18:00 ... both for cellular positioning and engineering 16:18:03 q? 16:18:20 jtandy: coming back to joshlieberman's comment; 16:18:35 ... agrees we ought to mention them 16:18:59 q+ 16:18:59 joshlieberman: there would be material for an engineering CRS BP 16:19:50 ... making engineering data sharable by tying points to geographic CRS 16:20:11 jtandy: this would be the place for AR info as well? 16:20:13 joshlieberman: yes 16:20:33 jtandy: proposes to ignore the cellular level in terms of spatial 16:21:01 ... and include in the next sprint a BP about engineering CRSs and tying them back to geographic CRS 16:21:14 joshlieberman: it could be an addition to BP9, if we make that relative and local positioning 16:21:30 eparsons: and I could add a sentence or two to the intro 16:21:52 ... something about global vs local CRS and engineering drawings being a subset of that 16:21:54 ClausStadler_ has joined #sdwbp 16:22:20 jtandy: please do 16:22:39 ... joshlieberman, I encourage you to develop BP9 along the lines you've just outlined. 16:22:42 q? 16:22:54 ... do you think that's possible within this sprint? 16:22:56 action eparsons to expand intro to include CAD drawings as another type of CRS 16:22:56 Created ACTION-276 - Expand intro to include cad drawings as another type of crs [on Ed Parsons - due 2017-03-08]. 16:23:20 joshlieberman: yes 16:23:36 topic: Review progress on BP8 16:23:36 topic: review progress for BP8 16:23:58 Current status: https://lists.w3.org/Archives/Public/public-sdw-wg/2017Mar/0008.html 16:24:21 AndreaPerego: I've completed the revision based on the discussion so far. 16:24:28 Preview: https://andrea-perego.github.io/sdw/bp/index.html#describe-geometry 16:24:30 ... I made a fork on my github 16:24:45 ... new parts in yellow, I kept also the original text 16:25:19 ... revised the why and intended outcome sections, mostly the wording 16:25:37 ... the rest is revised more thoroughly with more structure and more actionable guidelines 16:26:20 ...there are several notes 16:26:25 q? 16:26:39 q- 16:26:48 ... trying to describe the approaches in web, LD and geospatial communities 16:27:12 ... and added three examples 16:29:06 q? 16:29:08 (describes the examples in more detail) 16:29:19 AndreaPerego: asks for feedback 16:29:29 q? 16:29:32 jtandy: thanks AndreaPerego for the work he put in 16:29:43 q? 16:29:51 :) 16:29:55 mib_wh46xb has joined #sdwbp 16:30:19 mib_wh46xb has left #sdwbp 16:31:30 jtandy: did you find gaps in practice about how you ask for particular geometry representation? 16:32:01 AndreaPerego: this is the part causing more trouble 16:32:16 ... first you identify the users and applications 16:32:28 ... then you provide in differnet ways accordingly 16:33:12 ... I referred to what was already discussed in other parts of the BP eg about dimensions, crs, formats (the table in the appendix) 16:33:22 ... these tables are quite useful 16:33:50 joshlieberman has joined #sdwbp 16:33:54 q+ 16:34:12 ... referencing DWBP on conneg 16:34:37 ... of course there is not much detail but we could provide more detail in the examples 16:34:54 ... please let me know if more is needed 16:35:03 q+ 16:35:36 ... in my examples multiple representations of a spatial thing are all embedded in the thing 16:36:17 jtandy: joshlieberman, you mentioned the next version of geosparql might make it easy to identify things like bbox, center point. 16:36:25 ... is that worth referring to? 16:37:00 joshlieberman: coming slow. But will be something simple like georss as a core and adding more complexity from geosparql. 16:37:03 RRSAgent, draft minutes 16:37:03 I have made the request to generate http://www.w3.org/2017/03/01-sdwbp-minutes.html AndreaPerego 16:37:21 ... but in the core there are currently no geometry role properties. 16:37:45 s/differnet/different/ 16:38:08 ... there ARE geometry role properties in the core 16:38:27 ... The other issue is the distinction between positions and geometry. 16:38:54 ... important not to have just a geometry literal. A geometry has characteristics that need to be available. Type of geometry, dimensionality etc 16:39:38 ... And there are different serialization options for the position list. 16:39:50 ...geosparql used extended wkt for a reason 16:40:21 ...bp should be to treat that as a position literal and provide the geometry characteristics outside the literal as well 16:40:50 ...will look through AndreaPerego's work 16:40:55 q? 16:41:01 Thanks, Josh 16:41:02 AndreaPerego: thanks a lot joshlieberman 16:41:05 ack joshlieberman 16:41:08 ack ClemensPortele 16:42:15 ClemensPortele: when we talk about multiple representations we need to recognize there's also the difference between vocabularies where you represent spatial things and the geometry is a characteristic, 16:42:49 ... with one serialization, 16:42:50 q? 16:42:54 q+ 16:43:04 ... or vocabularies that have different serialization options 16:43:14 joshlieberman_ has joined #sdwbp 16:43:14 q? 16:43:17 ack AndreaPerego 16:43:17 ...e.g. GML or GeoJSON vs GeoSPARQL 16:43:27 AndreaPerego: was trying to take this issue into account 16:43:35 GeoSPARQL: asWKT vs asGML, etc. 16:43:39 ... therefore tried to be generic 16:43:57 q? 16:44:09 ... and added this in notes instead of the running text 16:44:38 ... to really address it you need to add a lot of detail, too much for a BP 16:44:58 ... a review by ClemensPortele might help 16:45:07 will do ... 16:45:13 jtandy: you are going in the right direction based on the discussion today 16:45:25 Thanks, Clemens! 16:45:40 jtandy: all: please continue to support AndreaPerego in unpicking this topic 16:45:57 Topic: Progress on BP 11, 12 and 13 16:46:06 New text: http://w3c.github.io/sdw/bp/#bp-exposing-via-api 16:46:29 ClemensPortele: I just updated the section at the link, both the intro and BP11. 16:46:38 ... haven't touched BP12 and 13 yet 16:47:02 ... but my feeling is we don't necessarily need these two. 16:47:38 ... The last versions of DWBP had updated info on the API topic. I consolidated our text with this. 16:47:51 ... making sure we build on that and focus on spatial aspects 16:47:57 ... and SDI related topics 16:48:44 ... the old BP11 had some ideas for examples, I deleted several of them eg WPS, WMS. These are not really convenience APIs. 16:49:40 q? 16:49:41 ... Bart should check if his content is covered correctly 16:50:11 q+ 16:50:20 ... DWBP has info on subsets of large datasets. We can't add that much to it. Coverages is addressed separately. 16:50:22 q+ to ask about BP13 16:50:32 q? 16:50:34 ... potentially we could do a subset example in BP11. Same goes for search. 16:50:42 ... therefore BP12 and BP13 could go. 16:51:28 jtandy: BP13 is well covered by DWBP. 16:51:46 joshlieberman has joined #sdwbp 16:52:03 ... I'd like to propose this to a larger group before deciding. Could you start a discussion thread about dropping BP13? 16:52:13 ClemensPortele: ok 16:52:29 q? 16:52:34 ack jtandy 16:52:34 jtandy, you wanted to ask about BP13 16:52:37 action ClemensPortele to start a discussion thread on the mailing list about dropping BP13. 16:52:37 Error finding 'ClemensPortele'. You can review and register nicknames at . 16:53:12 action Clemens Portele to start a discussion thread on the mailing list about dropping BP13. 16:53:12 Created ACTION-277 - Portele to start a discussion thread on the mailing list about dropping bp13. [on Clemens Portele - due 2017-03-08]. 16:53:53 jtandy: is search special / does it need its own BP? 16:54:02 q? 16:54:10 joshlieberman: not sure, it could be merged into something about APIs. 16:54:35 ... e.g. what search options would we want to recommend. 16:54:59 Current text: "The API should support queries for spatial things based on user needs. For spatial data, a typical need is to support searching data located in a specific area, for example, an area shown as a map in an application. Where users often look for a particular spatial thing without knowning its identifier, a fault-tolerant free-text search on the name, label or other property may be useful." 16:55:10 jtandy: part of a convenience api is providing search for cases where users don't know the identifiers of spatial things. 16:55:18 ...would that be enough? 16:55:40 ClemensPortele: is the current text (pasted above) enough? 16:56:12 joshlieberman: the other important thing is some sort of neighborhood search. 16:56:44 jtandy: makes sense 16:56:54 ClemensPortele: will add that 16:57:57 joshlieberman: near and within covers about 80% of spatial queries 16:58:27 q? 16:59:04 jtandy: so we've agreed here that given the minor amendment of BP11, BP12 can go. 16:59:46 prese 16:59:52 ... wrapping up, I will continue pushing discussions on sameplaceas and BP2. 17:00:29 ...Ed, when we resolve to remove BPs, should we have minuted resolutions in a plenary call? 17:00:36 eparsons: yes 17:01:02 jtandy: then it would be useful to have those resolutions in the next plenary call. 17:01:07 eparsons: drop me an email to remind 17:01:35 jtandy: thanks everyone including demon Linda 17:01:35 thx 17:01:38 Thanks, and bye! 17:01:38 thanks and bye! 17:01:39 bye 17:01:40 Thanks Linda + jtandy 17:01:41 bye! 17:01:42 jtandy: meeting closed 17:01:44 bye 17:01:44 bye! 17:01:46 RRSAgent, draft minutes v2 17:01:46 I have made the request to generate http://www.w3.org/2017/03/01-sdwbp-minutes.html tidoust 17:01:48 ClemensPortele has left #sdwbp 19:09:37 Zakim has left #sdwbp