During the Frascati meeting in February 23th, 2023, the following motion was submitted and got no objection:
- Delete the current GeoAPI 1.0.0 milestone. That "release" was a milestone for a GO-1 draft, not a final GO-1 release (the GeoAPI version for the final GO-1 release was 2.0.0).
- Rename the current GeoAPI 0.1 as GeoAPI 1.0.0. What we retroactively called "GeoAPI 0.1" was the set of interfaces associated with OGC O1-009, which was a formal OGC release.
In other words, all GeoAPI releases were associated to a formal OGC standard, except GeoAPI 1.0.0. Furthermore GeoAPI 0.1 was the real beginning of interfaces in the org.opengis namespace. The proposed change would reflect better the GeoAPI history. Note that GeoAPI 0.1, 1.0.0 and 2.0.0 have not been approved directly by the Technical Committee (TC). But GeoAPI 0.1 and 2.0.0 were by-products of formal OGC standards.
This change impacts only old GeoAPI archives. It has not incidence on latest GeoAPI versions (2.0.0, 3.0.0, 3.0.1 and 3.0.2). The intent is to make GeoAPI historical root clearer.
During the Frascati meeting in February 23th, 2023, the following motion was submitted and got no objection:
In other words, all GeoAPI releases were associated to a formal OGC standard, except GeoAPI 1.0.0. Furthermore GeoAPI 0.1 was the real beginning of interfaces in the
org.opengisnamespace. The proposed change would reflect better the GeoAPI history. Note that GeoAPI 0.1, 1.0.0 and 2.0.0 have not been approved directly by the Technical Committee (TC). But GeoAPI 0.1 and 2.0.0 were by-products of formal OGC standards.This change impacts only old GeoAPI archives. It has not incidence on latest GeoAPI versions (2.0.0, 3.0.0, 3.0.1 and 3.0.2). The intent is to make GeoAPI historical root clearer.