W3C home > Mailing lists > Public > public-sdw-wg@w3.org > May 2016

Re: Agenda for Best Practice sub-group, 14:00UTC 4-May-2016

From: Clemens Portele <portele@interactive-instruments.de>
Date: Wed, 4 May 2016 07:40:16 +0000
To: Jeremy Tandy <jeremy.tandy@gmail.com>
CC: SDW WG Public List <public-sdw-wg@w3.org>
Message-ID: <B33C6E26-9AA0-483F-A74D-9BC75C9D26AB@interactive-instruments.de>
My apologies for today. I thought the meeting yesterday was instead of the one today and now have another commitment for this afternoon.

Clemens



Am 03.05.2016 um 17:56 schrieb Jeremy Tandy <jeremy.tandy@gmail.com<mailto:jeremy.tandy@gmail.com>>:

Hi- the Best Practice sub-group meet again tomorrow. The agenda is posted here [1]. For convenience, the agenda items are copied below.

See you all tomorrow! (else please advise any regrets).

Jeremy

---
Agenda:
* Summary of main points from Best Practice sub-group 'virtual meeting', 3-May-2016 Minutes [2]
** Overview of flooding scenario required for non-technical users
** Flooding scenario focuses on single event not longer term 'flood [risk] prediction'
** Terminology ("real-world Thing" not "Feature")
** Crowd-sourced spatial data (best practices are ''mostly'' for the platform providers, not the crowd)- "Web is the data sharing platform"
** Spatial data web usage: "small" and "large" categories (offline [spatial] analysis is out of scope- it's not 'on the web')
** Prioritise data publication examples; include data usage if we've time left over
** BP Narrative 2 [3]: it's technical but fit for purpose ...
* Overview of BP Narrative 2 [3]
** (1) Publish flood inundation forecast data (the results of the urban flood prediction model) as a coverage dataset
** (2) Publish information about administrative areas within the municipality
** (3) Publish flood inundation forecast data as vector dataset and identify the administrative areas (?) that each inundation area is predicted to impact
** (4) Publish details of fixed assets (e.g. dikes & dams, buildings, roads, critical infrastructure etc.) and topographical features (e.g. water bodies)
** (5) Publish census data which contains population statistics for each administrative area [and cross reference with inundated areas to determine numbers of impacted citizens]
** (6) Publish the evacuation plan [as HTML with embedded markup & for use by downstream Web developers]
** (7) Publish real-time data-stream of water-level observations
** (8) Publish ‘volunteer geographic information’ using social media ... ''requires modification to reflect discussion from 'virtual meeting''' (minutes [2])
** (9) Publish Synthetic Aperture Radar data as a coverage dataset
* Allocate examples to WG members to complete (thanks to Josh, Andrea, Linda and Clemens for taking (7), (4) [metadata only], (3) and (2) respectively)
** (i) reference source implementations "in the wild"
** (ii) convert the implementation pattern to discuss the relevant aspect of the flooding scenario;
** (iii) create a full worked example; publish to GitHub?
** (iv) grab code snippets for the Best Practice document
* Should SDW Best Practices ''extend'' DWBP in just those areas that need extra guidance for spatial data?
** Don't Repeat Yourself (DRY): we're currently repeating much of DWBP!
---

[1]: https://www.w3.org/2015/spatial/wiki/Meetings:BP-Telecon20160504

[2]: http://www.w3.org/2016/05/03-sdwbp-minutes.html

[3]: https://www.w3.org/2015/spatial/wiki/BP_Narrative_2


Received on Wednesday, 4 May 2016 07:43:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:21 UTC