12:56:02 RRSAgent has joined #sdw 12:56:02 logging to http://www.w3.org/2016/07/20-sdw-irc 12:56:04 RRSAgent, make logs world 12:56:04 Zakim has joined #sdw 12:56:06 Zakim, this will be SDW 12:56:06 ok, trackbot 12:56:08 Meeting: Spatial Data on the Web Working Group Teleconference 12:56:08 Date: 20 July 2016 12:56:25 RRSAgent, make logs public 12:56:35 Present+ eparsons 12:56:56 agenda: https://www.w3.org/2015/spatial/wiki/Meetings:Telecon20160720 12:57:15 Chair: eparsons 12:58:08 Regrets: Rachel, Lars, SimonCox 12:58:44 Regrets: Andrea, Danh 12:58:59 billroberts has joined #sdw 12:59:32 ScottSimmons has joined #sdw 12:59:39 sigh+ remind of webex password, please 12:59:46 BartvanLeeuwen has joined #sdw 12:59:48 Linda has joined #sdw 13:00:25 sdw 13:00:38 present+ NickyVanOorschot 13:00:44 ByronCinNZ has joined #sdw 13:00:56 kerry has joined #sdw 13:00:56 +present 13:01:08 present+ BartvanLeeuwen 13:01:09 present+ kerry 13:01:15 aharth has joined #sdw 13:01:26 present+ ScottSimmons 13:01:47 present+ billroberts 13:01:56 present+ aharth 13:01:56 present+ ByronCinNZ 13:02:05 present+ Linda 13:02:12 present+ josh 13:02:34 http://www.slideshare.net/semanticfire/action-85-64205032 13:02:40 RaulGarciaCastro has joined #sdw 13:03:16 jonblower_ has joined #sdw 13:03:23 present+ jonblower 13:03:55 present+ RaulGarciaCastro 13:04:03 jtandy has joined #sdw 13:04:12 MattPerry has joined #sdw 13:04:17 scribe: Linda 13:04:20 present+ jtandy 13:04:43 Topic : Approve last week's minutes 13:04:45 eparsons: lets start 13:04:49 PROPOSED : Approve last week's minutes 13:04:50 present+ MattPerry 13:04:53 Maik has joined #sdw 13:04:57 http://www.w3.org/2016/07/06-sdw-minutes.html 13:05:05 +1 13:05:07 +1 13:05:13 +1 13:05:17 ChrisLittle has joined #Sdw 13:05:21 +1 13:05:22 +1 13:05:23 +1 13:05:25 +1 13:05:30 +1 13:05:30 RESOLUTION : Approve last week's minutes 13:05:31 Present+ 13:05:38 +1 minutes 13:06:08 Topic : Patent Call 13:06:10 eparsons: checks attendees - ok 13:06:11 +present Maik 13:06:15 https://www.w3.org/2015/spatial/wiki/Patent_Call 13:06:24 Topic : Demo 13:06:25 [silence] 13:06:25 +1 minutes 13:07:00 http://www.slideshare.net/semanticfire/action-85-64205032 13:07:00 eparsons: bart and nicky have put together a demo. Mentioned at BP call last week but better to show it in this bigger group. 13:07:17 BartvanLeeuwen: link to the slides is here. 13:07:21 yes, got it 13:07:23 +1 13:07:23 +1 works 13:07:46 ... we do a lot of work for emergency response orgs who need to work together in crisis situations 13:08:13 ... for proper information sharing between them we created the Firebrary, a SKOS vocabulary 13:09:03 ... people started putting things on maps so then sharing geo-information became a topic 13:09:29 ... for example here a map of the Netherlands with companies at risk for high water 13:09:43 ... represented as purple dot but user has no idea what it means 13:10:32 jtandy just the one... 13:11:22 ... in the demo we have geo data in a postgis data, served in a standard WFS but also R2R mapping to RDF 13:12:52 ... used a rdf:about attribute on the data, linking to Firebrary 13:13:30 ... and can visualise the data based on the semantics 13:13:41 ... based on DWBP work 13:14:25 ... SKOS can also be used to map icons from different communities or countries. 13:14:51 ... could this be a BP? 13:14:55 roba has joined #sdw 13:14:59 ... Is this in scope? 13:15:08 ... is rdf:about the right way of doing a backlink? 13:15:10 http://geo.resc.info/geoserver/netage/wms?service=WMS&version=1.1.0&request=GetMap&layers=netage:fb_demo&styles=&bbox=7.00324749210733,52.2615836944433,7.00881387704046,52.2640494501209&width=768&height=340&srs=EPSG:4326&format=application/openlayers 13:15:46 ... this map shows red dots, each has a link to RDF information about the item 13:16:06 +1 13:16:09 q+ 13:16:09 q+ 13:16:13 ack next 13:16:21 q+ 13:17:10 jtandy: use of rdf:about to include identifier which allows users to lookup information, right? 13:17:38 rrsagent, draft minutes 13:17:38 I have made the request to generate http://www.w3.org/2016/07/20-sdw-minutes.html eparsons 13:18:05 BartvanLeeuwen: yes, this separates use of WFS only for markers on maps, the information is elsewhere 13:18:22 jtandy: why rdf:about? 13:18:42 BartvanLeeuwen: had to pick something, any suggestions? 13:18:48 rdfs:seeAlso 13:18:57 jtandy: anyone on the call has suggestions? 13:19:04 ack next 13:19:24 aharth: rdf:about is a remnant of rdf/xml 13:19:36 ... but not worrying to use this. Cool demo. 13:19:52 ... is there live lat/lon information in the maps? 13:20:05 BartvanLeeuwen: no, it's a scenario drawn on a map, but live info is also possible 13:20:28 aharth: do you have datasets with polygons as well? 13:21:30 BartvanLeeuwen: for me representing geometries in RDF was out of scope for this demo 13:21:45 ack next 13:22:12 josh: there is an RML extension that encorporates the geosparql spatial functions 13:22:37 present+ roba 13:22:49 ... would be interesting to standardize that 13:22:57 +1 to what Josh is saying about ontop-spatial. It's good but documentation is lacking 13:24:02 ... Interesting way of linking information to spatial data, valuable. 13:24:15 ... but not easy 13:24:36 eparsons: if this isn't a BP, what would it need to be to become one? 13:25:20 josh: should be general; in linking spatial data the links should be available 13:25:47 BartvanLeeuwen: the links should be from the SDI to the data published on the web 13:25:55 q+ 13:26:06 eparsons: would be valuable to give a contribution on this in the BP 13:26:52 jtandy: so the BP is if you provide data through an SDI, publish the information in a complementary manner and link them 13:27:11 BartvanLeeuwen: yes, and somehow do the backlinking 13:27:30 ack next 13:27:38 eparsons: any comments on the backlinking? 13:28:17 we hear you rob 13:28:26 It seems to me to be a mismatch to develop links "back" to non-linked data. It would make more sense to me to make sure that SDI data is (alternately) accessible as linked data. 13:29:03 +1 13:29:15 roba: see redundancy in the identifiers in the example 13:29:37 ... you could generate some automatically during rendering 13:30:20 ... Also, in LD world there are often multiple views, one of them can be backlinks. 13:31:08 ...e.g. links from data back to services where you can get the data 13:31:41 eparsons: Thanks Bart for this interesting example. 13:32:08 Topic : Simple Spatial Ontology, 13:32:24 https://www.w3.org/2015/spatial/wiki/Further_development_of_GeoSPARQL 13:32:31 josh: put some info in the wiki 13:33:31 ... there needs to be a common way to express spatial data so that you can have a common way to query it using geosparql. 13:33:57 ... the spatial ontology in geosparql 1.0 has good things but is not well-used 13:34:37 ... if we create version 1.1 it would be an OGC update of an existing standard. Not sure what it would be in SDWWG terms 13:35:06 ... geosparql 1.0 is considered too complicated, but just using lat/long is too simple and unexpressive 13:35:26 ... update could be to add simple geometry properties 13:36:26 ... another update is to have a way to infer relationships between features from relationships between geometries 13:36:45 ... Features and Geometries are disjoint 13:37:16 ... but are both SpatialObjects and share the same possible relationships 13:37:41 ... There was an issue with three different types of spatial relations which many found confusing. 13:39:55 ... explains the new proposed spatial ontology 13:40:11 q? 13:41:17 ...Another possible improvement is the addition of serialization types, e.g. GeoJSON 13:42:11 ... theoretical foundation in ISO191xx 13:42:53 q+ ask about conneg for geometry serialisations 13:43:06 q+ to ask about conneg for geometry serialisations 13:44:16 ... simple geometric properties could be added 13:45:29 q+ to ask about possible compatibility with W3C wgs84_pos vocab 13:45:38 ... not done, some things are not completely clear yet. 13:46:10 ... maybe define a practice for CRS reference and definition, perhaps machine readable? 13:46:22 ... or for UOM 13:47:04 ... there's a version on Webprotege, but this is hard to work with. Will work with ttl file on Github 13:47:13 ack next 13:47:14 aharth, you wanted to ask about conneg for geometry serialisations and to ask about possible compatibility with W3C wgs84_pos vocab 13:47:51 aharth: maybe possible to make the new voc compatible with the simple geo vocabulary by Brickley. 13:48:02 ... would be good for existing data on the web 13:48:28 ... Also, using conneg for serialization: can that be considered? 13:49:07 josh: compatibility with W3C vocabulary: looked at it, but in existing data the use of it is ambiguous. 13:49:24 ChrisLit has joined #Sdw 13:49:39 Present+ 13:49:40 ... so worthwile doing, but existing data might have meant different things. 13:50:18 present+ ChrisLit 13:50:51 ... About conneg: you could offer different serializations of the data. Have this in separate properties? 13:51:11 aharth: depends on which community you do it for. Using conneg on URI is fav of some communities 13:52:20 josh: how do you negotiate against a property within a geometry? Useful, but not clear how to. 13:52:26 ... will think on it 13:52:39 eparsons: continue this on email list 13:52:51 Topic : Coverages update 13:53:02 https://lists.w3.org/Archives/Public/public-sdw-wg/2016Jul/0172.html 13:53:43 billroberts: we made progress, in this email there's a proposal for what we should do in the coverages subgroup 13:53:51 ...a fair bit of work but achievable 13:54:00 ...need to move on to really doing stuff 13:55:09 ... take the CoverageJSON work, though incomplete, and see if that could become a W3C rec / OGC standard 13:55:58 ... conceptually it's compatible with existing work, but addressing a user group that is not happy with existing approaches. Web developer type audience. 13:56:18 ... also looking at how to use data cubes, different audience. 13:56:46 Q+ 13:56:53 ... For discussion: pure RDF datacube is useful for representing coverages, and a note could be writtne on how to do that 13:57:12 ... Also, outstanding tasks for BP narrative. 13:57:26 ... Also, plans to write a Primer alongside the spec. 13:58:03 ... we welcome opinions through maillist and our call next week. 13:58:18 ack next 13:58:46 ChrisLit: extensions to datacube model are needed. 13:59:30 ... e.g. datatiles, webtiles. Could be interesting followup work. Will get in touch with bill about this. 13:59:33 Any new coverage encodings or representation do need to share the conceptual model of existing coverages. 13:59:42 eparsons: out of time 13:59:47 thanks Chris - will follow up wiht you on that 14:00:07 ... will send email about meetings during holiday 14:00:25 One issue to explore is that the coverage conceptual model is really a mapping between domain and range spaces. Expression in grids or cubes is convenient, but not fundamental. 14:00:31 ... closes meeting 14:00:35 bye! 14:00:38 linda thank you !!! 14:00:38 thx bye 14:00:38 bye 14:00:38 bye1 14:00:42 thx Linda 14:00:48 bye ... thanks to Ed for Chairing and Linda for scribing 14:00:49 bye 14:00:50 rrsagent, draft minutes 14:00:50 I have made the request to generate http://www.w3.org/2016/07/20-sdw-minutes.html eparsons 14:00:54 bye 14:00:56 Nicky has left #sdw 14:01:06 Bye 14:29:40 jtandy has joined #sdw 16:08:03 Zakim has left #sdw 18:23:37 eparsons has joined #sdw 21:02:58 eparsons has joined #sdw