-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lack of standardization for collection metadata response with application/xml media type #58
Comments
Yes, this is a weak area. Originally we had XML annotations in the OpenAPI fragments (link), but removed them because the way OpenAPI currently supports XML is kind of messy and likely to change (based on some discussions in the OpenAPI issues). I guess you are right and we should specify an explicit XML schema for the resource, when XML is used. |
I generated a schema for this at http://www.pvretano.com/schemas/wfs/3.0/wfs.xsd
Another option might be to look at how ATOMPUB defines collections and extend slightly for spatial. |
Discussion in web-meeting 2018-03-12: Include schema for XML in first draft release. |
Work in progress: http://pvretano.com/schemas/wfs/3.0/wfs.xsd |
Discussion on 2018-03-27: The schema should be available in a few days. |
As far as I can see in the spec, there's no XML schema defined for the collection metadata response with application/xml metadata type
For example,
$ curl -s -H "Accept: application/xml" "https://www.ldproxy.nrw.de/kataster" | xmllint --format -
returns
but it is not immediately obvious that this is howl https://github.com/opengeospatial/WFS_FES/blob/master/core/openapi/schemas/content.yaml should be encoded in XML
The text was updated successfully, but these errors were encountered: