Warning:
This wiki has been archived and is now read-only.

Meetings:BP-Telecon20160504

From Spatial Data on the Web Working Group
Jump to: navigation, search

Agenda for SDWWG BP Sub Group teleconference 4 May 2016 14:00 UTC

  • Chair: Jeremy
  • Scribe: TBD
  • Regrets: Clemens

Preliminaries

  1. Check bots are running (see below)
  2. Matching everyone on IRC and Webex: Each person should type 'present+ ' followed by their name.
  3. Appoint Scribe. Scribe should enter 'regrets+ ' followed by the names of people who have sent regrets (ideally by adding their own name to this page)
  4. Approving last meeting's minutes
  5. Patent Call

Main agenda

  • Summary of main points from Best Practice sub-group 'virtual meeting', 3-May-2016 Minutes
    • 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: it's technical but fit for purpose ...
  • Overview of BP Narrative 2
    • (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)
    • (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!

Dial in details

NB These details only apply for the BP sub group, they are different from the joint calls

  Joining instructions: (official participants and invited guests only)
  For audio: WebEx link
  Check IRC for password
  For text discussions, minutes, joining the speaker queue, actions & issues IRC channel: #sdwbp on irc.w3.org on port 6667
  Please be sure to join both IRC and WebEx and use the same nick in both (or it gets very confusing)
  When you join the IRC channel, please immediately type 'present+ {yourname}' (this adds your name to the participants list in the minutes)
  If you dial in by phone you'll need this:
  Meeting number: 643 407 318 
  Audio connection: +1-617-324-0000 (US Toll Number )
  See WebEx Best Practices for more
  W3C Telecon Resources:
  Zakim instructions in English
  Basic instructions in Portuguese

To start the meeting, check that trackbot is in the IRC channel (it usually is). If not, type:

/invite trackbot

Then you can type:

trackbot, start meeting

That should invite zakim and RRSAgent and generally get things ready to go. As a reminder: the Zakim IRC bot handles things like the speaker queue, RRSAgent handles the minute-taking, present and regrets list etc.

Please note that you will see a message that Zakim does not see any meetings scheduled at this time. This is a reference to the old conference bridge (also called Zakim) that is no longer in use. Scheduling is now done under the WebEx system. If you're feeling nostalgic for the old Zakim greeting, it's archived (of course).

Once you have started the meeting, you should see all three bots running:

If any are not in the room, type /invite and then the name of the bot

During the meeting you may need to set the access permissions on the chat log with this command:

RRSAgent, make logs public

Then to create the minutes, type RRSAgent, draft minutes

Annotations

Minuteshttps://www.w3.org/2016/05/04-sdwbp-minutes +
ScribeEd +
SubjectVirtual meeting summary & tasking +
TypeTelecon +
Date
"Date" is a type and predefined property provided by Semantic MediaWiki to represent date values.
May 4, 2016 +