- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 May 2019 10:47:29 +0000
- To: public-dxwg-wg@w3.org
andrea-perego has just created a new issue for https://github.com/w3c/dxwg: == CONNEG: Reference to WFS3 == I don't remember if any reference has been made to WFS3 in relation to profile negotiation: https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html Notably, in [Section 10 (Media Types)](https://rawcdn.githack.com/opengeospatial/WFS_FES/3.0.0-draft.1/docs/17-069.html#mediatypes), WFS3 makes use of a `profile` param in the HTTP headers / quoting: > JSON media types that would typically be used in a WFS that supports JSON are > - `application/geo+json` for feature collections and features, and > - `application/json` for all other resources. > > XML media types that would typically occur in a WFS that supports XML are > - `application/gml+xml;version=3.2` for any GML 3.2 feature collections and features, > - `application/gml+xml;version=3.2;profile=http://www.opengis.net/def/profile/ogc/2.0/gml-sf0` for GML 3.2 feature collections and features conforming to the GML Simple Feature Level 0 profile, > - `application/gml+xml;version=3.2;profile=http://www.opengis.net/def/profile/ogc/2.0/gml-sf2` for GML 3.2 feature collections and features conforming to the GML Simple Feature Level 2 profile, and > - `application/xml` for all other resources. > > The typical HTML media type for all "web pages" in a WFS would be `text/html`. > > The media type for an OpenAPI definition in JSON is `application/openapi+json;version=3.0`. /cc @cportele Please view or discuss this issue at https://github.com/w3c/dxwg/issues/942 using your GitHub account
Received on Thursday, 23 May 2019 10:47:30 UTC