Deviations between XML and JSON encoding of various structures. · Issue #133 · opengeospatial/ogcapi-features (original) (raw)

At the moment, the XML encoding and JSON encoding of various structures deviates slightly making it difficult to use certain generation tools such as Jackson. For example, the XML encodings use atom:links to encode links while the JSON encoding uses a similar "link" structure define the WFS 3.0 specification (because there are no OWS common encodings defined in JSON). Similarly, the XML encoding uses the OWS Common encoding for bbox while the JSON encoding uses the bbox structure defined in WFS 3.0.
The main reason for doing this was to allow people who have already invested code building WFS 2.X to reuse some of that code for supporting WFS 3.0.
However, this raises a question! For the XML encoding, should we try to reuse existing, familiar encodings (e.g. from OWS common) OR should we try to mirror the JSON encodings?
Also, we would like to hear from people using other languages (e.g. Python or Go) and who are implementing both XML and JSON support .