IRC log of sdwbp on 2016-05-04

Timestamps are in UTC.

14:01:38 [RRSAgent]
RRSAgent has joined #sdwbp
14:01:38 [RRSAgent]
logging to http://www.w3.org/2016/05/04-sdwbp-irc
14:01:40 [trackbot]
RRSAgent, make logs world
14:01:40 [Zakim]
Zakim has joined #sdwbp
14:01:42 [trackbot]
Zakim, this will be SDW
14:01:42 [Zakim]
ok, trackbot
14:01:43 [trackbot]
Meeting: Spatial Data on the Web Working Group Teleconference
14:01:43 [trackbot]
Date: 04 May 2016
14:02:09 [ScottSimmons]
present+ ScottSimmons
14:03:10 [phila]
agenda: https://www.w3.org/2015/spatial/wiki/Meetings:BP-Telecon20160504
14:03:18 [eparsons]
present+ eparsons
14:03:18 [phila]
regrets+ Clemens
14:03:25 [frans]
present+ frans
14:03:27 [phila]
zakim, code?
14:03:27 [Zakim]
I have been told this is SDW
14:03:46 [jtandy]
jtandy has joined #sdwbp
14:03:56 [phila]
zakim, this is https://mit.webex.com/mit/e.php?MTID=mbda94b24cafd410bd9c86a84e033919f meeting ID 643 407 318, pw sdwbp
14:03:56 [Zakim]
got it, phila
14:04:02 [phila]
zakim, save this description
14:04:02 [Zakim]
this conference description has been saved, phila
14:04:03 [jtandy]
zakim, code
14:04:04 [Zakim]
I don't understand 'code', jtandy
14:04:06 [phila]
zakim, code?
14:04:06 [Zakim]
I have been told this is https://mit.webex.com/mit/e.php?MTID=mbda94b24cafd410bd9c86a84e033919f meeting ID 643 407 318, pw sdwbp
14:04:14 [Linda|2]
present+ Linda
14:04:19 [phila]
present= phila
14:04:24 [phila]
present+ phila
14:04:38 [Linda|2]
regrets+ Payam
14:04:59 [billroberts]
present+ billroberts
14:05:05 [jtandy]
present+ jtandy
14:06:12 [frans]
top left?
14:06:19 [josh]
josh has joined #sdwbp
14:07:14 [josh]
present+
14:07:21 [MattPerry]
MattPerry has joined #sdwbp
14:07:30 [MattPerry]
present+ MattPerry
14:07:44 [eparsons]
scribe: eparsons
14:08:11 [eparsons]
topic : last weeks minutes
14:08:16 [jtandy]
scribenick: eparsons
14:08:18 [jtandy]
http://www.w3.org/2016/05/03-sdwbp-minutes.html
14:08:36 [jtandy]
Proposed: approve minutes of last meeting
14:08:40 [jtandy]
+1
14:08:42 [josh]
+1
14:08:44 [Linda|2]
+1
14:08:48 [eparsons]
+0
14:08:51 [ScottSimmons]
+1
14:09:07 [jtandy]
(actually = http://www.w3.org/2016/04/20-sdwbp-minutes)
14:09:19 [josh]
We're being supportive...
14:09:25 [frans]
+1
14:09:34 [Linda|2]
+1
14:09:37 [jtandy]
RESOLVED: approve minutes of last meeting (on 20 April)
14:10:01 [jtandy]
topic: patent call
14:10:05 [jtandy]
link: https://www.w3.org/2015/spatial/wiki/Patent_Call
14:10:05 [phila]
q+
14:10:14 [jtandy]
ack phila
14:11:11 [eparsons]
phila Pleased with jtandy good practice of checking irc and webex participants
14:11:53 [eparsons]
phila important for IPR reasions
14:11:55 [jtandy]
topic: Summary of main points from Best Practice sub-group 'virtual meeting', 3-May-2016 Minutes
14:12:37 [eparsons]
jtandy josh, lindy, phil (decorating) present on call yesterday - thanks to all
14:12:50 [jtandy]
s/lindy/linda/
14:13:13 [eparsons]
jtandy Seemed to work well, recommended as good way of working
14:13:24 [Linda|2]
Also Clemens, Andrea were there.
14:13:34 [Linda|2]
And Bart
14:13:52 [jtandy]
https://www.w3.org/2015/spatial/wiki/BP_Narrative_2
14:14:10 [eparsons]
jtandy flooding story rewrite by jtandy link above
14:14:39 [eparsons]
jtandy too techie language perhaps
14:15:53 [frans]
q+
14:15:57 [eparsons]
jtandy Flooding emotive subject - event not prediction of flooding is relevant only
14:16:02 [jtandy]
ack frans
14:16:44 [eparsons]
frans 2 versions really needed ?
14:17:49 [eparsons]
jtandy Not tech story with links to details or details mixed within narrative are the options, tech content is really needed and important
14:17:54 [Linda|2]
q+
14:18:04 [jtandy]
ack Linda|2
14:18:25 [josh]
q+
14:18:29 [eparsons]
jtandy DRY Don't Repeat Yourself
14:18:35 [jtandy]
ack josh
14:18:57 [eparsons]
Linda|2 Domain language was identified yesterday as issue
14:18:58 [AndreaPerego]
AndreaPerego has joined #sdwbp
14:19:26 [AndreaPerego]
zakim, what is the conference code?
14:19:26 [Zakim]
I have been told this is https://mit.webex.com/mit/e.php?MTID=mbda94b24cafd410bd9c86a84e033919f meeting ID 643 407 318, pw sdwbp
14:19:26 [eparsons]
josh Understandable to web and GI communities to issue
14:19:41 [eparsons]
josh Matching terms needed
14:20:07 [josh]
Example from yesterday: "spatial join" vs "mashup"
14:20:09 [eparsons]
jtandy Key to avoid hydrological terms
14:20:49 [eparsons]
jtandy "Real world Thing" is a useful term rather than feature
14:21:12 [jtandy]
q?
14:21:20 [eparsons]
jtandy Not Happy with thing but best we could come up with
14:21:20 [AndreaPerego]
present+ AndreaPerego
14:21:22 [jtandy]
ack Linda|
14:22:26 [eparsons]
jtandy Good talk of crowd sourcing - is the audience platform devs eg. twitter or users of platform api's
14:23:04 [eparsons]
jtandy Platform devs temselves eg twitter, facebook not so different to SDI publishers
14:23:35 [eparsons]
jtandy URL's to identify things good in tweets etc..
14:24:26 [eparsons]
jtandy eg. what 3 words
14:24:26 [frans]
q+
14:24:30 [ScottSimmons]
sorry - ScottSimmons must leave
14:24:36 [jtandy]
ack frans
14:25:28 [jtandy]
"acknowledge other types of platform providers as audience for BP doc" said Frans
14:25:32 [eparsons]
frans Platform devs good audience - Data Storage providers good also be interested - looking for guidance
14:26:33 [eparsons]
jtandy Audience discussion fruitful - SDI providers, twitter, API builders are all platforms of sorts
14:27:04 [eparsons]
josh All web server based technologies are platforms ?
14:27:20 [eparsons]
jtandy The web is the one platform to rule them all
14:28:38 [eparsons]
jtandy What does Spatial data on the web mean to Small publishers - links to other resources / large publishers more complex use of data
14:28:52 [eparsons]
jtandy josh ? anything to add
14:29:23 [eparsons]
josh similar cases - fine grained links not scalable - large is scalable
14:29:29 [jtandy]
"APIs that add scaleability to that fine grained access" said Josh
14:29:45 [eparsons]
jtandy loves josh
14:30:07 [eparsons]
jtandy platonic
14:30:52 [frans]
s/providers good also/providers could also/
14:30:52 [eparsons]
jtandy Our examples need to focus on data publication - first step if not published, cannot be used
14:31:14 [billroberts]
q+
14:31:18 [eparsons]
eparsons Agree completely
14:31:25 [jtandy]
ack billroberts
14:32:01 [eparsons]
billroberts Happy with focus on data publishers - risk we miss the step to make it easy for users of data
14:32:06 [josh]
The goal of publishing data to enable "better mashups" means that implementation feedback is crucial.
14:32:40 [eparsons]
jtandy Test the usage of data against each BP - "Is the data easy for users to access"
14:33:04 [eparsons]
billroberts Usage patterns need to promote use
14:33:23 [eparsons]
jtandy "web as data sharing platform"
14:33:24 [jtandy]
Topic: Overview of BP Narrative 2
14:33:35 [jtandy]
https://www.w3.org/2015/spatial/wiki/BP_Narrative_2
14:33:51 [eparsons]
jtandy Linda|2 has made updates to above
14:34:18 [eparsons]
jtandy Key points against 9 steps
14:34:43 [billroberts]
what?...wakes up
14:34:53 [eparsons]
jtandy First step publish flood prediction data as a coverage
14:34:53 [billroberts]
yes I was listening
14:35:19 [eparsons]
jtandy Nobody owns theis example - Bill ?
14:36:15 [eparsons]
jtandy Second step Admin Areas from SDI source using proxy layer
14:36:48 [eparsons]
jtandy includes CRS, precision etc
14:37:29 [eparsons]
jtandy third step - web developer takes coverage data - converts to vector features
14:37:36 [eparsons]
q
14:37:38 [eparsons]
q+
14:37:58 [jtandy]
ack eparsons
14:38:24 [josh]
WPS!
14:38:25 [eparsons]
eparsons Is that realistic for web dev ?
14:38:50 [eparsons]
jtandy Open source dev - might make an app..
14:40:31 [eparsons]
josh Might use a restful service to join spatial data
14:40:34 [frans]
Spatial joins are often needed
14:41:21 [eparsons]
josh spatial join wrong language mashup is more appropriate
14:42:18 [eparsons]
jtandy web dev called Helen wants to use her edge finding algorithm in javascript - so can do that
14:42:56 [eparsons]
jtandy Helens vectors are very details - brings in issue of performance - need to generalise for example ?
14:43:22 [eparsons]
jtandy - point taken think about better ways...
14:44:12 [eparsons]
jtandy Step Four publish fixed assets, topographical features not using SDI in this case - normal web tech
14:44:33 [eparsons]
jtandy SDI use case but not using SDI tech..
14:45:48 [eparsons]
jtandy Step five of interest to billroberts - Figure out number of people the food covers, CSV file of peoples location converted to RDF
14:46:13 [eparsons]
jtandy RDF data ingested into triple store for SPARQL query
14:46:39 [eparsons]
jtandy billroberts Is this your bag ?
14:47:19 [eparsons]
billroberts Almost - different tools - but census data as RDF is relevant
14:48:05 [eparsons]
billroberts CSV to RDF then exposed as SPARQL endpoint but small community
14:48:28 [eparsons]
jtandy Capture what billroberts does would be really useful
14:48:28 [frans]
q+
14:48:42 [jtandy]
ack frans
14:49:23 [billroberts]
q+
14:49:29 [jtandy]
ack billroberts
14:49:37 [eparsons]
frans Point 5 realistic ? Census publishers often use more advanced publishing tools
14:50:24 [eparsons]
billroberts 50% agreement with frans - Many do use csv however, jsonstat another common format, specific api's etc
14:51:02 [eparsons]
billroberts Good Step however..
14:51:37 [eparsons]
jtandy Realism is aim - BP needs to expose problems
14:51:57 [eparsons]
billroberts - Too much detail would be an issue in too real examples
14:52:57 [eparsons]
jtandy Not trying to build flood prevention system, details not relevant to our use of scenario
14:54:13 [eparsons]
frans Something not so based on semantics, weather data might be better, not as loading with semantic problems in stats
14:54:48 [eparsons]
jtandy maybe, pop broken down into groups
14:55:27 [eparsons]
jtandy Step six - emergency teams use GIS to create evac plan
14:57:06 [eparsons]
jtandy Take GIS analysis product and publish as html, or API for embedded use on web pages
14:57:22 [eparsons]
jtandy eparsons would you work on this
14:57:27 [eparsons]
eparsons yes !!
14:57:52 [eparsons]
jtandy Step seven data streams - josh to take up
14:58:55 [eparsons]
jtandy step eight - social media examples, twitter users advertising phone charging, Instagram users taking pictures of floods
14:59:14 [eparsons]
josh links to step seven
14:59:45 [eparsons]
josh IoT testbed, causing stress with SSN work however
15:00:30 [eparsons]
jtandy step nine - most event SAR data cross referenced with insurance data
15:00:34 [jtandy]
Topic: Allocate examples to WG members to complete
15:00:40 [eparsons]
jtandy - makes sense ?
15:01:10 [eparsons]
jtandy - Step 1 coverage data needs someone to help work on..
15:01:21 [eparsons]
jtandy - Step 2 clemens
15:01:29 [eparsons]
jtandy step 3 - Linda|2
15:01:43 [eparsons]
jtandy Step 4 - Andrea
15:02:00 [eparsons]
jtandy Step 5 - billroberts
15:02:12 [eparsons]
jtandy Step 6 -eparsons
15:02:32 [eparsons]
jtandy steps 7 & 8 - josh
15:03:37 [eparsons]
jtandy Linda|2 had added to narrative for step 3 good example
15:03:43 [jtandy]
Topic: AOB
15:04:04 [eparsons]
RRSAgent, make logs public
15:04:24 [eparsons]
rrsagent, draft minutes
15:04:24 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/05/04-sdwbp-minutes.html eparsons
15:04:25 [frans]
Thanks to all the BP people!
15:04:27 [josh]
bye
15:04:28 [AndreaPerego]
bye
15:04:37 [eparsons]
Bye
15:04:37 [Linda|2]
bye
15:04:39 [josh]
josh has left #sdwbp
15:05:03 [phila]
RRSAgent, draft minutes
15:05:03 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/05/04-sdwbp-minutes.html phila
15:08:47 [phila]
chair: Jeremy
16:20:10 [phila]
zakim, bye
16:20:10 [Zakim]
leaving. As of this point the attendees have been phila, billroberts, jtandy, josh, MattPerry, AndreaPerego
16:20:10 [Zakim]
Zakim has left #sdwbp
16:20:14 [phila]
RRSAgent, bye
16:20:14 [RRSAgent]
I see no action items