Fixes from 2/25/24 telecon

Keywords expanded Digital Flanders fixed Added paragraph on multiple schema and added paragraph on definitions. Fixed broken link in Abstract Test Suite Updated History Misc. other minor fixes.
opengeospatial · Feb 15, 2024 · 4f7310c · 4f7310c
1 parent 77191b7
commit 4f7310c
Show file tree

Hide file tree

Showing 16 changed files with 567 additions and 583 deletions.
diff --git a/21-049/21-049.adoc b/21-049/21-049.adoc
@@ -14,7 +14,7 @@
 :fullname_2: Matthew Brian 
 :fullname_3: John Purss
 :docsubtype: conceptual
-:keywords: ogcdoc, OGC document, API, openapi, html
+:keywords: ogcdoc, OGC document, Point of Interest, POI, Feature 
 :submitting-organizations:  Digital Flanders; Google; HeazelTech; Pangaea Innovations; PEREY Research & Consulting; US Army Geospatial Center
 :mn-document-class: ogc
 :mn-output-extensions: xml,html,doc,pdf

diff --git a/21-049/21-049.err.html b/21-049/21-049.err.html
diff --git a/21-049/21-049.html b/21-049/21-049.html
diff --git a/21-049/21-049.pdf b/21-049/21-049.pdf
diff --git a/21-049/21-049.pdf.err b/21-049/21-049.pdf.err
@@ -1,9 +1,2 @@
 The contents of fo:region-body on page 20 exceed its viewport by 9295 millipoints. (See position 1:1490)
-Page 30: Unresolved ID reference "iso19109" found.
 Page 34: Unresolved ID reference "iso19109" found.
-Page 43: Unresolved ID reference "iso19107" found.
-Page 51: Unresolved ID reference "iso19109" found.
-Page 51: Unresolved ID reference "iso19115" found.
-Page 52: Unresolved ID reference "iso19115" found.
-Page 53: Unresolved ID reference "iso19115" found.
-Page 57: Unresolved ID reference "iso19109" found.
diff --git a/21-049/21-049.presentation.xml b/21-049/21-049.presentation.xml
diff --git a/21-049/21-049.xml b/21-049/21-049.xml
diff --git a/21-049/abstract_tests/Core/ATS_Core_AbstractPOI.adoc b/21-049/abstract_tests/Core/ATS_Core_AbstractPOI.adoc
@@ -5,7 +5,7 @@
 [abstract_test]
 ====
 [%metadata]
-identifier:: /conf/core/astract-poi
+identifier:: /conf/core/abstract-poi
 target:: /req/core/abstract-poi
 inherit:: /conf/core/featurewithlifespan
 classification:: Target Type: Implementation Specification
@@ -17,7 +17,7 @@ description:: Validate that the Implementation Specification correctly implement
 
 part:: Validate that the implementation of the AbstractPOI class is also a valid implementation of the AbstractFeatureWithLifespan class using test <<ats_core_featurewithlifespan,/conf/core/featurewithlifespan>>.
 
-part:: Validate correct implementation of the `contactInfo` attribute using test <<ats_core_poi-contactinfo,/conf/core/poi-contactinfo>.
+part:: Validate correct implementation of the `contactInfo` attribute using test <<ats_core_poi-contactinfo,/conf/core/poi-contactinfo>>.
 
 part:: Validate correct implementation of the `hasFeatureOfInterest` aggregation using the test <<ats_core_poi-featureofinterest,/conf/core/poi-featureOfInterest>>.
 
@@ -50,7 +50,7 @@ description:: Validate the cardinality and type of the `contactInfo` attribute.
 
 part:: Validate that zero or more `contactInfo` attributes are allowed in an AbstractPOI class.
 
-part:: Validate that the `contactInfo` attribute is a valid implementation of the CI_Responsibility class from <<iso19115,ISO 19115-1:2014>>.
+part:: Validate that the `contactInfo` attribute is a valid implementation of the CI_Responsibility class from <<ISO19115,ISO 19115-1:2014>>.
 ====
 
 ====== Abstract POI Feature Of Interest
@@ -70,7 +70,7 @@ description:: Validate the cardinality and target class of the `hasFeatureOfInte
 
 part:: Validate that zero or more `hasFeatureOfIntestest` aggregations are allowed in an AbstractPOI class.
 
-part:: Validate that the target of the `hasFeatureOfIntestest` aggregation is a valid implementation of the Feature class from <<iso19109,ISO 19109:2015>>.
+part:: Validate that the target of the `hasFeatureOfIntestest` aggregation is a valid implementation of the Feature class from <<ISO19109,ISO 19109:2015>>.
 ====
 
 ====== Abstract POI Metadata
@@ -110,7 +110,7 @@ description:: Validate the cardinality and type of the `keywords` attribute.
 
 part:: Validate that zero or more `keywords` attributes are allowed in an AbstractPOI class.
 
-part:: Validate that the `keywords` attribute is a valid implementation of the MD_Keywords class from <<iso19115,ISO 19115-1:2014>>.
+part:: Validate that the `keywords` attribute is a valid implementation of the MD_Keywords class from <<ISO19115,ISO 19115-1:2014>>.
 ====
 
 ====== Abstract POI Rights
@@ -130,7 +130,7 @@ description:: Validate the cardinality and type of the `rights` attribute.
 
 part:: Validate that zero, one, or two `rights` attributes are allowed in an AbstractPOI class.
 
-part:: Validate that the `contactInfo` attribute is a valid implementation of the MD_Constraints class from <<iso19115,ISO 19115-1:2014>>.
+part:: Validate that the `contactInfo` attribute is a valid implementation of the MD_Constraints class from <<ISO19115,ISO 19115-1:2014>>.
 ====
 
 ====== Abstract POI Symbology

diff --git a/21-049/abstract_tests/Core/ATS_Core_Geometry.adoc b/21-049/abstract_tests/Core/ATS_Core_Geometry.adoc
@@ -10,7 +10,7 @@ target:: /req/core/geometry
 
 classification:: Target Type: Implementation Specification
 
-test-purpose:: To validate that the POI Implementation Specification is conformant with the <<iso19107,ISO 19107>> Geometry Model.
+test-purpose:: To validate that the POI Implementation Specification is conformant with the <<ISO19107,ISO 19107>> Geometry Model.
 
 test-method-type:: Manual Inspection
 

diff --git a/21-049/abstract_tests/Core/ATS_Core_POI_Payload.adoc b/21-049/abstract_tests/Core/ATS_Core_POI_Payload.adoc
@@ -78,7 +78,7 @@ description:: Validate the cardinality and target class of the `hasFeatureOfInte
 
 part:: Validate that zero or more `hasFeatureOfIntestest` aggregations are allowed in an POI_Payload class.
 
-part:: Validate that the target of the `hasFeatureOfInterest` aggregation is a valid implementation of the Feature class from <<iso19109,ISO 19109:2015>>.
+part:: Validate that the target of the `hasFeatureOfInterest` aggregation is a valid implementation of the Feature class from <<ISO19109,ISO 19109:2015>>.
 ====
 
 
diff --git a/21-049/requirements/Core/Req_Core_AbstractFeature.adoc b/21-049/requirements/Core/Req_Core_AbstractFeature.adoc
@@ -53,7 +53,7 @@ An encoding of the AbstractFeature class SHALL include zero or one `description`
 
 [.component,class=part]
 --
-Encodings of the `description` attribute SHALL be a valid implementation of the CharacterString class from ISO 19103.
+Encodings of the `description` attribute SHALL be a valid implementation of the CharacterString class from <<ISO19103,ISO 19103>>.
 --
 ====
 
@@ -75,7 +75,7 @@ An encoding of the AbstractFeature class SHALL include one `featureID` attribute
 
 [.component,class=part]
 --
-Encodings of the `featureID` attribute SHALL be a valid implementation of the GenericName class from ISO 19103.
+Encodings of the `featureID` attribute SHALL be a valid implementation of the GenericName class from <<ISO19103,ISO 19103>>.
 --
 ====
 
@@ -97,7 +97,7 @@ An encoding of the AbstractFeature class SHALL include zero or one `identifier`
 
 [.component,class=part]
 --
-Encodings of the `identifier` attribute SHALL be a valid implementation of the ScopedName class from ISO 19103.
+Encodings of the `identifier` attribute SHALL be a valid implementation of the ScopedName class from <<ISO19103,ISO 19103>>.
 --
 ====
 
@@ -119,6 +119,6 @@ An encoding of the AbstractFeature class SHALL include zero or more `name` attri
 
 [.component,class=part]
 --
-Encodings of the `name` attribute SHALL be a valid implementation of the GenericName class from ISO 19103.
+Encodings of the `name` attribute SHALL be a valid implementation of the GenericName class from <<ISO19103,ISO 19103>>.
 --
 ====
diff --git a/21-049/requirements/Core/Req_Core_AbstractPOI.adoc b/21-049/requirements/Core/Req_Core_AbstractPOI.adoc
@@ -70,7 +70,7 @@ An encoding of the Abstract POI class SHALL include one or more `contactInfo` at
 
 [.component,class=part]
 --
-Encodings of the `contactInfo` attribute SHALL be a valid implementation of the CI_Responsibility class from ISO 19115-1:2014
+Encodings of the `contactInfo` attribute SHALL be a valid implementation of the CI_Responsibility class from <<ISO19115,ISO 19115-1:2014>>
 --
 ====
 
@@ -92,7 +92,7 @@ An encoding of the Abstract POI class SHALL include zero or more associated inst
 
 [.component,class=part]
 --
-The target of the `hasFeatureOfIntestest` aggregation SHALL be a valid implementation of the Feature class from <<iso19109,ISO 19109:2015>>
+The target of the `hasFeatureOfIntestest` aggregation SHALL be a valid implementation of the Feature class from <<ISO19109,ISO 19109:2015>>
 --
 ====
 
@@ -136,7 +136,7 @@ An encoding of the Abstract POI class SHALL include zero or more `keywords` attr
 
 [.component,class=part]
 --
-Encodings of the `keywords` attribute SHALL be a valid implementation of the MD_Keywords class from ISO 19115-1:2014
+Encodings of the `keywords` attribute SHALL be a valid implementation of the MD_Keywords class from <<ISO19115,ISO 19115-1:2014>>.
 --
 ====
 
@@ -158,7 +158,7 @@ An encoding of the Abstract POI class SHALL include zero, one, or two `rights` a
 
 [.component,class=part]
 --
-Encodings of the `rights` attribute SHALL be a valid implementation of the MD_Constraints class from ISO 19115-1:2014
+Encodings of the `rights` attribute SHALL be a valid implementation of the MD_Constraints class from <<ISO19115,ISO 19115-1:2014>>.
 --
 ====
 

diff --git a/21-049/requirements/Core/Req_Core_Feature_With_Lifespan.adoc b/21-049/requirements/Core/Req_Core_Feature_With_Lifespan.adoc
@@ -54,7 +54,7 @@ An encoding of the AbstractFeatureWithLifespan class SHALL include zero or one `
 
 [.component,class=part]
 --
-Encodings of the `creationDate` attribute SHALL be a valid implementation of the DateTime class from ISO 19103.
+Encodings of the `creationDate` attribute SHALL be a valid implementation of the DateTime class from <<ISO19103,ISO 19103>>.
 --
 ====
 
@@ -76,7 +76,7 @@ An encoding of the AbstractFeatureWithLifespan class SHALL include zero or one `
 
 [.component,class=part]
 --
-Encodings of the `terminationDate` attribute SHALL be a valid implementation of the DateTime class from ISO 19103.
+Encodings of the `terminationDate` attribute SHALL be a valid implementation of the DateTime class from <<ISO19103,ISO 19103>>.
 --
 ====
 
@@ -98,7 +98,7 @@ An encoding of the AbstractFeatureWithLifespan class SHALL include zero or one `
 
 [.component,class=part]
 --
-Encodings of the `validFrom` attribute SHALL be a valid implementation of the DateTime class from ISO 19103.
+Encodings of the `validFrom` attribute SHALL be a valid implementation of the DateTime class from <<ISO19103,ISO 19103>>.
 --
 ====
 
@@ -120,7 +120,7 @@ An encoding of the AbstractFeatureWithLifespan class SHALL include zero or one `
 
 [.component,class=part]
 --
-Encodings of the `validTo` attribute SHALL be a valid implementation of the DateTime class from ISO 19103.
+Encodings of the `validTo` attribute SHALL be a valid implementation of the DateTime class from <<ISO19103,ISO 19103>>.
 --
 ====
 
diff --git a/21-049/sections/annex-bibliography.adoc b/21-049/sections/annex-bibliography.adoc
@@ -13,7 +13,7 @@
 * [[[ISO19136-1,ISO 19136-1]]]
 * [[[ISO1087-1,ISO 1087-1]]]
 * [[[ISO19104,ISO 19104]]]
-* [[[ISO19150-1,ISO 19150-1]]] nofetch
+* [[[ISO19150-1,ISO 19150-1]]] _Geographic information — Ontology — Part 1: Framework._ International Organization for Standardization, Geneva https://www.iso.org/standard/57465.html[https://www.iso.org/standard/57465.html].
 * [[[ISO19150-2,ISO 19150-2]]]
 * [[[ISO19150-4,ISO 19150-4]]]
 * [[[ISO19160-4,ISO 19160-4]]]

diff --git a/21-049/sections/annex-history.adoc b/21-049/sections/annex-history.adoc
@@ -5,6 +5,5 @@
 |===
 |Date |Release |Editor | Primary clauses modified |Description
 |2021-06-17 |0.0.1 |Matthew Purss |all |initial version
-|2021-07-08 |0.0.1 |Matthew Purss |Clause 1 | initial scope text inserted from original POI draft standard
-|2021-07-09 |0.0.1 |Matthew Purss |Clause 4 | initial terms inserted from original POI draft standard (and reformatted to meet formal definition requirements)
+|2024-02-15 |1.0.0 |Chuck Heazel |all | POI draft standard for OAB review
 |===
diff --git a/21-049/sections/clause_7_normative_text.adoc b/21-049/sections/clause_7_normative_text.adoc
@@ -108,5 +108,9 @@ image::./images/POI_Extensions.png[align="center"]
 
 In the interest of interoperability, the POI Payload should be constructed using data types and concepts which are already in wide use by the Geospatial community. A collection of data types and concepts defined by the <<ISO19103,ISO 19103>>, <<ISO19107,ISO 19107>>, <<ISO19109,ISO 19109>>, and <<ISO19115,ISO 19115>> Standards is provided in <<iso_data_dictionary_section,Annex B>>.
 
+While the POI Payload should have a single syntactic model (schema), there may be more than one way to represent that model. For example, JSON Schemas are commonly provided using both JSON and YAML encodings. The POI abstract model allows a POI Payload to have mutiple `usesSchema` aggregations in order to support this practice. 
+
+The `hasDefinition` aggregation is provided in anticipation of the future use of ontologies to associate meaning (semantics) with the structure (syntax) of the POI Payload. Use of the `hasDefinition` aggregation is optional.  
+
 include::../requirements/core/Req_Core_POI-Payload.adoc[]