search

opengeospatial / CoverageJSON

Public repo for CoverageJSON project
Apache License 2.0
10 stars 8 forks source link

Various editorial improvements: IPR, source and validity #112

Closed chris-little closed 2 years ago

chris-little commented 2 years ago

@cnreed has made, and will make, several useful improvements to the phrasing and grammar of the specification.

chris-little commented 2 years ago

@cnreed We will make a PR including your suggestions. Do you wish to be a reviewer of the changes?

cnreed commented 2 years ago

Hi @chris-little, thank you for trying to include me in your project, unfortunately, I think you have the wrong person. Best of luck with your project! 😃

chris-little commented 2 years ago

OGC's Carl N Reed suggested two additional clauses that the OAB determined needed to be added to the introductory clauses: Source of the document; and Validity of the document. Some of this in the Scope but they are supposed to be separate clauses.

ii. Source of this document The majority of the content in this OGC document is a direct copy of the content originally contained at https://github.com/covjson/specification . No normative changes have been made to the content. This OGC document does contain content not in the original source CovJSON GitHub repository. Specifically, while derived from content of the original CovJSON 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 CovJSON.

The future community web site and source repository will contain the OGC version.

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 CoverageJSON Version 1.0 was taken on December 2021 from the CovJSON Version 0.2 GitHub Repository.

Also, it is interesting that the standard OGC License agreement is used. Typically, this standard agreement is for full blown OGC standards and not community standards. This is because to use the OGC license, the submission team (and probably the community) need to agree to transfer all intellectual property (IPR) to the OGC, totally unencumbered.

This is why, for example, other Community Standards have various licensing and rights to use agreements. For example, again, check out I3S.

letmaik commented 2 years ago

https://covjson.org/spec/ is not appropriate anymore since it links to the OGC draft only. I suggest https://github.com/covjson/specification.

chris-little commented 2 years ago

@letmaik Thanks for this - @jonblower and I were discussing exactly that this afternoon, but were side-tracked by other meetings. I have continued editting the above comment and the two new clauses (ii and iii) should now be close to a final version.

There are IPR statements that refer to University of Reading, but the OGC paragraphs were probably brought in automatically from the template.

chris-little commented 2 years ago

@cnreediii, @ghobona I created PR #120 to incorpoate missing sections and preferred security statement.

chris-little commented 2 years ago

@cnreddiii, @ghobona PR #120 has been reviewed and merged, so now closing this issue.