Comments (5)
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.
from ogcapi-features.
I generated a schema for this at http://www.pvretano.com/schemas/wfs/3.0/wfs.xsd
Some caveats:
- I created this file by copying the 2.5 schema and migrating it to 3.0. Most of it is not applicable but I figure over time I can prune the file to get rid of the stuff we no longer use.
- I really did not like the use of the wfs:extent and wfs:box elements so I used the ows:WGS84BoundingBox element instead. If the goal is to break any dependency with OWS Common then I think we should pull the WGS84BoundingBox element into the WFS 3.0 namespace thus breaking the dependency.
Another option might be to look at how ATOMPUB defines collections and extend slightly for spatial.
from ogcapi-features.
Discussion in web-meeting 2018-03-12: Include schema for XML in first draft release.
from ogcapi-features.
Work in progress: http://pvretano.com/schemas/wfs/3.0/wfs.xsd
from ogcapi-features.
Discussion on 2018-03-27: The schema should be available in a few days.
from ogcapi-features.
Related Issues (20)
- Schemas: `x-ogc-unit-lang` or `x-ogc-unitLang` ? HOT 3
- Schemas: Clarifications / Example on what URIs / vocabs should be used for `x-ogc-definition` HOT 4
- Simplify scalar expression
- CQL2/Grammar: Quoted identifiers not defined as expected HOT 6
- CQL2/Grammar: signedNumericLiteral does not seem to be defined correctly HOT 2
- A dedicated section for links HOT 2
- Part 4: Create: returning the created feature in the body of the response ? HOT 2
- Broken urls on Cubewerx page
- Extended property selection with CQL2 expressions (like SQL SELECT) HOT 2
- Part 5: relating the Schema requirement class to Part 1 describedBy HOT 4
- Query parameter properties: align with OGC API Coverages
- Collection extent: End inclusive or exclusive HOT 3
- Part 5: Feature references with more complex values
- Part 9: Simple text search to search multiple collections HOT 4
- Part 4: Discussions about submitting a list of Features?
- Part 4: application/json as media type?
- Part 5: x-ogc-propertySeq seems useless? HOT 1
- Part 5: Add table of x-ogc- properties HOT 1
- Part 5: The limitations of JSON data types HOT 5
- Part 4: Editorial link inconsistencies HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ogcapi-features.