10:44:13 RRSAgent has joined #sdwbp 10:44:13 logging to http://www.w3.org/2016/05/03-sdwbp-irc 10:44:15 RRSAgent, make logs world 10:44:15 Zakim has joined #sdwbp 10:44:17 Zakim, this will be SDW 10:44:17 ok, trackbot 10:44:18 Meeting: Spatial Data on the Web Working Group Teleconference 10:44:18 Date: 03 May 2016 10:44:39 zakim, help? 10:44:39 Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help. 10:44:41 Some of the commands I know are: 10:44:41 xxx is yyy - establish yyy as the name of unknown party xxx 10:44:41 if yyy is 'me' or 'I', your nick is substituted 10:44:42 xxx may be yyy - establish yyy as possibly the name of unknown party xxx 10:44:42 I am xxx - establish your nick as the name of unknown party xxx 10:44:42 xxx holds yyy [, zzz ...] - establish xxx as a group name and yyy, etc. as participants within that group 10:44:42 xxx also holds yyy - add yyy to the list of participants in group xxx 10:44:42 who's here? - lists the participants on the phone 10:44:42 who's muted? - lists the participants who are muted 10:44:43 mute xxx - mutes party xxx (like pressing 61#) 10:44:43 unmute xxx - reverses the effect of "mute" and of 61# 10:44:43 is xxx here? - reports whether a party named like xxx is present 10:44:44 list conferences - reports the active conferences 10:44:44 this is xxx - associates this channel with conference xxx 10:44:44 excuse us - disconnects from the irc channel 10:44:44 I last learned something new on $Date: 2015/08/27 12:24:56 $ 10:44:49 RRSAgent, help? 10:44:49 I'm logging. Sorry, nothing found for 'help' 10:45:05 RRSAgent, you really hsould have a help file 10:45:05 I'm logging. I don't understand 'you really hsould have a help file', phila. Try /msg RRSAgent help 10:45:40 jtandy the RRSAgent help file is at https://www.w3.org/2002/03/RRSAgent 10:46:54 Ah, good 10:48:34 meeting: SDW BP Special meeting 10:48:38 chair: jtandy 10:48:48 rrsagent, make logs public 10:49:35 agenda: https://www.w3.org/2015/spatial/wiki/Agenda_BP_VM_May_2016#Dial-in_details 10:50:03 RRSAgent, draft minutes 10:50:03 I have made the request to generate http://www.w3.org/2016/05/03-sdwbp-minutes.html phila 10:50:22 rrsagent, make logs public 10:50:25 RRSAgent, draft minutes 10:50:25 I have made the request to generate http://www.w3.org/2016/05/03-sdwbp-minutes.html phila 10:57:23 Linda has joined #sdwbp 11:00:15 present+ jtandy, Linda 11:03:47 ClemensPortele has joined #sdwbp 11:04:09 present+ ClemensPortele 11:04:55 Agenda is at: https://www.w3.org/2015/spatial/wiki/Agenda_BP_VM_May_2016#Main_agenda_.28DRAFT.29 11:05:43 Looks like the Goto meeting is started ... 11:06:35 Payam has joined #sdwbp 11:06:56 scribe: jtandy 11:07:52 scribe: Clemens Portele 11:08:01 scribenick: ClemensPortele 11:08:12 Topic: Patent Call 11:08:46 Topic: Check agenda 11:08:56 https://www.w3.org/2015/spatial/wiki/Agenda_BP_VM_May_2016 11:09:34 jtandy: will not be able to work through all of this 11:10:20 jtandy: Work on spatial ontology will be spin off to a separate activity, not this meeting 11:10:22 AndreaPerego has joined #sdwbp 11:10:32 https://www.w3.org/2015/spatial/wiki/BP_Narrative_2 11:10:39 (revised flooding scenario) 11:10:49 present+ AndreaPerego 11:11:49 +1 11:11:54 jtandy: We should go through the narrative and identify where we have best practices, recommended practices or gaps 11:12:46 jtandy: a bit of a challenge to get stuff into the BP document 11:13:31 jtandy: ... are we writing them from an SDI user/provider perspective, from the perspective of someone not familiar with SDIs, etc. 11:13:57 jtandy: anything else for the agenda? 11:14:00 (silence) 11:14:48 +1 11:14:55 +1 11:15:29 The proposed agenda is approved 11:15:34 BartvanLeeuwen has joined #sdwbp 11:15:38 hi 11:16:34 jtandy: may stop the meeting for a while a split into subgroups 11:18:26 original narrative 11:18:26 https://www.w3.org/2015/spatial/wiki/BP_Narrative 11:19:59 jtandy: questions was "how do people should contribute"? Difficult with the first narrative 11:20:16 jtandy: created second version of the narrative 11:20:18 who has read https://www.w3.org/2015/spatial/wiki/BP_Narrative_2 11:20:27 -1 11:20:28 -1 11:20:32 +1 11:20:36 +1 (but partially) 11:20:54 I did find it rather technical 11:21:21 Payam: what do want to achieve today? what can make our day productive? 11:22:44 jtandy: ensure that the (currently 9) steps cover everything or do we need a different approach. Identify where we can get best practices from and who can lead on those? 11:23:44 Payam: Do we go through them one-by-one or do we split? 11:24:15 jtandy: Not sure, need to see. Let's first go through the list in the group 11:26:03 jtandy: overview of narrative 2 11:26:22 joshlieberman has joined #sdwbp 11:26:33 jtandy: ... context at the beginning (no details) 11:28:08 jtandy: regarding the comment on this being technical, this is meant for a technical audience 11:28:32 question: is it right to pose this as a technical best practice / scenario 11:28:35 +1 11:29:13 +1 11:29:16 +1 11:29:32 I'm hoping that it addresses the needs of the BP audience 11:29:35 +1 - but shouldn't we have in mind also a non-technical audience? 11:29:36 +1 11:30:08 Bart, could you explain why you found it technical? 11:30:50 flooded area? 11:31:21 Linda: maybe avoid domain expert language? 11:31:30 terminology: avoid terms like "inundation extent" in favour of "flood extent" or "how far did the water reach" 11:32:36 Payam: maybe create two versions of the same story, one more technical and one less technical? 11:33:00 Payam: ... today we would work on the technical one (narrative 2) 11:33:30 payam: suggests we have a non-technical summary of the scenario as a complement to the technical version 11:34:09 I had the impression that there were some very domain specific terms in there 11:34:33 I agree Bart 11:34:52 proposed: we have a non-technical overview of the scenario to complement the technical version 11:35:03 Payam: Bart's comment is related to the terminology discussion earlier 11:35:05 I had to lookup some specific weahter / flooding related terms 11:35:21 +1 11:35:23 +1 11:35:28 +1 11:35:28 +1 11:35:29 +1 11:35:41 Resolution: we have a non-technical overview of the scenario to complement the technical version 11:36:42 q+ to make a general comment on "flood prediction" as a sensitive subject. 11:36:45 Linda: avoid domain specific terms in the technical version too 11:36:47 +1 11:36:51 +1 11:36:53 +1 11:36:56 +1 11:36:57 ack AndreaPerego 11:36:57 AndreaPerego, you wanted to make a general comment on "flood prediction" as a sensitive subject. 11:37:55 AndreaPerego: flood prediction is a sensitive subject, eg may have an impact on insurance rates 11:38:38 AndreaPerego: ... do we need to take this into account (potential misuse of the information)? 11:40:26 jtandy: everything that may have economic impact will be a sensitive subject. The narrative is not about publishing authoritative information, just someone who wants to help. 11:41:21 +1 - agreed. 11:41:27 jtandy: The waterboard (for example) would validate the data before using it. Maybe talke this into account later in the story? 11:41:55 The concern may not just be whether data is authoritative, but whether the Web application leads people to appreciate what the term "100 year flood" means for them. 11:42:37 jtandy: points to the text in step 8 that touches on the subject 11:43:59 intent (of SDW): web publishing is one in such a way that the connections between data can be followed 11:44:10 (said joshlieberman) 11:44:27 joshlieberman: even if we do not use technical terms, we still use technical concepts that need to be linked to from the data 11:44:36 joshlieberman: not so much data, but connections between data and its meaning or implication 11:45:37 jtandy: better look at a certain flooding event, not the long-term flooding prediction 11:46:43 Linda agrees 11:46:44 +1 11:47:10 jtandy: the story is just a vehicle to illustrate what we are doing 11:47:40 jtandy: step 1 11:47:56 https://www.w3.org/2015/spatial/wiki/BP_Narrative_2#.281.29_Publish_flood_inundation_forecast_data_.28the_results_of_the_urban_flood_prediction_model.29_as_a_coverage_dataset 11:48:40 +1 to stick to a single event instead of prediction 11:48:56 jtandy: coverage data suitable for use in web applications 11:50:02 jtandy: issues like versioning, volume, need for data extraction, bulk download for offline analysis 11:50:24 jtandy: quite a common scenario 11:50:25 +1 11:50:30 +1 11:51:32 next step - turn coverage into vector features 11:51:58 https://www.w3.org/2015/spatial/wiki/BP_Narrative_2#.282.29_Publish_information_about_administrative_areas_within_the_municipality 11:53:04 jtandy: how do I publish the admin area information on the web? 11:53:25 jtandy: Geonovum testbed topic 4 is related 11:54:12 jtandy: support for multiple formats including those for geo experts 11:54:37 jtandy: how far do we want to pursue Linked Data? 11:55:18 jtandy: also need to cover the feature / real-world thing subject 11:56:13 Linda: sounds like a large chunk (covers many BPs) 11:56:38 We use the term feature, but most Web developers think that's some capability of their software. Real world thing is more evocative for them, so we'd need to do quite the education job to switch 11:56:58 +1 to josh 11:58:00 jtandy: need to decide whether we recommend only one approach? 11:58:03 q+ 11:58:05 Argue that there may be two categories of tasks with Web technology -- link to data over the Web and use the Web to bring data together 11:58:16 ack ClemensPortele 11:59:43 ClemensPortele: "there's not a one-size fits all" solution 12:00:02 joshlieberman: there's a set of sizes ... 12:01:29 joshlieberman: "small" = linking _to_ something and "large" = integrate information together 'on the web' without needing to download stuff for offline work or use some obscure API 12:01:53 +1 12:02:42 jtandy: agrees, some will use the SDI as a starting point, others come from a different starting point 12:03:12 jtandy: ... same best practice applies, just different approaches to the same outcome 12:03:21 +1 12:04:21 jtandy: "small" would mean to publish resources with URIs? 12:05:09 joshlieberman: yes, fine-grained URIs. Or for queries to access 500 features to put them on a map. Both are needed 12:06:14 joshlieberman: "does the API let me make a single request to get 500 Features - rather than 500 fine grained requests, each with a URL of a Feature" 12:08:11 jtandy: what is the ecosystem for using spatial data on the Web? Using the Browser as the platform for application? 12:08:52 using data on the web: (i) referencing a resource that someone else has published via URL in _my_ data, (ii) integrating multiple data sources using 'Web engines' as application runtime environment 12:10:08 jtandy: classic process of downloading data and processing it in a GIS is not what we are looking at 12:10:11 Does the notion of "Web engine" includes machine-to-machine use cases? 12:10:36 jtandy: ... our focus is more the processing on the Web 12:10:43 Yes to @AndreaPerego 12:10:51 Thanks! 12:11:20 another classification of users: can our intended user base by classified by ‘those who are publishing information about individual Features’ and ‘those who are publishing information about collections of Features (e.g. as a dataset) … the former need to rely on the platform into which they publish to make their information discoverable [& accessible] and to expose provenance and licensing information; e.g. Twitter search API, search engines etc. 12:12:35 ... another Small and Large perspective 12:12:58 Should we also consider the (integrated) use of third-party / non-authoritative data here? E.g., OSM, Geonames. 12:13:44 joshlieberman: part of the web is others harvesting individually published information in large amounts 12:14:31 joshlieberman: small scale = publishing tweets from the area / with reference to the flooding 12:14:52 joshlieberman: "Small" = create a map with a pin on for the location of each #flood geo-located tweet ... just links 12:15:05 joshlieberman: large scale = merging this information with the admin units etc and analysing this to identify discrepancies etc 12:16:48 are we writing best practices for the people _using_ social media, or the social media platform providers to make sure the _aggregate_ set of social media can be exposed as spatial data? 12:18:23 joshlieberman: BPs should be helpful for platform providers 12:19:01 interpreting joshlieberman: we are writing best practices for social media platform providers - and _any_ platform provider that has spatial information 12:19:30 ... implication is that that might drive collection of particular information from users of the platform 12:20:38 jtandy: when thinking about crowdsourcing - we are more focussing on the platform that is used for crowdsourcing 12:21:02 joshlieberman: but this will be also about what the platform users want 12:21:57 Linda: agrees that the platform is the main focus 12:22:25 joshlieberman: but if the SDI has all the URIs for locations, Twitter users could use them in tweets without Twitter doing anything 12:23:17 "small" size of problem = encouraging people to use URLs for the things they might Tweet about 12:23:57 Payam: sees it a bit different, it is also about how people could send tweets (or publish the data) so that it can be used easily by others 12:24:25 s/the data/data/ 12:25:50 jtandy: The Web is the platform in this case? 12:27:09 interpreting Payam's comment: crowdsourcing information ... people will use the _web_ as the data sharing platform- either directly as Web resources, or via an App or some other platform 12:27:30 Here is a case: someone might tweet: #flooding the water is 2 feet deep at my house. Analysis requires parsing 2 ambiguous statements. Alternately: #flooding [2 feet] @{link to my house feature}. 12:29:01 RRSAgent, draft minutes 12:29:01 I have made the request to generate http://www.w3.org/2016/05/03-sdwbp-minutes.html phila 12:29:07 (people might publish information about their house flooding in a blog entry; native HTML perhaps) 12:29:55 Payam: cannot tell the Twitter user how to write tweets, but apps may provide a framework to make aggregated data reusable 12:29:55 payam: we're targeting the part of the story that enables the aggregated set of information on a platform to be access from / published to the web in a consistent way 12:31:05 there's the special case when people write HTML directly- but the majority of cases, people use a platform to do that 12:31:37 joshlieberman: usually there are lightweight means to help interpretation (eg the use of hashtags in tweets) 12:32:23 joshlieberman: what is the minimum that people could do to make their contribution more usable 12:32:46 joshlieberman: "what's the minimum we could ask people to do to make their [data] contribution more usable ... e.g. use a URL for the thing you're talking about!" 12:34:54 jtandy: so a recommendation would be to use a format that supports links 12:35:04 our BPs will include "use URLs when you talk about things" 12:35:25 joshlieberman: so we need to make the URLs for things easy to find 12:35:44 joshlieberman: ... e.g. small / tiny and easy to type 12:37:31 we're seeing Twitter (etc.) "just" as a Platform Provider that has spatial data that should be on the Web ... so our advice is targeted toward the Twitter API developers 12:37:56 q+ to ask if we should also consider the (integrated) use of third-party / non-authoritative data here? E.g., OSM, Geonames. 12:38:00 jtandy: anything else on crowdsourcing? 12:38:08 ack AndreaPerego 12:38:08 AndreaPerego, you wanted to ask if we should also consider the (integrated) use of third-party / non-authoritative data here? E.g., OSM, Geonames. 12:39:04 example of (pretty) tiny urls for locations: http://w3w.co/pumpkin.dwarves.issuer 12:39:27 AndreaPerego: also the cases where "authoritative" data may not be available 12:41:17 jtandy: so not just considering the publication of government data, but also other data like OSM or geonames 12:41:28 s/considering/consider/ 12:41:35 AndreaPerego: suggest linking stuff to non-authoritative URLs e.g. geonames or OSM ... non-official information 12:43:22 it sounds like a discussion on 'crowd truth' 12:43:29 :) 12:44:30 q+ 12:44:36 ack AndreaPerego 12:45:25 ClemensPortele: the result is the same, the important aspect is that we can link to location using URIs 12:46:08 joshlieberman: Twitter API has data structure for places 12:47:32 should we use the term Feature? 12:47:32 jtandy: let's go back to the "feature" topic 12:48:19 joshlieberman: confusion from IoT - folks often mean a software or IoT device capability 12:48:19 joshlieberman: divergence on terminology (feature = 'software capability' for many) 12:49:31 jtandy: should we impose the geo terminology on the world? 12:50:39 joshlieberman: we should have a "general feature model for dummies section" if we're going to use the term Feature 12:50:57 -1 to feature its a spatial expert thing 12:51:08 ClemensPortele: try to avoid geo-jargon where possible 12:51:33 +1 to Clemens & Bart 12:51:53 ClemensPortele: at the same time we need to mention it to be clear to the geo experts 12:52:09 BTW, was intentionally excluded from LOCN for the same issues. 12:52:32 s/BTW, was intentionally excluded from LOCN for the same issues./BTW, "feature" was intentionally excluded from LOCN for the same issues./ 12:52:35 Proposed: use alternative term to Feature in most of BP doc ... use the term Feature just once (to keep spatial experts clear on what we mean) 12:52:50 +1 12:52:59 +1 12:52:59 +1 12:53:05 +1 12:53:16 Resolution: use alternative term to Feature in most of BP doc ... use the term Feature just once (to keep spatial experts clear on what we mean) 12:53:35 Quoting: "If you're a geospatial dev, AJAX is not a domestic cleaning product. A polygon is not a dead parrot." -@open_data #LGD14 #geospatialhumour 12:53:55 :) 12:54:04 :D 12:54:27 what about SpatialThing? 12:54:53 joshlieberman: real-world Thing is quite evocative ... but doesn't cover the non-geo cases 12:55:19 Linda: spatial object in Geosparql 12:55:21 I think "spatial thing" is generic enough to be understood by most people. 12:55:27 ClemensPortele: this is the geometry 12:56:04 ClemensPortele: SpatialResource? 12:56:30 we need a term for "a thing that has location and a URI" 12:57:04 ClemensPortele: not necessarily "has location", but "related to a location" (?) 12:57:37 jtandy: (cites what some of the existing vocabularies have used) 12:58:46 AndreaPerego: LOCN avoids this, but using only the concrete terms without restricting their use 12:59:42 joshlieberman: in GeoRSS we used OWL Thing > Spatial Thing > Feature > Geometry ... but hey 13:00:11 schema.org uses "Place" 13:01:01 joshlieberman: for many linked to point locations, but in general are meaningful term 13:01:03 joshlieberman: would like to use Place- very useful for geo-humanities ... but often related to just a point location ... but we could address this in our definition 13:01:40 RRSAgent, draft minutes 13:01:40 I have made the request to generate http://www.w3.org/2016/05/03-sdwbp-minutes.html phila 13:01:51 I think not spatial people will talk about points / places anyway 13:01:54 jtandy: need to keep in mind that spatial is more than geo 13:02:42 +1 - e.g., geometry as the "shape" of a thing. 13:03:30 joshlieberman: geographers use "place" often as a synonym for "feature", not "location" 13:04:49 Proposed: we use the term SpatialThing because it has 'provenance' of over a decade 13:04:56 joshlieberman: quite obscure 13:05:04 Just "thing". 13:05:54 joshlieberman: "real-world thing"? 13:06:28 q+ 13:07:01 Proposed: we use "real-world Thing" or sometimes just "Thing" in place of the term Feature 13:07:09 ack AndreaPerego 13:07:29 +1 13:08:06 +1 (at least we can try if it works) 13:08:57 AndreaPerego: are abstract things like computer drawings included? 13:09:36 noting that we mean 'real-world' as in the 'universe of discourse', which should include fictional and abstract concepts 13:10:15 AndreaPerego: need to be more than "things we can touch" - need to cover abstract concepts too 13:10:24 ClemensPortele: like cadastral parcel 13:11:41 AndreaPerego: the notion of 'real-world' could be confusing - so our definition needs to make sure its clear that we also include abstract stuff 13:12:20 joshlieberman: let's use 'real-world Thing' with the disclaimer 'imaginary', 'abstract' etc. 13:12:34 +1 13:12:46 joshlieberman: as per Feature, it may not have representation - but it always has identity 13:12:50 +1! 13:13:39 proposed: we use "real-world Thing" or sometimes just "Thing" in place of the term Feature; with caveat that it includes abstract / imaginary / fictional entities ... as per Feature, it may not have representation - but it always has identity 13:14:07 +1 13:14:10 +1 13:14:51 (representation implies geometry etc. ... not the wider Web term) 13:14:55 +1 13:15:03 +1 13:15:11 "embodiment" (equally obscure) 13:15:11 Linda: geometry or a link to a location 13:15:21 +1 13:15:24 +1 13:15:29 Resolution: we use "real-world Thing" or sometimes just "Thing" in place of the term Feature; with caveat that it includes abstract / imaginary / fictional entities ... as per Feature, it may not have representation - but it always has identity 13:16:39 (short break) 13:16:47 [returning to the meeting at 13:30 utc] 13:20:17 RRSAgent, draft minutes 13:20:17 I have made the request to generate http://www.w3.org/2016/05/03-sdwbp-minutes.html jtandy 13:33:56 joshlieberman has joined #sdwbp 13:34:16 present+ / - 13:34:37 (starting again) 13:34:54 jtandy: let's get back to the narrative 13:35:23 step 3 13:35:37 https://www.w3.org/2015/spatial/wiki/BP_Narrative_2#.283.29_Publish_flood_inundation_forecast_data_as_vector_dataset_and_identify_the_administrative_areas_.28.3F.29_that_each_inundation_area_is_predicted_to_impact 13:35:59 jtandy: take SDI data and do something useful with it 13:37:10 jtandy: covers spatial analysis, identifiers to features, linking 13:37:38 jtandy: do we need to discuss spatial analysis or just assume he/she is using some library 13:37:55 do we need to talk about the spatial analysis? or just say that our developer is "using a library" 13:38:09 Linda: the latter 13:38:42 joshlieberman: different persons would use different terminology (eg the spatial analyst may use "spatial join") 13:39:26 joshlieberman: an spatial analyst calls this "a spatial join"; a web developer might says they are "integrating datasets" or combining two sources of data ... 13:39:36 ClemensPortele: a 'mashup' 13:40:01 joshlieberman: use both terms in our doc to appeal to both types of users 13:40:37 question: is there a specific javascript library we can cite? 13:42:24 jtandy: (walks through step 3 and the BPs referenced) 13:43:09 Linda: Are there overlaps between the steps? 13:43:20 q+ 13:43:35 ack Linda 13:43:36 jtandy: not yet a proper analysis, but there is overlap 13:44:17 Linda: Should we assign work for these steps? 13:45:14 jtandy: good idea. What we are looking for is how to figure out you would do it with a real-life implementation 13:45:36 Linda: ... point to existing implementation(s) 13:46:57 jtandy: Yes, but those may not exactly fit the flooding scenario 13:47:14 two tasks then: (i) point to existing implementations, (ii) frame those implementation patterns in the flooding scenario 13:47:59 payam likes the idea of creating a full example - e.g. for publication in GitHub ... and then taking code snippets for the BP doc 13:48:44 ... but always being able to reference a full example ... and hopefully, the original source implementation that our example apes 13:49:11 "this example is derived from what they did over there" 13:50:32 http://environment.data.gov.uk/flood-monitoring/doc/reference 13:50:47 Environment Agency Real Time flood-monitoring API: Environment Agency Real Time flood-monitoring API 13:51:26 unlikely to find implementation examples all in flooding domain- need to see the implementation patterns we want people to use and convert the subject to flooding ... 13:53:15 joshlieberman: often it may be difficult to point to existing JavaScript code that implements a best practice 13:53:41 jtandy: some examples will exist (see the coverage work eg in step 7), often from a different domain 13:55:13 joshlieberman: key issue for river gauge datastream is about pulling together information from the sensor and the location data in the SDI (linked geometries) and 'mash' those up in an application 13:55:32 (this is the "Large" type of usage) 13:56:41 scribe: Linda van den Brink 13:56:47 scribenick: Linda 13:58:00 Payam: does Metoffice do something like the environmental agencies ie publishing their data as API? 13:58:09 jtandy: no 13:58:56 The US has some "services" but mostly graphical -- http://water.weather.gov/ahps/about/about.php 13:59:00 jtandy: in terms of work on the first 3 narrative parts... 13:59:22 ... do we want to give clemens nr 2? 13:59:30 Linda: makes sense 14:00:46 e.g. the API's may only be as far as RSS: http://water.weather.gov/ahps/rss/forecasts.php 14:01:19 action: Linda to ask Clemens to provide an example for narrative item 2 14:01:19 Created ACTION-163 - Ask clemens to provide an example for narrative item 2 [on Linda van den Brink - due 2016-05-10]. 14:02:02 I'll need to depart as well. Apologies. I can do some work on #7 14:02:57 bye 14:03:01 joshlieberman has left #sdwbp 14:03:05 +1 14:04:04 jtandy: the way examples are used in the narrative_2 these are technical tasks that allow us to illustrate the best practices, yes? 14:04:20 +1 14:04:24 +1 14:04:25 +1 14:04:55 action: joshlieberman to work on narrative item 7 14:05:00 Created ACTION-164 - Work on narrative item 7 [on Joshua Lieberman - due 2016-05-10]. 14:05:08 yqp 14:05:31 jtandy: AndreaPerego, do you want to discuss anything before you leave? 14:05:41 AndreaPerego: no, it was quite productive 14:06:56 AndreaPerego: Am looking how I can contribute. Maybe something about metadata? 14:07:18 jtandy: it's not explicit because metadata is embedded in all of these things 14:07:51 AndreaPerego: it's mostly about the data 14:08:26 jtandy: but we have to publish the metadata anyway. It's necessary for us to publish some geodcat-ap stuff and a landing page with schema.org 14:09:07 AndreaPerego: it's part of number 1 I think 14:09:38 Linda: yes, I think it should be somewhere in the beginning 14:10:01 jtandy: let's add it to item 4 14:10:11 AndreaPerego: agrees 14:10:12 s/yqp/yep/ 14:11:44 action: AndreaPerego to add a section about publishing metadata to item nr 4 14:11:44 Created ACTION-165 - Add a section about publishing metadata to item nr 4 [on Andrea Perego - due 2016-05-10]. 14:12:28 AndreaPerego: the opensearch and geo extension are more about data? 14:12:36 jtandy: yes, about searching through the data 14:13:04 ... also keen to pick up on making info available for search engines to index. 14:13:32 ... also look at the work done within Geonovum testbed topics 3 and 4 on this. 14:13:56 AndreaPerego: also we are now working on mapping geodcat-ap to schema.org 14:17:42 jtandy: should we have the biweekly SDW BP subgroup call tomorrow? 14:18:04 Payam: we could continue this discussion 14:18:07 +1 14:18:11 +1 14:18:42 jtandy: so tomorrow we'll continue to work on these narrative parts and try to allocate them to people 14:19:41 ... about Bruce Bannerman's email: should we try to also include some usage? My concern is this could mean we could never finish the work. 14:19:55 ... if we try to describe in our BP how people should use spatial data 14:20:08 see email response to Bruce here: https://lists.w3.org/Archives/Public/public-sdw-wg/2016Apr/0104.html 14:20:21 potential data usage examples: 14:20:22 * web developer uses inundation coverage data to build a web app that 14:20:22 returns discrete (vector) Features for inundation areas 14:20:22 * web developer determines which administrative areas 'touch' inundation 14:20:22 areas 14:20:23 * emergency teams prioritise critical infrastructure to protect by 14:20:23 identifying categories of assets that are 'within' inundation areas - or 14:20:23 care-homes to assist with evacuation 14:20:23 * emergency teams determine hazard exposure by requesting water depth at 14:20:24 coordinates of critical infrastructure 14:20:24 * section (5) illustrates combining census data that is geocoded by 14:20:24 administrative areas with the administrative areas that are affected by 14:20:24 inundation 14:20:24 * emergency teams create the evacuation plans; refuges and safe transit 14:20:24 routes- no doubt a complex piece of GI analysis 14:20:24