Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Review comments from C. Reed #30

Merged
merged 1 commit into from
Mar 6, 2024
Merged

Review comments from C. Reed #30

merged 1 commit into from
Mar 6, 2024

Conversation

m-mohr
Copy link
Member

@m-mohr m-mohr commented Feb 12, 2024

Updated the document according to the document that was attached to the comment, see #29

@m-mohr m-mohr changed the title Review comments from Carl Reed Review comments from C. Reed Feb 12, 2024
@m-mohr m-mohr linked an issue Feb 12, 2024 that may be closed by this pull request

OGC API - Processes and the openEO API complement each other and cater for different user audiences.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment:

I read the comment about possible overlaps. I would strongly encourage the development of a openEO/Processes API crosswalk similar to the STAC/Records API done for Testbed 19. Such a cross walk would be really helpful.

Response:
Available at Open-EO/openeo-api#494

@@ -65,22 +65,23 @@ openEO is backed by various tools and resources that facilitate its use. These i

== Relationship to other OGC Standards

The openEO API builds on top of other standards and specifications an reuses other standards whenever possible.
The openEO API builds on top of other standards and specifications and reuses other standards whenever possible.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment:

All or parts (requirements classes)?


The primary use case is to simplify and unify the data processing using a common API with a set of pre-defined processes. It is beneficial for users as they can still work in their favored programming language without worrying about data organization and pre-processing. They can avoid vendor lock-in as the generated process descriptions can be executed at multiple providers and as such also allows to compare and reproduce processing results more easily between different providers.
The primary use case for developing openEO was to simplify and unify the data processing using a common API specification with a set of pre-defined processes. As such, users can still work in their favored programming language without worrying about data organization and pre-processing. Users can avoid vendor lock-in as the generated process descriptions can be executed at multiple provider endpoints supporting comparing and reproducing processing results more easily between different providers.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment:

Simplify the data processing or accessing processing services in some processing chain??

@m-mohr
Copy link
Member Author

m-mohr commented Feb 12, 2024

A general comment the last chapter:

FYI. A couple of years ago, the OAB stated that any OGC Community Standard shall have two additional clauses specified in the intro content. I provided examples at the end of the WIP document.

Example provided:

ii. Source of this document
The majority of the content in this OGC document is a direct copy of the content contained at https://github.com/Esri/i3s-spec . No normative changes have been made to the content. This OGC document does contain content not in source Esri GitHub repository. Specifically, while derived from content on the Esri I3S repository, the Abstract, Keywords, Preface, Submitting Organizations, Endorsers, Terms and Definitions, and References sections and Annex B (Bibliography) in this document are not found on the Esri I3S repository. The Terms and Definitions and References sections may be added into the Esri community GitHub repository in the future.

iii. Validity of content
The Submission Team has reviewed and certified that the snapshot content in this Community Standard is true and accurate. The snapshot for OGC I3S Version 1.3 was taken on April 23, 2022 from the Esri version 1.7 Git Repository.

@m-mohr m-mohr marked this pull request as ready for review March 6, 2024 14:06
@m-mohr m-mohr merged commit 737cf33 into main Mar 6, 2024
@m-mohr m-mohr deleted the comment-carl-reed branch March 6, 2024 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OGC Community Standard: Comment 2 (Reed)
1 participant