From 28bdad8359079027024ce3556cf44e681cb28b07 Mon Sep 17 00:00:00 2001 From: Arnout Engelen Date: Fri, 23 Dec 2022 12:18:44 +0100 Subject: [PATCH] Update some links to https --- content/_index.md | 6 +- content/coding-conventions.md | 2 +- .../annexes/geoapi/ConceptualModels.html | 8 +- .../annexes/geoapi/DefinitionProcess.html | 6 +- .../annexes/geoapi/GeoAPI.html | 24 +++--- .../annexes/geoapi/ReduceDependency.html | 2 +- .../coverage/SampleDimension.html | 2 +- .../developer-guide/introduction/index.html | 4 +- content/downloads.md | 10 +-- content/epsg.md | 2 +- .../annexes/geoapi/DefinitionProcess.html | 6 +- .../annexes/geoapi/ReduceDependency.html | 2 +- .../fr/developer-guide/coverage/index.html | 2 +- .../introduction/ConceptualModels.html | 8 +- .../developer-guide/introduction/GeoAPI.html | 26 +++--- content/mail-lists.md | 2 +- content/release-management-setup.md | 10 +-- content/release-management.md | 4 +- content/release-notes/0.3.md | 84 +++++++++---------- content/source.md | 10 +-- content/standards.md | 10 +-- content/team-list.md | 2 +- layouts/_default/baseof.fr.html | 4 +- layouts/_default/baseof.html | 4 +- layouts/partials/menu.fr.html | 2 +- layouts/partials/menu.html | 10 +-- static/openoffice/en/index.html | 4 +- static/openoffice/fr/index.html | 4 +- static/openoffice/update.xml | 4 +- static/tables/CoordinateOperationMethods.html | 2 +- 30 files changed, 133 insertions(+), 133 deletions(-) diff --git a/content/_index.md b/content/_index.md index 61fff0dc..9c8ba41f 100644 --- a/content/_index.md +++ b/content/_index.md @@ -73,13 +73,13 @@ However a [command-line tool](command-line.html) and a [JavaFX application](java are also provided for allowing users to experiment some SIS functionalities before writing code. -[geoapi]: http://www.geoapi.org/ +[geoapi]: https://www.geoapi.org/ [GML]: https://www.ogc.org/standards/gml [SF_SQL]: https://www.ogc.org/standards/sfs [filter]: https://www.ogc.org/standards/filter [geoTIFF]: https://www.ogc.org/standards/geotiff [netCDF]: https://www.ogc.org/standards/netcdf -[netCDF_MF]: http://docs.opengeospatial.org/bp/16-114r3/16-114r3.html -[MF_CSV]: http://docs.opengeospatial.org/is/14-084r2/14-084r2.html +[netCDF_MF]: https://docs.opengeospatial.org/bp/16-114r3/16-114r3.html +[MF_CSV]: https://docs.opengeospatial.org/is/14-084r2/14-084r2.html [JSR_363]: https://jcp.org/en/jsr/detail?id=363 [seshat]: https://unitsofmeasurement.github.io/seshat/ diff --git a/content/coding-conventions.md b/content/coding-conventions.md index fc430118..09594ddb 100644 --- a/content/coding-conventions.md +++ b/content/coding-conventions.md @@ -195,7 +195,7 @@ Internet Explorer users need to [install a plugin][mathml-plugin-ie]. Firefox users can optionally install the [fonts for Mozilla's MathML engine][mathml-fonts] for better results. Note that a [JavaScript display engine][mathml-mathjax] is available for all browsers, but not yet used by SIS. -[srcheaders]: http://www.apache.org/legal/src-headers.html +[srcheaders]: https://www.apache.org/legal/src-headers.html [JLS-order]: https://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.1.1 [mathml-W3C]: https://www.w3.org/Math/ [mathml-wolfram]: https://reference.wolfram.com/language/XML/tutorial/MathML.html diff --git a/content/developer-guide/annexes/geoapi/ConceptualModels.html b/content/developer-guide/annexes/geoapi/ConceptualModels.html index 9e9a20f8..b1bb674f 100644 --- a/content/developer-guide/annexes/geoapi/ConceptualModels.html +++ b/content/developer-guide/annexes/geoapi/ConceptualModels.html @@ -38,7 +38,7 @@

Sources of conceptual models used by Apache SIS

Most standards used by Apache SIS have been devised by the Open Geospatial Consortium (OGC), sometimes in collaboration with the International Organization for Standardization (ISO). - Some ISO standards themselves become European standards via the INSPIRE Directive. + Some ISO standards themselves become European standards via the INSPIRE Directive. These standards offer two key features:

Deviations from the standards are documented in each affected class and method. - Each mention of a deviation is also collected on a single page in order to provide an overview. + Each mention of a deviation is also collected on a single page in order to provide an overview. Since these deviations blur the relationships between the standards and certain Java interfaces, the correspondence between these languages is explained by @UML annotations and property files described in the following section.

diff --git a/content/developer-guide/annexes/geoapi/GeoAPI.html b/content/developer-guide/annexes/geoapi/GeoAPI.html index 395a9e4a..24289850 100644 --- a/content/developer-guide/annexes/geoapi/GeoAPI.html +++ b/content/developer-guide/annexes/geoapi/GeoAPI.html @@ -36,7 +36,7 @@

From conceptual models to Java interfaces: GeoAPI

- The GeoAPI project offers a set of Java interfaces for geospatial applications. + The GeoAPI project offers a set of Java interfaces for geospatial applications. In a series of org.opengis.* packages, GeoAPI defines structures representing metadata, coordinate reference systems and operations that perform cartographic projections. In a part that is not yet standardized — called pending — GeoAPI defines structures that represent geo-referenced images, @@ -51,9 +51,9 @@

From conceptual models to Java interfaces: GeoAPI

(due to the many publications related to OGC standards), as well as increased interoperability. Interoperability is facilitated by a better separation between applications that call GeoAPI functions, and libraries that implement GeoAPI. - The separation is similar to that offered by the JDBC (Java Database Connectivity) interfaces of standard Java. + The separation is similar to that offered by the JDBC (Java Database Connectivity) interfaces of standard Java. Using the interfaces’ API, developers can ignore the underlying implementation. - For example, they can perform cartographic projections with the help of the Proj.4 library, or the Apache SIS library, + For example, they can perform cartographic projections with the help of the Proj.4 library, or the Apache SIS library, without having to change their programs when they change libraries.

  • @@ -81,33 +81,33 @@

    GeoAPI project history

    At this time, the wave of web services had not yet eclipsed classical programming interfaces. The interfaces of the OGC did anticipate a networked world, but invested rather — in the case of Java — in RMI (Remote Method Invocation) technology. - As the GeoAPI project did not yet exist, we retroactively designate these historical interfaces “GeoAPI 0.1”. + As the GeoAPI project did not yet exist, we retroactively designate these historical interfaces “GeoAPI 0.1”. These interfaces already used the package name org.opengis, which would be adopted by GeoAPI.

    In 2002, developers of free projects launched a - call for the creation of a geospatial API. + call for the creation of a geospatial API. The initial proposal attracted the interest of at least five free projects. - The project was created using SourceForge, - which has since hosted the source code in a Subversion repository. + The project was created using SourceForge, + which has since hosted the source code in a Subversion repository. It was then that the project assumed the name “GeoAPI”, and used the interfaces of the OGC specification 01-009 as a starting point.

    A few months later, the OGC launched the GO-1: Geographic Objects project, which pursued goals similar to those of GeoAPI. In the meantime, the OGC abandonned some of their specifications in favor of ISO standards. GeoAPI and GO-1 worked jointly to rework the GeoAPI interfaces and base them on the new ISO norms. - Their first interation, GeoAPI 1.0, + Their first interation, GeoAPI 1.0, served as a starting point for the first draft of the OGC specification 03-064 by the GO-1 working group. The final version of this specification became an OGC standard in 2005, - and GeoAPI 2.0 was published at that time. + and GeoAPI 2.0 was published at that time.

    The GO-1 project was largely supported by a company called Polexis. Its acquisition by Sys Technology, and the change in priorities under the new owners, brought a halt to the GO-1 project, which in turn slowed development on GeoAPI. In order to resume development, a new working group entitled “GeoAPI 3.0” was created at the OGC. This group took a narrower focus compared to GeoAPI 2.0, concentrating on the most stable interfaces, and putting the others - — such as geometries — in a module entitled “pending”, for future consideration. - GeoAPI 3.0 became an OGC standard in 2011. - This version was the first to be deployed in the Maven central repository. + — such as geometries — in a module entitled “pending”, for future consideration. + GeoAPI 3.0 became an OGC standard in 2011. + This version was the first to be deployed in the Maven central repository.

    diff --git a/content/developer-guide/annexes/geoapi/ReduceDependency.html b/content/developer-guide/annexes/geoapi/ReduceDependency.html index 650f59d1..5560e53b 100644 --- a/content/developer-guide/annexes/geoapi/ReduceDependency.html +++ b/content/developer-guide/annexes/geoapi/ReduceDependency.html @@ -184,7 +184,7 @@
    Defining custom implementations

    The geoapi-examples module provides examples of simple implementations. Many of these classes implement more than one interface at a time in order to provide a simpler conceptual model. - The javadoc for this module + The javadoc for this module lists key packages and classes along with the combinations performed. This module illustrates not only how GeoAPI might be implemented, but also how the implementation might be tested using geoapi-conformance. diff --git a/content/developer-guide/coverage/SampleDimension.html b/content/developer-guide/coverage/SampleDimension.html index 9cc55283..a669c5d1 100644 --- a/content/developer-guide/coverage/SampleDimension.html +++ b/content/developer-guide/coverage/SampleDimension.html @@ -40,7 +40,7 @@

    Sample dimensions

    In Apache SIS, the distinction between ranges of numerical values and range of any types of values is represented by Number­Range and Range classes respectively. The Number­Range is used more often, and is also the one that most closely approaches the - the common mathematical concept of an interval. + the common mathematical concept of an interval. This textual representation approaches the specifications of ISO 31-11 standard, except that the comma is replaced by the character “…” as the separator of minimal and maximal values. For example, “[0 … 256)” represents the range of values from 0 inclusive to 256 exclusive. diff --git a/content/developer-guide/introduction/index.html b/content/developer-guide/introduction/index.html index 4e9473e7..a5be4fa3 100644 --- a/content/developer-guide/introduction/index.html +++ b/content/developer-guide/introduction/index.html @@ -44,13 +44,13 @@

    Introduction

    the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). The annex provides more context about international standards.

    - The library is an implementation of OGC GeoAPI interfaces. + The library is an implementation of OGC GeoAPI interfaces. In a series of org.opengis.* packages, GeoAPI offers a set of implementation-neutral Java interfaces for geospatial applications. These interfaces closely follow the specifications of the OGC, while interpreting and adapting them to meet the needs of Java developers — for example, conforming with Java naming conventions. The conceptual model of GeoAPI will be explained in detail in the chapters describing Apache SIS implementation. However, we can get an overview of its content by consulting the page listing the mapping between - GeoAPI methods and the standards where they come from. + GeoAPI methods and the standards where they come from. The annex provides more details about GeoAPI history and how to use it.

    While Apache SIS is primarily a library for helping developers to create their own applications, diff --git a/content/downloads.md b/content/downloads.md index 15356a5a..e7ab437b 100644 --- a/content/downloads.md +++ b/content/downloads.md @@ -126,12 +126,12 @@ For better flexibility and performance, it is also possible to use an uncompress and writable Derby database, or to install the EPSG dataset on HSQL or PostgreSQL. See [How to use EPSG geodetic dataset](epsg.html) page for more information. -[maven]: http://maven.apache.org/ +[maven]: https://maven.apache.org/ [keys]: https://www.apache.org/dist/sis/KEYS -[license]: http://www.apache.org/licenses/LICENSE-2.0 -[src]: http://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-src.zip -[doc]: http://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-doc.zip -[bin]: http://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-bin.zip +[license]: https://www.apache.org/licenses/LICENSE-2.0 +[src]: https://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-src.zip +[doc]: https://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-doc.zip +[bin]: https://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-bin.zip [src-PGP]: https://www.apache.org/dist/sis/{{% version %}}/apache-sis-{{% version %}}-src.zip.asc [doc-PGP]: https://www.apache.org/dist/sis/{{% version %}}/apache-sis-{{% version %}}-doc.zip.asc [bin-PGP]: https://www.apache.org/dist/sis/{{% version %}}/apache-sis-{{% version %}}-bin.zip.asc diff --git a/content/epsg.md b/content/epsg.md index 316c643a..dd4099c7 100644 --- a/content/epsg.md +++ b/content/epsg.md @@ -257,4 +257,4 @@ fetching the data source from the `context.xml` file. [IOGP]: https://www.iogp.org/ [EPSG]: https://epsg.org/ [EPSG-ToU]: https://epsg.org/terms-of-use.html -[Derby]: http://db.apache.org/derby/derby_downloads.html +[Derby]: https://db.apache.org/derby/derby_downloads.html diff --git a/content/fr/developer-guide/annexes/geoapi/DefinitionProcess.html b/content/fr/developer-guide/annexes/geoapi/DefinitionProcess.html index 18b13f0e..8260825e 100644 --- a/content/fr/developer-guide/annexes/geoapi/DefinitionProcess.html +++ b/content/fr/developer-guide/annexes/geoapi/DefinitionProcess.html @@ -40,9 +40,9 @@

    Des spécifications de l’OGC a tels que les fichiers XSD. Mais il y a toujours une révision manuelle, et très souvent des modifications par rapport aux fichiers générés par des processus automatiques. Il aurait été possible de générer automatiquement des interfaces Java à partir des standards de l’OGC à l’aide d’outils existants. - Par exemple une des approches les plus utilisées est de transformer les schémas XSD + Par exemple une des approches les plus utilisées est de transformer les schémas XSD en interfaces Java à l’aide de l’utilitaire en ligne de commande xjc. - Cet utilitaire étant fournit avec la plupart des distributions du Java (il fait partie des outils de JAXB), + Cet utilitaire étant fournit avec la plupart des distributions du Java (il fait partie des outils de JAXB), cette approche est choisie par plusieurs projets que l’on trouve sur internet. D’autres approches utilisent des outils intégrés à l’environnement de développement Eclipse, ou prennent comme point de départ les schémas UML plutôt que XSD. @@ -141,7 +141,7 @@

    Des spécifications de l’OGC a

    Les écarts par rapport aux normes sont documentés dans chaque classe et chaque méthode concernées. - Chaque mention d’un écart est aussi recopiée dans une page unique, + Chaque mention d’un écart est aussi recopiée dans une page unique, pour donner une vue d’ensemble. Étant donné que ces écarts brouillent les liens qui existent entre les standards et certaines interfaces Java, la correspondance entre ces langages est explicitée par des annotations @UML diff --git a/content/fr/developer-guide/annexes/geoapi/ReduceDependency.html b/content/fr/developer-guide/annexes/geoapi/ReduceDependency.html index c50c8475..85104714 100644 --- a/content/fr/developer-guide/annexes/geoapi/ReduceDependency.html +++ b/content/fr/developer-guide/annexes/geoapi/ReduceDependency.html @@ -187,7 +187,7 @@

    Fournir sa propre implémentation

    Le module geoapi-examples fournit des exemples d’implémentations simples. Plusieurs de ces classes implémentent plus d’une interface à la fois afin de proposer un modèle conceptuel plus simple. - La Javadoc de ce module + La Javadoc de ce module énumère les paquets et classes clés avec les combinaisons effectuées. Ce module illustre non-seulement comment GeoAPI peut-être implémenté, mais aussi comment l’implémentation peut être testée en utilisant geoapi-conformance. diff --git a/content/fr/developer-guide/coverage/index.html b/content/fr/developer-guide/coverage/index.html index 31ee6851..146369c6 100644 --- a/content/fr/developer-guide/coverage/index.html +++ b/content/fr/developer-guide/coverage/index.html @@ -92,7 +92,7 @@

    La classe Range de SIS et sa relation avec les standards

    La distinction entre les plages de tout type de valeurs et les plages de valeurs numériques est représentée dans SIS par les classes Range et NumberRange respectivement. La classe NumberRange est la plus utilisée, et elle est aussi celle qui se rapproche le plus de la - notion mathématique usuelle d’un intervalle. + notion mathématique usuelle d’un intervalle. Se représentation textuelle se rapproche des spécifications du standard ISO 31-11, excepté que la virgule est remplacée par le caractère “…” comme séparateur des valeurs minimales et maximales. Par exemple “[0 … 256)” représente la plage des valeurs 0 inclusivement à 256 exclusivement. diff --git a/content/fr/developer-guide/introduction/ConceptualModels.html b/content/fr/developer-guide/introduction/ConceptualModels.html index ccba068d..b2940da2 100644 --- a/content/fr/developer-guide/introduction/ConceptualModels.html +++ b/content/fr/developer-guide/introduction/ConceptualModels.html @@ -40,7 +40,7 @@

    Sources des modèles conceptuels de Apache SIS

    par le consortium Open Geospatial (OGC), parfois en collaboration avec l’organisation internationale de normalisation (ISO). Certains standards de l’ISO deviennent eux-mêmes des standards Européens via la - directive INSPIRE, ou des standards français via l’AFNOR. + directive INSPIRE, ou des standards français via l’AFNOR. Ces standards offrent deux technologies clés: