Labels

• bug: bad link

  broken link or reference
• bug: code

  markup or JS error
• bug: need info

  Important information or reference is missing.
• bug: typo

  typos or suggested wording improvements
• bug: upstream
• discussion: capability

  a specific capability or feature: should it be included? what details? should it be a requirement?
• discussion: cost-benefit tags

  all aspects of the priorities sections and cost-benefit tags
• discussion: report structure / other sections

  organization and structure of the report, or discussion of the intro/conclusions
• discussion: sample JS tool

  an existing web map tool: should we include it in the review? what should we say about it?
• discussion: use case

  a possible use case: should it be included? what should it say?
• duplicate
• help wanted
• meta/process

  An issue related to how the work or repo is managed.
• progressive enhancement
• section: client-side API

  Capabilities & use cases for client-side APIs
• section: data formats

  Capabilities & use cases for map data (file & server API) formats
• section: examples

  Discussion of the example pages
• section: introduction

  discussion of the introduction to the report
• section: map viewer

  Capabilities & use cases for declarative map viewer widgets
• section: principles

  The "Guiding Principles" section, including the tag definitions.
• section: reference tools

  The "Reviewed JavaScript Tools" overview section
• status: editor's draft

  there's a draft section in the report that corresponds to this discussion
• status: placeholder

  there's a matching section heading / some text in the report, but it's far from complete
• status: removed/merged

  This section has been removed or merged into another section.
• status: suggestion

  this issue discusses a suggested addition to the report, that is not yet in the draft