Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Release v1.0.1 of Part 1 and Part 2 #651

Open
cportele opened this issue Nov 8, 2021 · 7 comments
Open

Release v1.0.1 of Part 1 and Part 2 #651

cportele opened this issue Nov 8, 2021 · 7 comments
Assignees
Labels
Part 1: Core Issue related to Part 1 - Core Part 2: CRS

Comments

@cportele
Copy link
Member

cportele commented Nov 8, 2021

Meeting 2021-11-08:

  • It is two years (part 1) or one year (part 2) since the publication of v1.0.0 and both of the standards have seen some changes to clarify or improve the wording in the standards (links to the editor drafts for part 1 and part 2).
  • The SWG decided to review the backlog of open issues for both standards (with respect to issues that result in a corrigendum) and address those issues, where possible, before moving through the corrigendum process. If anyone has an issue that is not yet on GitHub, but wants it to be considered for v1.0.1, please create an issue as soon as possible.
@cportele cportele added Part 1: Core Issue related to Part 1 - Core Part 2: CRS labels Nov 8, 2021
@cportele
Copy link
Member Author

cportele commented Jan 31, 2022

Meeting 2022-01-31:

Motion: The Features API SWG resolves to submit the editor drafts of Part 1 and Part 2 for release as v1.0.1 (corrigendum release) by the Technical Committee.

Discussion:

Moved: Panagiotis (Peter) Vretanos

Second: Amy Youmans

Discussion:

  • For now keep the release notes (the list of changes/issues) in the document history and ask Scott how to handle this in the publication.
  • It should also be considered, if and how the ISO version of the two standards are updated.

NOTUC

@ogcscotts
Copy link
Contributor

While we do have a template for release notes (https://github.com/opengeospatial/templates/tree/master/response_to_comments_template), corrigenda changes are all minor, so the document history is fine.

@maaattes
Copy link

Hi,
idk if this is the right place to mention this but I've noticed some issues related to the release of v1.0.1 of Part 1 & 2:

@cportele
Copy link
Member Author

Thanks @maaattes - I did not notice that the new version had been posted.

External identifier URLs (https://www.opengis.net/doc/IS/ogcapi-features-1/1.0.1 and https://www.opengis.net/doc/IS/ogcapi-features-2/1.0.1) don't resolve

They shouldn't, the identifiers are wrong and should still be .../1.0 unless something changed with the versioning approach in OGC, but I don't think that this is the case. @ogcscotts @gbuehler @ghobona can you have a look? The 1.0 URI should now redirect to the 1.0.1 versions.

Also, the 1.0 spec URIs should now redirect to the 1.0.1 documents. I probably need to do some updates to the specification-elements CSV files. @ghobona - I will let you know, when they are updated.

At https://docs.opengeospatial.org/is/18-058r1/18-058r1.html the publication date is 2202-05-11

@gbuehler - can you fix that, too?

At https://github.com/opengeospatial/ogcapi-features#using-the-standard maybe there should be link to 1.0.1? Because it says “latest approved version”

Absolutely, I wasn't aware that documents have been published. I will update the repo. The revision number of the editor drafts will also change.

@maaattes
Copy link

They shouldn't, the identifiers are wrong and should still be .../1.0 unless something changed with the versioning approach in OGC, but I don't think that this is the case. @ogcscotts @gbuehler @ghobona can you have a look? The 1.0 URI should now redirect to the 1.0.1 versions.

Also, the 1.0 spec URIs should now redirect to the 1.0.1 documents. I probably need to do some updates to the specification-elements CSV files. @ghobona - I will let you know, when they are updated.

Ah, okay. Do you know if those external identifiers only work with approved standards?
Because some do work
http://www.opengis.net/doc/IS/ogcapi-edr-1/1.0

but some don't
http://www.opengis.net/doc/is/ogcapi-common-1/1.0
http://www.opengis.net/doc/is/ogcapi-records-1/1.0
https://www.opengis.net/doc/is/ogcapi-coverages-1/1.0
https://www.opengis.net/doc/IS/ogcapi-styles/1.0

@cportele
Copy link
Member Author

@maaattes - all those that don't resolve are not published standards yet, so there is no version 1.0 yet.

@cportele
Copy link
Member Author

@ghobona - https://ogcapi.ogc.org/features/ also needs an update (is there a way to automate the release process?)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Part 1: Core Issue related to Part 1 - Core Part 2: CRS
Development

No branches or pull requests

5 participants