Hi Ben and Rob,
Thanks for the feedback.
Regards,
On 02/27/2017 11:40 PM, Ben Caradoc-Davies wrote:
> Also note that gml:id is only mandatory in GML 3.2.1; it was optional
> in GML 3.1.1. gml:id has type xs:ID which forces uniqueness in a
> single document. WFS suggests (implies? urges?) that
Also note that gml:id is only mandatory in GML 3.2.1; it was optional in
GML 3.1.1. gml:id has type xs:ID which forces uniqueness in a single
document. WFS suggests (implies? urges?) that gml:id should be stable
and unique for a service, but there is nothing in GML to enforce this.
There is not
Gml:identifier was introduced for stable id. Gml:id is really meant for
reference with the response document but WFS blurred the line with its
getbyid.
So it comes down to implementation contracts between service and clients...
force ids to be stable, mirror in gml:identifier and allow wfs call on
