From 5b69084d127e58e9dc29fe1ace7cca1426f92ba8 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:13:06 +0000 Subject: [PATCH 01/18] add compile workflow --- .github/workflows/compile_doc.yml | 23 +++++++++++++++++++ .../.github}/workflows/docker.yml | 0 .../.github}/workflows/generate.yml | 0 3 files changed, 23 insertions(+) create mode 100644 .github/workflows/compile_doc.yml rename {.github => docs/.github}/workflows/docker.yml (100%) rename {.github => docs/.github}/workflows/generate.yml (100%) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml new file mode 100644 index 0000000..9a72ad9 --- /dev/null +++ b/.github/workflows/compile_doc.yml @@ -0,0 +1,23 @@ +name: compile_doc +on: + push: + branches: + - 'main' +jobs: + build: + runs-on: ubuntu-latest + container: metanorma/metanorma:latest + steps: + - name: Checkout repo + uses: actions/checkout@v3 + with: + path: main + - name: Generate document + run: | + cd main + metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc + git config --global user.name 'example' + git config --global user.email 'example@example.com' + git add document.html + git commit -am "Compilation of HTML documents" + git push \ No newline at end of file diff --git a/.github/workflows/docker.yml b/docs/.github/workflows/docker.yml similarity index 100% rename from .github/workflows/docker.yml rename to docs/.github/workflows/docker.yml diff --git a/.github/workflows/generate.yml b/docs/.github/workflows/generate.yml similarity index 100% rename from .github/workflows/generate.yml rename to docs/.github/workflows/generate.yml From 62736e8091b3ddbf98018977ad9aeea41c24e61b Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:16:09 +0000 Subject: [PATCH 02/18] rename standard folder & update workflow --- .github/workflows/compile_doc.yml | 6 +++--- {docs => standard}/.github/workflows/docker.yml | 0 {docs => standard}/.github/workflows/generate.yml | 0 {docs => standard}/.gitignore | 0 {docs => standard}/.gitlab-ci.yml | 0 {docs => standard}/Gemfile | 0 {docs => standard}/Makefile | 0 {docs => standard}/Makefile.win | 0 {docs => standard}/README.adoc | 0 {docs => standard}/UML/README.adoc | 0 {docs => standard}/abstract_tests/ATS_class_example1.adoc | 0 {docs => standard}/abstract_tests/ATS_test_example1.adoc | 0 {docs => standard}/abstract_tests/ATS_test_example2.adoc | 0 {docs => standard}/abstract_tests/README.adoc | 0 {docs => standard}/code/README.adoc | 0 {docs => standard}/document.adoc | 0 {docs => standard}/figures/README.adoc | 0 {docs => standard}/images/README.adoc | 0 {docs => standard}/metanorma.yml | 0 {docs => standard}/relaton/cache/iso/iso_19101_1_2014.xml | 0 {docs => standard}/relaton/cache/iso/iso_19115_1_2014.xml | 0 {docs => standard}/relaton/cache/iso/iso_19115_3.xml | 0 .../relaton/cache/iso/iso_19139_2007.notfound | 0 {docs => standard}/relaton/cache/iso/iso_19157_2013.xml | 0 {docs => standard}/relaton/cache/iso/version | 0 {docs => standard}/relaton/cache/ogc/06_121r9.xml | 0 {docs => standard}/relaton/cache/ogc/12_019.xml | 0 {docs => standard}/relaton/cache/ogc/14_005r3.xml | 0 {docs => standard}/relaton/cache/ogc/ogc_06_121r9.redirect | 0 {docs => standard}/relaton/cache/ogc/ogc_12_019.redirect | 0 {docs => standard}/relaton/cache/ogc/ogc_14_005r3.redirect | 0 {docs => standard}/relaton/cache/ogc/ogc_15_097.notfound | 0 {docs => standard}/relaton/cache/ogc/version | 0 {docs => standard}/requirements/README.adoc | 0 {docs => standard}/requirements/requirement001.adoc | 0 {docs => standard}/requirements/requirement002.adoc | 0 {docs => standard}/requirements/requirements_class.adoc | 0 {docs => standard}/sections/annex-a.adoc | 0 {docs => standard}/sections/annex-bibliography.adoc | 0 {docs => standard}/sections/annex-history.adoc | 0 {docs => standard}/sections/annex-n.adoc | 0 {docs => standard}/sections/clause_0_front_material.adoc | 0 {docs => standard}/sections/clause_1_scope.adoc | 0 {docs => standard}/sections/clause_2_conformance.adoc | 0 {docs => standard}/sections/clause_3_references.adoc | 0 .../sections/clause_4_terms_and_definitions.adoc | 0 {docs => standard}/sections/clause_5_conventions.adoc | 0 {docs => standard}/sections/clause_6_informative_text.adoc | 0 {docs => standard}/sections/clause_7_normative_text.adoc | 0 {docs => standard}/sections/clause_8_media_types.adoc | 0 50 files changed, 3 insertions(+), 3 deletions(-) rename {docs => standard}/.github/workflows/docker.yml (100%) rename {docs => standard}/.github/workflows/generate.yml (100%) rename {docs => standard}/.gitignore (100%) rename {docs => standard}/.gitlab-ci.yml (100%) rename {docs => standard}/Gemfile (100%) rename {docs => standard}/Makefile (100%) rename {docs => standard}/Makefile.win (100%) rename {docs => standard}/README.adoc (100%) rename {docs => standard}/UML/README.adoc (100%) rename {docs => standard}/abstract_tests/ATS_class_example1.adoc (100%) rename {docs => standard}/abstract_tests/ATS_test_example1.adoc (100%) rename {docs => standard}/abstract_tests/ATS_test_example2.adoc (100%) rename {docs => standard}/abstract_tests/README.adoc (100%) rename {docs => standard}/code/README.adoc (100%) rename {docs => standard}/document.adoc (100%) rename {docs => standard}/figures/README.adoc (100%) rename {docs => standard}/images/README.adoc (100%) rename {docs => standard}/metanorma.yml (100%) rename {docs => standard}/relaton/cache/iso/iso_19101_1_2014.xml (100%) rename {docs => standard}/relaton/cache/iso/iso_19115_1_2014.xml (100%) rename {docs => standard}/relaton/cache/iso/iso_19115_3.xml (100%) rename {docs => standard}/relaton/cache/iso/iso_19139_2007.notfound (100%) rename {docs => standard}/relaton/cache/iso/iso_19157_2013.xml (100%) rename {docs => standard}/relaton/cache/iso/version (100%) rename {docs => standard}/relaton/cache/ogc/06_121r9.xml (100%) rename {docs => standard}/relaton/cache/ogc/12_019.xml (100%) rename {docs => standard}/relaton/cache/ogc/14_005r3.xml (100%) rename {docs => standard}/relaton/cache/ogc/ogc_06_121r9.redirect (100%) rename {docs => standard}/relaton/cache/ogc/ogc_12_019.redirect (100%) rename {docs => standard}/relaton/cache/ogc/ogc_14_005r3.redirect (100%) rename {docs => standard}/relaton/cache/ogc/ogc_15_097.notfound (100%) rename {docs => standard}/relaton/cache/ogc/version (100%) rename {docs => standard}/requirements/README.adoc (100%) rename {docs => standard}/requirements/requirement001.adoc (100%) rename {docs => standard}/requirements/requirement002.adoc (100%) rename {docs => standard}/requirements/requirements_class.adoc (100%) rename {docs => standard}/sections/annex-a.adoc (100%) rename {docs => standard}/sections/annex-bibliography.adoc (100%) rename {docs => standard}/sections/annex-history.adoc (100%) rename {docs => standard}/sections/annex-n.adoc (100%) rename {docs => standard}/sections/clause_0_front_material.adoc (100%) rename {docs => standard}/sections/clause_1_scope.adoc (100%) rename {docs => standard}/sections/clause_2_conformance.adoc (100%) rename {docs => standard}/sections/clause_3_references.adoc (100%) rename {docs => standard}/sections/clause_4_terms_and_definitions.adoc (100%) rename {docs => standard}/sections/clause_5_conventions.adoc (100%) rename {docs => standard}/sections/clause_6_informative_text.adoc (100%) rename {docs => standard}/sections/clause_7_normative_text.adoc (100%) rename {docs => standard}/sections/clause_8_media_types.adoc (100%) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index 9a72ad9..a191789 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -2,7 +2,7 @@ name: compile_doc on: push: branches: - - 'main' + - 'master' jobs: build: runs-on: ubuntu-latest @@ -11,10 +11,10 @@ jobs: - name: Checkout repo uses: actions/checkout@v3 with: - path: main + path: master - name: Generate document run: | - cd main + cd master/standard metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc git config --global user.name 'example' git config --global user.email 'example@example.com' diff --git a/docs/.github/workflows/docker.yml b/standard/.github/workflows/docker.yml similarity index 100% rename from docs/.github/workflows/docker.yml rename to standard/.github/workflows/docker.yml diff --git a/docs/.github/workflows/generate.yml b/standard/.github/workflows/generate.yml similarity index 100% rename from docs/.github/workflows/generate.yml rename to standard/.github/workflows/generate.yml diff --git a/docs/.gitignore b/standard/.gitignore similarity index 100% rename from docs/.gitignore rename to standard/.gitignore diff --git a/docs/.gitlab-ci.yml b/standard/.gitlab-ci.yml similarity index 100% rename from docs/.gitlab-ci.yml rename to standard/.gitlab-ci.yml diff --git a/docs/Gemfile b/standard/Gemfile similarity index 100% rename from docs/Gemfile rename to standard/Gemfile diff --git a/docs/Makefile b/standard/Makefile similarity index 100% rename from docs/Makefile rename to standard/Makefile diff --git a/docs/Makefile.win b/standard/Makefile.win similarity index 100% rename from docs/Makefile.win rename to standard/Makefile.win diff --git a/docs/README.adoc b/standard/README.adoc similarity index 100% rename from docs/README.adoc rename to standard/README.adoc diff --git a/docs/UML/README.adoc b/standard/UML/README.adoc similarity index 100% rename from docs/UML/README.adoc rename to standard/UML/README.adoc diff --git a/docs/abstract_tests/ATS_class_example1.adoc b/standard/abstract_tests/ATS_class_example1.adoc similarity index 100% rename from docs/abstract_tests/ATS_class_example1.adoc rename to standard/abstract_tests/ATS_class_example1.adoc diff --git a/docs/abstract_tests/ATS_test_example1.adoc b/standard/abstract_tests/ATS_test_example1.adoc similarity index 100% rename from docs/abstract_tests/ATS_test_example1.adoc rename to standard/abstract_tests/ATS_test_example1.adoc diff --git a/docs/abstract_tests/ATS_test_example2.adoc b/standard/abstract_tests/ATS_test_example2.adoc similarity index 100% rename from docs/abstract_tests/ATS_test_example2.adoc rename to standard/abstract_tests/ATS_test_example2.adoc diff --git a/docs/abstract_tests/README.adoc b/standard/abstract_tests/README.adoc similarity index 100% rename from docs/abstract_tests/README.adoc rename to standard/abstract_tests/README.adoc diff --git a/docs/code/README.adoc b/standard/code/README.adoc similarity index 100% rename from docs/code/README.adoc rename to standard/code/README.adoc diff --git a/docs/document.adoc b/standard/document.adoc similarity index 100% rename from docs/document.adoc rename to standard/document.adoc diff --git a/docs/figures/README.adoc b/standard/figures/README.adoc similarity index 100% rename from docs/figures/README.adoc rename to standard/figures/README.adoc diff --git a/docs/images/README.adoc b/standard/images/README.adoc similarity index 100% rename from docs/images/README.adoc rename to standard/images/README.adoc diff --git a/docs/metanorma.yml b/standard/metanorma.yml similarity index 100% rename from docs/metanorma.yml rename to standard/metanorma.yml diff --git a/docs/relaton/cache/iso/iso_19101_1_2014.xml b/standard/relaton/cache/iso/iso_19101_1_2014.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19101_1_2014.xml rename to standard/relaton/cache/iso/iso_19101_1_2014.xml diff --git a/docs/relaton/cache/iso/iso_19115_1_2014.xml b/standard/relaton/cache/iso/iso_19115_1_2014.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19115_1_2014.xml rename to standard/relaton/cache/iso/iso_19115_1_2014.xml diff --git a/docs/relaton/cache/iso/iso_19115_3.xml b/standard/relaton/cache/iso/iso_19115_3.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19115_3.xml rename to standard/relaton/cache/iso/iso_19115_3.xml diff --git a/docs/relaton/cache/iso/iso_19139_2007.notfound b/standard/relaton/cache/iso/iso_19139_2007.notfound similarity index 100% rename from docs/relaton/cache/iso/iso_19139_2007.notfound rename to standard/relaton/cache/iso/iso_19139_2007.notfound diff --git a/docs/relaton/cache/iso/iso_19157_2013.xml b/standard/relaton/cache/iso/iso_19157_2013.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19157_2013.xml rename to standard/relaton/cache/iso/iso_19157_2013.xml diff --git a/docs/relaton/cache/iso/version b/standard/relaton/cache/iso/version similarity index 100% rename from docs/relaton/cache/iso/version rename to standard/relaton/cache/iso/version diff --git a/docs/relaton/cache/ogc/06_121r9.xml b/standard/relaton/cache/ogc/06_121r9.xml similarity index 100% rename from docs/relaton/cache/ogc/06_121r9.xml rename to standard/relaton/cache/ogc/06_121r9.xml diff --git a/docs/relaton/cache/ogc/12_019.xml b/standard/relaton/cache/ogc/12_019.xml similarity index 100% rename from docs/relaton/cache/ogc/12_019.xml rename to standard/relaton/cache/ogc/12_019.xml diff --git a/docs/relaton/cache/ogc/14_005r3.xml b/standard/relaton/cache/ogc/14_005r3.xml similarity index 100% rename from docs/relaton/cache/ogc/14_005r3.xml rename to standard/relaton/cache/ogc/14_005r3.xml diff --git a/docs/relaton/cache/ogc/ogc_06_121r9.redirect b/standard/relaton/cache/ogc/ogc_06_121r9.redirect similarity index 100% rename from docs/relaton/cache/ogc/ogc_06_121r9.redirect rename to standard/relaton/cache/ogc/ogc_06_121r9.redirect diff --git a/docs/relaton/cache/ogc/ogc_12_019.redirect b/standard/relaton/cache/ogc/ogc_12_019.redirect similarity index 100% rename from docs/relaton/cache/ogc/ogc_12_019.redirect rename to standard/relaton/cache/ogc/ogc_12_019.redirect diff --git a/docs/relaton/cache/ogc/ogc_14_005r3.redirect b/standard/relaton/cache/ogc/ogc_14_005r3.redirect similarity index 100% rename from docs/relaton/cache/ogc/ogc_14_005r3.redirect rename to standard/relaton/cache/ogc/ogc_14_005r3.redirect diff --git a/docs/relaton/cache/ogc/ogc_15_097.notfound b/standard/relaton/cache/ogc/ogc_15_097.notfound similarity index 100% rename from docs/relaton/cache/ogc/ogc_15_097.notfound rename to standard/relaton/cache/ogc/ogc_15_097.notfound diff --git a/docs/relaton/cache/ogc/version b/standard/relaton/cache/ogc/version similarity index 100% rename from docs/relaton/cache/ogc/version rename to standard/relaton/cache/ogc/version diff --git a/docs/requirements/README.adoc b/standard/requirements/README.adoc similarity index 100% rename from docs/requirements/README.adoc rename to standard/requirements/README.adoc diff --git a/docs/requirements/requirement001.adoc b/standard/requirements/requirement001.adoc similarity index 100% rename from docs/requirements/requirement001.adoc rename to standard/requirements/requirement001.adoc diff --git a/docs/requirements/requirement002.adoc b/standard/requirements/requirement002.adoc similarity index 100% rename from docs/requirements/requirement002.adoc rename to standard/requirements/requirement002.adoc diff --git a/docs/requirements/requirements_class.adoc b/standard/requirements/requirements_class.adoc similarity index 100% rename from docs/requirements/requirements_class.adoc rename to standard/requirements/requirements_class.adoc diff --git a/docs/sections/annex-a.adoc b/standard/sections/annex-a.adoc similarity index 100% rename from docs/sections/annex-a.adoc rename to standard/sections/annex-a.adoc diff --git a/docs/sections/annex-bibliography.adoc b/standard/sections/annex-bibliography.adoc similarity index 100% rename from docs/sections/annex-bibliography.adoc rename to standard/sections/annex-bibliography.adoc diff --git a/docs/sections/annex-history.adoc b/standard/sections/annex-history.adoc similarity index 100% rename from docs/sections/annex-history.adoc rename to standard/sections/annex-history.adoc diff --git a/docs/sections/annex-n.adoc b/standard/sections/annex-n.adoc similarity index 100% rename from docs/sections/annex-n.adoc rename to standard/sections/annex-n.adoc diff --git a/docs/sections/clause_0_front_material.adoc b/standard/sections/clause_0_front_material.adoc similarity index 100% rename from docs/sections/clause_0_front_material.adoc rename to standard/sections/clause_0_front_material.adoc diff --git a/docs/sections/clause_1_scope.adoc b/standard/sections/clause_1_scope.adoc similarity index 100% rename from docs/sections/clause_1_scope.adoc rename to standard/sections/clause_1_scope.adoc diff --git a/docs/sections/clause_2_conformance.adoc b/standard/sections/clause_2_conformance.adoc similarity index 100% rename from docs/sections/clause_2_conformance.adoc rename to standard/sections/clause_2_conformance.adoc diff --git a/docs/sections/clause_3_references.adoc b/standard/sections/clause_3_references.adoc similarity index 100% rename from docs/sections/clause_3_references.adoc rename to standard/sections/clause_3_references.adoc diff --git a/docs/sections/clause_4_terms_and_definitions.adoc b/standard/sections/clause_4_terms_and_definitions.adoc similarity index 100% rename from docs/sections/clause_4_terms_and_definitions.adoc rename to standard/sections/clause_4_terms_and_definitions.adoc diff --git a/docs/sections/clause_5_conventions.adoc b/standard/sections/clause_5_conventions.adoc similarity index 100% rename from docs/sections/clause_5_conventions.adoc rename to standard/sections/clause_5_conventions.adoc diff --git a/docs/sections/clause_6_informative_text.adoc b/standard/sections/clause_6_informative_text.adoc similarity index 100% rename from docs/sections/clause_6_informative_text.adoc rename to standard/sections/clause_6_informative_text.adoc diff --git a/docs/sections/clause_7_normative_text.adoc b/standard/sections/clause_7_normative_text.adoc similarity index 100% rename from docs/sections/clause_7_normative_text.adoc rename to standard/sections/clause_7_normative_text.adoc diff --git a/docs/sections/clause_8_media_types.adoc b/standard/sections/clause_8_media_types.adoc similarity index 100% rename from docs/sections/clause_8_media_types.adoc rename to standard/sections/clause_8_media_types.adoc From 2832580023f540a4d6e573b1740c6d1e61aab788 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:21:49 +0000 Subject: [PATCH 03/18] update title --- standard/document.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/standard/document.adoc b/standard/document.adoc index 6d3e876..766865b 100644 --- a/standard/document.adoc +++ b/standard/document.adoc @@ -1,16 +1,16 @@ -= OGC (add title text) += OGC Geoscience Markup Language :doctype: standard :encoding: utf-8 :lang: en :status: draft :committee: technical -:draft: 3.0 +:draft: 4.1.1 :external-id: http://www.opengis.net/doc/{doc-type}/{standard}/{m.n} :docnumber: YY-999 :received-date: 2029-03-30 :issued-date: 2029-03-30 :published-date: 2029-03-30 -:fullname: Editor One +:fullname: Edward Lewis :fullname_2: Editor Two :docsubtype: Interface :keywords: ogcdoc, OGC document, API, openapi, html From 1ae111aada15dacfb80a38b6b4a925288a4f49b1 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:23:43 +0000 Subject: [PATCH 04/18] Update compile_doc.yml --- .github/workflows/compile_doc.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index a191789..1d1ddcf 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -2,7 +2,7 @@ name: compile_doc on: push: branches: - - 'master' + - 'main' jobs: build: runs-on: ubuntu-latest @@ -11,13 +11,13 @@ jobs: - name: Checkout repo uses: actions/checkout@v3 with: - path: master + path: main - name: Generate document run: | - cd master/standard + cd main/standard metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc git config --global user.name 'example' git config --global user.email 'example@example.com' git add document.html git commit -am "Compilation of HTML documents" - git push \ No newline at end of file + git push From 72c500a4f813e37685b864aee1d949641870e599 Mon Sep 17 00:00:00 2001 From: example Date: Thu, 16 Mar 2023 15:25:02 +0000 Subject: [PATCH 05/18] Compilation of HTML documents --- standard/document.html | 1806 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1806 insertions(+) create mode 100644 standard/document.html diff --git a/standard/document.html b/standard/document.html new file mode 100644 index 0000000..8cbc106 --- /dev/null +++ b/standard/document.html @@ -0,0 +1,1806 @@ + + +OGC Geoscience Markup Language + + + + + + + + + + + + + + + + +Text here>'/>
+

Draft

+
+ +
+

OGC Standard

+
+ + + +
•
+ +
+ + +
+
+ +
+ +
+ OGC Geoscience Markup Language + +
+
+ + + + + +
+ + + + + + + Edward Lewis Editor + + Editor Two Editor + + +
+ +
+ Submission Date: 2029-03-30 + Approval Date: 2029-03-30 + Publication Date: 2029-03-30 + External identifier of this OGC® document: http://www.opengis.net/doc/{doc-type}/{standard}/{m.n} + Internal identifier of this OGC® document: YY-999 + + +
+ +
+ + Version: 1.0
+ + + Additional Formats: + + XML + + + PDF + + + DOC + +
+ +
+ +
+ +
+ +
+
+ OGC Standard +
+ +
+

Draft

+
+
+ +
+
+ + +

Notice for Drafts

+ +

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

+ +

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

+
+ + + + + +
+
+ + + +
+ + + + + + +
Document number:YY-999
Document type:OGC Standard
Document subtype:Implementation
Document stage:Draft
Document language:English
+
+ +
+
+
+

Copyright notice

+ + +

Copyright + © 2023 Open Geospatial Consortium
+ To obtain additional rights of use, visit + https://www.ogc.org/legal +

+
+

Note

+ +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+
+
+
+ +
+
+
+

+
+

License Agreement

+ + +

Use of this document is subject to the license agreement at + https://www.ogc.org/license

+
+
+ + +
+ +
+

Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/

+
+ +
+ + +
+ + + + +
+

+ + + + + + + + + +

I.  Abstract

<Insert Abstract Text here>

II.  Keywords

The following are keywords to be used by search engines and + document catalogues.

ogcdoc, OGC document, API, openapi, html


III.  Preface

NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

IV.  Security considerations

No security considerations have been made for this Standard.

V.  Submitting Organizations

The following organizations submitted this Document to the + Open Geospatial Consortium (OGC):

  • Organization One
    • +
  • Organization Two

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

OGC Geoscience Markup Language

1.  Scope

NOTE  Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

2.  Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

  • AAAA

    +
    • +

  • BBBB

    +
    • +

Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site.

In order to conform to this OGC® interface standard, a software implementation shall choose to implement:

  • Any one of the conformance levels specified in Annex A (normative).

    +
    • +

  • Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative).

    +
    • +

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

3.  Normative references

+

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

+ + + + +

Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)

+

ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)

+

The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).

+

Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)

+

The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)

+

National Center for Biotechnology Information, http://www.ncbi.nlm.nih.gov

+

ISO: ISO 19101-1:2014, Geographic information — Reference model — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/59164.html.

+

ISO: ISO 19115-1:2014, Geographic information — Metadata — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/53798.html.

+

ISO: ISO 19157:2013, Geographic information  — Data quality. International Organization for Standardization, Geneva (2013). https://www.iso.org/standard/32575.html.

+

ISO: ISO 19139:2007, Geographic information — Metadata — XML schema implementation. ISO (2007).

+

ISO: ISO 19115-3, Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts. International Organization for Standardization, Geneva https://www.iso.org/standard/80874.html.

+

OGC Geospatial User Feedback Standard: Conceptual Model (2016)

+

Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele: OGC 12-019, OGC City Geography Markup Language (CityGML) Encoding Standard. Open Geospatial Consortium (2012). https://portal.ogc.org/files/?artifact id=47842.

+

Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker: OGC 14-005r3, OGC® IndoorGML. Open Geospatial Consortium (2014). https://docs.ogc.org/is/14-005r3/14-005r3.html.

+

Arliss Whiteside Jim Greenwood: OGC 06-121r9, OGC Web Service Common Implementation Specification. Open Geospatial Consortium (2010). https://portal.ogc.org/files/?artifact id=38867.

+

4.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1. example term

+

term used for exemplary purposes

+ + + + + + +

Note 1 to entry: An example note.

Example

Here’s an example of an example term.

+

[SOURCE: ISO 19101-1:2014]

5.  Keywords

6.  Submitting organizations

7.  Contributors

Additional contributors to this Standard include the following:

Individual name(s), Organization

8.  Conventions

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

8.1.  Identifiers

+ +

The normative provisions in this standard are denoted by the URI

+ +

http://www.opengis.net/spec/{standard}/{m.n}

+ +

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

+

9.  Clauses not containing normative material

Paragraph

9.1.  Clauses not containing normative material sub-clause 1

+ +

Paragraph

+

9.2.  Clauses not containing normative material sub-clause 2

+ +

10.  Clause containing normative material

Paragraph

10.1.  Requirement Class A or Requirement A Example

+ +

Paragraph – intro text for the requirement class.

+ +

Use the following table for Requirements Classes.

+ +

Requirements class 1

Obligationrequirement
Description

Requirements Class

Normative statementsRequirement 1-1
Requirement 1-2
+ +

10.1.1.  Requirement 1

+ +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 1

Obligationrequirement
Statement

Requirement ‘shall’ statement

+ +

Dictionary tables for requirements can be added as necessary. Modify the following example as needed.

+ +

Table 1

NamesDefinitionData types and valuesMultiplicity and use
name 1definition of name 1floatOne or more (mandatory)
name 2definition of name 2character string type, not emptyZero or one (optional)
name 3definition of name 3GML:: Point PropertyTypeOne (mandatory)
+
+ +

10.1.2.  Requirement 2

+ +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 2

Label/req/req-class-a/req-name-2
Conditions

  1. The process input value is specified in-line in an execute request.

    +
    2. +

  2. The process input is defined as an object according to its schema.

    +
    3. +
+
A

The server SHALL support process input values encoded as qualified values.

+
B

The value of the value key SHALL be an object instance.

+
+
+

11.  Media Types for any data encoding(s)

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in http://www.iana.org/assignments/media-types/index.html then this section may be used to define a new MIME type for registration with IANA.


Annex A
(informative)
Conformance Class Abstract Test Suite (Normative)

NOTE  Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

A.1.  Conformance Class A

+ +

Example

label

http://www.opengis.net/spec/name-of-standard/1.0/conf/example1

+

subject

Requirements Class “example1”

+

classification

Target Type:Web API

+
+
+ +

A.1.1.  Example 1

+ +

Abstract test A.1

Subject/req/req-class-a/req-name-1
Label/conf/core/api-definition-op
Test purpose

Validate that the API Definition document can be retrieved from the expected location.

+
Test method
    +

  1. Construct a path for the API Definition document that ends with /api.

    +
    2. +

  2. Issue a HTTP GET request on that path

    +
    3. +

  3. Validate the contents of the returned document using test /conf/core/api-definition-success.

    +
    4. +
+ +
+
+ +

A.1.2.  Example 2

+ +

Abstract test A.2

Subject/req/req-class-a/req-name-2
Label/conf/core/http
Test purpose

Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

+
Test method
    +

  1. All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

    +
    2. +

  2. For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol.

    +
    3. +
+
+
+

Annex B
(informative)
Title

NOTE  Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography


Annex C
(informative)
Revision History

Table C.1

DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version

Bibliography

+ +

NOTE  The TC has approved Springer LNCS as the official document citation type.

Springer LNCS is widely used in technical and computer science journals and other publications

– Actual References:

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

[n] Web: Author Surname, A.: Title, http://Website-Url

[1]  OGC: OGC Testbed 12 Annex B: Architecture (2015).

+ + +
+ + + + + + + + + + + + + + + + + + + From 34bf1a1a960d10f87790e0e37f0430d1f2985511 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:37:10 +0000 Subject: [PATCH 06/18] move to docs update workflows --- .github/workflows/compile_doc.yml | 4 ++-- {standard => docs}/.gitignore | 0 {standard => docs}/.gitlab-ci.yml | 0 {standard => docs}/Gemfile | 0 {standard => docs}/Makefile | 0 {standard => docs}/Makefile.win | 0 {standard => docs}/README.adoc | 0 {standard => docs}/UML/README.adoc | 0 {standard => docs}/abstract_tests/ATS_class_example1.adoc | 0 {standard => docs}/abstract_tests/ATS_test_example1.adoc | 0 {standard => docs}/abstract_tests/ATS_test_example2.adoc | 0 {standard => docs}/abstract_tests/README.adoc | 0 {standard => docs}/code/README.adoc | 0 {standard => docs}/document.adoc | 0 {standard => docs}/document.html | 0 {standard => docs}/figures/README.adoc | 0 {standard => docs}/images/README.adoc | 0 {standard => docs}/metanorma.yml | 0 {standard => docs}/relaton/cache/iso/iso_19101_1_2014.xml | 0 {standard => docs}/relaton/cache/iso/iso_19115_1_2014.xml | 0 {standard => docs}/relaton/cache/iso/iso_19115_3.xml | 0 {standard => docs}/relaton/cache/iso/iso_19139_2007.notfound | 0 {standard => docs}/relaton/cache/iso/iso_19157_2013.xml | 0 {standard => docs}/relaton/cache/iso/version | 0 {standard => docs}/relaton/cache/ogc/06_121r9.xml | 0 {standard => docs}/relaton/cache/ogc/12_019.xml | 0 {standard => docs}/relaton/cache/ogc/14_005r3.xml | 0 {standard => docs}/relaton/cache/ogc/ogc_06_121r9.redirect | 0 {standard => docs}/relaton/cache/ogc/ogc_12_019.redirect | 0 {standard => docs}/relaton/cache/ogc/ogc_14_005r3.redirect | 0 {standard => docs}/relaton/cache/ogc/ogc_15_097.notfound | 0 {standard => docs}/relaton/cache/ogc/version | 0 {standard => docs}/requirements/README.adoc | 0 {standard => docs}/requirements/requirement001.adoc | 0 {standard => docs}/requirements/requirement002.adoc | 0 {standard => docs}/requirements/requirements_class.adoc | 0 {standard => docs}/sections/annex-a.adoc | 0 {standard => docs}/sections/annex-bibliography.adoc | 0 {standard => docs}/sections/annex-history.adoc | 0 {standard => docs}/sections/annex-n.adoc | 0 {standard => docs}/sections/clause_0_front_material.adoc | 0 {standard => docs}/sections/clause_1_scope.adoc | 0 {standard => docs}/sections/clause_2_conformance.adoc | 0 {standard => docs}/sections/clause_3_references.adoc | 0 .../sections/clause_4_terms_and_definitions.adoc | 0 {standard => docs}/sections/clause_5_conventions.adoc | 0 {standard => docs}/sections/clause_6_informative_text.adoc | 0 {standard => docs}/sections/clause_7_normative_text.adoc | 0 {standard => docs}/sections/clause_8_media_types.adoc | 0 {standard/.github => docs}/workflows/docker.yml | 0 {standard/.github => docs}/workflows/generate.yml | 0 51 files changed, 2 insertions(+), 2 deletions(-) rename {standard => docs}/.gitignore (100%) rename {standard => docs}/.gitlab-ci.yml (100%) rename {standard => docs}/Gemfile (100%) rename {standard => docs}/Makefile (100%) rename {standard => docs}/Makefile.win (100%) rename {standard => docs}/README.adoc (100%) rename {standard => docs}/UML/README.adoc (100%) rename {standard => docs}/abstract_tests/ATS_class_example1.adoc (100%) rename {standard => docs}/abstract_tests/ATS_test_example1.adoc (100%) rename {standard => docs}/abstract_tests/ATS_test_example2.adoc (100%) rename {standard => docs}/abstract_tests/README.adoc (100%) rename {standard => docs}/code/README.adoc (100%) rename {standard => docs}/document.adoc (100%) rename {standard => docs}/document.html (100%) rename {standard => docs}/figures/README.adoc (100%) rename {standard => docs}/images/README.adoc (100%) rename {standard => docs}/metanorma.yml (100%) rename {standard => docs}/relaton/cache/iso/iso_19101_1_2014.xml (100%) rename {standard => docs}/relaton/cache/iso/iso_19115_1_2014.xml (100%) rename {standard => docs}/relaton/cache/iso/iso_19115_3.xml (100%) rename {standard => docs}/relaton/cache/iso/iso_19139_2007.notfound (100%) rename {standard => docs}/relaton/cache/iso/iso_19157_2013.xml (100%) rename {standard => docs}/relaton/cache/iso/version (100%) rename {standard => docs}/relaton/cache/ogc/06_121r9.xml (100%) rename {standard => docs}/relaton/cache/ogc/12_019.xml (100%) rename {standard => docs}/relaton/cache/ogc/14_005r3.xml (100%) rename {standard => docs}/relaton/cache/ogc/ogc_06_121r9.redirect (100%) rename {standard => docs}/relaton/cache/ogc/ogc_12_019.redirect (100%) rename {standard => docs}/relaton/cache/ogc/ogc_14_005r3.redirect (100%) rename {standard => docs}/relaton/cache/ogc/ogc_15_097.notfound (100%) rename {standard => docs}/relaton/cache/ogc/version (100%) rename {standard => docs}/requirements/README.adoc (100%) rename {standard => docs}/requirements/requirement001.adoc (100%) rename {standard => docs}/requirements/requirement002.adoc (100%) rename {standard => docs}/requirements/requirements_class.adoc (100%) rename {standard => docs}/sections/annex-a.adoc (100%) rename {standard => docs}/sections/annex-bibliography.adoc (100%) rename {standard => docs}/sections/annex-history.adoc (100%) rename {standard => docs}/sections/annex-n.adoc (100%) rename {standard => docs}/sections/clause_0_front_material.adoc (100%) rename {standard => docs}/sections/clause_1_scope.adoc (100%) rename {standard => docs}/sections/clause_2_conformance.adoc (100%) rename {standard => docs}/sections/clause_3_references.adoc (100%) rename {standard => docs}/sections/clause_4_terms_and_definitions.adoc (100%) rename {standard => docs}/sections/clause_5_conventions.adoc (100%) rename {standard => docs}/sections/clause_6_informative_text.adoc (100%) rename {standard => docs}/sections/clause_7_normative_text.adoc (100%) rename {standard => docs}/sections/clause_8_media_types.adoc (100%) rename {standard/.github => docs}/workflows/docker.yml (100%) rename {standard/.github => docs}/workflows/generate.yml (100%) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index 1d1ddcf..ba527d9 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -14,10 +14,10 @@ jobs: path: main - name: Generate document run: | - cd main/standard + cd main/docs metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc git config --global user.name 'example' git config --global user.email 'example@example.com' - git add document.html + git add index.html git commit -am "Compilation of HTML documents" git push diff --git a/standard/.gitignore b/docs/.gitignore similarity index 100% rename from standard/.gitignore rename to docs/.gitignore diff --git a/standard/.gitlab-ci.yml b/docs/.gitlab-ci.yml similarity index 100% rename from standard/.gitlab-ci.yml rename to docs/.gitlab-ci.yml diff --git a/standard/Gemfile b/docs/Gemfile similarity index 100% rename from standard/Gemfile rename to docs/Gemfile diff --git a/standard/Makefile b/docs/Makefile similarity index 100% rename from standard/Makefile rename to docs/Makefile diff --git a/standard/Makefile.win b/docs/Makefile.win similarity index 100% rename from standard/Makefile.win rename to docs/Makefile.win diff --git a/standard/README.adoc b/docs/README.adoc similarity index 100% rename from standard/README.adoc rename to docs/README.adoc diff --git a/standard/UML/README.adoc b/docs/UML/README.adoc similarity index 100% rename from standard/UML/README.adoc rename to docs/UML/README.adoc diff --git a/standard/abstract_tests/ATS_class_example1.adoc b/docs/abstract_tests/ATS_class_example1.adoc similarity index 100% rename from standard/abstract_tests/ATS_class_example1.adoc rename to docs/abstract_tests/ATS_class_example1.adoc diff --git a/standard/abstract_tests/ATS_test_example1.adoc b/docs/abstract_tests/ATS_test_example1.adoc similarity index 100% rename from standard/abstract_tests/ATS_test_example1.adoc rename to docs/abstract_tests/ATS_test_example1.adoc diff --git a/standard/abstract_tests/ATS_test_example2.adoc b/docs/abstract_tests/ATS_test_example2.adoc similarity index 100% rename from standard/abstract_tests/ATS_test_example2.adoc rename to docs/abstract_tests/ATS_test_example2.adoc diff --git a/standard/abstract_tests/README.adoc b/docs/abstract_tests/README.adoc similarity index 100% rename from standard/abstract_tests/README.adoc rename to docs/abstract_tests/README.adoc diff --git a/standard/code/README.adoc b/docs/code/README.adoc similarity index 100% rename from standard/code/README.adoc rename to docs/code/README.adoc diff --git a/standard/document.adoc b/docs/document.adoc similarity index 100% rename from standard/document.adoc rename to docs/document.adoc diff --git a/standard/document.html b/docs/document.html similarity index 100% rename from standard/document.html rename to docs/document.html diff --git a/standard/figures/README.adoc b/docs/figures/README.adoc similarity index 100% rename from standard/figures/README.adoc rename to docs/figures/README.adoc diff --git a/standard/images/README.adoc b/docs/images/README.adoc similarity index 100% rename from standard/images/README.adoc rename to docs/images/README.adoc diff --git a/standard/metanorma.yml b/docs/metanorma.yml similarity index 100% rename from standard/metanorma.yml rename to docs/metanorma.yml diff --git a/standard/relaton/cache/iso/iso_19101_1_2014.xml b/docs/relaton/cache/iso/iso_19101_1_2014.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19101_1_2014.xml rename to docs/relaton/cache/iso/iso_19101_1_2014.xml diff --git a/standard/relaton/cache/iso/iso_19115_1_2014.xml b/docs/relaton/cache/iso/iso_19115_1_2014.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19115_1_2014.xml rename to docs/relaton/cache/iso/iso_19115_1_2014.xml diff --git a/standard/relaton/cache/iso/iso_19115_3.xml b/docs/relaton/cache/iso/iso_19115_3.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19115_3.xml rename to docs/relaton/cache/iso/iso_19115_3.xml diff --git a/standard/relaton/cache/iso/iso_19139_2007.notfound b/docs/relaton/cache/iso/iso_19139_2007.notfound similarity index 100% rename from standard/relaton/cache/iso/iso_19139_2007.notfound rename to docs/relaton/cache/iso/iso_19139_2007.notfound diff --git a/standard/relaton/cache/iso/iso_19157_2013.xml b/docs/relaton/cache/iso/iso_19157_2013.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19157_2013.xml rename to docs/relaton/cache/iso/iso_19157_2013.xml diff --git a/standard/relaton/cache/iso/version b/docs/relaton/cache/iso/version similarity index 100% rename from standard/relaton/cache/iso/version rename to docs/relaton/cache/iso/version diff --git a/standard/relaton/cache/ogc/06_121r9.xml b/docs/relaton/cache/ogc/06_121r9.xml similarity index 100% rename from standard/relaton/cache/ogc/06_121r9.xml rename to docs/relaton/cache/ogc/06_121r9.xml diff --git a/standard/relaton/cache/ogc/12_019.xml b/docs/relaton/cache/ogc/12_019.xml similarity index 100% rename from standard/relaton/cache/ogc/12_019.xml rename to docs/relaton/cache/ogc/12_019.xml diff --git a/standard/relaton/cache/ogc/14_005r3.xml b/docs/relaton/cache/ogc/14_005r3.xml similarity index 100% rename from standard/relaton/cache/ogc/14_005r3.xml rename to docs/relaton/cache/ogc/14_005r3.xml diff --git a/standard/relaton/cache/ogc/ogc_06_121r9.redirect b/docs/relaton/cache/ogc/ogc_06_121r9.redirect similarity index 100% rename from standard/relaton/cache/ogc/ogc_06_121r9.redirect rename to docs/relaton/cache/ogc/ogc_06_121r9.redirect diff --git a/standard/relaton/cache/ogc/ogc_12_019.redirect b/docs/relaton/cache/ogc/ogc_12_019.redirect similarity index 100% rename from standard/relaton/cache/ogc/ogc_12_019.redirect rename to docs/relaton/cache/ogc/ogc_12_019.redirect diff --git a/standard/relaton/cache/ogc/ogc_14_005r3.redirect b/docs/relaton/cache/ogc/ogc_14_005r3.redirect similarity index 100% rename from standard/relaton/cache/ogc/ogc_14_005r3.redirect rename to docs/relaton/cache/ogc/ogc_14_005r3.redirect diff --git a/standard/relaton/cache/ogc/ogc_15_097.notfound b/docs/relaton/cache/ogc/ogc_15_097.notfound similarity index 100% rename from standard/relaton/cache/ogc/ogc_15_097.notfound rename to docs/relaton/cache/ogc/ogc_15_097.notfound diff --git a/standard/relaton/cache/ogc/version b/docs/relaton/cache/ogc/version similarity index 100% rename from standard/relaton/cache/ogc/version rename to docs/relaton/cache/ogc/version diff --git a/standard/requirements/README.adoc b/docs/requirements/README.adoc similarity index 100% rename from standard/requirements/README.adoc rename to docs/requirements/README.adoc diff --git a/standard/requirements/requirement001.adoc b/docs/requirements/requirement001.adoc similarity index 100% rename from standard/requirements/requirement001.adoc rename to docs/requirements/requirement001.adoc diff --git a/standard/requirements/requirement002.adoc b/docs/requirements/requirement002.adoc similarity index 100% rename from standard/requirements/requirement002.adoc rename to docs/requirements/requirement002.adoc diff --git a/standard/requirements/requirements_class.adoc b/docs/requirements/requirements_class.adoc similarity index 100% rename from standard/requirements/requirements_class.adoc rename to docs/requirements/requirements_class.adoc diff --git a/standard/sections/annex-a.adoc b/docs/sections/annex-a.adoc similarity index 100% rename from standard/sections/annex-a.adoc rename to docs/sections/annex-a.adoc diff --git a/standard/sections/annex-bibliography.adoc b/docs/sections/annex-bibliography.adoc similarity index 100% rename from standard/sections/annex-bibliography.adoc rename to docs/sections/annex-bibliography.adoc diff --git a/standard/sections/annex-history.adoc b/docs/sections/annex-history.adoc similarity index 100% rename from standard/sections/annex-history.adoc rename to docs/sections/annex-history.adoc diff --git a/standard/sections/annex-n.adoc b/docs/sections/annex-n.adoc similarity index 100% rename from standard/sections/annex-n.adoc rename to docs/sections/annex-n.adoc diff --git a/standard/sections/clause_0_front_material.adoc b/docs/sections/clause_0_front_material.adoc similarity index 100% rename from standard/sections/clause_0_front_material.adoc rename to docs/sections/clause_0_front_material.adoc diff --git a/standard/sections/clause_1_scope.adoc b/docs/sections/clause_1_scope.adoc similarity index 100% rename from standard/sections/clause_1_scope.adoc rename to docs/sections/clause_1_scope.adoc diff --git a/standard/sections/clause_2_conformance.adoc b/docs/sections/clause_2_conformance.adoc similarity index 100% rename from standard/sections/clause_2_conformance.adoc rename to docs/sections/clause_2_conformance.adoc diff --git a/standard/sections/clause_3_references.adoc b/docs/sections/clause_3_references.adoc similarity index 100% rename from standard/sections/clause_3_references.adoc rename to docs/sections/clause_3_references.adoc diff --git a/standard/sections/clause_4_terms_and_definitions.adoc b/docs/sections/clause_4_terms_and_definitions.adoc similarity index 100% rename from standard/sections/clause_4_terms_and_definitions.adoc rename to docs/sections/clause_4_terms_and_definitions.adoc diff --git a/standard/sections/clause_5_conventions.adoc b/docs/sections/clause_5_conventions.adoc similarity index 100% rename from standard/sections/clause_5_conventions.adoc rename to docs/sections/clause_5_conventions.adoc diff --git a/standard/sections/clause_6_informative_text.adoc b/docs/sections/clause_6_informative_text.adoc similarity index 100% rename from standard/sections/clause_6_informative_text.adoc rename to docs/sections/clause_6_informative_text.adoc diff --git a/standard/sections/clause_7_normative_text.adoc b/docs/sections/clause_7_normative_text.adoc similarity index 100% rename from standard/sections/clause_7_normative_text.adoc rename to docs/sections/clause_7_normative_text.adoc diff --git a/standard/sections/clause_8_media_types.adoc b/docs/sections/clause_8_media_types.adoc similarity index 100% rename from standard/sections/clause_8_media_types.adoc rename to docs/sections/clause_8_media_types.adoc diff --git a/standard/.github/workflows/docker.yml b/docs/workflows/docker.yml similarity index 100% rename from standard/.github/workflows/docker.yml rename to docs/workflows/docker.yml diff --git a/standard/.github/workflows/generate.yml b/docs/workflows/generate.yml similarity index 100% rename from standard/.github/workflows/generate.yml rename to docs/workflows/generate.yml From c66453ecc2ebbba97e048cfd51bd8e1a4bf474eb Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:39:35 +0000 Subject: [PATCH 07/18] no jekyll --- docs/.nojekyll | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 docs/.nojekyll diff --git a/docs/.nojekyll b/docs/.nojekyll new file mode 100644 index 0000000..e69de29 From b5ef6d81402e127741ddffb67cc4cc682022cf64 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:42:48 +0000 Subject: [PATCH 08/18] update to index.html --- .github/workflows/compile_doc.yml | 2 +- docs/{document.adoc => index.adoc} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename docs/{document.adoc => index.adoc} (100%) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index ba527d9..fd16a23 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -15,7 +15,7 @@ jobs: - name: Generate document run: | cd main/docs - metanorma compile --agree-to-terms -t ogc -x xml,html,doc document.adoc + metanorma compile --agree-to-terms -t ogc -x xml,html,doc index.adoc git config --global user.name 'example' git config --global user.email 'example@example.com' git add index.html diff --git a/docs/document.adoc b/docs/index.adoc similarity index 100% rename from docs/document.adoc rename to docs/index.adoc From 600506d43a858c14205ed5c21a877eb09ef8edd4 Mon Sep 17 00:00:00 2001 From: example Date: Thu, 16 Mar 2023 15:44:36 +0000 Subject: [PATCH 09/18] Compilation of HTML documents --- docs/index.html | 1806 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1806 insertions(+) create mode 100644 docs/index.html diff --git a/docs/index.html b/docs/index.html new file mode 100644 index 0000000..0abb3e2 --- /dev/null +++ b/docs/index.html @@ -0,0 +1,1806 @@ + + +OGC Geoscience Markup Language + + + + + + + + + + + + + + + + +Text here>'/>
+

Draft

+
+ +
+

OGC Standard

+
+ + + +
•
+ +
+ + +
+
+ +
+ +
+ OGC Geoscience Markup Language + +
+
+ + + + + +
+ + + + + + + Edward Lewis Editor + + Editor Two Editor + + +
+ +
+ Submission Date: 2029-03-30 + Approval Date: 2029-03-30 + Publication Date: 2029-03-30 + External identifier of this OGC® document: http://www.opengis.net/doc/{doc-type}/{standard}/{m.n} + Internal identifier of this OGC® document: YY-999 + + +
+ +
+ + Version: 1.0
+ + + Additional Formats: + + XML + + + PDF + + + DOC + +
+ +
+ +
+ +
+ +
+
+ OGC Standard +
+ +
+

Draft

+
+
+ +
+
+ + +

Notice for Drafts

+ +

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

+ +

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

+
+ + + + + +
+
+ + + +
+ + + + + + +
Document number:YY-999
Document type:OGC Standard
Document subtype:Implementation
Document stage:Draft
Document language:English
+
+ +
+
+
+

Copyright notice

+ + +

Copyright + © 2023 Open Geospatial Consortium
+ To obtain additional rights of use, visit + https://www.ogc.org/legal +

+
+

Note

+ +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+
+
+
+ +
+
+
+

+
+

License Agreement

+ + +

Use of this document is subject to the license agreement at + https://www.ogc.org/license

+
+
+ + +
+ +
+

Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/

+
+ +
+ + +
+ + + + +
+

+ + + + + + + + + +

I.  Abstract

<Insert Abstract Text here>

II.  Keywords

The following are keywords to be used by search engines and + document catalogues.

ogcdoc, OGC document, API, openapi, html


III.  Preface

NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

IV.  Security considerations

No security considerations have been made for this Standard.

V.  Submitting Organizations

The following organizations submitted this Document to the + Open Geospatial Consortium (OGC):

  • Organization One
    • +
  • Organization Two

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

OGC Geoscience Markup Language

1.  Scope

NOTE  Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

2.  Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

  • AAAA

    +
    • +

  • BBBB

    +
    • +

Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site.

In order to conform to this OGC® interface standard, a software implementation shall choose to implement:

  • Any one of the conformance levels specified in Annex A (normative).

    +
    • +

  • Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative).

    +
    • +

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

3.  Normative references

+

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

+ + + + +

Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)

+

ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)

+

The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).

+

Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)

+

The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)

+

National Center for Biotechnology Information, http://www.ncbi.nlm.nih.gov

+

ISO: ISO 19101-1:2014, Geographic information — Reference model — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/59164.html.

+

ISO: ISO 19115-1:2014, Geographic information — Metadata — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/53798.html.

+

ISO: ISO 19157:2013, Geographic information  — Data quality. International Organization for Standardization, Geneva (2013). https://www.iso.org/standard/32575.html.

+

ISO: ISO 19139:2007, Geographic information — Metadata — XML schema implementation. ISO (2007).

+

ISO: ISO 19115-3, Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts. International Organization for Standardization, Geneva https://www.iso.org/standard/80874.html.

+

OGC Geospatial User Feedback Standard: Conceptual Model (2016)

+

Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele: OGC 12-019, OGC City Geography Markup Language (CityGML) Encoding Standard. Open Geospatial Consortium (2012). https://portal.ogc.org/files/?artifact id=47842.

+

Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker: OGC 14-005r3, OGC® IndoorGML. Open Geospatial Consortium (2014). https://docs.ogc.org/is/14-005r3/14-005r3.html.

+

Arliss Whiteside Jim Greenwood: OGC 06-121r9, OGC Web Service Common Implementation Specification. Open Geospatial Consortium (2010). https://portal.ogc.org/files/?artifact id=38867.

+

4.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1. example term

+

term used for exemplary purposes

+ + + + + + +

Note 1 to entry: An example note.

Example

Here’s an example of an example term.

+

[SOURCE: ISO 19101-1:2014]

5.  Keywords

6.  Submitting organizations

7.  Contributors

Additional contributors to this Standard include the following:

Individual name(s), Organization

8.  Conventions

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

8.1.  Identifiers

+ +

The normative provisions in this standard are denoted by the URI

+ +

http://www.opengis.net/spec/{standard}/{m.n}

+ +

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

+

9.  Clauses not containing normative material

Paragraph

9.1.  Clauses not containing normative material sub-clause 1

+ +

Paragraph

+

9.2.  Clauses not containing normative material sub-clause 2

+ +

10.  Clause containing normative material

Paragraph

10.1.  Requirement Class A or Requirement A Example

+ +

Paragraph – intro text for the requirement class.

+ +

Use the following table for Requirements Classes.

+ +

Requirements class 1

Obligationrequirement
Description

Requirements Class

Normative statementsRequirement 1-1
Requirement 1-2
+ +

10.1.1.  Requirement 1

+ +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 1

Obligationrequirement
Statement

Requirement ‘shall’ statement

+ +

Dictionary tables for requirements can be added as necessary. Modify the following example as needed.

+ +

Table 1

NamesDefinitionData types and valuesMultiplicity and use
name 1definition of name 1floatOne or more (mandatory)
name 2definition of name 2character string type, not emptyZero or one (optional)
name 3definition of name 3GML:: Point PropertyTypeOne (mandatory)
+
+ +

10.1.2.  Requirement 2

+ +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 2

Label/req/req-class-a/req-name-2
Conditions

  1. The process input value is specified in-line in an execute request.

    +
    2. +

  2. The process input is defined as an object according to its schema.

    +
    3. +
+
A

The server SHALL support process input values encoded as qualified values.

+
B

The value of the value key SHALL be an object instance.

+
+
+

11.  Media Types for any data encoding(s)

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in http://www.iana.org/assignments/media-types/index.html then this section may be used to define a new MIME type for registration with IANA.


Annex A
(informative)
Conformance Class Abstract Test Suite (Normative)

NOTE  Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

A.1.  Conformance Class A

+ +

Example

label

http://www.opengis.net/spec/name-of-standard/1.0/conf/example1

+

subject

Requirements Class “example1”

+

classification

Target Type:Web API

+
+
+ +

A.1.1.  Example 1

+ +

Abstract test A.1

Subject/req/req-class-a/req-name-1
Label/conf/core/api-definition-op
Test purpose

Validate that the API Definition document can be retrieved from the expected location.

+
Test method
    +

  1. Construct a path for the API Definition document that ends with /api.

    +
    2. +

  2. Issue a HTTP GET request on that path

    +
    3. +

  3. Validate the contents of the returned document using test /conf/core/api-definition-success.

    +
    4. +
+ +
+
+ +

A.1.2.  Example 2

+ +

Abstract test A.2

Subject/req/req-class-a/req-name-2
Label/conf/core/http
Test purpose

Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

+
Test method
    +

  1. All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

    +
    2. +

  2. For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol.

    +
    3. +
+
+
+

Annex B
(informative)
Title

NOTE  Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography


Annex C
(informative)
Revision History

Table C.1

DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version

Bibliography

+ +

NOTE  The TC has approved Springer LNCS as the official document citation type.

Springer LNCS is widely used in technical and computer science journals and other publications

– Actual References:

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

[n] Web: Author Surname, A.: Title, http://Website-Url

[1]  OGC: OGC Testbed 12 Annex B: Architecture (2015).

+ + +
+ + + + + + + + + + + + + + + + + + + From b4ebf6fcde49506b8c38c4288597b91bf435ed8e Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:55:14 +0000 Subject: [PATCH 10/18] add artifacts to workflow --- .github/workflows/compile_doc.yml | 13 +- docs/document.html | 1806 ----------------- {docs => standard}/.gitignore | 0 {docs => standard}/.gitlab-ci.yml | 0 {docs => standard}/Gemfile | 0 {docs => standard}/Makefile | 0 {docs => standard}/Makefile.win | 0 {docs => standard}/README.adoc | 0 {docs => standard}/UML/README.adoc | 0 .../abstract_tests/ATS_class_example1.adoc | 0 .../abstract_tests/ATS_test_example1.adoc | 0 .../abstract_tests/ATS_test_example2.adoc | 0 {docs => standard}/abstract_tests/README.adoc | 0 {docs => standard}/code/README.adoc | 0 {docs => standard}/figures/README.adoc | 0 {docs => standard}/images/README.adoc | 0 {docs => standard}/index.adoc | 0 {docs => standard}/metanorma.yml | 0 .../relaton/cache/iso/iso_19101_1_2014.xml | 0 .../relaton/cache/iso/iso_19115_1_2014.xml | 0 .../relaton/cache/iso/iso_19115_3.xml | 0 .../relaton/cache/iso/iso_19139_2007.notfound | 0 .../relaton/cache/iso/iso_19157_2013.xml | 0 {docs => standard}/relaton/cache/iso/version | 0 .../relaton/cache/ogc/06_121r9.xml | 0 .../relaton/cache/ogc/12_019.xml | 0 .../relaton/cache/ogc/14_005r3.xml | 0 .../relaton/cache/ogc/ogc_06_121r9.redirect | 0 .../relaton/cache/ogc/ogc_12_019.redirect | 0 .../relaton/cache/ogc/ogc_14_005r3.redirect | 0 .../relaton/cache/ogc/ogc_15_097.notfound | 0 {docs => standard}/relaton/cache/ogc/version | 0 {docs => standard}/requirements/README.adoc | 0 .../requirements/requirement001.adoc | 0 .../requirements/requirement002.adoc | 0 .../requirements/requirements_class.adoc | 0 {docs => standard}/sections/annex-a.adoc | 0 .../sections/annex-bibliography.adoc | 0 .../sections/annex-history.adoc | 0 {docs => standard}/sections/annex-n.adoc | 0 .../sections/clause_0_front_material.adoc | 0 .../sections/clause_1_scope.adoc | 0 .../sections/clause_2_conformance.adoc | 0 .../sections/clause_3_references.adoc | 0 .../clause_4_terms_and_definitions.adoc | 0 .../sections/clause_5_conventions.adoc | 0 .../sections/clause_6_informative_text.adoc | 0 .../sections/clause_7_normative_text.adoc | 0 .../sections/clause_8_media_types.adoc | 0 {docs => standard}/workflows/docker.yml | 0 {docs => standard}/workflows/generate.yml | 0 51 files changed, 7 insertions(+), 1812 deletions(-) delete mode 100644 docs/document.html rename {docs => standard}/.gitignore (100%) rename {docs => standard}/.gitlab-ci.yml (100%) rename {docs => standard}/Gemfile (100%) rename {docs => standard}/Makefile (100%) rename {docs => standard}/Makefile.win (100%) rename {docs => standard}/README.adoc (100%) rename {docs => standard}/UML/README.adoc (100%) rename {docs => standard}/abstract_tests/ATS_class_example1.adoc (100%) rename {docs => standard}/abstract_tests/ATS_test_example1.adoc (100%) rename {docs => standard}/abstract_tests/ATS_test_example2.adoc (100%) rename {docs => standard}/abstract_tests/README.adoc (100%) rename {docs => standard}/code/README.adoc (100%) rename {docs => standard}/figures/README.adoc (100%) rename {docs => standard}/images/README.adoc (100%) rename {docs => standard}/index.adoc (100%) rename {docs => standard}/metanorma.yml (100%) rename {docs => standard}/relaton/cache/iso/iso_19101_1_2014.xml (100%) rename {docs => standard}/relaton/cache/iso/iso_19115_1_2014.xml (100%) rename {docs => standard}/relaton/cache/iso/iso_19115_3.xml (100%) rename {docs => standard}/relaton/cache/iso/iso_19139_2007.notfound (100%) rename {docs => standard}/relaton/cache/iso/iso_19157_2013.xml (100%) rename {docs => standard}/relaton/cache/iso/version (100%) rename {docs => standard}/relaton/cache/ogc/06_121r9.xml (100%) rename {docs => standard}/relaton/cache/ogc/12_019.xml (100%) rename {docs => standard}/relaton/cache/ogc/14_005r3.xml (100%) rename {docs => standard}/relaton/cache/ogc/ogc_06_121r9.redirect (100%) rename {docs => standard}/relaton/cache/ogc/ogc_12_019.redirect (100%) rename {docs => standard}/relaton/cache/ogc/ogc_14_005r3.redirect (100%) rename {docs => standard}/relaton/cache/ogc/ogc_15_097.notfound (100%) rename {docs => standard}/relaton/cache/ogc/version (100%) rename {docs => standard}/requirements/README.adoc (100%) rename {docs => standard}/requirements/requirement001.adoc (100%) rename {docs => standard}/requirements/requirement002.adoc (100%) rename {docs => standard}/requirements/requirements_class.adoc (100%) rename {docs => standard}/sections/annex-a.adoc (100%) rename {docs => standard}/sections/annex-bibliography.adoc (100%) rename {docs => standard}/sections/annex-history.adoc (100%) rename {docs => standard}/sections/annex-n.adoc (100%) rename {docs => standard}/sections/clause_0_front_material.adoc (100%) rename {docs => standard}/sections/clause_1_scope.adoc (100%) rename {docs => standard}/sections/clause_2_conformance.adoc (100%) rename {docs => standard}/sections/clause_3_references.adoc (100%) rename {docs => standard}/sections/clause_4_terms_and_definitions.adoc (100%) rename {docs => standard}/sections/clause_5_conventions.adoc (100%) rename {docs => standard}/sections/clause_6_informative_text.adoc (100%) rename {docs => standard}/sections/clause_7_normative_text.adoc (100%) rename {docs => standard}/sections/clause_8_media_types.adoc (100%) rename {docs => standard}/workflows/docker.yml (100%) rename {docs => standard}/workflows/generate.yml (100%) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index fd16a23..8a2892a 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -14,10 +14,11 @@ jobs: path: main - name: Generate document run: | - cd main/docs + cd main/standard metanorma compile --agree-to-terms -t ogc -x xml,html,doc index.adoc - git config --global user.name 'example' - git config --global user.email 'example@example.com' - git add index.html - git commit -am "Compilation of HTML documents" - git push + - name: Archive production artifacts + uses: actions/upload-artifact@v3 + with: + name: dist + path: | + docs diff --git a/docs/document.html b/docs/document.html deleted file mode 100644 index 8cbc106..0000000 --- a/docs/document.html +++ /dev/null @@ -1,1806 +0,0 @@ - - -OGC Geoscience Markup Language - - - - - - - - - - - - - - - - -Text here>'/>
-

Draft

-
- -
-

OGC Standard

-
- - - -
•
- -
- - -
-
- -
- -
- OGC Geoscience Markup Language - -
-
- - - - - -
- - - - - - - Edward Lewis Editor - - Editor Two Editor - - -
- -
- Submission Date: 2029-03-30 - Approval Date: 2029-03-30 - Publication Date: 2029-03-30 - External identifier of this OGC® document: http://www.opengis.net/doc/{doc-type}/{standard}/{m.n} - Internal identifier of this OGC® document: YY-999 - - -
- -
- - Version: 1.0
- - - Additional Formats: - - XML - - - PDF - - - DOC - -
- -
- -
- -
- -
-
- OGC Standard -
- -
-

Draft

-
-
- -
-
- - -

Notice for Drafts

- -

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

- -

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

-
- - - - - -
-
- - - -
- - - - - - -
Document number:YY-999
Document type:OGC Standard
Document subtype:Implementation
Document stage:Draft
Document language:English
-
- -
-
-
-

Copyright notice

- - -

Copyright - © 2023 Open Geospatial Consortium
- To obtain additional rights of use, visit - https://www.ogc.org/legal -

-
-

Note

- -

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

- -

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

-
-
-
- -
-
-
-

-
-

License Agreement

- - -

Use of this document is subject to the license agreement at - https://www.ogc.org/license

-
-
- - -
- -
-

Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/

-
- -
- - -
- - - - -
-

- - - - - - - - - -

I.  Abstract

<Insert Abstract Text here>

II.  Keywords

The following are keywords to be used by search engines and - document catalogues.

ogcdoc, OGC document, API, openapi, html


III.  Preface

NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

IV.  Security considerations

No security considerations have been made for this Standard.

V.  Submitting Organizations

The following organizations submitted this Document to the - Open Geospatial Consortium (OGC):

  • Organization One
    • -
  • Organization Two

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

OGC Geoscience Markup Language

1.  Scope

NOTE  Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

2.  Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

  • AAAA

    -
    • -

  • BBBB

    -
    • -

Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site.

In order to conform to this OGC® interface standard, a software implementation shall choose to implement:

  • Any one of the conformance levels specified in Annex A (normative).

    -
    • -

  • Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative).

    -
    • -

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

3.  Normative references

-

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

- - - - -

Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)

-

ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)

-

The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).

-

Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)

-

The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)

-

National Center for Biotechnology Information, http://www.ncbi.nlm.nih.gov

-

ISO: ISO 19101-1:2014, Geographic information — Reference model — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/59164.html.

-

ISO: ISO 19115-1:2014, Geographic information — Metadata — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/53798.html.

-

ISO: ISO 19157:2013, Geographic information  — Data quality. International Organization for Standardization, Geneva (2013). https://www.iso.org/standard/32575.html.

-

ISO: ISO 19139:2007, Geographic information — Metadata — XML schema implementation. ISO (2007).

-

ISO: ISO 19115-3, Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts. International Organization for Standardization, Geneva https://www.iso.org/standard/80874.html.

-

OGC Geospatial User Feedback Standard: Conceptual Model (2016)

-

Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele: OGC 12-019, OGC City Geography Markup Language (CityGML) Encoding Standard. Open Geospatial Consortium (2012). https://portal.ogc.org/files/?artifact id=47842.

-

Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker: OGC 14-005r3, OGC® IndoorGML. Open Geospatial Consortium (2014). https://docs.ogc.org/is/14-005r3/14-005r3.html.

-

Arliss Whiteside Jim Greenwood: OGC 06-121r9, OGC Web Service Common Implementation Specification. Open Geospatial Consortium (2010). https://portal.ogc.org/files/?artifact id=38867.

-

4.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1. example term

-

term used for exemplary purposes

- - - - - - -

Note 1 to entry: An example note.

Example

Here’s an example of an example term.

-

[SOURCE: ISO 19101-1:2014]

5.  Keywords

6.  Submitting organizations

7.  Contributors

Additional contributors to this Standard include the following:

Individual name(s), Organization

8.  Conventions

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

8.1.  Identifiers

- -

The normative provisions in this standard are denoted by the URI

- -

http://www.opengis.net/spec/{standard}/{m.n}

- -

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

-

9.  Clauses not containing normative material

Paragraph

9.1.  Clauses not containing normative material sub-clause 1

- -

Paragraph

-

9.2.  Clauses not containing normative material sub-clause 2

- -

10.  Clause containing normative material

Paragraph

10.1.  Requirement Class A or Requirement A Example

- -

Paragraph – intro text for the requirement class.

- -

Use the following table for Requirements Classes.

- -

Requirements class 1

Obligationrequirement
Description

Requirements Class

Normative statementsRequirement 1-1
Requirement 1-2
- -

10.1.1.  Requirement 1

- -

Paragraph — intro text for the requirement.

- -

Use the following table for Requirements, number sequentially.

- -

Requirement 1

Obligationrequirement
Statement

Requirement ‘shall’ statement

- -

Dictionary tables for requirements can be added as necessary. Modify the following example as needed.

- -

Table 1

NamesDefinitionData types and valuesMultiplicity and use
name 1definition of name 1floatOne or more (mandatory)
name 2definition of name 2character string type, not emptyZero or one (optional)
name 3definition of name 3GML:: Point PropertyTypeOne (mandatory)
-
- -

10.1.2.  Requirement 2

- -

Paragraph — intro text for the requirement.

- -

Use the following table for Requirements, number sequentially.

- -

Requirement 2

Label/req/req-class-a/req-name-2
Conditions

  1. The process input value is specified in-line in an execute request.

    -
    2. -

  2. The process input is defined as an object according to its schema.

    -
    3. -
-
A

The server SHALL support process input values encoded as qualified values.

-
B

The value of the value key SHALL be an object instance.

-
-
-

11.  Media Types for any data encoding(s)

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in http://www.iana.org/assignments/media-types/index.html then this section may be used to define a new MIME type for registration with IANA.


Annex A
(informative)
Conformance Class Abstract Test Suite (Normative)

NOTE  Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

A.1.  Conformance Class A

- -

Example

label

http://www.opengis.net/spec/name-of-standard/1.0/conf/example1

-

subject

Requirements Class “example1”

-

classification

Target Type:Web API

-
-
- -

A.1.1.  Example 1

- -

Abstract test A.1

Subject/req/req-class-a/req-name-1
Label/conf/core/api-definition-op
Test purpose

Validate that the API Definition document can be retrieved from the expected location.

-
Test method
    -

  1. Construct a path for the API Definition document that ends with /api.

    -
    2. -

  2. Issue a HTTP GET request on that path

    -
    3. -

  3. Validate the contents of the returned document using test /conf/core/api-definition-success.

    -
    4. -
- -
-
- -

A.1.2.  Example 2

- -

Abstract test A.2

Subject/req/req-class-a/req-name-2
Label/conf/core/http
Test purpose

Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

-
Test method
    -

  1. All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

    -
    2. -

  2. For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol.

    -
    3. -
-
-
-

Annex B
(informative)
Title

NOTE  Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography


Annex C
(informative)
Revision History

Table C.1

DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version

Bibliography

- -

NOTE  The TC has approved Springer LNCS as the official document citation type.

Springer LNCS is widely used in technical and computer science journals and other publications

– Actual References:

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

[n] Web: Author Surname, A.: Title, http://Website-Url

[1]  OGC: OGC Testbed 12 Annex B: Architecture (2015).

- - -
- - - - - - - - - - - - - - - - - - - diff --git a/docs/.gitignore b/standard/.gitignore similarity index 100% rename from docs/.gitignore rename to standard/.gitignore diff --git a/docs/.gitlab-ci.yml b/standard/.gitlab-ci.yml similarity index 100% rename from docs/.gitlab-ci.yml rename to standard/.gitlab-ci.yml diff --git a/docs/Gemfile b/standard/Gemfile similarity index 100% rename from docs/Gemfile rename to standard/Gemfile diff --git a/docs/Makefile b/standard/Makefile similarity index 100% rename from docs/Makefile rename to standard/Makefile diff --git a/docs/Makefile.win b/standard/Makefile.win similarity index 100% rename from docs/Makefile.win rename to standard/Makefile.win diff --git a/docs/README.adoc b/standard/README.adoc similarity index 100% rename from docs/README.adoc rename to standard/README.adoc diff --git a/docs/UML/README.adoc b/standard/UML/README.adoc similarity index 100% rename from docs/UML/README.adoc rename to standard/UML/README.adoc diff --git a/docs/abstract_tests/ATS_class_example1.adoc b/standard/abstract_tests/ATS_class_example1.adoc similarity index 100% rename from docs/abstract_tests/ATS_class_example1.adoc rename to standard/abstract_tests/ATS_class_example1.adoc diff --git a/docs/abstract_tests/ATS_test_example1.adoc b/standard/abstract_tests/ATS_test_example1.adoc similarity index 100% rename from docs/abstract_tests/ATS_test_example1.adoc rename to standard/abstract_tests/ATS_test_example1.adoc diff --git a/docs/abstract_tests/ATS_test_example2.adoc b/standard/abstract_tests/ATS_test_example2.adoc similarity index 100% rename from docs/abstract_tests/ATS_test_example2.adoc rename to standard/abstract_tests/ATS_test_example2.adoc diff --git a/docs/abstract_tests/README.adoc b/standard/abstract_tests/README.adoc similarity index 100% rename from docs/abstract_tests/README.adoc rename to standard/abstract_tests/README.adoc diff --git a/docs/code/README.adoc b/standard/code/README.adoc similarity index 100% rename from docs/code/README.adoc rename to standard/code/README.adoc diff --git a/docs/figures/README.adoc b/standard/figures/README.adoc similarity index 100% rename from docs/figures/README.adoc rename to standard/figures/README.adoc diff --git a/docs/images/README.adoc b/standard/images/README.adoc similarity index 100% rename from docs/images/README.adoc rename to standard/images/README.adoc diff --git a/docs/index.adoc b/standard/index.adoc similarity index 100% rename from docs/index.adoc rename to standard/index.adoc diff --git a/docs/metanorma.yml b/standard/metanorma.yml similarity index 100% rename from docs/metanorma.yml rename to standard/metanorma.yml diff --git a/docs/relaton/cache/iso/iso_19101_1_2014.xml b/standard/relaton/cache/iso/iso_19101_1_2014.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19101_1_2014.xml rename to standard/relaton/cache/iso/iso_19101_1_2014.xml diff --git a/docs/relaton/cache/iso/iso_19115_1_2014.xml b/standard/relaton/cache/iso/iso_19115_1_2014.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19115_1_2014.xml rename to standard/relaton/cache/iso/iso_19115_1_2014.xml diff --git a/docs/relaton/cache/iso/iso_19115_3.xml b/standard/relaton/cache/iso/iso_19115_3.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19115_3.xml rename to standard/relaton/cache/iso/iso_19115_3.xml diff --git a/docs/relaton/cache/iso/iso_19139_2007.notfound b/standard/relaton/cache/iso/iso_19139_2007.notfound similarity index 100% rename from docs/relaton/cache/iso/iso_19139_2007.notfound rename to standard/relaton/cache/iso/iso_19139_2007.notfound diff --git a/docs/relaton/cache/iso/iso_19157_2013.xml b/standard/relaton/cache/iso/iso_19157_2013.xml similarity index 100% rename from docs/relaton/cache/iso/iso_19157_2013.xml rename to standard/relaton/cache/iso/iso_19157_2013.xml diff --git a/docs/relaton/cache/iso/version b/standard/relaton/cache/iso/version similarity index 100% rename from docs/relaton/cache/iso/version rename to standard/relaton/cache/iso/version diff --git a/docs/relaton/cache/ogc/06_121r9.xml b/standard/relaton/cache/ogc/06_121r9.xml similarity index 100% rename from docs/relaton/cache/ogc/06_121r9.xml rename to standard/relaton/cache/ogc/06_121r9.xml diff --git a/docs/relaton/cache/ogc/12_019.xml b/standard/relaton/cache/ogc/12_019.xml similarity index 100% rename from docs/relaton/cache/ogc/12_019.xml rename to standard/relaton/cache/ogc/12_019.xml diff --git a/docs/relaton/cache/ogc/14_005r3.xml b/standard/relaton/cache/ogc/14_005r3.xml similarity index 100% rename from docs/relaton/cache/ogc/14_005r3.xml rename to standard/relaton/cache/ogc/14_005r3.xml diff --git a/docs/relaton/cache/ogc/ogc_06_121r9.redirect b/standard/relaton/cache/ogc/ogc_06_121r9.redirect similarity index 100% rename from docs/relaton/cache/ogc/ogc_06_121r9.redirect rename to standard/relaton/cache/ogc/ogc_06_121r9.redirect diff --git a/docs/relaton/cache/ogc/ogc_12_019.redirect b/standard/relaton/cache/ogc/ogc_12_019.redirect similarity index 100% rename from docs/relaton/cache/ogc/ogc_12_019.redirect rename to standard/relaton/cache/ogc/ogc_12_019.redirect diff --git a/docs/relaton/cache/ogc/ogc_14_005r3.redirect b/standard/relaton/cache/ogc/ogc_14_005r3.redirect similarity index 100% rename from docs/relaton/cache/ogc/ogc_14_005r3.redirect rename to standard/relaton/cache/ogc/ogc_14_005r3.redirect diff --git a/docs/relaton/cache/ogc/ogc_15_097.notfound b/standard/relaton/cache/ogc/ogc_15_097.notfound similarity index 100% rename from docs/relaton/cache/ogc/ogc_15_097.notfound rename to standard/relaton/cache/ogc/ogc_15_097.notfound diff --git a/docs/relaton/cache/ogc/version b/standard/relaton/cache/ogc/version similarity index 100% rename from docs/relaton/cache/ogc/version rename to standard/relaton/cache/ogc/version diff --git a/docs/requirements/README.adoc b/standard/requirements/README.adoc similarity index 100% rename from docs/requirements/README.adoc rename to standard/requirements/README.adoc diff --git a/docs/requirements/requirement001.adoc b/standard/requirements/requirement001.adoc similarity index 100% rename from docs/requirements/requirement001.adoc rename to standard/requirements/requirement001.adoc diff --git a/docs/requirements/requirement002.adoc b/standard/requirements/requirement002.adoc similarity index 100% rename from docs/requirements/requirement002.adoc rename to standard/requirements/requirement002.adoc diff --git a/docs/requirements/requirements_class.adoc b/standard/requirements/requirements_class.adoc similarity index 100% rename from docs/requirements/requirements_class.adoc rename to standard/requirements/requirements_class.adoc diff --git a/docs/sections/annex-a.adoc b/standard/sections/annex-a.adoc similarity index 100% rename from docs/sections/annex-a.adoc rename to standard/sections/annex-a.adoc diff --git a/docs/sections/annex-bibliography.adoc b/standard/sections/annex-bibliography.adoc similarity index 100% rename from docs/sections/annex-bibliography.adoc rename to standard/sections/annex-bibliography.adoc diff --git a/docs/sections/annex-history.adoc b/standard/sections/annex-history.adoc similarity index 100% rename from docs/sections/annex-history.adoc rename to standard/sections/annex-history.adoc diff --git a/docs/sections/annex-n.adoc b/standard/sections/annex-n.adoc similarity index 100% rename from docs/sections/annex-n.adoc rename to standard/sections/annex-n.adoc diff --git a/docs/sections/clause_0_front_material.adoc b/standard/sections/clause_0_front_material.adoc similarity index 100% rename from docs/sections/clause_0_front_material.adoc rename to standard/sections/clause_0_front_material.adoc diff --git a/docs/sections/clause_1_scope.adoc b/standard/sections/clause_1_scope.adoc similarity index 100% rename from docs/sections/clause_1_scope.adoc rename to standard/sections/clause_1_scope.adoc diff --git a/docs/sections/clause_2_conformance.adoc b/standard/sections/clause_2_conformance.adoc similarity index 100% rename from docs/sections/clause_2_conformance.adoc rename to standard/sections/clause_2_conformance.adoc diff --git a/docs/sections/clause_3_references.adoc b/standard/sections/clause_3_references.adoc similarity index 100% rename from docs/sections/clause_3_references.adoc rename to standard/sections/clause_3_references.adoc diff --git a/docs/sections/clause_4_terms_and_definitions.adoc b/standard/sections/clause_4_terms_and_definitions.adoc similarity index 100% rename from docs/sections/clause_4_terms_and_definitions.adoc rename to standard/sections/clause_4_terms_and_definitions.adoc diff --git a/docs/sections/clause_5_conventions.adoc b/standard/sections/clause_5_conventions.adoc similarity index 100% rename from docs/sections/clause_5_conventions.adoc rename to standard/sections/clause_5_conventions.adoc diff --git a/docs/sections/clause_6_informative_text.adoc b/standard/sections/clause_6_informative_text.adoc similarity index 100% rename from docs/sections/clause_6_informative_text.adoc rename to standard/sections/clause_6_informative_text.adoc diff --git a/docs/sections/clause_7_normative_text.adoc b/standard/sections/clause_7_normative_text.adoc similarity index 100% rename from docs/sections/clause_7_normative_text.adoc rename to standard/sections/clause_7_normative_text.adoc diff --git a/docs/sections/clause_8_media_types.adoc b/standard/sections/clause_8_media_types.adoc similarity index 100% rename from docs/sections/clause_8_media_types.adoc rename to standard/sections/clause_8_media_types.adoc diff --git a/docs/workflows/docker.yml b/standard/workflows/docker.yml similarity index 100% rename from docs/workflows/docker.yml rename to standard/workflows/docker.yml diff --git a/docs/workflows/generate.yml b/standard/workflows/generate.yml similarity index 100% rename from docs/workflows/generate.yml rename to standard/workflows/generate.yml From f839530fbdff0a5b44b30795ee02f17e059fbdd3 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 15:57:20 +0000 Subject: [PATCH 11/18] change path --- .github/workflows/compile_doc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index 8a2892a..3b15f06 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -21,4 +21,4 @@ jobs: with: name: dist path: | - docs + standard From f46c2aff377b1dea3fd64759767df3a0e8f115a7 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 16:06:13 +0000 Subject: [PATCH 12/18] update artifeact path --- .github/workflows/compile_doc.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index 3b15f06..467ccf6 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -16,9 +16,10 @@ jobs: run: | cd main/standard metanorma compile --agree-to-terms -t ogc -x xml,html,doc index.adoc + - name: Archive production artifacts uses: actions/upload-artifact@v3 with: name: dist path: | - standard + main/standard/index.** From 8e0859bd1b805045755e79d85c0c0ba025b89f92 Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 16:14:14 +0000 Subject: [PATCH 13/18] move back to docs --- .github/workflows/compile_doc.yml | 14 ++++++-------- {standard => docs}/.gitignore | 0 {standard => docs}/.gitlab-ci.yml | 0 {standard => docs}/Gemfile | 0 {standard => docs}/Makefile | 0 {standard => docs}/Makefile.win | 0 {standard => docs}/README.adoc | 0 {standard => docs}/UML/README.adoc | 0 .../abstract_tests/ATS_class_example1.adoc | 0 .../abstract_tests/ATS_test_example1.adoc | 0 .../abstract_tests/ATS_test_example2.adoc | 0 {standard => docs}/abstract_tests/README.adoc | 0 {standard => docs}/code/README.adoc | 0 {standard => docs}/figures/README.adoc | 0 {standard => docs}/images/README.adoc | 0 {standard => docs}/index.adoc | 0 {standard => docs}/metanorma.yml | 0 .../relaton/cache/iso/iso_19101_1_2014.xml | 0 .../relaton/cache/iso/iso_19115_1_2014.xml | 0 .../relaton/cache/iso/iso_19115_3.xml | 0 .../relaton/cache/iso/iso_19139_2007.notfound | 0 .../relaton/cache/iso/iso_19157_2013.xml | 0 {standard => docs}/relaton/cache/iso/version | 0 {standard => docs}/relaton/cache/ogc/06_121r9.xml | 0 {standard => docs}/relaton/cache/ogc/12_019.xml | 0 {standard => docs}/relaton/cache/ogc/14_005r3.xml | 0 .../relaton/cache/ogc/ogc_06_121r9.redirect | 0 .../relaton/cache/ogc/ogc_12_019.redirect | 0 .../relaton/cache/ogc/ogc_14_005r3.redirect | 0 .../relaton/cache/ogc/ogc_15_097.notfound | 0 {standard => docs}/relaton/cache/ogc/version | 0 {standard => docs}/requirements/README.adoc | 0 .../requirements/requirement001.adoc | 0 .../requirements/requirement002.adoc | 0 .../requirements/requirements_class.adoc | 0 {standard => docs}/sections/annex-a.adoc | 0 .../sections/annex-bibliography.adoc | 0 {standard => docs}/sections/annex-history.adoc | 0 {standard => docs}/sections/annex-n.adoc | 0 .../sections/clause_0_front_material.adoc | 0 {standard => docs}/sections/clause_1_scope.adoc | 0 .../sections/clause_2_conformance.adoc | 0 .../sections/clause_3_references.adoc | 0 .../sections/clause_4_terms_and_definitions.adoc | 0 .../sections/clause_5_conventions.adoc | 0 .../sections/clause_6_informative_text.adoc | 0 .../sections/clause_7_normative_text.adoc | 0 .../sections/clause_8_media_types.adoc | 0 {standard => docs}/workflows/docker.yml | 0 {standard => docs}/workflows/generate.yml | 0 50 files changed, 6 insertions(+), 8 deletions(-) rename {standard => docs}/.gitignore (100%) rename {standard => docs}/.gitlab-ci.yml (100%) rename {standard => docs}/Gemfile (100%) rename {standard => docs}/Makefile (100%) rename {standard => docs}/Makefile.win (100%) rename {standard => docs}/README.adoc (100%) rename {standard => docs}/UML/README.adoc (100%) rename {standard => docs}/abstract_tests/ATS_class_example1.adoc (100%) rename {standard => docs}/abstract_tests/ATS_test_example1.adoc (100%) rename {standard => docs}/abstract_tests/ATS_test_example2.adoc (100%) rename {standard => docs}/abstract_tests/README.adoc (100%) rename {standard => docs}/code/README.adoc (100%) rename {standard => docs}/figures/README.adoc (100%) rename {standard => docs}/images/README.adoc (100%) rename {standard => docs}/index.adoc (100%) rename {standard => docs}/metanorma.yml (100%) rename {standard => docs}/relaton/cache/iso/iso_19101_1_2014.xml (100%) rename {standard => docs}/relaton/cache/iso/iso_19115_1_2014.xml (100%) rename {standard => docs}/relaton/cache/iso/iso_19115_3.xml (100%) rename {standard => docs}/relaton/cache/iso/iso_19139_2007.notfound (100%) rename {standard => docs}/relaton/cache/iso/iso_19157_2013.xml (100%) rename {standard => docs}/relaton/cache/iso/version (100%) rename {standard => docs}/relaton/cache/ogc/06_121r9.xml (100%) rename {standard => docs}/relaton/cache/ogc/12_019.xml (100%) rename {standard => docs}/relaton/cache/ogc/14_005r3.xml (100%) rename {standard => docs}/relaton/cache/ogc/ogc_06_121r9.redirect (100%) rename {standard => docs}/relaton/cache/ogc/ogc_12_019.redirect (100%) rename {standard => docs}/relaton/cache/ogc/ogc_14_005r3.redirect (100%) rename {standard => docs}/relaton/cache/ogc/ogc_15_097.notfound (100%) rename {standard => docs}/relaton/cache/ogc/version (100%) rename {standard => docs}/requirements/README.adoc (100%) rename {standard => docs}/requirements/requirement001.adoc (100%) rename {standard => docs}/requirements/requirement002.adoc (100%) rename {standard => docs}/requirements/requirements_class.adoc (100%) rename {standard => docs}/sections/annex-a.adoc (100%) rename {standard => docs}/sections/annex-bibliography.adoc (100%) rename {standard => docs}/sections/annex-history.adoc (100%) rename {standard => docs}/sections/annex-n.adoc (100%) rename {standard => docs}/sections/clause_0_front_material.adoc (100%) rename {standard => docs}/sections/clause_1_scope.adoc (100%) rename {standard => docs}/sections/clause_2_conformance.adoc (100%) rename {standard => docs}/sections/clause_3_references.adoc (100%) rename {standard => docs}/sections/clause_4_terms_and_definitions.adoc (100%) rename {standard => docs}/sections/clause_5_conventions.adoc (100%) rename {standard => docs}/sections/clause_6_informative_text.adoc (100%) rename {standard => docs}/sections/clause_7_normative_text.adoc (100%) rename {standard => docs}/sections/clause_8_media_types.adoc (100%) rename {standard => docs}/workflows/docker.yml (100%) rename {standard => docs}/workflows/generate.yml (100%) diff --git a/.github/workflows/compile_doc.yml b/.github/workflows/compile_doc.yml index 467ccf6..7ffd4e2 100644 --- a/.github/workflows/compile_doc.yml +++ b/.github/workflows/compile_doc.yml @@ -14,12 +14,10 @@ jobs: path: main - name: Generate document run: | - cd main/standard + cd main/docs metanorma compile --agree-to-terms -t ogc -x xml,html,doc index.adoc - - - name: Archive production artifacts - uses: actions/upload-artifact@v3 - with: - name: dist - path: | - main/standard/index.** + git config --global user.name 'example' + git config --global user.email 'example@example.com' + git add --all + git commit -am "Compilation of HTML documents" + git push diff --git a/standard/.gitignore b/docs/.gitignore similarity index 100% rename from standard/.gitignore rename to docs/.gitignore diff --git a/standard/.gitlab-ci.yml b/docs/.gitlab-ci.yml similarity index 100% rename from standard/.gitlab-ci.yml rename to docs/.gitlab-ci.yml diff --git a/standard/Gemfile b/docs/Gemfile similarity index 100% rename from standard/Gemfile rename to docs/Gemfile diff --git a/standard/Makefile b/docs/Makefile similarity index 100% rename from standard/Makefile rename to docs/Makefile diff --git a/standard/Makefile.win b/docs/Makefile.win similarity index 100% rename from standard/Makefile.win rename to docs/Makefile.win diff --git a/standard/README.adoc b/docs/README.adoc similarity index 100% rename from standard/README.adoc rename to docs/README.adoc diff --git a/standard/UML/README.adoc b/docs/UML/README.adoc similarity index 100% rename from standard/UML/README.adoc rename to docs/UML/README.adoc diff --git a/standard/abstract_tests/ATS_class_example1.adoc b/docs/abstract_tests/ATS_class_example1.adoc similarity index 100% rename from standard/abstract_tests/ATS_class_example1.adoc rename to docs/abstract_tests/ATS_class_example1.adoc diff --git a/standard/abstract_tests/ATS_test_example1.adoc b/docs/abstract_tests/ATS_test_example1.adoc similarity index 100% rename from standard/abstract_tests/ATS_test_example1.adoc rename to docs/abstract_tests/ATS_test_example1.adoc diff --git a/standard/abstract_tests/ATS_test_example2.adoc b/docs/abstract_tests/ATS_test_example2.adoc similarity index 100% rename from standard/abstract_tests/ATS_test_example2.adoc rename to docs/abstract_tests/ATS_test_example2.adoc diff --git a/standard/abstract_tests/README.adoc b/docs/abstract_tests/README.adoc similarity index 100% rename from standard/abstract_tests/README.adoc rename to docs/abstract_tests/README.adoc diff --git a/standard/code/README.adoc b/docs/code/README.adoc similarity index 100% rename from standard/code/README.adoc rename to docs/code/README.adoc diff --git a/standard/figures/README.adoc b/docs/figures/README.adoc similarity index 100% rename from standard/figures/README.adoc rename to docs/figures/README.adoc diff --git a/standard/images/README.adoc b/docs/images/README.adoc similarity index 100% rename from standard/images/README.adoc rename to docs/images/README.adoc diff --git a/standard/index.adoc b/docs/index.adoc similarity index 100% rename from standard/index.adoc rename to docs/index.adoc diff --git a/standard/metanorma.yml b/docs/metanorma.yml similarity index 100% rename from standard/metanorma.yml rename to docs/metanorma.yml diff --git a/standard/relaton/cache/iso/iso_19101_1_2014.xml b/docs/relaton/cache/iso/iso_19101_1_2014.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19101_1_2014.xml rename to docs/relaton/cache/iso/iso_19101_1_2014.xml diff --git a/standard/relaton/cache/iso/iso_19115_1_2014.xml b/docs/relaton/cache/iso/iso_19115_1_2014.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19115_1_2014.xml rename to docs/relaton/cache/iso/iso_19115_1_2014.xml diff --git a/standard/relaton/cache/iso/iso_19115_3.xml b/docs/relaton/cache/iso/iso_19115_3.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19115_3.xml rename to docs/relaton/cache/iso/iso_19115_3.xml diff --git a/standard/relaton/cache/iso/iso_19139_2007.notfound b/docs/relaton/cache/iso/iso_19139_2007.notfound similarity index 100% rename from standard/relaton/cache/iso/iso_19139_2007.notfound rename to docs/relaton/cache/iso/iso_19139_2007.notfound diff --git a/standard/relaton/cache/iso/iso_19157_2013.xml b/docs/relaton/cache/iso/iso_19157_2013.xml similarity index 100% rename from standard/relaton/cache/iso/iso_19157_2013.xml rename to docs/relaton/cache/iso/iso_19157_2013.xml diff --git a/standard/relaton/cache/iso/version b/docs/relaton/cache/iso/version similarity index 100% rename from standard/relaton/cache/iso/version rename to docs/relaton/cache/iso/version diff --git a/standard/relaton/cache/ogc/06_121r9.xml b/docs/relaton/cache/ogc/06_121r9.xml similarity index 100% rename from standard/relaton/cache/ogc/06_121r9.xml rename to docs/relaton/cache/ogc/06_121r9.xml diff --git a/standard/relaton/cache/ogc/12_019.xml b/docs/relaton/cache/ogc/12_019.xml similarity index 100% rename from standard/relaton/cache/ogc/12_019.xml rename to docs/relaton/cache/ogc/12_019.xml diff --git a/standard/relaton/cache/ogc/14_005r3.xml b/docs/relaton/cache/ogc/14_005r3.xml similarity index 100% rename from standard/relaton/cache/ogc/14_005r3.xml rename to docs/relaton/cache/ogc/14_005r3.xml diff --git a/standard/relaton/cache/ogc/ogc_06_121r9.redirect b/docs/relaton/cache/ogc/ogc_06_121r9.redirect similarity index 100% rename from standard/relaton/cache/ogc/ogc_06_121r9.redirect rename to docs/relaton/cache/ogc/ogc_06_121r9.redirect diff --git a/standard/relaton/cache/ogc/ogc_12_019.redirect b/docs/relaton/cache/ogc/ogc_12_019.redirect similarity index 100% rename from standard/relaton/cache/ogc/ogc_12_019.redirect rename to docs/relaton/cache/ogc/ogc_12_019.redirect diff --git a/standard/relaton/cache/ogc/ogc_14_005r3.redirect b/docs/relaton/cache/ogc/ogc_14_005r3.redirect similarity index 100% rename from standard/relaton/cache/ogc/ogc_14_005r3.redirect rename to docs/relaton/cache/ogc/ogc_14_005r3.redirect diff --git a/standard/relaton/cache/ogc/ogc_15_097.notfound b/docs/relaton/cache/ogc/ogc_15_097.notfound similarity index 100% rename from standard/relaton/cache/ogc/ogc_15_097.notfound rename to docs/relaton/cache/ogc/ogc_15_097.notfound diff --git a/standard/relaton/cache/ogc/version b/docs/relaton/cache/ogc/version similarity index 100% rename from standard/relaton/cache/ogc/version rename to docs/relaton/cache/ogc/version diff --git a/standard/requirements/README.adoc b/docs/requirements/README.adoc similarity index 100% rename from standard/requirements/README.adoc rename to docs/requirements/README.adoc diff --git a/standard/requirements/requirement001.adoc b/docs/requirements/requirement001.adoc similarity index 100% rename from standard/requirements/requirement001.adoc rename to docs/requirements/requirement001.adoc diff --git a/standard/requirements/requirement002.adoc b/docs/requirements/requirement002.adoc similarity index 100% rename from standard/requirements/requirement002.adoc rename to docs/requirements/requirement002.adoc diff --git a/standard/requirements/requirements_class.adoc b/docs/requirements/requirements_class.adoc similarity index 100% rename from standard/requirements/requirements_class.adoc rename to docs/requirements/requirements_class.adoc diff --git a/standard/sections/annex-a.adoc b/docs/sections/annex-a.adoc similarity index 100% rename from standard/sections/annex-a.adoc rename to docs/sections/annex-a.adoc diff --git a/standard/sections/annex-bibliography.adoc b/docs/sections/annex-bibliography.adoc similarity index 100% rename from standard/sections/annex-bibliography.adoc rename to docs/sections/annex-bibliography.adoc diff --git a/standard/sections/annex-history.adoc b/docs/sections/annex-history.adoc similarity index 100% rename from standard/sections/annex-history.adoc rename to docs/sections/annex-history.adoc diff --git a/standard/sections/annex-n.adoc b/docs/sections/annex-n.adoc similarity index 100% rename from standard/sections/annex-n.adoc rename to docs/sections/annex-n.adoc diff --git a/standard/sections/clause_0_front_material.adoc b/docs/sections/clause_0_front_material.adoc similarity index 100% rename from standard/sections/clause_0_front_material.adoc rename to docs/sections/clause_0_front_material.adoc diff --git a/standard/sections/clause_1_scope.adoc b/docs/sections/clause_1_scope.adoc similarity index 100% rename from standard/sections/clause_1_scope.adoc rename to docs/sections/clause_1_scope.adoc diff --git a/standard/sections/clause_2_conformance.adoc b/docs/sections/clause_2_conformance.adoc similarity index 100% rename from standard/sections/clause_2_conformance.adoc rename to docs/sections/clause_2_conformance.adoc diff --git a/standard/sections/clause_3_references.adoc b/docs/sections/clause_3_references.adoc similarity index 100% rename from standard/sections/clause_3_references.adoc rename to docs/sections/clause_3_references.adoc diff --git a/standard/sections/clause_4_terms_and_definitions.adoc b/docs/sections/clause_4_terms_and_definitions.adoc similarity index 100% rename from standard/sections/clause_4_terms_and_definitions.adoc rename to docs/sections/clause_4_terms_and_definitions.adoc diff --git a/standard/sections/clause_5_conventions.adoc b/docs/sections/clause_5_conventions.adoc similarity index 100% rename from standard/sections/clause_5_conventions.adoc rename to docs/sections/clause_5_conventions.adoc diff --git a/standard/sections/clause_6_informative_text.adoc b/docs/sections/clause_6_informative_text.adoc similarity index 100% rename from standard/sections/clause_6_informative_text.adoc rename to docs/sections/clause_6_informative_text.adoc diff --git a/standard/sections/clause_7_normative_text.adoc b/docs/sections/clause_7_normative_text.adoc similarity index 100% rename from standard/sections/clause_7_normative_text.adoc rename to docs/sections/clause_7_normative_text.adoc diff --git a/standard/sections/clause_8_media_types.adoc b/docs/sections/clause_8_media_types.adoc similarity index 100% rename from standard/sections/clause_8_media_types.adoc rename to docs/sections/clause_8_media_types.adoc diff --git a/standard/workflows/docker.yml b/docs/workflows/docker.yml similarity index 100% rename from standard/workflows/docker.yml rename to docs/workflows/docker.yml diff --git a/standard/workflows/generate.yml b/docs/workflows/generate.yml similarity index 100% rename from standard/workflows/generate.yml rename to docs/workflows/generate.yml From d10889bc6ecb3013b48c7851b2eb269863637a18 Mon Sep 17 00:00:00 2001 From: example Date: Thu, 16 Mar 2023 16:15:40 +0000 Subject: [PATCH 14/18] Compilation of HTML documents --- docs/iev/cache/version | 1 + docs/index.doc | 3385 +++++++++++++++++++++++++++++++++++ docs/index.err | 149 ++ docs/index.html | 74 +- docs/index.presentation.xml | 971 ++++++++++ docs/index.xml | 513 ++++++ 6 files changed, 5056 insertions(+), 37 deletions(-) create mode 100644 docs/iev/cache/version create mode 100644 docs/index.doc create mode 100644 docs/index.err create mode 100644 docs/index.presentation.xml create mode 100644 docs/index.xml diff --git a/docs/iev/cache/version b/docs/iev/cache/version new file mode 100644 index 0000000..a2268e2 --- /dev/null +++ b/docs/iev/cache/version @@ -0,0 +1 @@ +0.3.1 \ No newline at end of file diff --git a/docs/index.doc b/docs/index.doc new file mode 100644 index 0000000..91741a3 --- /dev/null +++ b/docs/index.doc @@ -0,0 +1,3385 @@ +MIME-Version: 1.0 +Content-Type: multipart/related; boundary="----=_NextPart_76813f2d.4980.4528" + +------=_NextPart_76813f2d.4980.4528 +Content-ID: +Content-Disposition: inline; filename="index.htm" +Content-Type: text/html; charset="utf-8" + + + + + + +Print +100 + + + + + + + + +

+ + Open Geospatial Consortium + + + + + + +

+ +

+ Submission Date: 2029-03-30 +

 

+

+
+

+
+
+

License Agreement

+ + +

Use of this document is subject to the license agreement at + https://www.ogc.org/license

+
+
+ + +
+ +
+

Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/

+
+ +
+ +
+ +
+
+ +

Contents

+ +

 TOC \o "1-2" \h \z \u + +Copyright notice +. + + + PAGEREF _Toc740474489 \h + 1 +

+ +

+Note +. + + + PAGEREF _Toc200364577 \h + 1 +

+ +

+License Agreement +. + + + PAGEREF _Toc556883737 \h + 1 +

+ +

+Notice for Drafts +. + + + PAGEREF _Toc854942633 \h + 1 +

+ +

+I. Abstract +. + + + PAGEREF _Toc858615328 \h + 1 +

+ +

+II. Keywords +. + + + PAGEREF _Toc625251657 \h + 1 +

+ +

+III. Preface +. + + + PAGEREF _Toc809826198 \h + 1 +

+ +

+IV. Security considerations +. + + + PAGEREF _Toc258311618 \h + 1 +

+ +

+V. Submitting Organizations +. + + + PAGEREF _Toc765728328 \h + 1 +

+ +

+VI. Submitters +. + + + PAGEREF _Toc872902253 \h + 1 +

+ +

+1. Scope +. + + + PAGEREF _Toc730504638 \h + 1 +

+ +

+2. Conformance +. + + + PAGEREF _Toc935167211 \h + 1 +

+ +

+3. Normative references +. + + + PAGEREF _Toc153023762 \h + 1 +

+ +

+4. Terms and definitions +. + + + PAGEREF _Toc779668084 \h + 1 +

+ +

+5. Keywords +. + + + PAGEREF _Toc883396748 \h + 1 +

+ +

+6. Submitting organizations +. + + + PAGEREF _Toc574164226 \h + 1 +

+ +

+7. Contributors +. + + + PAGEREF _Toc305764257 \h + 1 +

+ +

+8. Conventions +. + + + PAGEREF _Toc720420944 \h + 1 +

+ +

+8.1. Identifiers +. + + + PAGEREF _Toc113839212 \h + 1 +

+ +

+9. Clauses not containing normative material +. + + + PAGEREF _Toc772005082 \h + 1 +

+ +

+9.1. Clauses not containing normative material sub-clause 1 +. + + + PAGEREF _Toc826142593 \h + 1 +

+ +

+9.2. Clauses not containing normative material sub-clause 2 +. + + + PAGEREF _Toc119030601 \h + 1 +

+ +

+10. Clause containing normative material +. + + + PAGEREF _Toc850418522 \h + 1 +

+ +

+10.1. Requirement Class A or Requirement A Example +. + + + PAGEREF _Toc622081566 \h + 1 +

+ +

+11. Media Types for any data encoding(s) +. + + + PAGEREF _Toc600747805 \h + 1 +

+ +

+Annex A (informative) Conformance Class Abstract Test Suite (Normative) +. + + + PAGEREF _Toc828939072 \h + 1 +

+ +

+A.1. Conformance Class A +. + + + PAGEREF _Toc868430590 \h + 1 +

+ +

+Annex B (informative) Title +. + + + PAGEREF _Toc963161365 \h + 1 +

+ +

+Annex C (informative) Revision History +. + + + PAGEREF _Toc867398826 \h + 1 +

+ +

+Bibliography +. + + + PAGEREF _Toc806464743 \h + 1 +

+ +

 

+ +
+
+

Copyright notice

+ + +

Copyright + © 2023 Open Geospatial Consortium
+ To obtain additional rights of use, visit + https://www.ogc.org/legal +

+
+

Note

+ +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+
+
+ + +
+ + +

Notice for Drafts

+ +

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

+ +

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

+
+ + + + + +
+ + + + + +


I.  Abstract

<Insert Abstract Text here>

II.  Keywords

The following are keywords to be used by search engines and + document catalogues.

ogcdoc, OGC document, API, openapi, html


III.  Preface

NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

IV.  Security considerations

No security considerations have been made for this Standard.

V.  Submitting Organizations

The following organizations submitted this Document to the + Open Geospatial Consortium (OGC):

Organization One

+

Organization Two

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

 

+

+
+

+
+

OGC Geoscience Markup Language

+
+ +

1.  Scope

+
+ +

NOTE  Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

+
+
+

2.  Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

AAAA +

+

BBBB +

+

Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site.

In order to conform to this OGC® interface standard, a software implementation shall choose to implement:

Any one of the conformance levels specified in Annex A (normative). +

+

Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative). +

+

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

+

3.  Normative references

+

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

+ + + + +

Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)

+

ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)

+

The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).

+

Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)

+

The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)

+

National Center for Biotechnology Information, http://www.ncbi.nlm.nih.gov

+

ISO: ISO 19101-1:2014, Geographic information — Reference model — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/59164.html.

+

ISO: ISO 19115-1:2014, Geographic information — Metadata — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/53798.html.

+

ISO: ISO 19157:2013, Geographic information  — Data quality. International Organization for Standardization, Geneva (2013). https://www.iso.org/standard/32575.html.

+

ISO: ISO 19139:2007, Geographic information — Metadata — XML schema implementation. ISO (2007).

+

ISO: ISO 19115-3, Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts. International Organization for Standardization, Geneva https://www.iso.org/standard/80874.html.

+

OGC Geospatial User Feedback Standard: Conceptual Model (2016)

+

Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele: OGC 12-019, OGC City Geography Markup Language (CityGML) Encoding Standard. Open Geospatial Consortium (2012). https://portal.ogc.org/files/?artifact id=47842.

+

Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker: OGC 14-005r3, OGC® IndoorGML. Open Geospatial Consortium (2014). https://docs.ogc.org/is/14-005r3/14-005r3.html.

+

Arliss Whiteside Jim Greenwood: OGC 06-121r9, OGC Web Service Common Implementation Specification. Open Geospatial Consortium (2010). https://portal.ogc.org/files/?artifact id=38867.

+
+

4.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1. example term

+

term used for exemplary purposes

+ + + + + + +

Note 1 to entry: An example note.

Example

Here’s an example of an example term.

+

[SOURCE: ISO 19101-1:2014]

+
+ +

5.  Keywords

+
+
+ +

6.  Submitting organizations

+
+
+ +

7.  Contributors

+

Additional contributors to this Standard include the following:

+

Individual name(s), Organization

+
+
+ +

8.  Conventions

+

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

+

8.1.  Identifiers

+ +

The normative provisions in this standard are denoted by the URI

+ +

http://www.opengis.net/spec/{standard}/{m.n}

+ +

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

+
+
+
+ +

9.  Clauses not containing normative material

+

Paragraph

+

9.1.  Clauses not containing normative material sub-clause 1

+ +

Paragraph

+
+

9.2.  Clauses not containing normative material sub-clause 2

+ +
+
+
+ +

10.  Clause containing normative material

+

Paragraph

+

10.1.  Requirement Class A or Requirement A Example

+ +

Paragraph – intro text for the requirement class.

+ +

Use the following table for Requirements Classes.

+ +

Requirements class 1

Obligationrequirement
Description

Requirements Class

http://www.example.org/req/blah +

+

urn:iso:ts:iso:19139:clause:6 +

+
Normative statementsRequirement 1-1
Requirement 1-2
+ +

10.1.1.  Requirement 1

+ +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 1

Obligationrequirement
Statement

Requirement ‘shall’ statement

+ +

Dictionary tables for requirements can be added as necessary. Modify the following example as needed.

+ +

Table 1

NamesDefinitionData types and valuesMultiplicity and use
name 1definition of name 1floatOne or more (mandatory)
name 2definition of name 2character string type, not emptyZero or one (optional)
name 3definition of name 3GML:: Point PropertyTypeOne (mandatory)
+
+ +

10.1.2.  Requirement 2

+ +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 2

Label/req/req-class-a/req-name-2
Conditions

The process input value is specified in-line in an execute request. +

+

The process input is defined as an object according to its schema. +

+ +
A

The server SHALL support process input values encoded as qualified values.

+
B

The value of the value key SHALL be an object instance.

+
+
+
+
+
+ +

11.  Media Types for any data encoding(s)

+

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in http://www.iana.org/assignments/media-types/index.html then this section may be used to define a new MIME type for registration with IANA.

+
+

+
+

+
+ +

Annex A
(informative)
Conformance Class Abstract Test Suite (Normative)

+
+ +

NOTE  Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

+
+

A.1.  Conformance Class A

+ +

Example

label

http://www.opengis.net/spec/name-of-standard/1.0/conf/example1

+

subject

Requirements Class “example1”

+

classification

Target Type:Web API

+
+
+ +

A.1.1.  Example 1

+ +

Abstract test A.1

Subject/req/req-class-a/req-name-1
Label/conf/core/api-definition-op
Test purpose

Validate that the API Definition document can be retrieved from the expected location.

+
Test method +

Construct a path for the API Definition document that ends with /api. +

+

Issue a HTTP GET request on that path +

+

Validate the contents of the returned document using test /conf/core/api-definition-success. +

+ + +
+
+ +

A.1.2.  Example 2

+ +

Abstract test A.2

Subject/req/req-class-a/req-name-2
Label/conf/core/http
Test purpose

Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

+
Test method +

All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively. +

+

For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol. +

+ +
+
+
+
+

+
+

+
+ +

Annex B
(informative)
Title

+
+ +

NOTE  Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography

+
+
+

+
+

+
+ +

Annex C
(informative)
Revision History

+

Table C.1

+
+ + + + + + + + + + + + + + + + + + + + +
DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version
+
+
+

+
+

+

Bibliography

+ +

NOTE  The TC has approved Springer LNCS as the official document citation type.

Springer LNCS is widely used in technical and computer science journals and other publications

– Actual References:

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

[n] Web: Author Surname, A.: Title, http://Website-Url

[1]  OGC: OGC Testbed 12 Annex B: Architecture (2015).

+ + +
+
+
+ + + + +------=_NextPart_76813f2d.4980.4528 +Content-ID: +Content-Disposition: inline; filename="filelist.xml" +Content-Transfer-Encoding: base64 +Content-Type: application/xml + +PHhtbCB4bWxuczpvPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiPgog +ICAgICAgIDxvOk1haW5GaWxlIEhSZWY9Ii4uLy9fX3cvT0dDLUdlb1NjaU1ML09HQy1HZW9TY2lN +TC9tYWluL2RvY3MvaW5kZXguaHRtIi8+ICA8bzpGaWxlIEhSZWY9ImZpbGVsaXN0LnhtbCIvPgog +IDxvOkZpbGUgSFJlZj0iaGVhZGVyLmh0bWwiLz4KPC94bWw+Cg== + +------=_NextPart_76813f2d.4980.4528 +Content-ID: +Content-Disposition: inline; filename="header.html" +Content-Transfer-Encoding: base64 +Content-Type: text/html charset="utf-8" + +PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiDQp4bWxuczpvPSJ1 +cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiDQp4bWxuczp3PSJ1cm46c2No +ZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIg0KeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMu +bWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIg0KeG1sbnM6bXY9Imh0dHA6Ly9tYWNW +bWxTY2hlbWFVcmkiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCg0K +PGhlYWQ+DQo8bWV0YSBuYW1lPVRpdGxlIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPUtleXdvcmRz +IGNvbnRlbnQ9IiI+DQo8bWV0YSBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZSBjb250ZW50PSJ0ZXh0 +L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1ldGEgbmFtZT1Qcm9nSWQgY29udGVudD1Xb3JkLkRv +Y3VtZW50Pg0KPG1ldGEgbmFtZT1HZW5lcmF0b3IgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUi +Pg0KPG1ldGEgbmFtZT1PcmlnaW5hdG9yIGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDE1Ij4NCjxs +aW5rIGlkPU1haW4tRmlsZSByZWw9TWFpbi1GaWxlIGhyZWY9Ii4uLy9fX3cvT0dDLUdlb1NjaU1M +L09HQy1HZW9TY2lNTC9tYWluL2RvY3MvaW5kZXguaHRtbCI+DQo8IS0tW2lmIGd0ZSBtc28gOV0+ +PHhtbD4NCiA8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIyMDQ5Ii8+DQo8 +L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCg0KPGJvZHkgbGFuZz1FTiBsaW5rPWJsdWUgdmxp +bms9IiM5NTRGNzIiPg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290bm90ZS1zZXBhcmF0 +b3InIGlkPWZzPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21hcmdpbi1ib3R0b206MGNt +O21hcmdpbi1ib3R0b206LjAwMDFwdDtsaW5lLWhlaWdodDoNCm5vcm1hbCc+PHNwYW4gbGFuZz1F +Ti1HQj48c3BhbiBzdHlsZT0nbXNvLXNwZWNpYWwtY2hhcmFjdGVyOmZvb3Rub3RlLXNlcGFyYXRv +cic+PCFbaWYgIXN1cHBvcnRGb290bm90ZXNdPg0KDQo8aHIgYWxpZ249bGVmdCBzaXplPTEgd2lk +dGg9IjMzJSI+DQoNCjwhW2VuZGlmXT48L3NwYW4+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxk +aXYgc3R5bGU9J21zby1lbGVtZW50OmZvb3Rub3RlLWNvbnRpbnVhdGlvbi1zZXBhcmF0b3InIGlk +PWZjcz4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjBjbTttYXJn +aW4tYm90dG9tOi4wMDAxcHQ7bGluZS1oZWlnaHQ6DQpub3JtYWwnPjxzcGFuIGxhbmc9RU4tR0I+ +PHNwYW4gc3R5bGU9J21zby1zcGVjaWFsLWNoYXJhY3Rlcjpmb290bm90ZS1jb250aW51YXRpb24t +c2VwYXJhdG9yJz48IVtpZiAhc3VwcG9ydEZvb3Rub3Rlc10+DQoNCjxociBhbGlnbj1sZWZ0IHNp +emU9MT4NCg0KPCFbZW5kaWZdPjwvc3Bhbj48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdiBz +dHlsZT0nbXNvLWVsZW1lbnQ6ZW5kbm90ZS1zZXBhcmF0b3InIGlkPWVzPg0KDQo8cCBjbGFzcz1N +c29Ob3JtYWwgc3R5bGU9J21hcmdpbi1ib3R0b206MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDts +aW5lLWhlaWdodDoNCm5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQj48c3BhbiBzdHlsZT0nbXNvLXNw +ZWNpYWwtY2hhcmFjdGVyOmZvb3Rub3RlLXNlcGFyYXRvcic+PCFbaWYgIXN1cHBvcnRGb290bm90 +ZXNdPg0KDQo8aHIgYWxpZ249bGVmdCBzaXplPTEgd2lkdGg9IjMzJSI+DQoNCjwhW2VuZGlmXT48 +L3NwYW4+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmVu +ZG5vdGUtY29udGludWF0aW9uLXNlcGFyYXRvcicgaWQ9ZWNzPg0KDQo8cCBjbGFzcz1Nc29Ob3Jt +YWwgc3R5bGU9J21hcmdpbi1ib3R0b206MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtsaW5lLWhl +aWdodDoNCm5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQj48c3BhbiBzdHlsZT0nbXNvLXNwZWNpYWwt +Y2hhcmFjdGVyOmZvb3Rub3RlLWNvbnRpbnVhdGlvbi1zZXBhcmF0b3InPjwhW2lmICFzdXBwb3J0 +Rm9vdG5vdGVzXT4NCg0KPGhyIGFsaWduPWxlZnQgc2l6ZT0xPg0KDQo8IVtlbmRpZl0+PC9zcGFu +Pjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpoZWFkZXIn +IGlkPWVoMT4NCg0KPHAgY2xhc3M9TXNvSGVhZGVyIGFsaWduPWxlZnQgc3R5bGU9J3RleHQtYWxp +Z246bGVmdDtsaW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5 +Jz48c3BhbiBsYW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7WVktOTk5 +PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicg +aWQ9aDE+DQoNCjxwIGNsYXNzPU1zb0hlYWRlciBzdHlsZT0nbWFyZ2luLWJvdHRvbToxOC4wcHQn +PjxzcGFuIGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQt +c2l6ZToxMS4wcHQ7Zm9udC13ZWlnaHQ6bm9ybWFsJz4NCk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0 +aXVtJm5ic3A7WVktOTk5PC9zcGFuPjxzcGFuIGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXdlaWdo +dDpub3JtYWwnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9 +J21zby1lbGVtZW50OmZvb3RlcicgaWQ9ZWYxPg0KDQo8cCBjbGFzcz1Nc29Gb290ZXIgc3R5bGU9 +J21hcmdpbi10b3A6MTIuMHB0O2xpbmUtaGVpZ2h0OjEyLjBwdDttc28tbGluZS1oZWlnaHQtcnVs +ZToNCmV4YWN0bHknPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PGIgc3R5bGU9J21zby1iaWRpLWZv +bnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4w +cHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4NCnN0eWxlPSdtc28tZWxlbWVudDpm +aWVsZC1iZWdpbic+PC9zcGFuPjxzcGFuDQpzdHlsZT0nbXNvLXNwYWNlcnVuOnllcyc+wqA8L3Nw +YW4+UEFHRTxzcGFuIHN0eWxlPSdtc28tc3BhY2VydW46eWVzJz7CoMKgDQo8L3NwYW4+XCogTUVS +R0VGT1JNQVQgPHNwYW4gc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLXNlcGFyYXRvcic+PC9zcGFu +Pjwvc3Bhbj48L2I+PCFbZW5kaWZdLS0+PGINCnN0eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDpu +b3JtYWwnPjxzcGFuIGxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7DQptc28tYmlk +aS1mb250LXNpemU6MTEuMHB0Jz48c3BhbiBzdHlsZT0nbXNvLW5vLXByb29mOnllcyc+Mjwvc3Bh +bj48L3NwYW4+PC9iPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PGINCnN0eWxlPSdtc28tYmlkaS1m +b250LXdlaWdodDpub3JtYWwnPjxzcGFuIGxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4w +cHQ7DQptc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3BhbiBzdHlsZT0nbXNvLWVsZW1lbnQ6 +ZmllbGQtZW5kJz48L3NwYW4+PC9zcGFuPjwvYj48IVtlbmRpZl0tLT48c3Bhbg0KbGFuZz1FTi1H +QiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3Bh +bg0Kc3R5bGU9J21zby10YWItY291bnQ6MSc+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8L3NwYW4+wqkgT3BlbiBHZW9zcGF0aWFsIENvbnNv +cnRpdW0mbmJzcDsyMDIzIOKAkyBBbGwgcmlnaHRzIHJlc2VydmVkPG86cD48L286cD48L3NwYW4+ +PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6aGVhZGVyJyBpZD1laDI+ +DQo8cCBjbGFzcz1Nc29IZWFkZXIgYWxpZ249bGVmdCBzdHlsZT0ndGV4dC1hbGlnbjpsZWZ0O2xp +bmUtaGVpZ2h0OjEyLjBwdDsNCm1zby1saW5lLWhlaWdodC1ydWxlOmV4YWN0bHknPjxzcGFuIGxh +bmc9RU4tR0I+T3BlbiBHZW9zcGF0aWFsIENvbnNvcnRpdW0mbmJzcDtZWS05OTk8L3NwYW4+PC9w +Pg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicgaWQ9ZWgybD4NCjxw +IGNsYXNzPU1zb0hlYWRlckxhbmRzY2FwZSBhbGlnbj1sZWZ0IHN0eWxlPSd0ZXh0LWFsaWduOmxl +ZnQ7bGluZS1oZWlnaHQ6MTIuMHB0Ow0KbXNvLWxpbmUtaGVpZ2h0LXJ1bGU6ZXhhY3RseSc+PHNw +YW4gbGFuZz1FTi1HQj5PcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwO1lZLTk5OTwvc3Bh +bj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6aGVhZGVyJyBpZD1oMj4N +CjxwIGNsYXNzPU1zb0hlYWRlciBhbGlnbj1yaWdodCBzdHlsZT0ndGV4dC1hbGlnbjpyaWdodDts +aW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48c3BhbiBs +YW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7WVktOTk5PC9zcGFuPjwv +cD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpoZWFkZXInIGlkPWgybD4NCjxw +IGNsYXNzPU1zb0hlYWRlckxhbmRzY2FwZSBhbGlnbj1yaWdodCBzdHlsZT0ndGV4dC1hbGlnbjpy +aWdodDtsaW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48 +c3BhbiBsYW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7WVktOTk5PC9z +cGFuPjwvcD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWVm +Mj4NCjxwIGNsYXNzPU1zb0Zvb3RlciBzdHlsZT0nbGluZS1oZWlnaHQ6MTIuMHB0O21zby1saW5l +LWhlaWdodC1ydWxlOmV4YWN0bHknPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9 +RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+ +PHNwYW4NCnN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1iZWdpbic+PC9zcGFuPjxzcGFuDQpzdHls +ZT0nbXNvLXNwYWNlcnVuOnllcyc+wqA8L3NwYW4+UEFHRTxzcGFuIHN0eWxlPSdtc28tc3BhY2Vy +dW46eWVzJz7CoMKgDQo8L3NwYW4+XCogTUVSR0VGT1JNQVQgPHNwYW4gc3R5bGU9J21zby1lbGVt +ZW50OmZpZWxkLXNlcGFyYXRvcic+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0tLT48c3Bhbg0KbGFu +Zz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0 +Jz48c3Bhbg0Kc3R5bGU9J21zby1uby1wcm9vZjp5ZXMnPmlpPC9zcGFuPjwvc3Bhbj48IS0tW2lm +IHN1cHBvcnRGaWVsZHNdPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0 +O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6Zmll +bGQtZW5kJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuIGxhbmc9RU4tR0INCnN0eWxl +PSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIA0Kc3R5 +bGU9J21zby10YWItY291bnQ6MSc+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoCA8L3NwYW4+wqkgT3BlbiBHZW9zcGF0aWFsIENvbnNvcnRpdW0m +bmJzcDsyMDIzJm5ic3A74oCTIEFsbCByaWdodHMgcmVzZXJ2ZWQ8bzpwPjwvbzpwPjwvc3Bhbj48 +L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWVmMmw+ +DQo8cCBjbGFzcz1Nc29Gb290ZXJMYW5kc2NhcGUgc3R5bGU9J2xpbmUtaGVpZ2h0OjEyLjBwdDtt +c28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxzcGFu +DQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZTox +MS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtYmVnaW4nPjwvc3Bhbj48c3Bh +bg0Kc3R5bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgPC9zcGFuPlBBR0U8c3BhbiBzdHlsZT0nbXNv +LXNwYWNlcnVuOnllcyc+wqDCoA0KPC9zcGFuPlwqIE1FUkdFRk9STUFUIDxzcGFuIHN0eWxlPSdt +c28tZWxlbWVudDpmaWVsZC1zZXBhcmF0b3InPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdLS0+PHNw +YW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXpl +OjExLjBwdCc+PHNwYW4NCnN0eWxlPSdtc28tbm8tcHJvb2Y6eWVzJz5paTwvc3Bhbj48L3NwYW4+ +PCEtLVtpZiBzdXBwb3J0RmllbGRzXT48c3Bhbg0KbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXpl +OjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3Bhbg0Kc3R5bGU9J21zby1lbGVt +ZW50OmZpZWxkLWVuZCc+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0tLT48c3BhbiBsYW5nPUVOLUdC +DQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3Bh +biANCnN0eWxlPSdtc28tdGFiLWNvdW50OjEnPsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPC9zcGFuPsKpIE9wZW4gR2Vvc3BhdGlhbCBDb25z +b3J0aXVtJm5ic3A7MjAyMyZuYnNwO+KAkyBBbGwgcmlnaHRzIHJlc2VydmVkPG86cD48L286cD48 +L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6Zm9vdGVyJyBp +ZD1mMj4NCjxwIGNsYXNzPU1zb0Zvb3RlciBzdHlsZT0nbGluZS1oZWlnaHQ6MTIuMHB0Jz48c3Bh +biBsYW5nPUVOLUdCDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6 +MTEuMHB0Jz7CqSBPcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwOzIwMjMmbmJzcDvigJMg +QWxsDQpyaWdodHMgcmVzZXJ2ZWQ8c3BhbiBzdHlsZT0nbXNvLXRhYi1jb3VudDoxJz7CoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8L3NwYW4+PC9z +cGFuPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQt +c2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4NCnN0eWxlPSdtc28t +ZWxlbWVudDpmaWVsZC1iZWdpbic+PC9zcGFuPiBQQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1 +bjp5ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBzdHlsZT0nbXNvLWVsZW1l +bnQ6ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuDQpsYW5n +PUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQn +PjxzcGFuDQpzdHlsZT0nbXNvLW5vLXByb29mOnllcyc+aWlpPC9zcGFuPjwvc3Bhbj48IS0tW2lm +IHN1cHBvcnRGaWVsZHNdPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0 +O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6Zmll +bGQtZW5kJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuIGxhbmc9RU4tR0INCnN0eWxl +PSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxvOnA+PC9vOnA+ +PC9zcGFuPjwvcD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlk +PWYybD4NCjxwIGNsYXNzPU1zb0Zvb3RlckxhbmRzY2FwZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTIu +MHB0Jz48c3BhbiBsYW5nPUVOLUdCDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1m +b250LXNpemU6MTEuMHB0Jz7CqSBPcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwOzIwMjMm +bmJzcDvigJMgQWxsDQpyaWdodHMgcmVzZXJ2ZWQ8c3BhbiBzdHlsZT0nbXNvLXRhYi1jb3VudDox +Jz7CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8 +L3NwYW4+PC9zcGFuPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9RU4tR0Igc3R5 +bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4NCnN0 +eWxlPSdtc28tZWxlbWVudDpmaWVsZC1iZWdpbic+PC9zcGFuPiBQQUdFPHNwYW4gc3R5bGU9J21z +by1zcGFjZXJ1bjp5ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBzdHlsZT0n +bXNvLWVsZW1lbnQ6ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxz +cGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6 +ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLW5vLXByb29mOnllcyc+aWlpPC9zcGFuPjwvc3Bh +bj48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNp +emU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLWVs +ZW1lbnQ6ZmllbGQtZW5kJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuIGxhbmc9RU4t +R0INCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxv +OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpm +b290ZXInIGlkPWVmMz4NCjxwIGNsYXNzPU1zb0Zvb3RlciBzdHlsZT0nbWFyZ2luLXRvcDoxMi4w +cHQ7bGluZS1oZWlnaHQ6MTIuMHB0O21zby1saW5lLWhlaWdodC1ydWxlOg0KZXhhY3RseSc+PCEt +LVtpZiBzdXBwb3J0RmllbGRzXT48YiBzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFs +Jz48c3Bhbg0KbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250 +LXNpemU6MTEuMHB0Jz48c3Bhbg0Kc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWJlZ2luJz48L3Nw +YW4+PHNwYW4NCnN0eWxlPSdtc28tc3BhY2VydW46eWVzJz7CoDwvc3Bhbj5QQUdFPHNwYW4gc3R5 +bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBz +dHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwvYj48IVtl +bmRpZl0tLT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFu +Zz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4w +cHQnPjxzcGFuIHN0eWxlPSdtc28tbm8tcHJvb2Y6eWVzJz4yPC9zcGFuPjwvc3Bhbj48L2I+PCEt +LVtpZiBzdXBwb3J0RmllbGRzXT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1h +bCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZv +bnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bh +bj48L3NwYW4+PC9iPjwhW2VuZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNp +emU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLXRh +Yi1jb3VudDoxJz7CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgIDwvc3Bhbj7CqSBPcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwOzIwMjMm +bmJzcDvigJMgQWxsIHJpZ2h0cyByZXNlcnZlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9k +aXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmZvb3RlcicgaWQ9ZWYzbD4NCjxwIGNsYXNz +PU1zb0Zvb3RlckxhbmRzY2FwZSBzdHlsZT0nbWFyZ2luLXRvcDoxMi4wcHQ7bGluZS1oZWlnaHQ6 +MTIuMHB0O21zby1saW5lLWhlaWdodC1ydWxlOg0KZXhhY3RseSc+PCEtLVtpZiBzdXBwb3J0Rmll +bGRzXT48YiBzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3Bhbg0KbGFuZz1F +Ti1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48 +c3Bhbg0Kc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWJlZ2luJz48L3NwYW4+PHNwYW4NCnN0eWxl +PSdtc28tc3BhY2VydW46eWVzJz7CoDwvc3Bhbj5QQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1 +bjp5ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBzdHlsZT0nbXNvLWVsZW1l +bnQ6ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwvYj48IVtlbmRpZl0tLT48Yg0Kc3R5 +bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0n +Zm9udC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxl +PSdtc28tbm8tcHJvb2Y6eWVzJz4yPC9zcGFuPjwvc3Bhbj48L2I+PCEtLVtpZiBzdXBwb3J0Rmll +bGRzXT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1F +Ti1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQn +PjxzcGFuIHN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bhbj48L3NwYW4+PC9iPjwh +W2VuZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1i +aWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLXRhYi1jb3VudDoxJz7CoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDwvc3Bh +bj7CqSBPcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwOzIwMjMmbmJzcDvigJMgQWxsIHJp +Z2h0cyByZXNlcnZlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXYgc3R5 +bGU9J21zby1lbGVtZW50OmZvb3RlcicgaWQ9ZjM+DQo8cCBjbGFzcz1Nc29Gb290ZXIgc3R5bGU9 +J2xpbmUtaGVpZ2h0OjEyLjBwdCc+PHNwYW4gbGFuZz1FTi1HQg0Kc3R5bGU9J2ZvbnQtc2l6ZTox +MC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+wqkgT3BlbiBHZW9zcGF0aWFsIENvbnNv +cnRpdW0mbmJzcDsyMDIzJm5ic3A74oCTIEFsbA0KcmlnaHRzIHJlc2VydmVkPHNwYW4gc3R5bGU9 +J21zby10YWItY291bnQ6MSc+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoCA8L3NwYW4+PC9zcGFuPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PGIN +CnN0eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDpub3JtYWwnPjxzcGFuIGxhbmc9RU4tR0Igc3R5 +bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7DQptc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3BhbiBz +dHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtYmVnaW4nPjwvc3Bhbj4NClBBR0U8c3BhbiBzdHlsZT0n +bXNvLXNwYWNlcnVuOnllcyc+wqDCoCA8L3NwYW4+XCogTUVSR0VGT1JNQVQgPHNwYW4NCnN0eWxl +PSdtc28tZWxlbWVudDpmaWVsZC1zZXBhcmF0b3InPjwvc3Bhbj48L3NwYW4+PC9iPjwhW2VuZGlm +XS0tPjxiDQpzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3BhbiBsYW5nPUVO +LUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KbXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+ +PHNwYW4gc3R5bGU9J21zby1uby1wcm9vZjp5ZXMnPjM8L3NwYW4+PC9zcGFuPjwvYj48IS0tW2lm +IHN1cHBvcnRGaWVsZHNdPjxiDQpzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48 +c3BhbiBsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KbXNvLWJpZGktZm9udC1z +aXplOjExLjBwdCc+PHNwYW4gc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWVuZCc+PC9zcGFuPjwv +c3Bhbj48L2I+PCFbZW5kaWZdLS0+PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZTox +MC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PG86cD48L286cD48L3NwYW4+PC9wPg0K +PC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmZvb3RlcicgaWQ9ZjNsPg0KPHAgY2xh +c3M9TXNvRm9vdGVyTGFuZHNjYXBlIHN0eWxlPSdsaW5lLWhlaWdodDoxMi4wcHQnPjxzcGFuIGxh +bmc9RU4tR0INCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4w +cHQnPsKpIE9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7MjAyMyZuYnNwO+KAkyBBbGwN +CnJpZ2h0cyByZXNlcnZlZDxzcGFuIHN0eWxlPSdtc28tdGFiLWNvdW50OjEnPsKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPC9zcGFuPjwvc3Bh +bj48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxiDQpzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6 +bm9ybWFsJz48c3BhbiBsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KbXNvLWJp +ZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4gc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWJlZ2lu +Jz48L3NwYW4+DQpQQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgwqAgPC9zcGFu +PlwqIE1FUkdFRk9STUFUIDxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtc2VwYXJhdG9y +Jz48L3NwYW4+PC9zcGFuPjwvYj48IVtlbmRpZl0tLT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQt +d2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsN +Cm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxlPSdtc28tbm8tcHJvb2Y6eWVz +Jz4zPC9zcGFuPjwvc3Bhbj48L2I+PCEtLVtpZiBzdXBwb3J0RmllbGRzXT48Yg0Kc3R5bGU9J21z +by1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1z +aXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxlPSdtc28t +ZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bhbj48L3NwYW4+PC9iPjwhW2VuZGlmXS0tPjxzcGFuDQps +YW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4w +cHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KDQo8L2JvZHk+DQoNCjwvaHRtbD4N +Cg== + +------=_NextPart_76813f2d.4980.4528-- \ No newline at end of file diff --git a/docs/index.err b/docs/index.err new file mode 100644 index 0000000..997af85 --- /dev/null +++ b/docs/index.err @@ -0,0 +1,149 @@ +./index.err errors + + +== Document Attributes + +(): 'Interface' is not a permitted subtype of Standard: reverting to 'implementation' +(): draft is not an allowed status for standard + + +== AsciiDoc Input + +(Section: Bibliography): no anchor on reference, markup may be malformed: see +https://www.metanorma.com/author/topics/document-format/bibliography/ , +https://www.metanorma.com/author/iso/topics/markup/#bibliographies +: For citations in the text please use square brackets and consecutive numbers: [1], [2], [3] + # + + +== Anchors + +(XML Line 000241): Crossreference target OGC06-121r9 is undefined + +(XML Line 000299): normalised identifier in from http://www.opengis.net/spec/ABCD/m.n/req/req-class-a +

Requirements Class

  • +
    • +

  • urn:iso:ts:iso:19139:clause:6

    +
    • +
+(XML Line 000318): normalised identifier in from /req/req-class-a/req-name-1 +

Requirement ‘shall’ statement

 + +(XML Line 000410): Crossreference target ats_core_api-definition-success is undefined + /conf/core/api-definition-success +(XML Line 000429): Crossreference target rfc2818 is undefined + HTTP over TLS + + +== Style + +(): Prefatory material must be followed by (clause) Scope +(): Scope must be followed by Conformance +(): Normative References must be followed by Terms and Definitions + + +== Metanorma XML Style Warning + +(XML Line 000054): Table should have title + + + +
NameAffiliation
+(XML Line 000261): Hanging paragraph in clause + + Conventions +

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

+ + +(XML Line 000275): Hanging paragraph in clause + + Clauses not containing normative material +

Paragraph

+ + +(XML Line 000289): Hanging paragraph in clause + + Clause containing normative material +

Paragraph

+ + +(XML Line 000293): Hanging paragraph in clause + + Requirement Class A or Requirement A Example +

Paragraph – intro text for the requirement class.

+ +

Use the following table for Requirements Classes.

+(XML Line 000323): Table should have title + + + + + +(XML Line 000374): Hanging paragraph in clause + + Conformance Class Abstract Test Suite (Normative) +

Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

+ + +(XML Line 000379): Hanging paragraph in clause + + Conformance Class A +
label
+

+
+(XML Line 000443): Table should have title +
NamesDefinitionData types and valuesMultiplicity and use
+ + + + + + +== Requirements + +(XML Line 000299): Requirement class http___www.opengis.net_spec_ABCD_m.n_req_req-class-a has no corresponding Conformance class +

Requirements Class

  • +
    • +

  • urn:iso:ts:iso:19139:clause:6

    +
    • +
+(XML Line 000318): Requirement _req_req-class-a_req-name-1 has no corresponding Conformance test +

Requirement ‘shall’ statement

 + +(XML Line 000350): Requirement req_core_process-execute-input-inline-object has no corresponding Conformance test + label/req/req-class-a/req-name-2 + +

  1. The process input value is specified in-line in an execute request.

    +
    2. +

  2. The process input is defined as an object according to its schema.

    +(XML Line 000395): Conformance test ats_core_api-definition-op has no corresponding Requirement + /req/req-class-a/req-name-1label/conf/core/api-definition-op

    Validate that the API Definition document can be retrieved from the expected location.

    +     + +

    Construct a path for the API Definition document that ends with /api.

    +     +(XML Line 000395): Conformance test ats_core_api-definition-op has no corresponding Conformance class + /req/req-class-a/req-name-1label/conf/core/api-definition-op

    Validate that the API Definition document can be retrieved from the expected location.

    +     + +

    Construct a path for the API Definition document that ends with /api.

    +     +(XML Line 000416): Conformance test ats_core_http has no corresponding Requirement + /req/req-class-a/req-name-2label/conf/core/http

    Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

    +     + +

    All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

    +     +(XML Line 000416): Conformance test ats_core_http has no corresponding Conformance class + /req/req-class-a/req-name-2label/conf/core/http

    Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

    +     + +

    All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

    +     + + +== Metanorma XML Syntax + +(XML Line 000082:91): element "clause" not allowed here; expected the element end-tag or element "submitters" +(XML Line 000099:50): element "foreword" not allowed here; expected the element end-tag or element "clause", "definitions", "floating-title" or "terms" +(XML Line 000301:91): attribute "metadata" not allowed here; expected attribute "columns", "keep-lines-together", "keep-with-next", "key", "multilingual-rendering" or "tag" diff --git a/docs/index.html b/docs/index.html index 0abb3e2..09a52b2 100644 --- a/docs/index.html +++ b/docs/index.html @@ -1436,32 +1436,32 @@ @@ -1477,10 +1477,10 @@

    Contents

    -

    I.  Abstract

    <Insert Abstract Text here>

    II.  Keywords

    The following are keywords to be used by search engines and - document catalogues.

    ogcdoc, OGC document, API, openapi, html


    III.  Preface

    NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

    Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

    Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

    IV.  Security considerations

    No security considerations have been made for this Standard.

    V.  Submitting Organizations

    The following organizations submitted this Document to the +


    I.  Abstract

    <Insert Abstract Text here>

    II.  Keywords

    The following are keywords to be used by search engines and + document catalogues.

    ogcdoc, OGC document, API, openapi, html


    III.  Preface

    NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

    Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

    Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

    IV.  Security considerations

    No security considerations have been made for this Standard.

    V.  Submitting Organizations

    The following organizations submitted this Document to the Open Geospatial Consortium (OGC):

    • Organization One
      • -
    • Organization Two

    VI.  Submitters

    All questions regarding this submission should be directed to the editor or the submitters:

DateReleaseEditorPrimary clauses modifiedDescription
NameAffiliation

OGC Geoscience Markup Language

1.  Scope

NOTE  Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

2.  Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

  • AAAA

    +
  • Organization Two

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

OGC Geoscience Markup Language

1.  Scope

NOTE  Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

2.  Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

  • AAAA

  • BBBB

    • @@ -1488,7 +1488,7 @@

    Contents

  • Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative).

    • -

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

3.  Normative references

+

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

3.  Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

@@ -1509,7 +1509,7 @@

Contents

Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele: OGC 12-019, OGC City Geography Markup Language (CityGML) Encoding Standard. Open Geospatial Consortium (2012). https://portal.ogc.org/files/?artifact id=47842.

Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker: OGC 14-005r3, OGC® IndoorGML. Open Geospatial Consortium (2014). https://docs.ogc.org/is/14-005r3/14-005r3.html.

Arliss Whiteside Jim Greenwood: OGC 06-121r9, OGC Web Service Common Implementation Specification. Open Geospatial Consortium (2010). https://portal.ogc.org/files/?artifact id=38867.

-

4.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1. example term

+

4.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1. example term

term used for exemplary purposes

@@ -1518,19 +1518,19 @@

Contents

Note 1 to entry: An example note.

Example

Here’s an example of an example term.

-

[SOURCE: ISO 19101-1:2014]

5.  Keywords

6.  Submitting organizations

7.  Contributors

Additional contributors to this Standard include the following:

Individual name(s), Organization

8.  Conventions

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

8.1.  Identifiers

+

[SOURCE: ISO 19101-1:2014]

5.  Keywords

6.  Submitting organizations

7.  Contributors

Additional contributors to this Standard include the following:

Individual name(s), Organization

8.  Conventions

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

8.1.  Identifiers

The normative provisions in this standard are denoted by the URI

http://www.opengis.net/spec/{standard}/{m.n}

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

-

9.  Clauses not containing normative material

Paragraph

9.1.  Clauses not containing normative material sub-clause 1

+

9.  Clauses not containing normative material

Paragraph

9.1.  Clauses not containing normative material sub-clause 1

Paragraph

-

9.2.  Clauses not containing normative material sub-clause 2

+

9.2.  Clauses not containing normative material sub-clause 2

-

10.  Clause containing normative material

Paragraph

10.1.  Requirement Class A or Requirement A Example

+

10.  Clause containing normative material

Paragraph

10.1.  Requirement Class A or Requirement A Example

Paragraph – intro text for the requirement class.

@@ -1570,7 +1570,7 @@

Contents

B

The value of the value key SHALL be an object instance.

-

11.  Media Types for any data encoding(s)

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in http://www.iana.org/assignments/media-types/index.html then this section may be used to define a new MIME type for registration with IANA.


Annex A
(informative)
Conformance Class Abstract Test Suite (Normative)

NOTE  Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

A.1.  Conformance Class A

+

11.  Media Types for any data encoding(s)

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in http://www.iana.org/assignments/media-types/index.html then this section may be used to define a new MIME type for registration with IANA.


Annex A
(informative)
Conformance Class Abstract Test Suite (Normative)

NOTE  Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

A.1.  Conformance Class A

Example

label

http://www.opengis.net/spec/name-of-standard/1.0/conf/example1

subject

Requirements Class “example1”

@@ -1604,7 +1604,7 @@

Contents

-

Annex B
(informative)
Title

NOTE  Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography


Annex C
(informative)
Revision History

Table C.1

DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version

Bibliography

+

Annex B
(informative)
Title

NOTE  Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography


Annex C
(informative)
Revision History

Table C.1

DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version

Bibliography

NOTE  The TC has approved Springer LNCS as the official document citation type.

Springer LNCS is widely used in technical and computer science journals and other publications

– Actual References:

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

[n] Web: Author Surname, A.: Title, http://Website-Url

[1]  OGC: OGC Testbed 12 Annex B: Architecture (2015).

diff --git a/docs/index.presentation.xml b/docs/index.presentation.xml new file mode 100644 index 0000000..50d8049 --- /dev/null +++ b/docs/index.presentation.xml @@ -0,0 +1,971 @@ + + + +OGC Geoscience Markup Language +./document.xml./document.pdf./document.dochttp://www.opengis.net/doc/{doc-type}/{standard}/{m.n}YY-999YY-9992029-03-302029-03-302029-03-30 +Organization One + +Organization Two + +Edward Lewis + +Editor Two + +Open Geospatial Consortium +1.04.1.1en

<Insert Abstract Text here>

+draftDraft2023 +Open Geospatial Consortium +ogcdocOGC documentAPIopenapihtmlstandardimplementationtechnicalScopeSymbols and abbreviated termsAbbreviated termsSymbolsTable of contentsIntroductionPrefaceAbstractAcknowledgementsTerms and definitionsTerms, definitions, symbols and abbreviated termsTerms, definitions and symbolsTerms, definitions and abbreviated termsNormative referencesBibliographyPrefaceClauseAnnexAppendix

No terms and definitions are listed in this document.

+

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

+

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the 'ModSpec'. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

+

For the purposes of this document, the following additional terms and definitions apply.

+The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.There are no normative references in this document.

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

+

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the 'ModSpec'. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

+

For the purposes of this document, the terms and definitions given in % additionally apply.

+

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

+

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the 'ModSpec'. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

+

For the purposes of this document, the terms and definitions given in % and the following additionally apply.

+(%)%1 and %2%1, and %2%1 or %2%1, or %2%1 and %2%1 or %2%1 from %2%1 to %2spellout-ordinalNOTENoteNote % to entryListDefinition ListFigureDiagramFormulaFormulaTableRequirementRecommendationPermissionBoxRecommendation testRequirement testPermission testRecommendations classRequirements classPermissions classAbstract testConformance classKeyExampleExamplewherewhereWhole of textdraftinformativenormativemodifiedDEPRECATEDSOURCEandAll Parts%Spellout editioneditionversionList of figuresList of tablesList of recommendationsJanuaryFebruaryMarchAprilMayJuneJulyAugustSeptemberOctoberNovemberDecemberObligationDangerWarningCautionImportantSafety PrecautionsEditorial NoteSectionClausePartParagraphChapterPageTableAnnexFigureExampleNoteFormulamfncommonsgdualplpreppartadjadvnounverbdeprecatessupersedesnarrowerbroaderequivalentcomparecontrastseesee alsoClauseClausesAnnexAnnexesAppendixAppendixesNoteNotesNote % to entryNotes % to entryListListsFigureFiguresFormulaFormulasTableTablesRequirementRequirementsRecommendationRecommendationsPermissionPermissionsExampleExamplesPartPartsSectionSectionsParagraphParagraphsChapterChaptersPagePagesADMITTEDSubmittersNo security considerations have been made for this document.DraftWork Item DraftCandidate SWG DraftCandidate OAB Review DraftCandidate Public RFC DraftCandidate TC Vote DraftApprovedPublishedDeprecatedRescindedRetiredenLatnTOC Heading Levels2HTML TOC Heading Levels2DOC TOC Heading Levels2 + +OGC Geoscience Markup Language +./document.xml./document.pdf./document.dochttp://www.opengis.net/doc/{doc-type}/{standard}/{m.n}YY-999YY-9992029-03-302029-03-302029-03-30 +Organization One + +Organization Two + +Edward Lewis + +Editor Two + +Open Geospatial Consortium +1.04.1.1enLatn<Insert Abstract Text here> +draft2023 +Open Geospatial Consortium +ogcdocOGC documentAPIopenapihtmlstandardimplementationtechnicalTOC Heading Levels2HTML TOC Heading Levels2DOC TOC Heading Levels2 + + + + Copyright notice + + Copyright + © 2023 Open Geospatial Consortium + To obtain additional rights of use, visit + https://www.ogc.org/legal + + + + Note + Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. + + Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. + + + + + License Agreement + + Use of this document is subject to the license agreement at + https://www.ogc.org/license + + + + + + + + Notice for Drafts + This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard. + + Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. + + + + + + + + + + + + + + + Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/ + + + + +Abstract<Insert Abstract Text here> + +Keywords +The following are keywords to be used by search engines and + document catalogues. +ogcdoc, OGC document, API, openapi, html + +Preface +Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work. + + +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. + +Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. + +Security considerations +No security considerations have been made for this Standard. + +Submitting Organizations +The following organizations submitted this Document to the + Open Geospatial Consortium (OGC): + Organization One +Organization Two + + +Submitters +All questions regarding this submission should be directed to the editor or the submitters: + +Name +Affiliation + + + + + +Keywords + + + +Preface +Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work. > +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. + +Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. + + + + + +Submitting organizations + + + + +Contributors +Additional contributors to this Standard include the following: + +Individual name(s), Organization + + + +Scope +Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document. + + + + +Conformance +This standard defines XXXX. + +Requirements for N standardization target types are considered: + +AAAA + +BBBB + + + +Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site. + +In order to conform to this OGC® interface standard, a software implementation shall choose to implement: + +Any one of the conformance levels specified in Annex A (normative). + +Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative). + + + +All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified. + + + + + +Terms and definitionsThis document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2. +This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec. +For the purposes of this document, the following additional terms and definitions apply. + +This document uses the terms defined in Sub-clause 5.3 of , which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard. + +For the purposes of this document, the following additional terms and definitions apply. + + +example term + + +term used for exemplary purposes + + + + + + + An example note. +Here’s an example of an example term. + + + + +Conventions +This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document. + + +Identifiers +The normative provisions in this standard are denoted by the URI + + + +All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base. + + + + +Clauses not containing normative material +Paragraph + + +Clauses not containing normative material sub-clause 1 +Paragraph + + + +Clauses not containing normative material sub-clause 2 + + + + +Clause containing normative material +Paragraph + + +Requirement Class A or Requirement A Example +Paragraph – intro text for the requirement class. + +Use the following table for Requirements Classes. + +Requirements Class + +urn:iso:ts:iso:19139:clause:6 + + + + + + + + + +Requirement 1 +Paragraph — intro text for the requirement. + +Use the following table for Requirements, number sequentially. + + Requirement ‘shall’ statement + + +Dictionary tables for requirements can be added as necessary. Modify the following example as needed. + +Names +Definition +Data types and values +Multiplicity and use + +name 1 +definition of name 1 +float +One or more (mandatory) +name 2 +definition of name 2 +character string type, not empty +Zero or one (optional) +name 3 +definition of name 3 +GML:: Point PropertyType +One (mandatory) + + + + + +Requirement 2 +Paragraph — intro text for the requirement. + +Use the following table for Requirements, number sequentially. + + label/req/req-class-a/req-name-2 + +The process input value is specified in-line in an execute request. + +The process input is defined as an object according to its schema. + + + +The server SHALL support process input values encoded as qualified values. + +The value of the value key SHALL be an object instance. + + + + + + +Media Types for any data encoding(s) +A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in then this section may be used to define a new MIME type for registration with IANA. + + + + + + + + + + +Conformance Class Abstract Test Suite (Normative) +Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number) + + + +Conformance Class A +label + + +subject +Requirements Class “example1” + +classification +Target Type:Web API + + + + + +Example 1 + /req/req-class-a/req-name-1label/conf/core/api-definition-opValidate that the API Definition document can be retrieved from the expected location. + + +Construct a path for the API Definition document that ends with /api. + +Issue a HTTP GET request on that path + +Validate the contents of the returned document using test /conf/core/api-definition-success. + + + + +Example 2 + /req/req-class-a/req-name-2label/conf/core/httpValidate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS. + + +All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively. + +For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol. + + + + +Title +Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography + + +Revision History +Date +Release +Editor +Primary clauses modified +Description + +2016-04-28 +0.1 +G. Editor +all +initial version + + + +Normative referencesThe following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. + + + + +Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)Identification of Common Molecular Subsequences +ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)ZIB Structure Prediction Pipeline +The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).The Grid +Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)Grid Information Services for Distributed Resource Sharing +The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)The Physiology of the Grid +National Center for Biotechnology Information, NCBI + 2023-03-16 +Geographic information + +Reference model + +Part 1: Fundamentals + +Geographic information — Reference model — Part 1: Fundamentals + https://www.iso.org/standard/59164.html https://www.iso.org/obp/ui/#!iso:std:59164:en https://www.iso.org/contents/data/standard/05/91/59164.detail.rss ISO 19101-1:2014 urn:iso:std:iso:19101:-1:stage-90.93:ed-1 19101 2014-11 +International Organization for Standardization + ISO www.iso.org 1 en Latn ISO 19101-1:2014 defines the reference model for standardization in the field of geographic information. This reference model describes the notion of interoperability and sets forth the fundamentals by which this standardization takes place. Although structured in the context of information technology and information technology standards, ISO 19101-1:2014 is independent of any application development method or technology implementation approach. 90 93 2014 +ISO + ISO 19101:2002 ISO 19101:2002 + Geneva + 2023-03-16 +Geographic information + +Metadata + +Part 1: Fundamentals + +Geographic information — Metadata — Part 1: Fundamentals + https://www.iso.org/standard/53798.html https://www.iso.org/obp/ui/#!iso:std:53798:en https://www.iso.org/contents/data/standard/05/37/53798.detail.rss ISO 19115-1:2014 urn:iso:std:iso:19115:-1:stage-90.93:ed-1 19115 2014-04 +International Organization for Standardization + ISO www.iso.org 1 en Latn ISO 19115-1:2014 defines the schema required for describing geographic information and services by means of metadata. It provides information about the identification, the extent, the quality, the spatial and temporal aspects, the content, the spatial reference, the portrayal, distribution, and other properties of digital geographic data and services. ISO 19115-1:2014 is applicable to: -the cataloguing of all types of resources, clearinghouse activities, and the full description of datasets and services; -geographic services, geographic datasets, dataset series, and individual geographic features and feature properties. ISO 19115-1:2014 defines: -mandatory and conditional metadata sections, metadata entities, and metadata elements; -the minimum set of metadata required to serve most metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data and services); -optional metadata elements to allow for a more extensive standard description of resources, if required; -a method for extending metadata to fit specialized needs. Though ISO 19115-1:2014 is applicable to digital data and services, its principles can be extended to many other types of resources such as maps, charts, and textual documents as well as non-geographic data. Certain conditional metadata elements might not apply to these other forms of data. 90 93 2014 +ISO + ISO 19115:2003 ISO 19115:2003 + ISO 19115:2003/Cor 1:2006 ISO 19115:2003/Cor 1:2006 + ISO 19115-1:2014/Amd 1:2018 ISO 19115-1:2014/Amd 1:2018 2019-06-13 + ISO 19115-1:2014/Amd 2:2020 ISO 19115-1:2014/Amd 2:2020 2019-06-13 + Geneva + 2023-03-16 +Geographic information + +Data quality + +Geographic information  — Data quality + https://www.iso.org/standard/32575.html https://www.iso.org/obp/ui/#!iso:std:32575:en https://www.iso.org/contents/data/standard/03/25/32575.detail.rss ISO 19157:2013 urn:iso:std:iso:19157:stage-90.92:ed-1 19157 2013-12 +International Organization for Standardization + ISO www.iso.org 1 en Latn ISO 19157:2013 establishes the principles for describing the quality of geographic data. It —  defines components for describing data quality; —  specifies components and content structure of a register for data quality measures; —  describes general procedures for evaluating the quality of geographic data; —  establishes principles for reporting data quality. ISO 19157:2013 also defines a set of data quality measures for use in evaluating and reporting data quality. It is applicable to data producers providing quality information to describe and assess how well a data set conforms to its product specification and to data users attempting to determine whether or not specific geographic data are of sufficient quality for their particular application. ISO 19157:2013 does not attempt to define minimum acceptable levels of quality for geographic data. 90 92 2013 +ISO + ISO 19113:2002 ISO 19113:2002 + ISO 19114:2003 ISO 19114:2003 + ISO/TS 19138:2006 ISO/TS 19138:2006 + ISO 19157-1 ISO 19157-1 2019-07-01 + ISO/AWI 19157-3 ISO/AWI 19157-3 2019-07-01 + ISO 19157:2013/Amd 1:2018 ISO 19157:2013/Amd 1:2018 2019-07-01 + Geneva + +Geographic information — Metadata — XML schema implementation +ISO 19139:2007191392007 +ISO + + 2023-03-16 +Geographic information + +Metadata + +Part 3: XML schema implementation for fundamental concepts + +Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts + https://www.iso.org/standard/80874.html https://www.iso.org/contents/data/standard/08/08/80874.detail.rss ISO 19115-3 urn:iso:std:iso:19115:-3:stage-draft:ed-1 19115 +International Organization for Standardization + ISO www.iso.org 1 en Latn 50 00 2023 +ISO/PRF + ISO/TS 19115-3:2016 ISO/TS 19115-3:2016 + 2023-03-16 +Geographic information + +Metadata + +Part 3: XML schema implementation for fundamental concepts + +Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts + https://www.iso.org/standard/80874.html https://www.iso.org/contents/data/standard/08/08/80874.detail.rss ISO 19115-3 urn:iso:std:iso:19115:-3:stage-draft:ed-1 19115 +International Organization for Standardization + ISO www.iso.org 1 en Latn 50 00 2023 +ISO/PRF + ISO/TS 19115-3:2016 ISO/TS 19115-3:2016 + Geneva + Geneva +OGC Geospatial User Feedback Standard: Conceptual Model (2016)OGC 15-09715-097 + 2023-03-16 +OGC City Geography Markup Language (CityGML) Encoding Standard + +OGC City Geography Markup Language (CityGML) Encoding Standard + https://portal.ogc.org/files/?artifact_id=47842 12-019 2012-04-04 + Gerhard Gröger + + Thomas H. Kolbe + + Claus Nagel + + Karl-Heinz Häfele + +Open Geospatial Consortium + en Latn CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. + 2023-03-16 +OGC® IndoorGML + +OGC® IndoorGML + https://docs.ogc.org/is/14-005r3/14-005r3.html 14-005r3 2014-12-02 + Jiyeong Lee + + Ki-Joune Li + + Sisi Zlatanova + + Thomas H. Kolbe + + Claus Nagel + + Thomas Becker + +Open Geospatial Consortium + 3 en Latn This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. + 2023-03-16 +OGC Web Service Common Implementation Specification + +OGC Web Service Common Implementation Specification + https://portal.ogc.org/files/?artifact_id=38867 06-121r9 2010-04-07 + Arliss Whiteside Jim Greenwood + +Open Geospatial Consortium + 9 en Latn This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + +Bibliography +The TC has approved Springer LNCS as the official document citation type. + +Springer LNCS is widely used in technical and computer science journals and other publications + + +– Actual References: + +[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published) + +[n] Web: Author Surname, A.: Title, + + OGC: OGC Testbed 12 Annex B: Architecture (2015). + OGCTB12 + 12 + + + + +sourcecode table td { padding: 5px; } +sourcecode table pre { margin: 0; } +sourcecode, sourcecode .w { + color: #444444; +} +sourcecode .cp { + color: #CC00A3; +} +sourcecode .cs { + color: #CC00A3; +} +sourcecode .c, sourcecode .ch, sourcecode .cd, sourcecode .cm, sourcecode .cpf, sourcecode .c1 { + color: #FF0000; +} +sourcecode .kc { + color: #C34E00; +} +sourcecode .kd { + color: #0000FF; +} +sourcecode .kr { + color: #007575; +} +sourcecode .k, sourcecode .kn, sourcecode .kp, sourcecode .kt, sourcecode .kv { + color: #0000FF; +} +sourcecode .s, sourcecode .sb, sourcecode .sc, sourcecode .ld, sourcecode .sd, sourcecode .s2, sourcecode .se, sourcecode .sh, sourcecode .si, sourcecode .sx, sourcecode .sr, sourcecode .s1, sourcecode .ss { + color: #009C00; +} +sourcecode .sa { + color: #0000FF; +} +sourcecode .nb, sourcecode .bp { + color: #C34E00; +} +sourcecode .nt { + color: #0000FF; +} + + + + + + Copyright notice + +

Copyright + © 2023 Open Geospatial Consortium
+ To obtain additional rights of use, visit + https://www.ogc.org/legal +

+ + + Note +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+ + + + + License Agreement + +

Use of this document is subject to the license agreement at + https://www.ogc.org/license

+ + + + + + + + Notice for Drafts +

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

+ +

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

+ + + + + + + + + + + + + + +

Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/

+ + + + +I.<tab/>Abstract

<Insert Abstract Text here>

+ +II.<tab/>Keywords +

The following are keywords to be used by search engines and + document catalogues.

+

ogcdoc, OGC document, API, openapi, html

 + +III.<tab/>Preface +NOTE

Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

+ + +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+ +IV.<tab/>Security considerations +

No security considerations have been made for this Standard.

+ +V.<tab/>Submitting Organizations +

The following organizations submitted this Document to the + Open Geospatial Consortium (OGC):

+
  • Organization One
    • +
  • Organization Two
+ + +VI.<tab/>Submitters +

All questions regarding this submission should be directed to the editor or the submitters:

+ + + + +
NameAffiliation
+ + + +5.<tab/>Keywords + + + +Preface +NOTE

Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work. > +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+ + + + + +6.<tab/>Submitting organizations + + + + +7.<tab/>Contributors +

Additional contributors to this Standard include the following:

+ +

Individual name(s), Organization

+ + + +1.<tab/>Scope +NOTE

Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

+ + + + +2.<tab/>Conformance +

This standard defines XXXX.

+ +

Requirements for N standardization target types are considered:

+ +

  • AAAA

    +
    • +

  • BBBB

    +
    • +
+ +

Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site.

+ +

In order to conform to this OGC® interface standard, a software implementation shall choose to implement:

+ +

  • Any one of the conformance levels specified in Annex A (normative).

    +
    • +

  • Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative).

    +
    • +
+ +

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

+ + + + + +4.<tab/>Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

+

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

+

For the purposes of this document, the following additional terms and definitions apply.

+ +

This document uses the terms defined in Sub-clause 5.3 of [OGC06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

+ +

For the purposes of this document, the following additional terms and definitions apply.

+ +4.1.example term +

term used for exemplary purposes

 + + + + + + + Note 1 to entry

An example note.

+Example

Here’s an example of an example term.

+[SOURCE: ISO 19101-1:2014] + + + +8.<tab/>Conventions +

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

+ + +8.1.<tab/>Identifiers +

The normative provisions in this standard are denoted by the URI

+ +

+ +

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

+ + + + +9.<tab/>Clauses not containing normative material +

Paragraph

+ + +9.1.<tab/>Clauses not containing normative material sub-clause 1 +

Paragraph

+ + + +9.2.<tab/>Clauses not containing normative material sub-clause 2 + + + + +10.<tab/>Clause containing normative material +

Paragraph

+ + +10.1.<tab/>Requirement Class A or Requirement A Example +

Paragraph – intro text for the requirement class.

+ +

Use the following table for Requirements Classes.

+ +

Requirements class 1

Obligationrequirement
Description

Requirements Class

  • +
    • +

  • urn:iso:ts:iso:19139:clause:6

    +
    • +
Normative statementsRequirement 1-1
Requirement 1-2
+ + +10.1.1.<tab/>Requirement 1 +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 1

Obligationrequirement
Statement

Requirement ‘shall’ statement

+ +

Dictionary tables for requirements can be added as necessary. Modify the following example as needed.

+ +Table 1 + + + + + + + + + + + + + + + + + +
NamesDefinitionData types and valuesMultiplicity and use
name 1definition of name 1floatOne or more (mandatory)
name 2definition of name 2character string type, not emptyZero or one (optional)
name 3definition of name 3GML:: Point PropertyTypeOne (mandatory)
+ + + +10.1.2.<tab/>Requirement 2 +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement 2

Label/req/req-class-a/req-name-2
Conditions

  1. The process input value is specified in-line in an execute request.

    +
    2. +

  2. The process input is defined as an object according to its schema.

    +
    3. +
+
A

The server SHALL support process input values encoded as qualified values.

+
B

The value of the value key SHALL be an object instance.

+
+ + + + + +11.<tab/>Media Types for any data encoding(s) +

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in then this section may be used to define a new MIME type for registration with IANA.

+ + + + + + + + + + +<strong>Annex A</strong><br/>(informative)<br/><strong>Conformance Class Abstract Test Suite (Normative)</strong> +NOTE

Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

+ + + +A.1.<tab/>Conformance Class A +Example
label
+

+
+
subject
+

Requirements Class “example1”

+
+
classification
+

Target Type:Web API

+
+
+ + + +A.1.1.<tab/>Example 1 +

Abstract test A.1

Subject/req/req-class-a/req-name-1
Label/conf/core/api-definition-op
Test purpose

Validate that the API Definition document can be retrieved from the expected location.

+
Test method
    +

  1. Construct a path for the API Definition document that ends with /api.

    +
    2. +

  2. Issue a HTTP GET request on that path

    +
    3. +

  3. Validate the contents of the returned document using test /conf/core/api-definition-success.

    +
    4. +
+ +
+ + + +A.1.2.<tab/>Example 2 +

Abstract test A.2

Subject/req/req-class-a/req-name-2
Label/conf/core/http
Test purpose

Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

+
Test method
    +

  1. All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

    +
    2. +

  2. For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol.

    +
    3. +
+
+ + + +<strong>Annex B</strong><br/>(informative)<br/><strong>Title</strong> +NOTE

Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography

+ + +<strong>Annex C</strong><br/>(informative)<br/><strong>Revision History</strong> +Table C.1 + + + + + + + + + + + +
DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version
+ +3.<tab/>Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

+ + + + +Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)Identification of Common Molecular Subsequences +ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)ZIB Structure Prediction Pipeline +The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).The Grid +Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)Grid Information Services for Distributed Resource Sharing +The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)The Physiology of the Grid +National Center for Biotechnology Information, NCBI +ISO: ISO 19101-1:2014, Geographic information — Reference model — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/59164.html.https://www.iso.org/standard/59164.htmlhttps://www.iso.org/obp/ui/#!iso:std:59164:enhttps://www.iso.org/contents/data/standard/05/91/59164.detail.rssISO 19101-1:2014URN urn:iso:std:iso:19101:-1:stage-90.93:ed-1 90 93 + ISO: ISO 19115-1:2014, Geographic information — Metadata — Part 1: Fundamentals. International Organization for Standardization, Geneva (2014). https://www.iso.org/standard/53798.html.https://www.iso.org/standard/53798.htmlhttps://www.iso.org/obp/ui/#!iso:std:53798:enhttps://www.iso.org/contents/data/standard/05/37/53798.detail.rssISO 19115-1:2014URN urn:iso:std:iso:19115:-1:stage-90.93:ed-1 90 93 + ISO: ISO 19157:2013, Geographic information  — Data quality. International Organization for Standardization, Geneva (2013). https://www.iso.org/standard/32575.html.https://www.iso.org/standard/32575.htmlhttps://www.iso.org/obp/ui/#!iso:std:32575:enhttps://www.iso.org/contents/data/standard/03/25/32575.detail.rssISO 19157:2013URN urn:iso:std:iso:19157:stage-90.92:ed-1 90 92 +ISO: ISO 19139:2007, Geographic information — Metadata — XML schema implementation. ISO (2007).ISO 19139:2007 +ISO: ISO 19115-3, Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts. International Organization for Standardization, Geneva https://www.iso.org/standard/80874.html.https://www.iso.org/standard/80874.htmlhttps://www.iso.org/contents/data/standard/08/08/80874.detail.rssISO 19115-3URN urn:iso:std:iso:19115:-3:stage-draft:ed-1 50 00 +OGC Geospatial User Feedback Standard: Conceptual Model (2016)OGC 15-09715-097 +Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele: OGC 12-019, OGC City Geography Markup Language (CityGML) Encoding Standard. Open Geospatial Consortium (2012). https://portal.ogc.org/files/?artifact id=47842.https://portal.ogc.org/files/?artifact_id=47842OGC 12-019 + Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker: OGC 14-005r3, OGC® IndoorGML. Open Geospatial Consortium (2014). https://docs.ogc.org/is/14-005r3/14-005r3.html.https://docs.ogc.org/is/14-005r3/14-005r3.htmlOGC 14-005r3 + Arliss Whiteside Jim Greenwood: OGC 06-121r9, OGC Web Service Common Implementation Specification. Open Geospatial Consortium (2010). https://portal.ogc.org/files/?artifact id=38867.https://portal.ogc.org/files/?artifact_id=38867OGC 06-121r9 + +Bibliography +NOTE

The TC has approved Springer LNCS as the official document citation type.

+ +

Springer LNCS is widely used in technical and computer science journals and other publications

+ + +

– Actual References:

+ +

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

+ +

[n] Web: Author Surname, A.: Title,

+ + OGC: OGC Testbed 12 Annex B: Architecture (2015).[1] + OGCTB12 + 12 +[1] + + + + diff --git a/docs/index.xml b/docs/index.xml new file mode 100644 index 0000000..ea29fed --- /dev/null +++ b/docs/index.xml @@ -0,0 +1,513 @@ + + + +OGC Geoscience Markup Language +./document.xml./document.pdf./document.dochttp://www.opengis.net/doc/{doc-type}/{standard}/{m.n}YY-999YY-9992029-03-302029-03-302029-03-30 +Organization One + +Organization Two + +Edward Lewis + +Editor Two + +Open Geospatial Consortium +1.04.1.1en

<Insert Abstract Text here>

+draft2023 +Open Geospatial Consortium +ogcdocOGC documentAPIopenapihtmlstandardimplementationtechnicalTOC Heading Levels2HTML TOC Heading Levels2DOC TOC Heading Levels2 + + + + Copyright notice + +

Copyright + © 2023 Open Geospatial Consortium
+ To obtain additional rights of use, visit + https://www.ogc.org/legal +

+ + + Note +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+ + + + + License Agreement + +

Use of this document is subject to the license agreement at + https://www.ogc.org/license

+ + + + + + + + Notice for Drafts +

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

+ +

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

+ + + + + + + + + + + + + + +

Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/

+ + + + +Abstract

<Insert Abstract Text here>

+ +Preface +

Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

+ + +

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+ +Security considerations +

No security considerations have been made for this Standard.

+ +Submitters +

All questions regarding this submission should be directed to the editor or the submitters:

+ + + + +
NameAffiliation
+ + + +Keywords + + + +Preface +

Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work. > +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

+ +

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

+ + + + + +Submitting organizations + + + + +Contributors +

Additional contributors to this Standard include the following:

+ +

Individual name(s), Organization

+ + + +Scope +

Insert Scope text here. Give the subject of the document and the aspects of that scope covered by the document.

+ + + + +Conformance +

This standard defines XXXX.

+ +

Requirements for N standardization target types are considered:

+ +

  • AAAA

    +
    • +

  • BBBB

    +
    • +
+ +

Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site.

+ +

In order to conform to this OGC® interface standard, a software implementation shall choose to implement:

+ +

  • Any one of the conformance levels specified in Annex A (normative).

    +
    • +

  • Any one of the Distributed Computing Platform profiles specified in Annexes TBD through TBD (normative).

    +
    • +
+ +

All requirements-classes and conformance-classes described in this document are owned by the standard(s) identified.

+ + + + + +Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

+

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

+

For the purposes of this document, the following additional terms and definitions apply.

+ +

This document uses the terms defined in Sub-clause 5.3 of , which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

+ +

For the purposes of this document, the following additional terms and definitions apply.

+ + +example term + + +

term used for exemplary purposes

 + + + + + + +

An example note.

+

Here’s an example of an example term.

+ + + + +Conventions +

This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

+ + +Identifiers +

The normative provisions in this standard are denoted by the URI

+ +

+ +

All requirements and conformance tests that appear in this document are denoted by partial URIs which are relative to this base.

+ + + + +Clauses not containing normative material +

Paragraph

+ + +Clauses not containing normative material sub-clause 1 +

Paragraph

+ + + +Clauses not containing normative material sub-clause 2 + + + + +Clause containing normative material +

Paragraph

+ + +Requirement Class A or Requirement A Example +

Paragraph – intro text for the requirement class.

+ +

Use the following table for Requirements Classes.

+ +

Requirements Class

  • +
    • +

  • urn:iso:ts:iso:19139:clause:6

    +
    • +
 + + + + + + + +Requirement 1 +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ +

Requirement ‘shall’ statement

 + + +

Dictionary tables for requirements can be added as necessary. Modify the following example as needed.

+ + + + + + + + + + + + + + + + + + + +
NamesDefinitionData types and valuesMultiplicity and use
name 1definition of name 1floatOne or more (mandatory)
name 2definition of name 2character string type, not emptyZero or one (optional)
name 3definition of name 3GML:: Point PropertyTypeOne (mandatory)
+ + + +Requirement 2 +

Paragraph — intro text for the requirement.

+ +

Use the following table for Requirements, number sequentially.

+ + label/req/req-class-a/req-name-2 + +

  1. The process input value is specified in-line in an execute request.

    +
    2. +

  2. The process input is defined as an object according to its schema.

    +
    3. +
+ +

The server SHALL support process input values encoded as qualified values.

+ +

The value of the value key SHALL be an object instance.

+ + + + + + +Media Types for any data encoding(s) +

A section describing the MIME-types to be used is mandatory for any standard involving data encodings. If no suitable MIME type exists in then this section may be used to define a new MIME type for registration with IANA.

+ + + + + + + + + + +Conformance Class Abstract Test Suite (Normative) +

Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

+ + + +Conformance Class A +
label
+

+
+
subject
+

Requirements Class “example1”

+
+
classification
+

Target Type:Web API

+
+
+ + + +Example 1 + /req/req-class-a/req-name-1label/conf/core/api-definition-op

Validate that the API Definition document can be retrieved from the expected location.

+ + +

Construct a path for the API Definition document that ends with /api.

+ +

Issue a HTTP GET request on that path

+ +

Validate the contents of the returned document using test /conf/core/api-definition-success.

+ + + + +Example 2 + /req/req-class-a/req-name-2label/conf/core/http

Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

+ + +

All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

+ +

For APIs which support HTTPS, all compliance tests SHALL be configured to use HTTP over TLS (RFC 2818) with their HTTP 1.1 protocol.

+ + + + +Title +

Place other Annex material in sequential annexes beginning with “B” and leave final two annexes for the Revision History and Bibliography

+ + +Revision History + + + + + + + + + + + + +
DateReleaseEditorPrimary clauses modifiedDescription
2016-04-280.1G. Editorallinitial version
+ +Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

+ + + + +Identification of Common Molecular Subsequences. Smith, T.F., Waterman, M.S., J. Mol. Biol. 147, 195–197 (1981)Identification of Common Molecular Subsequences +ZIB Structure Prediction Pipeline: Composing a Complex Biological Workflow through Web Services. May, P., Ehrlich, H.C., Steinke, T. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)ZIB Structure Prediction Pipeline +The Grid: Blueprint for a New Computing Infrastructure., Foster, I., Kesselman, C.. Morgan Kaufmann, San Francisco (1999).The Grid +Grid Information Services for Distributed Resource Sharing. Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)Grid Information Services for Distributed Resource Sharing +The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Foster, I., Kesselman, C., Nick, J., Tuecke, S. Technical report, Global Grid Forum (2002)The Physiology of the Grid +National Center for Biotechnology Information, NCBI + 2023-03-16 +Geographic information + +Reference model + +Part 1: Fundamentals + +Geographic information — Reference model — Part 1: Fundamentals + https://www.iso.org/standard/59164.html https://www.iso.org/obp/ui/#!iso:std:59164:en https://www.iso.org/contents/data/standard/05/91/59164.detail.rss ISO 19101-1:2014 urn:iso:std:iso:19101:-1:stage-90.93:ed-1 19101 2014-11 +International Organization for Standardization + ISO www.iso.org 1 en ISO 19101-1:2014 defines the reference model for standardization in the field of geographic information. This reference model describes the notion of interoperability and sets forth the fundamentals by which this standardization takes place. Although structured in the context of information technology and information technology standards, ISO 19101-1:2014 is independent of any application development method or technology implementation approach. 90 93 2014 +ISO + ISO 19101:2002 ISO 19101:2002 + Geneva + 2023-03-16 +Geographic information + +Metadata + +Part 1: Fundamentals + +Geographic information — Metadata — Part 1: Fundamentals + https://www.iso.org/standard/53798.html https://www.iso.org/obp/ui/#!iso:std:53798:en https://www.iso.org/contents/data/standard/05/37/53798.detail.rss ISO 19115-1:2014 urn:iso:std:iso:19115:-1:stage-90.93:ed-1 19115 2014-04 +International Organization for Standardization + ISO www.iso.org 1 en ISO 19115-1:2014 defines the schema required for describing geographic information and services by means of metadata. It provides information about the identification, the extent, the quality, the spatial and temporal aspects, the content, the spatial reference, the portrayal, distribution, and other properties of digital geographic data and services. ISO 19115-1:2014 is applicable to: -the cataloguing of all types of resources, clearinghouse activities, and the full description of datasets and services; -geographic services, geographic datasets, dataset series, and individual geographic features and feature properties. ISO 19115-1:2014 defines: -mandatory and conditional metadata sections, metadata entities, and metadata elements; -the minimum set of metadata required to serve most metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data and services); -optional metadata elements to allow for a more extensive standard description of resources, if required; -a method for extending metadata to fit specialized needs. Though ISO 19115-1:2014 is applicable to digital data and services, its principles can be extended to many other types of resources such as maps, charts, and textual documents as well as non-geographic data. Certain conditional metadata elements might not apply to these other forms of data. 90 93 2014 +ISO + ISO 19115:2003 ISO 19115:2003 + ISO 19115:2003/Cor 1:2006 ISO 19115:2003/Cor 1:2006 + ISO 19115-1:2014/Amd 1:2018 ISO 19115-1:2014/Amd 1:2018 2019-06-13 + ISO 19115-1:2014/Amd 2:2020 ISO 19115-1:2014/Amd 2:2020 2019-06-13 + Geneva + 2023-03-16 +Geographic information + +Data quality + +Geographic information  — Data quality + https://www.iso.org/standard/32575.html https://www.iso.org/obp/ui/#!iso:std:32575:en https://www.iso.org/contents/data/standard/03/25/32575.detail.rss ISO 19157:2013 urn:iso:std:iso:19157:stage-90.92:ed-1 19157 2013-12 +International Organization for Standardization + ISO www.iso.org 1 en ISO 19157:2013 establishes the principles for describing the quality of geographic data. It —  defines components for describing data quality; —  specifies components and content structure of a register for data quality measures; —  describes general procedures for evaluating the quality of geographic data; —  establishes principles for reporting data quality. ISO 19157:2013 also defines a set of data quality measures for use in evaluating and reporting data quality. It is applicable to data producers providing quality information to describe and assess how well a data set conforms to its product specification and to data users attempting to determine whether or not specific geographic data are of sufficient quality for their particular application. ISO 19157:2013 does not attempt to define minimum acceptable levels of quality for geographic data. 90 92 2013 +ISO + ISO 19113:2002 ISO 19113:2002 + ISO 19114:2003 ISO 19114:2003 + ISO/TS 19138:2006 ISO/TS 19138:2006 + ISO 19157-1 ISO 19157-1 2019-07-01 + ISO/AWI 19157-3 ISO/AWI 19157-3 2019-07-01 + ISO 19157:2013/Amd 1:2018 ISO 19157:2013/Amd 1:2018 2019-07-01 + Geneva + +Geographic information — Metadata — XML schema implementation +ISO 19139:2007191392007 +ISO + + 2023-03-16 +Geographic information + +Metadata + +Part 3: XML schema implementation for fundamental concepts + +Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts + https://www.iso.org/standard/80874.html https://www.iso.org/contents/data/standard/08/08/80874.detail.rss ISO 19115-3 urn:iso:std:iso:19115:-3:stage-draft:ed-1 19115 +International Organization for Standardization + ISO www.iso.org 1 en 50 00 2023 +ISO/PRF + ISO/TS 19115-3:2016 ISO/TS 19115-3:2016 + 2023-03-16 +Geographic information + +Metadata + +Part 3: XML schema implementation for fundamental concepts + +Geographic information — Metadata — Part 3: XML schema implementation for fundamental concepts + https://www.iso.org/standard/80874.html https://www.iso.org/contents/data/standard/08/08/80874.detail.rss ISO 19115-3 urn:iso:std:iso:19115:-3:stage-draft:ed-1 19115 +International Organization for Standardization + ISO www.iso.org 1 en 50 00 2023 +ISO/PRF + ISO/TS 19115-3:2016 ISO/TS 19115-3:2016 + Geneva + Geneva +OGC Geospatial User Feedback Standard: Conceptual Model (2016)OGC 15-09715-097 + 2023-03-16 +OGC City Geography Markup Language (CityGML) Encoding Standard + +OGC City Geography Markup Language (CityGML) Encoding Standard + https://portal.ogc.org/files/?artifact_id=47842 12-019 2012-04-04 + Gerhard Gröger + + Thomas H. Kolbe + + Claus Nagel + + Karl-Heinz Häfele + +Open Geospatial Consortium + en CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. + 2023-03-16 +OGC® IndoorGML + +OGC® IndoorGML + https://docs.ogc.org/is/14-005r3/14-005r3.html 14-005r3 2014-12-02 + Jiyeong Lee + + Ki-Joune Li + + Sisi Zlatanova + + Thomas H. Kolbe + + Claus Nagel + + Thomas Becker + +Open Geospatial Consortium + 3 en This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. + 2023-03-16 +OGC Web Service Common Implementation Specification + +OGC Web Service Common Implementation Specification + https://portal.ogc.org/files/?artifact_id=38867 06-121r9 2010-04-07 + Arliss Whiteside Jim Greenwood + +Open Geospatial Consortium + 9 en This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + +Bibliography +

The TC has approved Springer LNCS as the official document citation type.

+ +

Springer LNCS is widely used in technical and computer science journals and other publications

+ + +

– Actual References:

+ +

[n] Journal: Author Surname, A.: Title. Publication Title. Volume number, Issue number, Pages Used (Year Published)

+ +

[n] Web: Author Surname, A.: Title,

+ + OGC: OGC Testbed 12 Annex B: Architecture (2015). + OGCTB12 + 12 + + + + + From 83be2296aea06411dc5259c1c46b04bae26171cf Mon Sep 17 00:00:00 2001 From: KoalaGeo Date: Thu, 16 Mar 2023 16:37:54 +0000 Subject: [PATCH 15/18] Update metadata --- docs/index.adoc | 28 ++++++++++++---------- docs/sections/clause_0_front_material.adoc | 7 ++++-- 2 files changed, 20 insertions(+), 15 deletions(-) diff --git a/docs/index.adoc b/docs/index.adoc index 766865b..24a58e1 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -1,4 +1,4 @@ -= OGC Geoscience Markup Language += OGC Geoscience Markup Language - GeoSciML :doctype: standard :encoding: utf-8 :lang: en @@ -6,23 +6,25 @@ :committee: technical :draft: 4.1.1 :external-id: http://www.opengis.net/doc/{doc-type}/{standard}/{m.n} -:docnumber: YY-999 -:received-date: 2029-03-30 -:issued-date: 2029-03-30 -:published-date: 2029-03-30 -:fullname: Edward Lewis -:fullname_2: Editor Two +:docnumber: 16-008 +:received-date: 2016-08-23 +:issued-date: 2016-11-29 +:published-date: 2017-01-31 +:fullname: GeoSciML Modeling Team +:fullname_2: Eric Boisvert +:fullname_3: Ollie Raymond +:fullname_3: Marcus Sen :docsubtype: Interface -:keywords: ogcdoc, OGC document, API, openapi, html -:submitting-organizations: Organization One; Organization Two +:keywords: ogcdoc, OGC document, API, openapi, html, geology, geoscience, stratigraphy, borehole, geochemistry, geophysics, rock, fault, contact, fold, fossil, UML, GML, XML +:submitting-organizations: Arizona Geological Survey (AzGS), Arizona, USA; British Geological Survey (NERC-BGS), UK; Bureau de Recherches Géologiques et Minières (BRGM), France; Commonwealth Scientific and Industrial Research Organisation (CSIRO), Australia; Geological Survey of Victoria (GSV), Australia; Geological Survey of Finland (GTK), Finland; Geological Survey of Italy (ISPRA), Italy; Geological Survey of Sweden (SGU), Sweden; Geoscience Australia (GA), Australia; Institute of Geological and Nuclear Sciences (GNS), New Zealand; Landcare Research, New Zealand; Natural Resources Canada (NRCan), Canada; U.S. Geological Survey (USGS), United States of America :mn-document-class: ogc :mn-output-extensions: xml,html,doc,pdf :local-cache-only: :data-uri-image: -:pdf-uri: ./document.pdf -:xml-uri: ./document.xml -:doc-uri: ./document.doc -:edition: 1.0 +:pdf-uri: ./index.pdf +:xml-uri: ./index.xml +:doc-uri: ./index.doc +:edition: 4.1 //// Make sure to complete each included document diff --git a/docs/sections/clause_0_front_material.adoc b/docs/sections/clause_0_front_material.adoc index c2ebda3..b3cab6e 100644 --- a/docs/sections/clause_0_front_material.adoc +++ b/docs/sections/clause_0_front_material.adoc @@ -30,7 +30,9 @@ Attention is drawn to the possibility that some of the elements of this document [abstract] == Abstract - +GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. + +The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. == Keywords @@ -40,7 +42,8 @@ Attention is drawn to the possibility that some of the elements of this document [NOTE] ==== -Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work. > +The primary goal of this specification is to capture the semantics, schema, and encoding syntax of key elements described and portrayed in geological maps and databases, in order to enable information systems to interoperate with such data. + Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. From ac026c87bd51231904c486fef940041281266a8c Mon Sep 17 00:00:00 2001 From: example Date: Thu, 16 Mar 2023 16:39:14 +0000 Subject: [PATCH 16/18] Compilation of HTML documents --- docs/index.doc | 165 +++++++++++++++++++----------------- docs/index.err | 54 ++++++------ docs/index.html | 119 ++++++++++++++------------ docs/index.presentation.xml | 148 ++++++++++++++++++++++++-------- docs/index.xml | 53 +++++++++--- 5 files changed, 336 insertions(+), 203 deletions(-) diff --git a/docs/index.doc b/docs/index.doc index 91741a3..5b7867d 100644 --- a/docs/index.doc +++ b/docs/index.doc @@ -1,7 +1,7 @@ MIME-Version: 1.0 -Content-Type: multipart/related; boundary="----=_NextPart_76813f2d.4980.4528" +Content-Type: multipart/related; boundary="----=_NextPart_9eb71348.c2a3.49f3" -------=_NextPart_76813f2d.4980.4528 +------=_NextPart_9eb71348.c2a3.49f3 Content-ID: Content-Disposition: inline; filename="index.htm" Content-Type: text/html; charset="utf-8" @@ -2494,7 +2494,7 @@ span.AdmittedLabel {

- Submission Date: 2029-03-30 + Submission Date: 2016-08-23

 


@@ -2527,272 +2527,272 @@ span.AdmittedLabel {

 TOC \o "1-2" \h \z \u -Copyright notice +Copyright notice . - PAGEREF _Toc740474489 \h + PAGEREF _Toc131697310 \h 1

-Note +Note . - PAGEREF _Toc200364577 \h + PAGEREF _Toc093436017 \h 1

-License Agreement +License Agreement . - PAGEREF _Toc556883737 \h + PAGEREF _Toc730883078 \h 1

-Notice for Drafts +Notice for Drafts . - PAGEREF _Toc854942633 \h + PAGEREF _Toc085064748 \h 1

-I. Abstract +I. Abstract . - PAGEREF _Toc858615328 \h + PAGEREF _Toc888062709 \h 1

-II. Keywords +II. Keywords . - PAGEREF _Toc625251657 \h + PAGEREF _Toc463137407 \h 1

-III. Preface +III. Preface . - PAGEREF _Toc809826198 \h + PAGEREF _Toc023902587 \h 1

-IV. Security considerations +IV. Security considerations . - PAGEREF _Toc258311618 \h + PAGEREF _Toc711019016 \h 1

-V. Submitting Organizations +V. Submitting Organizations . - PAGEREF _Toc765728328 \h + PAGEREF _Toc160137032 \h 1

-VI. Submitters +VI. Submitters . - PAGEREF _Toc872902253 \h + PAGEREF _Toc234198634 \h 1

-1. Scope +1. Scope . - PAGEREF _Toc730504638 \h + PAGEREF _Toc145680322 \h 1

-2. Conformance +2. Conformance . - PAGEREF _Toc935167211 \h + PAGEREF _Toc024575621 \h 1

-3. Normative references +3. Normative references . - PAGEREF _Toc153023762 \h + PAGEREF _Toc952559201 \h 1

-4. Terms and definitions +4. Terms and definitions . - PAGEREF _Toc779668084 \h + PAGEREF _Toc814991310 \h 1

-5. Keywords +5. Keywords . - PAGEREF _Toc883396748 \h + PAGEREF _Toc868981011 \h 1

-6. Submitting organizations +6. Submitting organizations . - PAGEREF _Toc574164226 \h + PAGEREF _Toc237117627 \h 1

-7. Contributors +7. Contributors . - PAGEREF _Toc305764257 \h + PAGEREF _Toc352785071 \h 1

-8. Conventions +8. Conventions . - PAGEREF _Toc720420944 \h + PAGEREF _Toc271910228 \h 1

-8.1. Identifiers +8.1. Identifiers . - PAGEREF _Toc113839212 \h + PAGEREF _Toc919049356 \h 1

-9. Clauses not containing normative material +9. Clauses not containing normative material . - PAGEREF _Toc772005082 \h + PAGEREF _Toc597119418 \h 1

-9.1. Clauses not containing normative material sub-clause 1 +9.1. Clauses not containing normative material sub-clause 1 . - PAGEREF _Toc826142593 \h + PAGEREF _Toc288458774 \h 1

-9.2. Clauses not containing normative material sub-clause 2 +9.2. Clauses not containing normative material sub-clause 2 . - PAGEREF _Toc119030601 \h + PAGEREF _Toc360778729 \h 1

-10. Clause containing normative material +10. Clause containing normative material . - PAGEREF _Toc850418522 \h + PAGEREF _Toc272726488 \h 1

-10.1. Requirement Class A or Requirement A Example +10.1. Requirement Class A or Requirement A Example . - PAGEREF _Toc622081566 \h + PAGEREF _Toc893975987 \h 1

-11. Media Types for any data encoding(s) +11. Media Types for any data encoding(s) . - PAGEREF _Toc600747805 \h + PAGEREF _Toc427345908 \h 1

-Annex A (informative) Conformance Class Abstract Test Suite (Normative) +Annex A (informative) Conformance Class Abstract Test Suite (Normative) . - PAGEREF _Toc828939072 \h + PAGEREF _Toc831525102 \h 1

-A.1. Conformance Class A +A.1. Conformance Class A . - PAGEREF _Toc868430590 \h + PAGEREF _Toc858967655 \h 1

-Annex B (informative) Title +Annex B (informative) Title . - PAGEREF _Toc963161365 \h + PAGEREF _Toc993316508 \h 1

-Annex C (informative) Revision History +Annex C (informative) Revision History . - PAGEREF _Toc867398826 \h + PAGEREF _Toc468523136 \h 1

-Bibliography +Bibliography . - PAGEREF _Toc806464743 \h + PAGEREF _Toc721167008 \h 1

@@ -2838,15 +2838,26 @@ span.AdmittedLabel { -


I.  Abstract

<Insert Abstract Text here>

II.  Keywords

The following are keywords to be used by search engines and - document catalogues.

ogcdoc, OGC document, API, openapi, html


III.  Preface

NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

IV.  Security considerations

No security considerations have been made for this Standard.

V.  Submitting Organizations

The following organizations submitted this Document to the - Open Geospatial Consortium (OGC):

Organization One

-

Organization Two

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

 

+


I.  Abstract

GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios.

The specification also provides patterns, profiles (most notably of Observations and Measurements — ISO19156), and best practices to deal with common geoscience use cases.

II.  Keywords

The following are keywords to be used by search engines and + document catalogues.

ogcdoc, OGC document, API, openapi, html, geology, geoscience, stratigraphy, borehole, geochemistry, geophysics, rock, fault, contact, fold, fossil, UML, GML, XML


III.  Preface

NOTE  Insert Preface Text here. Give OGC specific commentary: describe the technical content, reason for document, history of the document and precursors, and plans for future work.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

IV.  Security considerations

No security considerations have been made for this Standard.

V.  Submitting Organizations

The following organizations submitted this Document to the + Open Geospatial Consortium (OGC):

Arizona Geological Survey (AzGS), Arizona, USA

+

British Geological Survey (NERC-BGS), UK

+

Bureau de Recherches Géologiques et Minières (BRGM), France

+

Commonwealth Scientific and Industrial Research Organisation (CSIRO), Australia

+

Geological Survey of Victoria (GSV), Australia

+

Geological Survey of Finland (GTK), Finland

+

Geological Survey of Italy (ISPRA), Italy

+

Geological Survey of Sweden (SGU), Sweden

+

Geoscience Australia (GA), Australia

+

Institute of Geological and Nuclear Sciences (GNS), New Zealand

+

Landcare Research, New Zealand

+

Natural Resources Canada (NRCan), Canada

+

U.S. Geological Survey (USGS), United States of America

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliation

 


-

OGC Geoscience Markup Language

+

OGC Geoscience Markup Language - GeoSciML

1.  Scope

@@ -3089,7 +3100,7 @@ span.AdmittedLabel { -------=_NextPart_76813f2d.4980.4528 +------=_NextPart_9eb71348.c2a3.49f3 Content-ID: Content-Disposition: inline; filename="filelist.xml" Content-Transfer-Encoding: base64 @@ -3100,7 +3111,7 @@ ICAgICAgIDxvOk1haW5GaWxlIEhSZWY9Ii4uLy9fX3cvT0dDLUdlb1NjaU1ML09HQy1HZW9TY2lN TC9tYWluL2RvY3MvaW5kZXguaHRtIi8+ICA8bzpGaWxlIEhSZWY9ImZpbGVsaXN0LnhtbCIvPgog IDxvOkZpbGUgSFJlZj0iaGVhZGVyLmh0bWwiLz4KPC94bWw+Cg== -------=_NextPart_76813f2d.4980.4528 +------=_NextPart_9eb71348.c2a3.49f3 Content-ID: Content-Disposition: inline; filename="header.html" Content-Transfer-Encoding: base64 @@ -3146,12 +3157,12 @@ Rm9vdG5vdGVzXT4NCg0KPGhyIGFsaWduPWxlZnQgc2l6ZT0xPg0KDQo8IVtlbmRpZl0+PC9zcGFu Pjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpoZWFkZXIn IGlkPWVoMT4NCg0KPHAgY2xhc3M9TXNvSGVhZGVyIGFsaWduPWxlZnQgc3R5bGU9J3RleHQtYWxp Z246bGVmdDtsaW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5 -Jz48c3BhbiBsYW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7WVktOTk5 +Jz48c3BhbiBsYW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7MTYtMDA4 PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicg aWQ9aDE+DQoNCjxwIGNsYXNzPU1zb0hlYWRlciBzdHlsZT0nbWFyZ2luLWJvdHRvbToxOC4wcHQn PjxzcGFuIGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQt c2l6ZToxMS4wcHQ7Zm9udC13ZWlnaHQ6bm9ybWFsJz4NCk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0 -aXVtJm5ic3A7WVktOTk5PC9zcGFuPjxzcGFuIGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXdlaWdo +aXVtJm5ic3A7MTYtMDA4PC9zcGFuPjxzcGFuIGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXdlaWdo dDpub3JtYWwnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9 J21zby1lbGVtZW50OmZvb3RlcicgaWQ9ZWYxPg0KDQo8cCBjbGFzcz1Nc29Gb290ZXIgc3R5bGU9 J21hcmdpbi10b3A6MTIuMHB0O2xpbmUtaGVpZ2h0OjEyLjBwdDttc28tbGluZS1oZWlnaHQtcnVs @@ -3180,19 +3191,19 @@ cnRpdW0mbmJzcDsyMDIzIOKAkyBBbGwgcmlnaHRzIHJlc2VydmVkPG86cD48L286cD48L3NwYW4+ PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6aGVhZGVyJyBpZD1laDI+ DQo8cCBjbGFzcz1Nc29IZWFkZXIgYWxpZ249bGVmdCBzdHlsZT0ndGV4dC1hbGlnbjpsZWZ0O2xp bmUtaGVpZ2h0OjEyLjBwdDsNCm1zby1saW5lLWhlaWdodC1ydWxlOmV4YWN0bHknPjxzcGFuIGxh -bmc9RU4tR0I+T3BlbiBHZW9zcGF0aWFsIENvbnNvcnRpdW0mbmJzcDtZWS05OTk8L3NwYW4+PC9w +bmc9RU4tR0I+T3BlbiBHZW9zcGF0aWFsIENvbnNvcnRpdW0mbmJzcDsxNi0wMDg8L3NwYW4+PC9w Pg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicgaWQ9ZWgybD4NCjxw IGNsYXNzPU1zb0hlYWRlckxhbmRzY2FwZSBhbGlnbj1sZWZ0IHN0eWxlPSd0ZXh0LWFsaWduOmxl ZnQ7bGluZS1oZWlnaHQ6MTIuMHB0Ow0KbXNvLWxpbmUtaGVpZ2h0LXJ1bGU6ZXhhY3RseSc+PHNw -YW4gbGFuZz1FTi1HQj5PcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwO1lZLTk5OTwvc3Bh +YW4gbGFuZz1FTi1HQj5PcGVuIEdlb3NwYXRpYWwgQ29uc29ydGl1bSZuYnNwOzE2LTAwODwvc3Bh bj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6aGVhZGVyJyBpZD1oMj4N CjxwIGNsYXNzPU1zb0hlYWRlciBhbGlnbj1yaWdodCBzdHlsZT0ndGV4dC1hbGlnbjpyaWdodDts aW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48c3BhbiBs -YW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7WVktOTk5PC9zcGFuPjwv +YW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7MTYtMDA4PC9zcGFuPjwv cD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpoZWFkZXInIGlkPWgybD4NCjxw IGNsYXNzPU1zb0hlYWRlckxhbmRzY2FwZSBhbGlnbj1yaWdodCBzdHlsZT0ndGV4dC1hbGlnbjpy aWdodDtsaW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48 -c3BhbiBsYW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7WVktOTk5PC9z +c3BhbiBsYW5nPUVOLUdCPk9wZW4gR2Vvc3BhdGlhbCBDb25zb3J0aXVtJm5ic3A7MTYtMDA4PC9z cGFuPjwvcD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWVm Mj4NCjxwIGNsYXNzPU1zb0Zvb3RlciBzdHlsZT0nbGluZS1oZWlnaHQ6MTIuMHB0O21zby1saW5l LWhlaWdodC1ydWxlOmV4YWN0bHknPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9 @@ -3382,4 +3393,4 @@ YW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4w cHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KDQo8L2JvZHk+DQoNCjwvaHRtbD4N Cg== -------=_NextPart_76813f2d.4980.4528-- \ No newline at end of file +------=_NextPart_9eb71348.c2a3.49f3-- \ No newline at end of file diff --git a/docs/index.err b/docs/index.err index 997af85..49001ed 100644 --- a/docs/index.err +++ b/docs/index.err @@ -18,20 +18,20 @@ https://www.metanorma.com/author/iso/topics/markup/#bibliographies == Anchors -(XML Line 000241): Crossreference target OGC06-121r9 is undefined +(XML Line 000268): Crossreference target OGC06-121r9 is undefined -(XML Line 000299): normalised identifier in from http://www.opengis.net/spec/ABCD/m.n/req/req-class-a -

Requirements Class

  • +(XML Line 000326): normalised identifier in from http://www.opengis.net/spec/ABCD/m.n/req/req-class-a +

    Requirements Class

      • -

    • urn:iso:ts:iso:19139:clause:6

      +

    • urn:iso:ts:iso:19139:clause:6

     -(XML Line 000318): normalised identifier in from /req/req-class-a/req-name-1 -

    Requirement ‘shall’ statement

     +(XML Line 000345): normalised identifier in from /req/req-class-a/req-name-1 +

    Requirement ‘shall’ statement

         -(XML Line 000410): Crossreference target ats_core_api-definition-success is undefined +(XML Line 000437): Crossreference target ats_core_api-definition-success is undefined /conf/core/api-definition-success -(XML Line 000429): Crossreference target rfc2818 is undefined +(XML Line 000456): Crossreference target rfc2818 is undefined HTTP over TLS @@ -44,54 +44,54 @@ https://www.metanorma.com/author/iso/topics/markup/#bibliographies == Metanorma XML Style Warning -(XML Line 000054): Table should have title +(XML Line 000081): Table should have title
    Name Affiliation
    -(XML Line 000261): Hanging paragraph in clause +(XML Line 000288): Hanging paragraph in clause Conventions

    This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document.

    -(XML Line 000275): Hanging paragraph in clause +(XML Line 000302): Hanging paragraph in clause Clauses not containing normative material

    Paragraph

    -(XML Line 000289): Hanging paragraph in clause +(XML Line 000316): Hanging paragraph in clause Clause containing normative material

    Paragraph

    -(XML Line 000293): Hanging paragraph in clause +(XML Line 000320): Hanging paragraph in clause Requirement Class A or Requirement A Example

    Paragraph – intro text for the requirement class.

    Use the following table for Requirements Classes.

    -(XML Line 000323): Table should have title +(XML Line 000350): Table should have title -(XML Line 000374): Hanging paragraph in clause +(XML Line 000401): Hanging paragraph in clause Conformance Class Abstract Test Suite (Normative)

    Ensure that there is a conformance class for each requirements class and a test for each requirement (identified by requirement name and number)

     -(XML Line 000379): Hanging paragraph in clause +(XML Line 000406): Hanging paragraph in clause Conformance Class A
    label

    -(XML Line 000443): Table should have title +(XML Line 000470): Table should have title
    Names Definition Data types and values Multiplicity and use
    @@ -101,40 +101,40 @@ https://www.metanorma.com/author/iso/topics/markup/#bibliographies == Requirements -(XML Line 000299): Requirement class http___www.opengis.net_spec_ABCD_m.n_req_req-class-a has no corresponding Conformance class +(XML Line 000326): Requirement class http___www.opengis.net_spec_ABCD_m.n_req_req-class-a has no corresponding Conformance class

    Requirements Class

    • urn:iso:ts:iso:19139:clause:6

     -(XML Line 000318): Requirement _req_req-class-a_req-name-1 has no corresponding Conformance test +(XML Line 000345): Requirement _req_req-class-a_req-name-1 has no corresponding Conformance test

    Requirement ‘shall’ statement

         -(XML Line 000350): Requirement req_core_process-execute-input-inline-object has no corresponding Conformance test +(XML Line 000377): Requirement req_core_process-execute-input-inline-object has no corresponding Conformance test label/req/req-class-a/req-name-2

    1. The process input value is specified in-line in an execute request.

    2. The process input is defined as an object according to its schema.

      -(XML Line 000395): Conformance test ats_core_api-definition-op has no corresponding Requirement +(XML Line 000422): Conformance test ats_core_api-definition-op has no corresponding Requirement /req/req-class-a/req-name-1label/conf/core/api-definition-op

      Validate that the API Definition document can be retrieved from the expected location.

      Construct a path for the API Definition document that ends with /api.

       -(XML Line 000395): Conformance test ats_core_api-definition-op has no corresponding Conformance class +(XML Line 000422): Conformance test ats_core_api-definition-op has no corresponding Conformance class /req/req-class-a/req-name-1label/conf/core/api-definition-op

      Validate that the API Definition document can be retrieved from the expected location.

      Construct a path for the API Definition document that ends with /api.

       -(XML Line 000416): Conformance test ats_core_http has no corresponding Requirement +(XML Line 000443): Conformance test ats_core_http has no corresponding Requirement /req/req-class-a/req-name-2label/conf/core/http

      Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

      All compliance tests SHALL be configured to use the HTTP 1.1 protocol exclusively.

       -(XML Line 000416): Conformance test ats_core_http has no corresponding Conformance class +(XML Line 000443): Conformance test ats_core_http has no corresponding Conformance class /req/req-class-a/req-name-2label/conf/core/http

      Validate that the resource paths advertised through the API conform with HTTP 1.1 and, where appropriate, TLS.

       @@ -144,6 +144,6 @@ https://www.metanorma.com/author/iso/topics/markup/#bibliographies == Metanorma XML Syntax -(XML Line 000082:91): element "clause" not allowed here; expected the element end-tag or element "submitters" -(XML Line 000099:50): element "foreword" not allowed here; expected the element end-tag or element "clause", "definitions", "floating-title" or "terms" -(XML Line 000301:91): attribute "metadata" not allowed here; expected attribute "columns", "keep-lines-together", "keep-with-next", "key", "multilingual-rendering" or "tag" +(XML Line 000110:91): element "clause" not allowed here; expected the element end-tag or element "submitters" +(XML Line 000127:50): element "foreword" not allowed here; expected the element end-tag or element "clause", "definitions", "floating-title" or "terms" +(XML Line 000330:91): attribute "metadata" not allowed here; expected attribute "columns", "keep-lines-together", "keep-with-next", "key", "multilingual-rendering" or "tag" diff --git a/docs/index.html b/docs/index.html index 09a52b2..e53ac2f 100644 --- a/docs/index.html +++ b/docs/index.html @@ -1247,7 +1247,7 @@ color: #0000FF; } --->OGC Geoscience Markup Language +-->OGC Geoscience Markup Language - GeoSciML @@ -1265,7 +1265,7 @@ -Text here>'/>
      +

      Draft

      @@ -1286,13 +1286,13 @@
      - OGC Geoscience Markup Language + OGC Geoscience Markup Language - GeoSciML
    Date Release Editor