Merge pull request #208 from opengeospatial/issue-189

New Title

PR merged after the 2 week review period as discussed in the 20 May 2019 conference call.

Parts.md

@@ -1,17 +1,18 @@
-# WFS
+# OGC API - Features
 
-## Part 1 - Core
+## Current parts under development
 
-* see draft
+* Part 1: Core
+* Part 2: Extension for Coordinate Reference Systems (by reference)
 
-## Capabilities to be supported in additional WFS parts
+## Capabilities to be supported in additional parts
 
 * Transactions
 * Locking
 * 2D geometries not included in Simple Features
 * 3D geometries
 * GML application schemas
-* other CRS than geodetic WGS84 may be used as the default CRS
+* other CRS than geodetic WGS 84 may be used as the default CRS
 * return other CRS than the default CRS
 * support for resolve=local
 * Queries (dependency to FES)
@@ -23,6 +24,6 @@
 * Units of measure
 * ...
 
-## FES
+## Informative documents under development
 
-* to be discussed
+* Users Guide

README.md

@@ -1,12 +1,20 @@
-# Web Feature Service 3.0
+# OGC API - Features
 
-This GitHub repository contains the new revision of the [OGC](http://opengeospatial.org)'s
-Web Feature Service standard for querying geospatial information on the web. It is a complete
-rewrite of previous versions, focusing on a simple RESTful core specified
-as reusable [OpenAPI](http://openapis.org) components with responses
-in JSON and HTML.
+This GitHub repository contains [OGC](http://opengeospatial.org)'s
+standard for querying geospatial information on the web, "OGC API - Features".
 
-Alternate renderings of this standard are available for [HTML](http://docs.opengeospatial.org/DRAFTS/17-069.html) and [PDF](http://docs.opengeospatial.org/DRAFTS/17-069.pdf)
+OGC API standards define modular API building blocks to spatially enable Web APIs
+in a consistent way. [OpenAPI](http://openapis.org) is used to define the reusable
+API building blocks with responses in JSON and HTML.
+
+The OGC API family of standards is organized by resource type. OGC API Features
+specifies the fundamental API building blocks for interacting with features.
+The spatial data community uses the term 'feature' for things in the real world
+that are of interest.
+
+If you are unfamiliar with the term 'feature', the explanations on
+[Spatial Things, Features and Geometry](https://www.w3.org/TR/sdw-bp/#spatial-things-features-and-geometry)
+in the W3C/OGC Spatial Data on the Web Best Practice document provide more detail.
 
 ## Overview
 
@@ -16,47 +24,48 @@ A Web Feature Service is a standard API that represents collections of geospatia
 GET /collections
 ```
 
-Lists the collections of data on the server that can be queried ([7.11](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html#_feature_collections_metadata)),
+Lists the collections of data on the server that can be queried ([7.11](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html#_feature_collections)),
 and each describes basic information about the geospatial data collection, like its id and description, as well as the
 spatial and temporal extents of all the data contained
 
 ```
-GET /collections/{collectionId}/items?bbox=160.6,-55.95,-170,-25.89
+GET /collections/buildings/items?bbox=160.6,-55.95,-170,-25.89
 ```
 
-Requests all the data in the collection that is in the New Zealand economic zone.
+Requests all the data in the collection "buildings" that is in the New Zealand economic zone.
 The response format (typically HTML or a [GeoJSON](http://geojson.org/) feature
 collection, but GML is supported, too, and extensions can easily supply others) is determined using
 [HTTP content negotiation](https://restfulapi.net/content-negotiation/).
 
 Data is returned in pageable chunks, with each response containing a `next` link
 as many collections are quite large. The core specification supports a few basic filters, in
 addition to the `bbox` filter above, with extensions providing more advanced options.
-([7.13](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html#_feature_collections))
+([7.13](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html#_feature_collection))
 
 ```
 GET /collections/{collectionId}/items/{featureId}
 ```
 
-Returns a single geographic 'feature' - something in the real-world (a building,
+Returns a single 'feature' - something in the real-world (a building,
 a stream, a county, etc.) that typically is described by a geometry plus other properties.
 This provides a stable, canonical URL to link to the 'thing'.
 
 ## Using the standard
 
-A draft of WFS 3.0 is available:
+A stable draft is available. Note that the draft uses the title "Web Feature Service" or "WFS",
+version 3.0. This was the original title and newer editor's drafts already use the title
+"OGC API - Features".
 
-* [OGC Web Feature Service 3.0 - Part 1: Core, First Draft Release](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html)
+* [OGC API - Features - Part 1: Core, First Draft Release](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html)
 
 A [PDF version](https://portal.opengeospatial.org/files/?artifact_id=79027&version=1) is available, too.
 
 Those who want to just see the endpoints and responses can explore the generic
 OpenAPI definition on SwaggerHub:
 
-* [WFS 3.0.0-draft.1 openapi.yaml](https://app.swaggerhub.com/apis/cholmesgeo/WFS3/M1)
+* [OGC API Features 1.0.0-draft.1 openapi.yaml](https://app.swaggerhub.com/apis/cholmesgeo/WFS3/M1)
 
-There have been several implementations of the draft standard, though they are
-still getting up to compliance with the first draft release:
+Several implementations of the draft standard exist:
 
 * [Implementations of the draft specification / demo services](implementations.md)
 
@@ -71,18 +80,19 @@ so browse there to get a good idea of what is happening, as well as past decisio
 
 * [Checklist for implementers](guide/conformance_checklist.md)
 
-Also a non-normative document, the "WFS 3.0 Users Guide", is being developed.
+Also a non-normative document, the "Users Guide", is being developed.
 
 In addition to feedback from the initial implementations as well as discussions on GitHub and in the OGC/ISO working group,
 the current draft standard has been tested in a [WFS 3.0 Hackathon](http://www.opengeospatial.org/blog/2764), the [OGC Testbed-14](http://www.opengeospatial.org/projects/initiatives/testbed14), the [OGC Vector Tiles Pilot](https://www.opengeospatial.org/projects/initiatives/vt-pilot-2018) and other activities.
 
 Feedback for the Core is collected and discussed in the
-[GitHub issues for Part 1, Core](https://github.com/opengeospatial/WFS_FES/issues?q=is%3Aissue+is%3Aopen+label%3A%22Document%3A+Part+1+-+Core%22). The current expectation is to have a stable version of the Core specification around mid-2019. This version would
+[GitHub issues for Part 1, Core](https://github.com/opengeospatial/WFS_FES/issues?q=is%3Aissue+is%3Aopen+label%3A%22Document%3A+Part+1+-+Core%22). The current expectation is to have a stable version of the Core specification by August 2019. This version would
 then be the input for the next steps in the standardization process in OGC and ISO/TC 211.
 
 * [Background of this activity](background.md)
 * [The next version of WFS - an overview](overview.md)
-* [OGC Web Feature Service 3.0 - Part 1: Core, Editor's Draft](http://docs.opengeospatial.org/DRAFTS/17-069.html)
+* [OGC API - Features - Part 1: Core, Editor's Draft](http://docs.opengeospatial.org/DRAFTS/17-069.html), also available as
+[PDF](http://docs.opengeospatial.org/DRAFTS/17-069.pdf)
 
 ## Contributing
 

asciidoctor.json

@@ -1,8 +1,8 @@
 {
         "0":  {
                 "OGC_doc_number": "18-000",
-                "urn":"http://www.opengis.net/doc/DP/wfs/3.0",
-                "title":"OGC Web Feature Service 3.0 - Users Guide",
+                "urn":"http://www.opengis.net/doc/DP/ogcapi-features/1.0",
+                "title":"OGC API - Features - Users Guide",
                 "path":"guide/user_guide.adoc",
                 "options": ["--trace"],
                 "a":[
@@ -15,8 +15,8 @@
                 ]
         },
         "1":  { "OGC_doc_number": "18-058",
-                "urn":"http://www.opengis.net/doc/IS/wfs-2/3.0",
-                "title":"OGC Web Feature Service 3.0: Part 2 - Extension for Coordinate Reference Systems (by reference)",
+                "urn":"http://www.opengis.net/doc/IS/ogcapi-features-2/1.0",
+                "title":"OGC API - Features - Part 2: Extension for Coordinate Reference Systems (by reference)",
                 "path":"extensions/crs/18-058.adoc",
                 "options": ["--trace"],
                 "a":[
@@ -29,9 +29,9 @@
                 ]
         },
         "2":  {
-                "OGC_doc_number": "17-069",
-                "urn":"http://www.opengis.net/doc/IS/wfs-1/3.0",
-                "title":"OGC Web Feature Service 3.0: Part 1 - Core",
+                "OGC_doc_number": "17-069r1",
+                "urn":"http://www.opengis.net/doc/IS/ogcapi-features-1/1.0",
+                "title":"OGC API - Features - Part 1: Core",
                 "path":"core/standard/17-069.adoc",
                 "options": ["--trace"],
                 "a":[

background.md

@@ -4,16 +4,22 @@ Version 2.0 of the Web Feature Service (WFS, ISO 19142) and Filter Encoding (FES
 
 OGC has been processing change requests since 2012 to prepare a new minor revision version (version 2.x). The changes can be split into two categories: Additional capabilities in new conformance classes (units of measure, asynchronous responses, etc.) and adding a REST binding.
 
-To synchronize publication in OGC and ISO, the ongoing work is now a joint working group of OGC (via the WFS/FES SWG) and ISO/TC 211 (via PT 19142/43) which held its first meeting in May 2017 at the ISO/TC 211 meeting in Stockholm.
+To synchronize publication in OGC and ISO, the ongoing work became a joint working group of OGC (via the WFS/FES SWG) and ISO/TC 211 (via PT 19142/43) which held its first meeting in May 2017 at the ISO/TC 211 meeting in Stockholm.
 
 In parallel to the work on the revision, OGC and W3C have collaborated in a joint [W3C/OGC Spatial Data on the Web Working Group](https://www.w3.org/2015/spatial/). A key result of that work is the [Spatial Data on the Web Best Practice](https://www.w3.org/TR/sdw-bp/). The document builds on the general [W3C Data on the Web Best Practice](https://www.w3.org/TR/dwbp/) and adds practices and recommendations that are specific to spatial data. The abstract of the document is:
 
 >"This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices presented here are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting an approach based on general Web standards. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Web of data.”
 
 The Spatial Data on the Web Best Practice is an OGC Best Practice since July 2017. It will be maintained and updated as necessary by the new [Spatial Data on the Web Interest Group](https://www.w3.org/2017/sdwig/) that has started its work in October 2017.
 
-The OGC is discussing how to take the best practices and related developments like the release of the [OpenAPI 3.0 specification](https://www.openapis.org/blog/2017/07/26/the-oai-announces-the-openapi-specification-3-0-0) in July 2017 into account in the evolution of the OGC standards baseline. WFS is the first standard where this has resulted in concrete steps.
+The OGC is discussing how to take the best practices and related developments like the release of the [OpenAPI 3.0 specification](https://www.openapis.org/blog/2017/07/26/the-oai-announces-the-openapi-specification-3-0-0) in July 2017 into account in the evolution of the OGC standards baseline. WFS was the first standard where this has resulted in concrete steps.
 
 A [change proposal](http://ogc.standardstracker.org/show_request.cgi?id=488) to support the best practices was discussed and the joint OGC/ISO working group decided with unanimous consent to accept it as the basis for the development of the next version of WFS, which will be a major revision, i.e. WFS 3.0. The group also decided to open the GitHub repository that is used to develop the specification to the public.
 
-See [here](overview.md) for an overview of the differences between the previous versions of WFS and the planned WFS 3.0 specifications.
+With similar developments to modernize other OGC web service standards, the OGC decided to publish the new Web API standards as new standards under the brand "OGC API".
+
+OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.
+
+The OGC API family of standards is organized by resource type. What was formerly known as "WFS 3.0 Part 1: Core" is now "OGC API - Features - part 1:Core 1.0".
+
+See [here](overview.md) for an overview of the differences between "OGC API - Features - part 1:Core 1.0" and the WFS standard.

core/README.md

@@ -1,6 +1,6 @@
 # Standard template
 
-This folder contains the content for the WFS Part 1 (Core) standard.
+This folder contains the content for the OGC API - Features - Part 1: Core standard.
 
 The repo is organized as follows: