]> and does not modify that standard."
+ "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the ogc URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -12644,35 +12614,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "20-006"
+ "@value": "05-096r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC CDB Version 1.2 Release Notes"
+ "@value": "GML 3.1.1 grid CRSs profile"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/11-110",
+ "@id": "http://www.opengis.net/def/docs/08-068r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2011-08-11"
+ "@value": "2021-06-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Arnulf Christl and Carl Reed"
+ "@value": "Peter Baumann"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/techpaper"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -12682,27 +12652,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=45126"
+ "@id": "https://docs.ogc.org/is/08-068r3/08-068r3.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Open Source and Open Standards"
+ "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard"
},
{
"@language": "en",
- "@value": "11-110"
+ "@value": "08-068r3"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/techpaper"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This article is a White Paper jointly published by OGC and OSGeo. It was approved as an official joint OSGeo and OGC White Paper by the OSGeo Board of Directors in their 2011-05-05 Board meeting. \r\nThe text was collaboratively edited, reviewed and finalized by more than a a dozen active OSGeo and OGC members. Thanks especially to Gavin Fleming, Lance McKee, Markus Neteler, Athina Trakas, Michael Gerlek, Adrian Custer, Jeff McKenna, Cameron Shorter, Carl Reed, Frank Warmerdam, Steven Ramage, Daniel Morissette, Arnulf Christl and others for their contributions.\r\nPlease feel free to add comments, criticisms, links to other concise definitions on the associated Talk page: http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards."
+ "@value": "The OGC Web Coverage Processing Service (WCPS) defines a protocol-independent language for on-demand extraction, processing, and analysis of multi-dimensional gridded coverages (datacubes) representing among others spatio-temporal sensor, image, simulation, or statistics data."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -12713,35 +12683,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "11-110"
+ "@value": "08-068r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Open Source and Open Standards"
+ "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-086r1",
+ "@id": "http://www.opengis.net/def/docs/16-005r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-11-03"
+ "@value": "2017-02-23"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Josh Lieberman, Johannes Echterhoff, Matt de Ris, George Wilber"
+ "@value": "Carl Reed"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -12751,27 +12721,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/60176"
+ "@id": "https://portal.ogc.org/files/?artifact_id=72713"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report"
+ "@value": "16-005r2"
},
{
"@language": "en",
- "@value": "14-086r1"
+ "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® document summarizes the Aircraft Access to SWIM (AAtS) Harmonization activity developed by a team funded by the FAA and led by the Open Geospatial Consortium (OGC). The activity involved assembling a core team of industry participant experts to analyze and harmonize four standards suites and/or standards-based architectures relevant to air-ground information exchange:\r\n•\tThe Aircraft Access to SWIM (AAtS) concept, \r\n•\tRTCA aeronautical information services (AIS) and meteorological (MET) information data link service committee’s (SC-206) concepts and standards, \r\n•\tAir-Ground Information Exchange A830 (AGIE) standard and \r\n•\tOGC standards and architectural perspectives. \r\nElements of this effort have included:\r\n•\tCreation and public release of a Request for Information\r\n•\tAnalysis of the fits and overlaps between the four standards suites\r\n•\tEngagement with ongoing standards development efforts to reduce incompatibilities\r\n"
+ "@value": "This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -12782,296 +12752,350 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-086r1"
+ "@value": "16-005r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report"
+ "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes"
}
]
},
{
- "@id": "http://www.opengis.net/def/doc-type/bp",
- "http://www.w3.org/2004/02/skos/core#narrower": [
- {
- "@id": "http://www.opengis.net/def/docs/21-007"
- },
+ "@id": "http://www.opengis.net/def/docs/15-027r1",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Concept"
+ ],
+ "http://purl.org/dc/terms/created": [
{
- "@id": "http://www.opengis.net/def/docs/14-004r1"
- },
+ "@type": "xsd:date",
+ "@value": "2016-01-18"
+ }
+ ],
+ "http://purl.org/dc/terms/creator": [
{
- "@id": "http://www.opengis.net/def/docs/21-070"
- },
+ "@value": "Aleksandar Balaban"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/docs/11-135r2"
- },
+ "@id": "http://www.opengis.net/def/doc-type/per"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/status": [
{
- "@id": "http://www.opengis.net/def/docs/16-005r4"
- },
+ "@id": "http://www.opengis.net/def/status/valid"
+ }
+ ],
+ "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "http://www.opengis.net/def/docs/17-011r2"
- },
+ "@id": "https://portal.ogc.org/files/?artifact_id=64141"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#altLabel": [
{
- "@id": "http://www.opengis.net/def/docs/16-003r4"
+ "@language": "en",
+ "@value": "Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report"
},
{
- "@id": "http://www.opengis.net/def/docs/16-011r4"
- },
+ "@language": "en",
+ "@value": "15-027r1"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/docs/09-102r3"
- },
+ "@id": "http://www.opengis.net/def/doc-type/per"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#definition": [
{
- "@id": "http://www.opengis.net/def/docs/16-003r2"
- },
+ "@value": "This OGC Engineering Report (ER) is a deliverable of the OGC Testbed 11. This ER describes the Digital Notice to Airmen (NOTAM) enrichment and validation services in the Testbed 11 Aviation thread, including:\r\n•\tA description of the architecture and architectural options.\r\n•\tAn overview of the implemented components and workflows followed by a short description of each component.\r\n•\tDocumentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread.\r\nMore detailed information on other specific aspects considered in OWS-11 Aviation may be found in the individual Aviation Engineering Reports.\r\n"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/docs/07-063r1"
- },
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#notation": [
{
- "@id": "http://www.opengis.net/def/docs/15-107"
- },
+ "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
+ "@value": "15-027r1"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@id": "http://www.opengis.net/def/docs/15-120r4"
- },
+ "@language": "en",
+ "@value": "OGC® Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-129",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Concept"
+ ],
+ "http://purl.org/dc/terms/created": [
{
- "@id": "http://www.opengis.net/def/docs/15-005r2"
- },
+ "@type": "xsd:date",
+ "@value": "2017-03-31"
+ }
+ ],
+ "http://purl.org/dc/terms/creator": [
{
- "@id": "http://www.opengis.net/def/docs/16-011r5"
- },
+ "@value": "Ingo Simonis, Rob Atkinson"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/docs/02-007r4"
- },
+ "@id": "http://www.opengis.net/def/doc-type/dp"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/status": [
{
- "@id": "http://www.opengis.net/def/docs/10-028r1"
- },
+ "@id": "http://www.opengis.net/def/status/valid"
+ }
+ ],
+ "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "http://www.opengis.net/def/docs/20-095"
- },
+ "@id": "https://portal.ogc.org/files/?artifact_id=70328"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#altLabel": [
{
- "@id": "http://www.opengis.net/def/docs/16-003r3"
+ "@language": "en",
+ "@value": "16-129"
},
{
- "@id": "http://www.opengis.net/def/docs/13-043"
- },
+ "@language": "en",
+ "@value": "Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/docs/07-107r3"
- },
+ "@id": "http://www.opengis.net/def/doc-type/dp"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#definition": [
{
- "@id": "http://www.opengis.net/def/docs/14-003"
- },
+ "@value": "This discussion paper describes a data model for the standardized exchange of citizen science sampling data. To do that it applies the Sensor Web Enablement (SWE) to Citizen Science (SWE4CS). In particular, exposes how Observations and Measurements (O&M) can be used to model the data of the Citizen Science project, in a way that can be retrieved using Sensor Observing System (SOS).This discussion paper is a result of the research project Citizen Observatory Web (COBWEB). COBWEB is supported by the European Commission through grant agreement 308513"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/docs/15-003"
- },
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#notation": [
{
- "@id": "http://www.opengis.net/def/docs/16-005r2"
- },
+ "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
+ "@value": "16-129"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@id": "http://www.opengis.net/def/docs/12-066"
- },
+ "@language": "en",
+ "@value": "Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-176r1",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Concept"
+ ],
+ "http://purl.org/dc/terms/created": [
{
- "@id": "http://www.opengis.net/def/docs/16-009r5"
- },
+ "@type": "xsd:date",
+ "@value": "2009-07-29"
+ }
+ ],
+ "http://purl.org/dc/terms/creator": [
{
- "@id": "http://www.opengis.net/def/docs/16-004r3"
- },
+ "@value": "Andreas Matheus"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/docs/06-021r4"
- },
+ "@id": "http://www.opengis.net/def/doc-type/per"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/status": [
{
- "@id": "http://www.opengis.net/def/docs/14-110r2"
- },
+ "@id": "http://www.opengis.net/def/status/valid"
+ }
+ ],
+ "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "http://www.opengis.net/def/docs/03-002r9"
- },
+ "@id": "https://portal.ogc.org/files/?artifact_id=34273"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#altLabel": [
{
- "@id": "http://www.opengis.net/def/docs/16-006r5"
+ "@language": "en",
+ "@value": "OWS-6 Secure Sensor Web Engineering Report"
},
{
- "@id": "http://www.opengis.net/def/docs/17-084r1"
- },
+ "@language": "en",
+ "@value": "08-176r1"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/docs/06-142r1"
- },
+ "@id": "http://www.opengis.net/def/doc-type/per"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#definition": [
{
- "@id": "http://www.opengis.net/def/docs/07-018r2"
- },
+ "@value": "The main purpose of this Engineering Report is to introduce standards-based security solutions for making the existing OGC Sensor Web Services, as described in the OWS-6 SWE baseline, ready towards the handling of sensors in the intelligence domain."
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/docs/15-120r6"
- },
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#notation": [
{
- "@id": "http://www.opengis.net/def/docs/12-032r2"
- },
+ "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
+ "@value": "08-176r1"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@id": "http://www.opengis.net/def/docs/07-097"
- },
+ "@language": "en",
+ "@value": "OWS-6 Secure Sensor Web Engineering Report"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-036",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Concept"
+ ],
+ "http://purl.org/dc/terms/created": [
{
- "@id": "http://www.opengis.net/def/docs/12-111r1"
- },
+ "@type": "xsd:date",
+ "@value": "2007-10-05"
+ }
+ ],
+ "http://purl.org/dc/terms/creator": [
{
- "@id": "http://www.opengis.net/def/docs/16-004r4"
- },
+ "@value": "Clemens Portele"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/docs/16-140r1"
- },
+ "@id": "http://www.opengis.net/def/doc-type/is"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/status": [
{
- "@id": "http://www.opengis.net/def/docs/16-070r3"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-010r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/21-068"
- },
- {
- "@id": "http://www.opengis.net/def/docs/08-139r3"
- },
- {
- "@id": "http://www.opengis.net/def/docs/08-167r2"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-006r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/15-037"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-011r3"
- },
- {
- "@id": "http://www.opengis.net/def/docs/20-089r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-004r5"
- },
- {
- "@id": "http://www.opengis.net/def/docs/11-169r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/14-012r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/07-118r9"
- },
- {
- "@id": "http://www.opengis.net/def/docs/08-125r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-010r5"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-114r3"
- },
- {
- "@id": "http://www.opengis.net/def/docs/05-035r2"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-009r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/07-118r8"
- },
- {
- "@id": "http://www.opengis.net/def/docs/16-070r2"
- },
- {
- "@id": "http://www.opengis.net/def/docs/05-042r2"
- },
- {
- "@id": "http://www.opengis.net/def/docs/14-106"
- },
- {
- "@id": "http://www.opengis.net/def/docs/11-122r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/06-129r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/11-035r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/07-092r3"
- },
+ "@id": "http://www.opengis.net/def/status/valid"
+ }
+ ],
+ "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "http://www.opengis.net/def/docs/15-120r5"
- },
+ "@id": "https://portal.ogc.org/files/?artifact_id=20509"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#altLabel": [
{
- "@id": "http://www.opengis.net/def/docs/06-188r1"
+ "@language": "en",
+ "@value": "07-036"
},
{
- "@id": "http://www.opengis.net/def/docs/10-189r2"
- },
+ "@language": "en",
+ "@value": "Geography Markup Language (GML) Encoding Standard"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/docs/15-004"
- },
+ "@id": "http://www.opengis.net/def/doc-type/is"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#definition": [
{
- "@id": "http://www.opengis.net/def/docs/13-039"
- },
+ "@value": "The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data.\r\nA GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it.\r\n\r\nClients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. \r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/docs/16-086r3"
- },
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#notation": [
{
- "@id": "http://www.opengis.net/def/docs/16-009r3"
- },
+ "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
+ "@value": "07-036"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@id": "http://www.opengis.net/def/docs/06-095"
- },
+ "@language": "en",
+ "@value": "OpenGIS Geography Markup Language (GML) Encoding Standard"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/d-rp",
+ "http://www.w3.org/2004/02/skos/core#narrower": [
{
- "@id": "http://www.opengis.net/def/docs/06-126r2"
+ "@id": "http://www.opengis.net/def/docs/03-064r5"
},
{
- "@id": "http://www.opengis.net/def/docs/10-003r1"
+ "@id": "http://www.opengis.net/def/docs/01-029"
},
{
- "@id": "http://www.opengis.net/def/docs/13-042"
+ "@id": "http://www.opengis.net/def/docs/04-019r2"
},
{
- "@id": "http://www.opengis.net/def/docs/16-006r3"
+ "@id": "http://www.opengis.net/def/docs/04-016r3"
},
{
- "@id": "http://www.opengis.net/def/docs/19-066"
+ "@id": "http://www.opengis.net/def/docs/03-022r3"
},
{
- "@id": "http://www.opengis.net/def/docs/16-005r3"
+ "@id": "http://www.opengis.net/def/docs/03-010r9"
},
{
- "@id": "http://www.opengis.net/def/docs/13-015"
+ "@id": "http://www.opengis.net/def/docs/02-024"
},
{
- "@id": "http://www.opengis.net/def/docs/09-102"
+ "@id": "http://www.opengis.net/def/docs/01-014r5"
},
{
- "@id": "http://www.opengis.net/def/docs/09-153r1"
+ "@id": "http://www.opengis.net/def/docs/03-010r7"
},
{
- "@id": "http://www.opengis.net/def/docs/15-005r1"
+ "@id": "http://www.opengis.net/def/docs/02-066r1"
},
{
- "@id": "http://www.opengis.net/def/docs/06-028r3"
+ "@id": "http://www.opengis.net/def/docs/00-029"
},
{
- "@id": "http://www.opengis.net/def/docs/16-010r3"
+ "@id": "http://www.opengis.net/def/docs/03-088r6"
},
{
- "@id": "http://www.opengis.net/def/docs/16-070r4"
+ "@id": "http://www.opengis.net/def/docs/03-109r1"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-129r1",
+ "@id": "http://www.opengis.net/def/docs/16-004r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-12-26"
+ "@value": "2018-12-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Patrick Neal, John Davidson, Bruce Westcott"
+ "@value": "Carl Reed"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13086,17 +13110,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=16936"
+ "@id": "https://portal.ogc.org/files/16-004r4"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "06-129r1"
+ "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models"
},
{
"@language": "en",
- "@value": "FGDC CSDGM Application Profile for CSW 2.0"
+ "@value": "16-004r4"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13106,7 +13130,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW 2.0 explains how Catalogue Services based on the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html] Application Profile for the OpenGIS® Catalogue Service Interface Standard v2.0.1 [http://www.opengeospatial.org/standards/cs] are organized and implemented for the discovery, retrieval and management of data metadata."
+ "@value": "This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. \r\nPlease note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13117,30 +13141,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-129r1"
+ "@value": "16-004r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "FGDC CSDGM Application Profile for CSW 2.0"
+ "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-044",
+ "@id": "http://www.opengis.net/def/docs/21-035r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2015-02-02"
+ "@value": "2022-03-31"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Lew Leinenweber"
+ "@value": "Ronald Tse, Nick Nicholas"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13155,17 +13179,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=61108"
+ "@id": "https://docs.ogc.org/per/21-035r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed 10 Summary Engineering Report"
+ "@value": "21-035r1"
},
{
"@language": "en",
- "@value": "14-044"
+ "@value": "OGC Testbed-17: Model-Driven Standards Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13175,7 +13199,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OGC Testbed 10 was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for Testbed 10 was conducted between October 2013 and April 2014."
+ "@value": "This OGC Testbed 17 Engineering Report is deliverable D022 of the OGC Testbed 17 initiative performed under the OGC Innovation Program, incorporating the D022, D143 and D144 tasks that have produced Model Driven Architecture (MDA) tools.\r\n\r\nThis ER:\r\n\r\ndetails state-of-the-art analyses of existing MDA tools with their capabilities and limits; and\r\n\r\nprovides clear recommendations on how model-driven design can be fully exploited in the context of rich data model and API design efforts.\r\n\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13186,35 +13210,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-044"
+ "@value": "21-035r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Testbed 10 Summary Engineering Report"
+ "@value": "OGC Testbed-17: Model-Driven Standards Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/08-126",
+ "@id": "http://www.opengis.net/def/docs/05-015",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2009-01-15"
+ "@value": "2005-01-27"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Cliff Kottman and Carl Reed"
+ "@value": "Barry Schlesinger"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/as"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13224,27 +13248,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=29536"
+ "@id": "https://portal.ogc.org/files/?artifact_id=8826"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "08-126"
+ "@value": "05-015"
},
{
"@language": "en",
- "@value": "Topic 05 - Features"
+ "@value": "Imagery Metadata"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/as"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "From ISO 19101, “A feature is an abstraction of a real world phenomenon”; it is a geographic feature if it is associated with a location relative to the Earth. "
+ "@value": "Special XML schemas have been created for individual data sets, based on ISO 19115 and a general schema for the RSE. However, a generalized metadata XML schema should be available where possible; it should not be necessary to create special schemas for each data set. ISO 19139 can serve as such a general XML implementation specification for 19115. This implementation needs to be tested in practice. In addition, the new ISO standards are incorporating much, if not all, of the metadata not in 19115 that the RSE contain. XML schemas for these metadata need to be developed that are based upon the abstract model in the ISO standards. All of these implementations need to be tested in practice. This Report describes such tests and the results. It also describes to what extent metadata on which the test metadata are based are supported by 19139, to what extent they are supported by metadata specified in the new ISO standards or the RSE, and to what extent new metadata elements are needed. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13255,35 +13279,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "08-126"
+ "@value": "05-015"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Topic 5 - Features"
+ "@value": "Imagery Metadata"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-060r2",
+ "@id": "http://www.opengis.net/def/docs/03-029",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-11-27"
+ "@value": "2003-01-20"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Daniel Lee"
+ "@value": "Stephane Fellah, Steven Keens"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13293,27 +13317,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/16-060r2/16-060r2.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=1315"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "16-060r2"
+ "@value": "03-029"
},
{
"@language": "en",
- "@value": "GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile"
+ "@value": "OWS Messaging Framework"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC standard is a profile of the OGC GML Application Schema - Coverages version 1.0 [OC 09-146r2]. That document was renamed OGC Coverage Implementation Schema (CIS) for clarification in version 1.1. This standard specifies the usage of the GRIB2 data format for the encoding of OGC coverages. The GRIB2 specification is maintained by the World Meteorological Organization (WMO) and is the standard encoding for the exchange and storage of general regularly distributed information expressed in binary form."
+ "@value": "This document defines a messaging framework to conduct communications between the OGC web services. It is independent of any transport protocol and any messaging encoding. By using the framework, the service designer could focus only on the message definitions and messaging flows for every action supported by the service, without worry on the messaging transport and delivery. The framework should considerably simplify the implementations of the OGC web services and should enable service chaining."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13324,35 +13348,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-060r2"
+ "@value": "03-029"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile"
+ "@value": "OWS Messaging Framework"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/17-059",
+ "@id": "http://www.opengis.net/def/docs/18-005r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-10-30"
+ "@value": "2019-02-08"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Lars Schylberg, Lubos Belka"
+ "@value": "Roger Lott"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13362,27 +13386,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/dp/17-059/17-059.html"
+ "@id": "https://docs.ogc.org/as/18-005r4/18-005r4.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "17-059"
+ "@value": "18-005r4"
},
{
"@language": "en",
- "@value": "Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC"
+ "@value": "Topic 02 - Referencing by coordinates"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The DGIWG Portrayal Technical Panel (DPTP) has been investigating how to standardize the portrayal of military context symbology within Web Services. The team sought to use version 1.1.0 of OGC Style Layer Descriptor standard and version 1.1.0 of Symbology Encoding (SLD and SE) standard to achieve this.\r\nThe team sought to apply military-specific symbology to military-specific topographic feature vector datasets within a number of software products.\r\nThe testing and experimentation highlighted a number of deficiencies in the SLD and SE standards which result in a barrier to interoperability. The ideal situation would be to have SLD and SE descriptors interoperable between all software products that implement the standard. This was found not to be the current situation.\r\nThis position paper describes the findings and outlines recommendations for a revised future version of the SLD and SE standards that resolves these issues.\r\n"
+ "@value": "This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13393,30 +13417,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "17-059"
+ "@value": "18-005r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC"
+ "@value": "Topic 2 - Referencing by coordinates"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-131r6",
+ "@id": "http://www.opengis.net/def/docs/16-120r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-02-10"
+ "@value": "2017-03-12"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Frédéric Houbie, Lorenzo Bigagli"
+ "@value": "Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13431,17 +13455,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=35528"
+ "@id": "https://docs.ogc.org/is/16-120r3/16-120r3.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products"
+ "@value": "16-120r3"
},
{
"@language": "en",
- "@value": "06-131r6"
+ "@value": "Moving Features Access"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13451,7 +13475,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management."
+ "@value": "This document defines Moving Features Access, i.e., access methods to moving feature data for retrieving feature attributes, information on a relation between a trajectory object and one or more geometry objects, and information on a relation between two trajectory objects from a database storing trajectory data of moving features.\r\n\r\nAbstract methods of accessing moving features data are defined in ISO 19141:2008 (Geographic information - Schema for moving features) [ISO 19141:2008]. However, the methods are insufficient to access a database storing moving feature data from multiple sources. If implementations for access to moving features data using various programming languages or protocols (e.g., SQL, Java, and HTTP) are developed without any standards, these implementations might be inconsistent with each other, resulting in poor interoperability. Therefore, methods to access a database storing moving feature data are necessary to improve interoperability.\r\n\r\nApplications using moving feature data, typically representing vehicles or pedestrians, are rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create greater social and business value. Moreover, systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications.\r\n\r\nMoving Features Access ensures better data exchange by handling and integrating moving feature data to broaden the market for geo-spatial information such as Geospatial Big Data Analysis. OGC 14-083r2 (OGC® Moving Features Encoding Part I: XML Core) [OGC 14-083r2] and OGC 14-084r2 (OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)) [OGC 14-084r2] are existing implementation standards. Moving Features Access uses these standards to encode moving features."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13462,30 +13486,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-131r6"
+ "@value": "16-120r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products"
+ "@value": "OGC Moving Features Access"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-084r1",
+ "@id": "http://www.opengis.net/def/docs/09-010",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2009-10-13"
+ "@value": "2009-07-27"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jo Walsh, Pedro Gonçalves, Andrew Turner"
+ "@value": "Kristin Stock"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13500,17 +13524,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=35983"
+ "@id": "http://portal.opengeospatial.org/files/?artifact_id=32620"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "09-084r1"
+ "@value": "OGC® Catalogue Services - OWL Application Profile of CSW"
},
{
"@language": "en",
- "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard"
+ "@value": "09-010"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13520,7 +13544,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org."
+ "@value": "This document describes an Application Profile for the Web Ontology Language (OWL) [W3C OWL] for CSW. It is intended to define a specification for how ontologies built using RDF and OWL may be included within an OGC CSW catalogue to semantically-enable the catalogue."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13531,35 +13555,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-084r1"
+ "@value": "09-010"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard"
+ "@value": "OGC® Catalogue Services - OWL Application Profile of CSW"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-064r2",
+ "@id": "http://www.opengis.net/def/docs/16-142",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2009-09-11"
+ "@value": "2020-09-17"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Ingo Simonis"
+ "@value": "Rob Atkinson"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13569,27 +13593,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=34147"
+ "@id": "https://www.w3.org/TR/qb4st/"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "09-064r2"
+ "@value": "QB4ST: RDF Data Cube extensions for spatio-temporal components"
},
{
"@language": "en",
- "@value": "OWS-6 Sensor Web Enablement (SWE) Engineering Report"
+ "@value": "16-142"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread. "
+ "@value": "This document describes an extension to the existing RDF Data Cube ontology to support specification of key metadata required to interpret spatio-temporal data. The RDF Data Cube defines CodedProperties, which relate to a reference system based on a list of terms, QB4ST provides generalized support for numeric and other ordered references systems, particularly Spatial Reference Systems and Temporal Reference Systems. Although RDF Data Cube supports AttributeProperties for metadata of individual observations, the requirement is to specify such metadata per property, rather than for each observation, and thus allow different properties to use different spatial or temporal reference systems. QB4ST also provides for such properties to be defined for a ComponentProperty, or defined at the time of referencing that ComponentProperty in a ComponentSpecification. QB4ST is thus aimed at improving the scope and consistency of dataset metadata, and hence discovery and interpretation of spatio-temporal data through its spatio-temporal reference system and bounding values."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13600,30 +13624,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-064r2"
+ "@value": "16-142"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-6 Sensor Web Enablement (SWE) Engineering Report"
+ "@value": "QB4ST: RDF Data Cube extensions for spatio-temporal components"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/20-011",
+ "@id": "http://www.opengis.net/def/docs/16-039r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2020-05-04"
+ "@value": "2017-06-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Sara Saeedi"
+ "@value": "Aleksandar Balaban"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13638,17 +13662,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/20-011.html"
+ "@id": "https://docs.ogc.org/per/16-039r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "SCIRA Pilot Engineering Report"
+ "@value": "Testbed-12 Aviation Semantics Engineering Report"
},
{
"@language": "en",
- "@value": "20-011"
+ "@value": "16-039r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13658,7 +13682,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This engineering report (ER) captures Smart City Interoperability Reference Architecture (SCIRA) Pilot implementation outcomes and findings to demonstrate the risk mitigation and safety capability of the SCIRA interoperable and standard-based architecture. SCIRA Pilot is an OGC (Open Geospatial Consortium) Innovation Program project sponsored by the US Department of Homeland Security (DHS) Science & Technology (S&T) in collaboration with the city of St. Louis, Missouri. The purpose of this project is to advance standards for smart and safe cities and develop open, interoperable design patterns for incorporating the Internet of Things (IoT) sensors into city services."
+ "@value": "This engineering report examines the role of geospatial semantic technology in the domain of civil aviation. Many aeronautical services (providing information on request or processing the data) are based on OGC Web Service specifications. A number of aeronautical services possess geospatial attributes. The aviation services follow OWS Common Service requirements but also have domain specific capabilities. Services metadata is often very relevant for service consumption, especially in the SOA environment of aviation’s System Wide Information Management (SWIM). Therefore, it shall be exposed to consumer stakeholders for either design or runtime service discovery in an efficient, standardized way.\r\n\r\nThis ER starts introducing the WSDOM service ontology developed by FAA for semantic service discovery. It proposes several extensions useful for OWS compatible, geospatial aviation services. It combines GeoSPARQL with WSDOM ontology and FAA service classification taxonomies and elaborates the interoperability between ontology based WSDOM and OWS compatible service descriptions."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13669,35 +13693,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "20-011"
+ "@value": "16-039r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC SCIRA Pilot Engineering Report"
+ "@value": "Testbed-12 Aviation Semantics Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-036r1",
+ "@id": "http://www.opengis.net/def/docs/07-092r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-06-30"
+ "@value": "2009-01-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Christian Autermann"
+ "@value": "Arliss Whiteside"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13707,27 +13731,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/16-036r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=30575"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "16-036r1"
+ "@value": "07-092r3"
},
{
"@language": "en",
- "@value": "Testbed-12 Big Data Database Engineering Report"
+ "@value": "Definition identifier URNs in OGC namespace"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The amount of (geospatial) data collected and transferred is rapidly increasing. The purpose of this ER is to describe options and recommendations for the delivery of large amounts of data as database delivery. This ER therefore describes and evaluates different aspects of this challenge:\r\n\r\nData management: How to organize large amounts of data so that it can be efficiently accessed through OGC service interfaces?\r\n\r\nEncoding: Transferring large amounts of vector data in XML based formats (e.g. GML, O&M) leads to specific challenges as the parsing of large XML files is often problematic.\r\n\r\nAvailable implementation: Several software packages exist to handle large amounts of geospatial data. We will investigate to which these approaches are in-line with OGC standards or how standards compliance could be achieved.\r\n\r\nThe evaluation and findings in the related Big Data Tile Database Implementation are documented in this ER as well. The objective of this ER is to provide recommendations of how the delivery of large amounts of raster data as database delivery can be considered within OGC specifications and future activities."
+ "@value": "This document specifies Universal Resource Names (URNs) in the “ogc” URN namespace to be used for identifying definitions. These definitions include definitions of Coordinate Reference Systems (CRSs) and related objects, as specified in OGC Abstract Specification Topic 2: Spatial referencing by coordinates, plus several other resource types for which standard identifiers are useful in OGC Web Services. This document specifies the formats used by these URNs, including formats that can reference definitions recorded in the EPSG database and by other authorities. This document also specifies URNs for some specific definitions for which OGC is the custodian."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13738,30 +13762,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-036r1"
+ "@value": "07-092r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Testbed-12 Big Data Database Engineering Report"
+ "@value": "Definition identifier URNs in OGC namespace"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/22-023r2",
+ "@id": "http://www.opengis.net/def/docs/14-008",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2023-07-14"
+ "@value": "2014-07-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Sergio Taleisnik"
+ "@value": "Matthes Rieke"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13776,17 +13800,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/22-023r2.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=58927"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-18: Features Filtering Summary Engineering Report"
+ "@value": "14-008"
},
{
"@language": "en",
- "@value": "22-023r2"
+ "@value": "Testbed 10 Report on Aviation Architecture"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13796,7 +13820,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Testbed-18 (TB-18) Features Filtering Summary Engineering Report (ER) summarizes the implementations, findings, and recommendations that emerged from the efforts to better understand the current OGC API-Features filtering capabilities and limitations and how filtering can be decoupled from data services.\r\n\r\nThis ER describes:\r\n\r\n*\ttwo façades built to interface SWIM services and serve aviation data through APIs (built with OGC API Standards) including basic filtering capabilities;\r\n*\tthe two filtering services built to consume SWIM data and serve it through OGC based APIs featuring advanced filtering mechanism;\r\n*\tthe client application built to interface with the filtering services; and\r\n*\tthe developer client built to define filter statements that can be expressed in a machine-readable way and exchanged with the filtering service."
+ "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). This document describes the\r\narchitecture that was implemented in the Testbed-10 Aviation thread. Additionally, it provides\r\ndescriptions of all software components involved in the Aviation architecture as well as a\r\ndedicated chapter focusing on the evaluation and design of FIXM 2.0. Here, a special focus lies\r\non the integration into the data provisioning components, namely the Web Feature and Event\r\nServices."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13807,30 +13831,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "22-023r2"
+ "@value": "14-008"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Testbed-18: Features Filtering Summary Engineering Report"
+ "@value": "OGC® Testbed 10 Report on Aviation Architecture"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-033r1",
+ "@id": "http://www.opengis.net/def/docs/17-093r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-04-28"
+ "@value": "2018-08-22"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Ranjay Shrestha, Liping Di, Eugene G. Yu"
+ "@value": "Jeff Yutzler, Ashley Antonides"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -13845,17 +13869,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/16-033r1.html"
+ "@id": "https://docs.ogc.org/per/17-093r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "16-033r1"
+ "@value": "GeoPackage Related Tables Extension Interoperability Experiment Engineering Report"
},
{
"@language": "en",
- "@value": "Testbed-12 WCS Profile Update Engineering Report"
+ "@value": "17-093r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -13865,7 +13889,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This engineering report capture the work to extend the existing Web Coverage Service (WCS) profiles, particularly the Earth Observation Application Profile (EO-WCS [OGC 10-140r1]) to support multi-dimensional subsetting of 3D space and 1D time. The updated EO-WCS (EO-WCS1.1 [OGC 10-140r2]) have removed the requirement for the 2D coverages so that it can explicitly allow coverages with more dimensions as long as they have geographic footprint. Furthermore it also clarified the use of rangeType when non-NCNAME characters are present in a band identifier. The example of GetCapabilites, DescribeEOCoverageSet, and _GetCoverage request in the updated EO-WCS1.1 is shown with use case on fire emission data in San Francisco.\r\n\r\nFollowing the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0.25 deg wind data. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients.\r\n\r\nFor the extension of the WCS DescribeCoverage, it is recommended that CIS1.1 should be considered adopting a scheme for transmitting coordinates similar to the _cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part. Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order.\r\n\r\nFor the extension of EO_WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers.\r\n\r\nFor the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2.0 request interface provided adequate syntax for subsetting higher dimensional data. Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended.\r\n\r\nAfter performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server. Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations."
+ "@value": "This OGC Engineering Report describes the results of the OGC GeoPackage (GPKG) Related Tables Extension Interoperability Experiment (GPKG-RTE IE). This IE tested a proposed extension to the OGC GeoPackage Encoding Standard (12-128r14). The GPKG-RTE defines the rules and requirements for associating tables with existing feature or attribute tables in a GeoPackage data store. As part of this IE, the participants performed Technology Integration Experiments (TIEs) where they produced GeoPackages that used this extension, loaded them into GPKG-compliant software systems, and observed the results. As a result of this work, the IE participants agree that the extension is fit for use and consideration as a standard by OGC."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13876,35 +13900,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-033r1"
+ "@value": "17-093r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Testbed-12 WCS Profile Update Engineering Report"
+ "@value": "OGC GeoPackage Related Tables Extension Interoperability Experiment Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-011",
+ "@id": "http://www.opengis.net/def/docs/15-053r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-12-28"
+ "@value": "2015-08-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "OGC"
+ "@value": "Joan Masó"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/as"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13914,27 +13938,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=19820"
+ "@id": "https://portal.ogc.org/files/?artifact_id=64595"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-011"
+ "@value": "Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report"
},
{
"@language": "en",
- "@value": "Topic 06 - Schema for coverage geometry and functions"
+ "@value": "15-053r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/as"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This International Standard defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension."
+ "@value": "In the OGC Testbed 11, the Cross-Community Interoperability (CCI) thread had a key objective of building on the work accomplished in the OGC 8, 9 and 10 Testbeds. The goal of the CCI threads is to increase interoperability between communities sharing geospatial data. This thread made advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This particular Engineering Report (ER) is part of the OGC efforts to advance the OGC Architecture with the adoption of REST interfaces and more encodings such as JSON."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -13945,35 +13969,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-011"
+ "@value": "15-053r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Topic 6 - Schema for coverage geometry and functions"
+ "@value": "OGC® Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/03-022r3",
+ "@id": "http://www.opengis.net/def/docs/22-040",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2003-02-04"
+ "@value": "2023-03-06"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon Cox"
+ "@value": "David Blodgett, J. Michael Johnson"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -13983,27 +14007,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1324"
+ "@id": "https://docs.ogc.org/per/22-040.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "03-022r3"
+ "@value": "Hydrologic Modeling and River Corridor Applications of HY_Features Concepts"
},
{
"@language": "en",
- "@value": "Observations and Measurements"
+ "@value": "22-040"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document describes a framework and encoding for measurements and observations."
+ "@value": "Hydrologic geospatial data products contain geometries that represent features such as river segments and incremental catchments. The combination of these provides a 2D (XY) geospatial fabric (hydrofabic) that discretizes the landscape and flow network into hydrologically relevant features at a defined level of scale, resolution, or organization. Hydrofabrics have been created at the national and continental scale in many parts of the world. This engineering report presents progress on formalizing a hydrofabric for drainage basins that adheres to HY_Features concepts with a focus on the use of the concepts in modeling hydrologic processes. Furthermore, this report documents efforts to integrate river corridor data with the traditionally 2D hydrofabric representations. River corridors include the channel and adjacent land required to maintain or restore a dynamic geomorphic equilibrium."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14014,30 +14038,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "03-022r3"
+ "@value": "22-040"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Observations and Measurements"
+ "@value": "Hydrologic Modeling and River Corridor Applications of HY_Features Concepts"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-022",
+ "@id": "http://www.opengis.net/def/docs/16-044",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2015-08-19"
+ "@value": "2017-03-09"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Andreas Matheus"
+ "@value": "Panagiotis (Peter) A. Vretanos"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -14052,17 +14076,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=63312"
+ "@id": "https://docs.ogc.org/per/16-044.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards"
+ "@value": "16-044"
},
{
"@language": "en",
- "@value": "15-022"
+ "@value": "Testbed-12 Web Feature Service Synchronization"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -14072,7 +14096,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Engineering Report (ER) focuses on describing Common Security for all OGC\r\nWeb Service Standards. This work was performed as part of the OGC Testbed 11\r\nactivity."
+ "@value": "This engineering report describes a protocol for synchronizing data between two enterprise servers. While the protocol itself is generic, this engineering report describes its application to web feature servers.\r\n\r\nIn the simplest terms, the protocol involves each synchronization peer accessing the other’s Sync resource to get the set of changed objects since the last time the Sync resource was accessed. In the case of web feature servers, the objects are features. The requesting peer then compare that list of changed features with the identically identified features in its data store and performs any necessary changes so that the feature states match.\r\n\r\nContinuing the work done in Testbed-11, this engineering report describes the implementation of a Sync operation in a WFS server that:\r\n\r\nEnhances the Sync operation from Testbed-11 to include an abstract query element where each service type can then substitute their specific query syntax for identifying the specific sub-set of changed features to be synchronized. In the case of the WFS, several query syntaxes may be used including the wfs:Query element and a REST based feature type URI with query parameters.\r\n\r\nExtends the definition of the Sync operation with the addition of a resultType parameter to allow a client to obtain a hit count of the number of features that a Sync operation shall return.\r\n\r\nShall investigate the proper procedure for handling resource references. Implementing the resolvePath parameter alone is not sufficient to ensure complete data set synchronization.\r\n\r\nShall investigate concurrency and consistency issues."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14083,35 +14107,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-022"
+ "@value": "16-044"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards"
+ "@value": "Testbed-12 Web Feature Service Synchronization"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/02-027",
+ "@id": "http://www.opengis.net/def/docs/11-039r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2002-05-31"
+ "@value": "2014-02-24"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon Cox"
+ "@value": "Irina Dornblut, Rob Atkinson"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14121,27 +14145,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1137"
+ "@id": "https://portal.ogc.org/files/?artifact_id=55157"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Observations and Measurements"
+ "@value": "HY_Features: a Common Hydrologic Feature Model"
},
{
"@language": "en",
- "@value": "02-027"
+ "@value": "11-039r3"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document describes a framework and encoding for measurements and observations."
+ "@value": "Common semantics support the reference of features to the concept they represent and the integration of data proceed using the semantic framework such mappings provide. However there is no standard conceptual model for hydrologic feature identification. Different models of hydrologic processes, and different scales of detail, lead to a variety of information models to describe these features, and to different and mostly incompatible sets of feature identifiers. \r\nThis document describes requirements and a proposed design for a domain model of hydrologic features as a set of interrelated Application Schemas using the ISO 19109 General Feature Model, \r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14152,35 +14176,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "02-027"
+ "@value": "11-039r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Observations and Measurements"
+ "@value": "OGC HY_Features: a Common Hydrologic Feature Model"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-045",
+ "@id": "http://www.opengis.net/def/docs/03-026",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-08-07"
+ "@value": "2003-01-17"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Uwe Voges, Kristian Senkler"
+ "@value": "Joshua Lieberman"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/sap"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14190,27 +14214,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=21460"
+ "@id": "https://portal.ogc.org/files/?artifact_id=1319"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-045"
+ "@value": "Service Information Model"
},
{
"@language": "en",
- "@value": "ISO Metadata Application Profile"
+ "@value": "03-026"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/sap"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document specifies an application profile for ISO 19115/ISO 19119 metadata with support for XML encoding per ISO/TS19139 and HTTP protocol binding. It relies on requirements coming from the CSW 2.0.2 specification (OGC document 07-006)."
+ "@value": "SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14221,35 +14245,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-045"
+ "@value": "03-026"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile"
+ "@value": "Service Information Model"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-026r2",
+ "@id": "http://www.opengis.net/def/docs/08-053r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2008-02-23"
+ "@value": "2009-03-25"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Andreas Matheus, Jan Herrmann"
+ "@value": "Peter Baumann"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/ts"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14259,27 +14283,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=25218"
+ "@id": "https://portal.ogc.org/files/?artifact_id=32888"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-026r2"
+ "@value": "WCS Processing Extension (WCPS) Abstract Test Suite"
},
{
"@language": "en",
- "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML)"
+ "@value": "08-053r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/ts"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). "
+ "@value": ""
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14290,35 +14314,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-026r2"
+ "@value": "08-053r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML)"
+ "@value": "WCS Processing Extension (WCPS) Abstract Test Suite"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/13-082r2",
+ "@id": "http://www.opengis.net/def/docs/20-090",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2016-01-19"
+ "@value": "2021-01-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Joan Masó"
+ "@value": "Gobe Hobona"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/profile"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14328,27 +14352,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/13-082r2/13-082r2.html"
+ "@id": "https://docs.ogc.org/per/20-090.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "13-082r2"
+ "@value": "20-090"
},
{
"@language": "en",
- "@value": "Web Map Tile Service (WMTS) Simple Profile"
+ "@value": "OGC API – Maps Sprint 2020: Summary Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/profile"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Web Map Tile Service (WMTS) Simple profile defines restrictions that limit the flexibility in implementing a WMTS instance. Adding additional requirements has the goal of simplifying the creation of services and clients. By implementing this profile, clients can more easily combine data coming from different services including from other WMTS instances and even from some tile implementations that are not OGC WMTS based, such as some current distributions of OSM. In fact, most of these tiling services are implicitly following most of the WMTS requirements. Many current WMTS services that implement this profile will have to undergo some changes on how tiles are exposed, and a client that is compatible with WMTS 1.0 will be immediately compatible with this profile. The aim is to align the WMTS standard to other popular tile initiatives which are less flexible but widely adopted."
+ "@value": "This OGC Engineering Report (ER) documents the results and recommendations from a code sprint that was held from 28 to 29 July 2020 to advance the development of the draft OGC API – Maps Standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application, or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API - Maps Sprint was an online virtual event. The sprint was sponsored by Ordnance Survey."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14359,35 +14383,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "13-082r2"
+ "@value": "20-090"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Web Map Tile Service (WMTS) Simple Profile"
+ "@value": "OGC API – Maps Sprint 2020: Summary Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/19-008r4",
+ "@id": "http://www.opengis.net/def/docs/21-055",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-09-14"
+ "@value": "2021-11-29"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Emmanuel Devys, Ted Habermann, Chuck Heazel, Roger Lott, Even Rouault"
+ "@value": "Gobe Hobona, Joana Simoes"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14397,27 +14421,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/19-008r4/19-008r4.html"
+ "@id": "https://docs.ogc.org/per/21-055.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "19-008r4"
+ "@value": "21-055"
},
{
"@language": "en",
- "@value": "GeoTIFF Standard"
+ "@value": "July 2021 OGC API Code Sprint Summary Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset."
+ "@value": "The subject of this Engineering Report (ER) is a virtual code sprint that was held from July 21st to July 23rd, 2021 to advance the development of the OGC API - Processes draft standard, OGC API - Records draft standard, and the OGC API – Coverages draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016)."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14428,35 +14452,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-008r4"
+ "@value": "21-055"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC GeoTIFF Standard"
+ "@value": "July 2021 OGC API Code Sprint Summary Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-042",
+ "@id": "http://www.opengis.net/def/docs/19-082r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-03-15"
+ "@value": "2020-07-08"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff de La Beaujardiere"
+ "@value": "Sergio Taleisnik"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14466,27 +14490,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=14416"
+ "@id": "https://docs.ogc.org/per/19-082r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "06-042"
+ "@value": "19-082r1"
},
{
"@language": "en",
- "@value": "Web Map Service (WMS) Implementation Specification"
+ "@value": "Vector Tiles Pilot 2: Tile Set Metadata Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not. NOTE: WMS 1.3 and ISO 19128 are the same documents."
+ "@value": "The OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report (ER) describes a conceptual model for Tile Set Metadata that provides information about the intended usage of a Tile Set as well as the origin, security level, tiling scheme, layers and feature properties contained within. In this ER, a tile set is a series of tiles containing data and following a common tiling scheme.\r\n\r\nThe metadata is intended to facilitate retrieval of tile sets and describes the major characteristics of tile sets without actually accessing the tiles nor the content contained in a tile. Such a process could be time consuming when there are a large number of tiles in a tile set.\r\n\r\nAdditionally, this ER summarizes the discussions about Tile Set Metadata among the VTP2 participants, and draws up conclusions and recommendations for future work on the subject.\r\n\r\nFinally, this ER describes the Technology Integration Experiments (TIEs) performed to test the prototype implementation of the proposed Tile Set Metadata Model on API endpoints, client applications, and GeoPackages."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14497,30 +14521,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-042"
+ "@value": "19-082r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Web Map Service (WMS) Implementation Specification"
+ "@value": "OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/21-042",
+ "@id": "http://www.opengis.net/def/docs/10-086r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2021-11-29"
+ "@value": "2010-08-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Gobe Hobona"
+ "@value": "Andrew Turner"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -14535,17 +14559,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/21-042.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=40334"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "May 2021 OGC API Code Sprint Summary Engineering Report"
+ "@value": "10-086r1"
},
{
"@language": "en",
- "@value": "21-042"
+ "@value": "OWS-7 - Authoritative Data Source Directory Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -14555,7 +14579,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from 26 to 28 May 2021 to advance the development of the OGC API - Maps draft standard, OGC API - Tiles draft standard, and the OGC API – Styles draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The code sprint was sponsored by Ordnance Survey (OS) and Natural Resources Canada (NRCan)."
+ "@value": "This document presents the Authoritative Data Source Directory (ADSD) engineering suggestions and results of the OGC OWS-7 ADSD thread. This group focused on creating a workflow for geospatially referencing, finding, and federating data sources with associated authority and relevance."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14566,35 +14590,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "21-042"
+ "@value": "10-086r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "May 2021 OGC API Code Sprint Summary Engineering Report"
+ "@value": "OWS-7 - Authoritative Data Source Directory Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/19-070",
+ "@id": "http://www.opengis.net/def/docs/05-019",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2020-01-08"
+ "@value": "2005-02-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Joan Maso Pau"
+ "@value": "Udo Quadt, Thomas Kolbe"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14604,27 +14628,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/19-070.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=8869"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15:Images and ChangesSet API Engineering Report"
+ "@value": "05-019"
},
{
"@language": "en",
- "@value": "19-070"
+ "@value": "Web 3D Service"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OGC API – Images and Changeset draft specification addresses the use case of an OGC API tile server that serves image tiles and a client that portrays the result as a set of images. The tile server uses a set of images (e.g. a set of remote sensing satellite scenes or a set of drone pictures) in the backend and they are also accessible by an API - Images. The source images can be updated and therefore the tile server also needs to be able to deliver only the tiles that have changed. The draft specification is divided into two independent parts that can be used in broader scenarios:\r\n\r\nThe OGC API – Images: Enables managing (retrieving, creating and updating) sets of images that are georeferenced. The images does not follow any tile scheme, and can partiallyor totally overlap. The API enables a mosaicking use case (where the imagery is combined in a single bigger “picture”) but could also serve a use case in which a moving camera is taking pictures at locations along a route and then stores the images as a single collection.\r\n\r\nThe Changeset filter: Enables filtering a request to a data service in a way that only recent changes are delivered. It can be applied to OGC API that provide access to data and in particular to the OGC API tiles."
+ "@value": "The Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14635,65 +14659,29 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-070"
+ "@value": "05-019"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15:Images and ChangesSet API Engineering Report"
+ "@value": "Web 3D Service"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/11-108",
+ "@id": "http://www.opengis.net/def/doc-type/d-isc/collection",
"@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
- {
- "@type": "xsd:date",
- "@value": "2012-05-15"
- }
- ],
- "http://purl.org/dc/terms/creator": [
- {
- "@value": "Ingo Simonis"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
- {
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
- {
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
- {
- "@id": "https://portal.ogc.org/files/?artifact_id=46170"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
- {
- "@language": "en",
- "@value": "11-108"
- },
- {
- "@language": "en",
- "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)"
- }
+ "http://www.w3.org/2004/02/skos/core#Collection"
],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "http://www.w3.org/2000/01/rdf-schema#label": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@value": "Documents of type Implementation Specification Corrigendum - deprecated "
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document describes the usability of OGC services and encodings to implement the\r\nOWS-8 observation fusion and tracking thread in an abstract way. The real deployment\r\nand an actual perspective on the engineering and technology viewpoint can be found in\r\nOWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target Indicator\r\nProcess, Workflows and Implementation Results’. In addition, it describes an XMLSchema\r\nbased implementation of the UML information models defined in OWS-8\r\nengineering report “Information Model for Moving Target Indicators and Moving Object\r\nBookmarks” (OGC 11-113).\r\nThe report is also based on the results of the VMTI/GMTI and STANAG 4676 realization\r\nin the OGC concept of operations study; performed as part of OWS 8 and the EC cofunded\r\nresearch project Emergency Support System - ESS” (contract number 217951)."
+ "@value": "Documents of type Implementation Specification Corrigendum - deprecated "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14701,38 +14689,39 @@
"@id": "http://www.opengis.net/def/docs"
}
],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "http://www.w3.org/2004/02/skos/core#member": [
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "11-108"
+ "@id": "http://www.opengis.net/def/docs/12-128r11"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-189"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@language": "en",
- "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)"
+ "@value": "Documents of type Implementation Specification Corrigendum - deprecated "
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/01-013r1",
+ "@id": "http://www.opengis.net/def/docs/09-042",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2001-02-27"
+ "@value": "2009-10-13"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Arliss Whiteside"
+ "@value": "Steffen Neubauer, Alexander Zipf"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -14742,27 +14731,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1006"
+ "@id": "https://portal.ogc.org/files/?artifact_id=32904"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "High-Level Ground Coordinate Transformation Interface"
+ "@value": "09-042"
},
{
"@language": "en",
- "@value": "01-013r1"
+ "@value": "3D-Symbology Encoding Discussion Draft"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document specifies a "
+ "@value": "This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14773,65 +14762,29 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "01-013r1"
+ "@value": "09-042"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "High-Level Ground Coordinate Transformation Interface"
+ "@value": "3D-Symbology Encoding Discussion Draft"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-018r2",
+ "@id": "http://www.opengis.net/def/doc-type/d-profile/collection",
"@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
- {
- "@type": "xsd:date",
- "@value": "2012-08-27"
- }
- ],
- "http://purl.org/dc/terms/creator": [
- {
- "@value": "Peter Fitch"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
- {
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
- {
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
- {
- "@id": "https://portal.ogc.org/files/?artifact_id=50166"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
- {
- "@language": "en",
- "@value": "Surface Water Interoperability Experiment FINAL REPORT "
- },
- {
- "@language": "en",
- "@value": "12-018r2"
- }
+ "http://www.w3.org/2004/02/skos/core#Collection"
],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "http://www.w3.org/2000/01/rdf-schema#label": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@value": "Documents of type Specification Profile - deprecated "
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This report describes the methods, results, issues and recommendations generated by the Surface Water Interoperability Experiment (SW IE), carried out as an activity of the OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to advance the development of WaterML 2.0 and test its use with various OGC service standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the development of a hydrology domain feature model and vocabularies, which are essential for interoperability in the hydrology domain, although these are not the main focus for the IE. "
+ "@value": "Documents of type Specification Profile - deprecated "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14839,33 +14792,34 @@
"@id": "http://www.opengis.net/def/docs"
}
],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "http://www.w3.org/2004/02/skos/core#member": [
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-018r2"
+ "@id": "http://www.opengis.net/def/docs/06-049r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-100r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@language": "en",
- "@value": "OGC® Surface Water Interoperability Experiment FINAL REPORT "
+ "@value": "Documents of type Specification Profile - deprecated "
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-055r2",
+ "@id": "http://www.opengis.net/def/docs/06-104r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-04-07"
+ "@value": "2010-08-04"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Pedro Gonçalves, Roger Brackin"
+ "@value": "John Herring"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -14880,17 +14834,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=68826"
+ "@id": "https://portal.ogc.org/files/?artifact_id=25354"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS Context GeoJSON Encoding Standard"
+ "@value": "06-104r4"
},
{
"@language": "en",
- "@value": "14-055r2"
+ "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -14900,7 +14854,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This standard describes the GeoJSON encoding of the OGC Web Services (OWS) Context conceptual model. This standard defines how to encode an OWS context document that 1.) can be extended to allow a context referencing a fully configured service set, and 2.) can be defined and consistently interpreted by clients.\r\nThe OWS Context Document standard (OWS Context) was created to allow a set of configured information resources to be passed between applications primarily as a collection of services (but also potentially in-line content). The objective is to support use cases such as the distribution of search results, the exchange of a set of resources in a Common Operating Picture (COP), or delivery of a set of configured processing services to allow the processing to be reproduced on different processing nodes.\r\nThe goal for OWS Context is to replace previous OGC standards and best practices that provide similar capability. Web Map Context (WMC) has been reasonably successful but is limited to working with only Web Map Service (WMS) instances. Other work on the Location Organizer Folder1 (LOF) was also taken into consideration. The concept of OWS Context and the first prototype document was produced as part of OWS Testbed 7 and documented in [OGC10-035r1], Information Sharing Engineering Report.\r\nA principal goal of the OWS Context SWG was to develop encodings that would appeal for use in mass market applications yet also provide facilities for more advanced uses. OWS-7 originally considered the application of existing encoding standards for OWS Context. The OGC Standards Working Group (SWG) has concluded that this standard can have multiple encoding formats and that each encoding format will be described in a separate OGC Extension to the Core model.\r\n"
+ "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14911,30 +14865,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-055r2"
+ "@value": "06-104r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC OWS Context GeoJSON Encoding Standard"
+ "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-096",
+ "@id": "http://www.opengis.net/def/docs/12-097",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-02-01"
+ "@value": "2013-03-26"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Mike Botts"
+ "@value": "Jeff Harrison"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -14949,17 +14903,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=52162"
+ "@id": "https://portal.ogc.org/files/?artifact_id=51998"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging "
+ "@value": "OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)"
},
{
"@language": "en",
- "@value": "12-096"
+ "@value": "12-097"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -14969,7 +14923,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document is an Engineering Report for the OWS-9 Interoperability Test Bed. The focus of the document is discussion and demonstration on the use of SWE Common Data 2.0 encodings to support an interoperable messaging description and encoding for the next generation GPS message streams into and out of the GPS navigation accuracy improvement services. The connection of SWE Common to SensorML 2.0 and the application of SensorML to describe the processing surrounding GPS navigation improvement will also be discussed."
+ "@value": "This document provides a description of the Bulk Data Transfer investigations related to Geography Markup Language (GML) streaming and feature data transportation implemented in the OGC OWS-9 test bed. \r\n\r\nThis document extends the concept of Bulk Data Transfer to the dissemination of large payloads consisting of geospatial data sets and/or collections of data sets between machines that are connected via a network.\r\n\r\nThis document also describes the delivery of large payloads consisting of geospatial data sets and/or collections of data sets to SpatiaLite/SQLite to store the data for use by mobile applications.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -14980,35 +14934,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-096"
+ "@value": "12-097"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging "
+ "@value": "OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-018",
+ "@id": "http://www.opengis.net/def/docs/11-072r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-05-17"
+ "@value": "2012-01-25"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Philippe M"
+ "@value": "Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15018,27 +14972,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=20583"
+ "@id": "https://portal.ogc.org/files/?artifact_id=46322"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Sensor Planning Service Application Profile for EO Sensors"
+ "@value": "OWS-8 Aviation - WXXM Engineering Report"
},
{
"@language": "en",
- "@value": "07-018"
+ "@value": "11-072r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain."
+ "@value": "This OGC™ document specifies the advancement of WXXM and Weather Concepts in\r\nthe OWS-8 Aviation Thread. The focus is on investigating and demonstrating the\r\napplicability and suitability of WXXM in producing accurate, real-time aircraft weather\r\nradar data using OGC™ Web Coverage Services (WCS) to be used by meteorological\r\napplications and services supporting aviation. Such applications provide information\r\nwhich enhances safe and efficient tactical and"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15049,35 +15003,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-018"
+ "@value": "11-072r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors"
+ "@value": "OWS-8 Aviation - WXXM Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-127r2",
+ "@id": "http://www.opengis.net/def/docs/04-049r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2012-01-25"
+ "@value": "2005-04-22"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Tom O’Reilly "
+ "@value": "Philippe Duschene, Jerome Sonnet"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15087,27 +15041,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=47604"
+ "@id": "https://portal.ogc.org/files/?artifact_id=9540"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OGC® PUCK Protocol Standard "
+ "@value": "WCS Change Request: Support for WSDL & SOAP"
},
{
"@language": "en",
- "@value": "09-127r2"
+ "@value": "04-049r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself."
+ "@value": "The OpenGIS has been a precursor in Web Services matter, nevertheless, the pattern that has been used is not recognized by the industry as a standard XML Web Services. The work done during the the OpenGIS Web Service 2 initiative has provided the OpenGIS with interfaces that use the XML-related technologies supported by the industry, as SOAP for the communication protocol, WSDL for the interface description language, and UDDI for registering and searching services.\r\n\r\nThis change proposal present the required change to the WCS specification to interoperate with the industry standards.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15118,30 +15072,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-127r2"
+ "@value": "04-049r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® PUCK Protocol Standard "
+ "@value": "WCS Change Request: Support for WSDL & SOAP"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/13-046r2",
+ "@id": "http://www.opengis.net/def/docs/11-108",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-02-24"
+ "@value": "2012-05-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Lew Leinenweber"
+ "@value": "Ingo Simonis"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -15156,17 +15110,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=55432"
+ "@id": "https://portal.ogc.org/files/?artifact_id=46170"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "13-046r2"
+ "@value": "11-108"
},
{
"@language": "en",
- "@value": "CHISP-1 Summary Engineering Report"
+ "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -15176,7 +15130,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This report summarizes the results of OGC’s Climatology-Hydrology Information Sharing Pilot, Phase 1 (CHISP-1). The objective of this initiative was to develop an inter-disciplinary, inter-agency and international virtual observatory system for water resources information from observations in the U.S. and Canada, building on current networks and capabilities.\r\nThe CHISP-1 Initiative was designed to support these Use Case functions:\r\n•\tHydrologic modeling for historical and current stream flow and groundwater conditions\r\n•\tModeling and assessment of nutrient load into the Great Lakes\r\n"
+ "@value": "This document describes the usability of OGC services and encodings to implement the\r\nOWS-8 observation fusion and tracking thread in an abstract way. The real deployment\r\nand an actual perspective on the engineering and technology viewpoint can be found in\r\nOWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target Indicator\r\nProcess, Workflows and Implementation Results’. In addition, it describes an XMLSchema\r\nbased implementation of the UML information models defined in OWS-8\r\nengineering report “Information Model for Moving Target Indicators and Moving Object\r\nBookmarks” (OGC 11-113).\r\nThe report is also based on the results of the VMTI/GMTI and STANAG 4676 realization\r\nin the OGC concept of operations study; performed as part of OWS 8 and the EC cofunded\r\nresearch project Emergency Support System - ESS” (contract number 217951)."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15187,173 +15141,311 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "13-046r2"
+ "@value": "11-108"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC CHISP-1 Summary Engineering Report"
+ "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-011r5",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/doc-type/bp",
+ "http://www.w3.org/2004/02/skos/core#narrower": [
{
- "@type": "xsd:date",
- "@value": "2021-02-26"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/16-114r3"
+ },
{
- "@value": "Carl Reed"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/16-009r4"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/16-003r2"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/20-095"
+ },
{
- "@id": "https://docs.ogc.org/bp/16-011r5.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/15-004"
+ },
{
- "@language": "en",
- "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance"
+ "@id": "http://www.opengis.net/def/docs/11-169r1"
},
{
- "@language": "en",
- "@value": "16-011r5"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/14-106"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/06-126r2"
+ },
{
- "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames.\r\n\r\n"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/10-189r2"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/06-142r1"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-011r5"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/15-005r1"
+ },
{
- "@language": "en",
- "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/18-036r1",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/12-111r1"
+ },
{
- "@type": "xsd:date",
- "@value": "2019-02-07"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/20-089r1"
+ },
{
- "@value": "Benjamin Pross, Arnaud Cauchy"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/16-011r3"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/16-003r4"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/16-006r4"
+ },
{
- "@id": "https://docs.ogc.org/per/18-036r1.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/06-021r4"
+ },
{
- "@language": "en",
- "@value": "18-036r1"
+ "@id": "http://www.opengis.net/def/docs/13-015"
},
{
- "@language": "en",
- "@value": "WPS-T Engineering Report"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/16-010r5"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/16-010r4"
+ },
{
- "@value": "This Engineering Report describes a proposed transactional extension for the OGC Web Processing Service (WPS) 2.0 standard including Key-Value Pair (KVP) and Extensible Markup Language (XML) bindings and recommendations for a process deployment profile for BPMN (Business Process Model and Notation)."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/10-003r1"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/11-122r1"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-036r1"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/16-140r1"
+ },
{
- "@language": "en",
- "@value": "OGC Testbed-14: WPS-T Engineering Report"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/21-044",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
+ "@id": "http://www.opengis.net/def/docs/07-018r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-102"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-005r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-007"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-011r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-011r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/03-002r9"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-097"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-068"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-003"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-042r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-004r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-037"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-118r9"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-028r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-118r8"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-066"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-005r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/13-042"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-110r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-004r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-003r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-139r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-070"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-129r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-006r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/17-011r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-188r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-125r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-070r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/19-066"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-005r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-167r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-028r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-095"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-107r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-009r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-063r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-004r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/13-039"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-035r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-120r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-107"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-102r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/17-084r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-092r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-035r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/13-043"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-135r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-070r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-003"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-070r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-086r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/02-007r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-120r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-120r6"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-006r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-005r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-010r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-032r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-009r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-012r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-004r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-153r1"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-128r12",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Concept"
+ ],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2022-04-08"
+ "@value": "2015-08-04"
+ },
+ {
+ "@type": "xsd:date",
+ "@value": "2015-04-20"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Luis Bermudez"
+ "@value": "Jeff Yutzler"
+ },
+ {
+ "@value": "Paul Daisey"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/isc"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15363,27 +15455,40 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/21-044.html"
+ "@id": "https://www.geopackage.org/spec"
+ },
+ {
+ "@id": "https://portal.ogc.org/files/?artifact_id=64506"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "21-044"
+ "@value": "GeoPackage Encoding Standard - With Corrigendum"
},
{
"@language": "en",
- "@value": "OGC Testbed 17: CITE Engineering Report"
+ "@value": "12-128r12"
+ },
+ {
+ "@language": "en",
+ "@value": "GeoPackage Encoding Standard"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/isc"
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Testbed 17 Engineering Report (ER) documents the result of the work performed in the CITE thread of the OGC Testbed-17 initiative. CITE is the Compliance Interoperability & Testing Evaluation Subcommittee that provides a forum for an open, consensus discussion regarding approaches and issues related to conformance and interoperability testing as part of the OGC standards process. This ER provides information about the development of a test suite for the OGC API — Processes Standard (OGC18-062r2) to be executed in the OGC Test Evaluation tool (TEAM Engine). The ER also documents an evaluation of an alternative environment for OGC compliance testing.\r\n\r\n"
+ "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth."
+ },
+ {
+ "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector\r\ngeospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access\r\nand update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that\r\nguarantees data model and data set integrity and identical access and update results in response to identical requests from different\r\nclient applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly\r\nuseful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15394,30 +15499,34 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "21-044"
+ "@value": "12-128r12"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed 17: CITE Engineering Report"
+ "@value": "OGC® GeoPackage Encoding Standard - With Corrigendum"
+ },
+ {
+ "@language": "en",
+ "@value": "OGC® GeoPackage Encoding Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-156",
+ "@id": "http://www.opengis.net/def/docs/16-062",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-02-19"
+ "@value": "2017-05-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "George Percivall"
+ "@value": "Gobe Hobona, Roger Brackin"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -15432,17 +15541,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=51842"
+ "@id": "https://docs.ogc.org/per/16-062.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "12-156"
+ "@value": "16-062"
},
{
"@language": "en",
- "@value": "OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report"
+ "@value": "Testbed-12 Catalogue and SPARQL Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -15452,7 +15561,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Reference Architecture Profiler (RAP) Advisor™ is a web based application that\r\nrecommends OGC Standards and OGC Reference Model (ORM) Sections that are\r\nrelevant to a system development; such that a community of interest could derive and\r\nbuild a profile of suitable OGC standards to meet their specific needs. This Engineering\r\nReport contains the requirements, conceptual design, development methodology, and\r\nimplementation of the RAP Advisor.\r\nInitial development of the RAP Advisor™ was concurrent with the OGC Web Services\r\nTestbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, key\r\nconcepts of the RAP Advisor were confirmed through prototyping. Future development\r\nis required to complete the functions and content of the Advisor."
+ "@value": "This engineering report has been produced by the OGC® Testbed-12 initiative.\r\nThe engineering report evaluates interoperability between a variety of\r\ncatalogues. The report presents a comparison of the catalogues, with the same\r\ndatasets uploaded. The catalogues discussed in the report include services\r\nconforming to Catalogue Service for Web (CSW) version 2.0.2 and 3.0, including\r\nservices based on the ebRIM profile of CSW 2.0.2 and an extension of CSW 3.0\r\nwith OpenSearch and SOAP. The engineering report presents results from tests\r\nusing a multi-catalogue client to interact with each service. The engineering\r\nreport also provides a comparison of CSW and services based on the Data\r\nCatalogue (DCAT) specification covering functionality, expressiveness and\r\nusability of CSW and DCAT. The comparison is supported by a discussion on the\r\nimplementation of a SPARQL / GeoSPARQL service."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15463,30 +15572,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-156"
+ "@value": "16-062"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report"
+ "@value": "Testbed-12 Catalogue and SPARQL Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-017",
+ "@id": "http://www.opengis.net/def/docs/22-017",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-04-28"
+ "@value": "2023-03-09"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Gobe Hobona, Roger Brackin"
+ "@value": "Sam Lavender, Kate Williams, Caitlin Adams, Ivana Ivánová "
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -15501,17 +15610,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=57334"
+ "@id": "https://docs.ogc.org/per/22-017.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed 10 OWS Context in NIEM Engineering Report"
+ "@value": "22-017"
},
{
"@language": "en",
- "@value": "14-017"
+ "@value": "Testbed-18: Machine Learning Training Data ER"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -15521,7 +15630,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Open Mobility thread within the testbed.\r\nThe Engineering Report describes and evaluates options for integrating OWS Context documents in requests for information based on the National Information Exchange Model (NIEM).\r\n"
+ "@value": "This OGC Testbed 18 Engineering Report (ER) documents work to develop a foundation for future standardization of Training Datasets (TDS) for Earth Observation (EO) applications. The work performed in the Testbed 18 activity is based on previous OGC Machine Learning (ML) activities. TDS are essential to ML models, supporting accurate predictions in performing the desired task. However, a historical absence of standards has resulted in inconsistent and heterogeneous TDSs with limited discoverability and interoperability. Therefore, there is a need for best practices and guidelines for generating, structuring, describing, and curating TDSs that would include developing example software/packages to support these activities. Community and parallel OGC activities are working on these topics. This ER reviews those activities in parallel with making recommendations."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15532,35 +15641,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-017"
+ "@value": "22-017"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Testbed 10 OWS Context in NIEM Engineering Report"
+ "@value": "Testbed-18: Machine Learning Training Data ER"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/20-043",
+ "@id": "http://www.opengis.net/def/docs/12-084r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2020-10-22"
+ "@value": "2014-01-14"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Stefan Achtsnit, Joachim Ungar, and Stephan Meißl (EOX), Anja Vrecko and Grega Milčinski (Sinergise)"
+ "@value": "Roger Brackin, Pedro Gonçalves "
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15570,27 +15679,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/20-043.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=55183"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "20-043"
+ "@value": "OWS Context Atom Encoding Standard"
},
{
"@language": "en",
- "@value": "OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report"
+ "@value": "12-084r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Engineering Report documents findings, achievements, and learnings gained through activities during the OGC Earth Observation (EO) Applications Pilot by the EOX team (EOX, DLR, UVT, Sinergise, and Terrasigna). Both perspectives, from application developer’s as well as from platform provider’s view, are represented here."
+ "@value": "This standard describes the Atom encoding of the OWC Context conceptual model. The goal of this standard is to provide a definition of how to encode a context document, which can be extended to allow a context referencing a fully configured service set to be defined and consistently interpreted by clients.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15601,35 +15710,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "20-043"
+ "@value": "12-084r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report"
+ "@value": "OGC OWS Context Atom Encoding Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/17-083r2",
+ "@id": "http://www.opengis.net/def/docs/03-055r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-10-06"
+ "@value": "2003-06-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Joan Masó"
+ "@value": "Louis Rose"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/retired"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15639,27 +15748,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/17-083r2/17-083r2.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=1282"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Two Dimensional Tile Matrix Set"
+ "@value": "Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint"
},
{
"@language": "en",
- "@value": "17-083r2"
+ "@value": "03-055r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/retired"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OGC Tile Matrix Set standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in [OGC 08-015r2] Abstract Specification Topic 2: Spatial Referencing by Coordinates. Each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column a tile row and a tile matrix identifier. This document presents a data structure defining the properties of the tile matrix set in both UML diagrams and in tabular form. This document also presents a data structure to define a subset of a tile matrix set called tile matrix set limits. XML and JSON encodings are suggested both for tile matrix sets and tile matrix set limits. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions."
+ "@value": "*RETIRED* specifies the Engineering Viewpoint for the Critical Infrastructure Collaborative Environment (CICE). This open, distributed processing environment crosses organizational boundaries and includes a variety of components deployed within multiple communities. The CICE leverages OGC Web Services the publication of the availability of critical infrastructure services and data; the registration and categorization of published service and data providers; and the discovery and use of needed critical infrastructure services and data"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15670,46 +15779,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "17-083r2"
+ "@value": "03-055r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Two Dimensional Tile Matrix Set"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/doc-type/ipr",
- "http://www.w3.org/2004/02/skos/core#narrower": [
- {
- "@id": "http://www.opengis.net/def/docs/02-028"
- },
- {
- "@id": "http://www.opengis.net/def/docs/02-019r1"
+ "@value": "Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-045r2",
+ "@id": "http://www.opengis.net/def/docs/21-066r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2022-08-19"
+ "@value": "2022-09-09"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Uwe Voges, Kristian Senkler"
+ "@value": "Joan Maso"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/notes"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15719,27 +15817,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/80534"
+ "@id": "https://docs.ogc.org/is/17-083r4/21-066r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-045r2"
+ "@value": "Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0"
},
{
"@language": "en",
- "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum"
+ "@value": "21-066r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/notes"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Catalogue services are the key technology for locating, managing and maintaining\r\ndistributed geo-resources (i.e. geospatial data, applications and services). With OGC\r\ncatalogue services, client applications are capable of searching for geo-resources in a\r\nstandardized way (i.e. through standardized interfaces and operations) and, ideally, they\r\nare based on a well-known information model, which includes spatial references and\r\nfurther descriptive (thematic) information that enables client applications to search for\r\ngeo-resources in very efficient ways.\r\nWhereas interfaces and operations of OGC catalogue services are well defined, it is left\r\nup to the developer of the system to define a specific information model which a\r\ncatalogue service instance provides. This includes, but is not limited to, the information\r\nwhich can be inserted in the catalog, supported query languages, available search terms,\r\nresponse/result sets, etc. This point is of major importance with respect to interoperability\r\nbetween different catalogue service instances.\r\nIn Europe, running catalogue instances result from work being done within different SDI\r\ninitiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC\r\nEU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives\r\nhave developed an ISO-based application profile for ISO19115 metadata for\r\ngeodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled\r\ngeospatial services. The foundations of this profile were the OGC catalogue\r\nspecification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services\r\nStateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description.\r\nOGC's catalogue revision working group (CS-RWG) has revised and integrated the\r\ncatalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of\r\nthis OGC specification comprises the definition of application profiles according to ISO\r\n19106 (Geographic information – Profiles). The overall goal of these profiles is to\r\nimprove interoperability between systems conforming to a specific profile. Experience\r\nhas shown that the need for application profiles results from the fact that in practice, there\r\nis no single solution for catalogue services that fits every user’s needs. As stated in CS\r\n2.0.2, a base profile that provides a basic set of information objects has to be supported\r\nby each catalogue instance; in addition, application profiles for different information\r\ncommunities can be specified.\r\nHence, this document specifies an application profile for ISO 19115:2003/ISO\r\n19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the\r\nCS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application\r\nprofile will form the basis of conformance tests and reference implementations."
+ "@value": "This document provides the set of revision notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata [OGC 17-083r4] and does not modify that Standard."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15750,35 +15848,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-045r2"
+ "@value": "21-066r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum"
+ "@value": "Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-092r1",
+ "@id": "http://www.opengis.net/def/docs/12-018r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-11-14"
+ "@value": "2012-05-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Arliss Whiteside"
+ "@value": "Peter Fitch"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-bp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15788,27 +15886,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=24045"
+ "@id": "https://portal.ogc.org/files/?artifact_id=47989"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Definition identifier URNs in OGC namespace"
+ "@value": "Surface Water Interoperability Experiment FINAL REPORT"
},
{
"@language": "en",
- "@value": "07-092r1"
+ "@value": "12-018r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-bp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. "
+ "@value": "This report describes the methods, results, issues and recommendations generated by\r\nthe Surfacewater Interoperability Experiment (SW IE), carried out as an activity of the\r\nOGC Hydrology Domain Working Group (HDWG). The SW IE was designed to\r\nadvance the development of WaterML 2.0 and test its use with various OGC service\r\nstandards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the\r\ndevelopment of a hydrology domain feature model and vocabularies, which are\r\nessential for interoperability in the hydrology domain, although these are not the main\r\nfocus for the IE."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15819,35 +15917,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-092r1"
+ "@value": "12-018r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Definition identifier URNs in OGC namespace"
+ "@value": "Surface Water Interoperability Experiment FINAL REPORT"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-140",
+ "@id": "http://www.opengis.net/def/docs/15-001r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-06-08"
+ "@value": "2017-09-13"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Dr. Markus M"
+ "@value": "Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15857,27 +15955,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=19084"
+ "@id": "https://docs.ogc.org/is/15-001r4/15-001r4.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "06-140"
+ "@value": "3D Portrayal Service 1.0"
},
{
"@language": "en",
- "@value": "Feature Styling IPR"
+ "@value": "15-001r4"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Feature Styling is based on a distributed computational platform that employs a number\r\nof standard interfaces and encodings to allow for flexible, scalable and interoperable\r\nmanagement of symbology (styles and symbols) in the process of producing maps from\r\ndifferent kinds of data, most important being source GML data.\r\n"
+ "@value": "The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal.\r\n\r\nIt does not define or endorse particular content transmission formats, but specifies how geospatial 3D content is described, selected, and delivered. It does not prescribe how aforementioned content is to be organized and represented, but provides a framework to determine whether 3D content is interoperable at the content representation level. More details are available in Design of this standard."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15888,30 +15986,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-140"
+ "@value": "15-001r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Feature Styling IPR"
+ "@value": "OGC® 3D Portrayal Service 1.0"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/20-087",
+ "@id": "http://www.opengis.net/def/docs/22-031r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2021-01-26"
+ "@value": "2023-01-03"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Leonard Daly, Scott Serich"
+ "@value": "Pedro Gonçalves"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -15926,17 +16024,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/20-087.html"
+ "@id": "https://docs.ogc.org/per/22-031r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "20-087"
+ "@value": "22-031r1"
},
{
"@language": "en",
- "@value": "Interoperable Simulation and Gaming Sprint Engineering Report"
+ "@value": "Testbed-18: Reproducible FAIR Best Practices Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -15946,7 +16044,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OGC Interoperable Simulation and Gaming Sprint advanced the use of relevant OGC and Khronos standards in the modeling and simulation community through practical exercise and testing of the GeoVolumes API draft specification produced by the 3D Data Container and Tiles API Pilot. Of particular interest was the handling and integration of glTF models coming from multiple sources, but the sprint also examined the specification’s implementability, consistency, completeness, and maturity."
+ "@value": "The OGC Testbed-18 initiative included a discussion exploring the future of open science and building energy interoperability with the task of developing a set of best practices to make the data processing services of Exploitation Platforms both reproducible and follow the FAIR data principles.\r\n\r\nPortability and reproducibility are key factors for the long-term scientific impact of Earth Observation (EO) data processing applications provided by Exploitations Platforms. The EO application developers lack the tools and guidance to preserve all the elements, algorithms, software, and data resources used to produce the results. Without these elements, reproducibility becomes resubmission within the platform and only while the same platform resources such as data are preserved and available.\r\n\r\nThis Testbed 18 Engineering Report defines a list of requirements and respective best practices to support reproducible Earth Observation science covering the different resources of the Earth Observation Exploitation Platforms such as publications, data, services, products, information, software, or computing environments.\r\n\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -15957,35 +16055,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "20-087"
+ "@value": "22-031r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Interoperable Simulation and Gaming Sprint Engineering Report"
+ "@value": "Testbed-18: Reproducible FAIR Best Practices Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-090r3",
+ "@id": "http://www.opengis.net/def/docs/08-015r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2011-04-05"
+ "@value": "2010-04-27"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Ben Domenico"
+ "@value": "Roger Lott"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -15995,27 +16093,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=43732"
+ "@id": "https://portal.ogc.org/files/?artifact_id=39049"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Network Common Data Form (NetCDF) Core Encoding Standard version 1.0"
+ "@value": "08-015r2"
},
{
"@language": "en",
- "@value": "10-090r3"
+ "@value": "Topic 2 - Spatial referencing by coordinates"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena.\r\nNetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data.\r\n"
+ "@value": "This document is consistent with the second edition (2007) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2007]"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16026,35 +16124,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-090r3"
+ "@value": "08-015r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0"
+ "@value": "Topic 2 - Spatial referencing by coordinates"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-050r3",
+ "@id": "http://www.opengis.net/def/docs/03-105r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2016-01-25"
+ "@value": "2004-04-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff Harrison"
+ "@value": "Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16064,27 +16162,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=65421"
+ "@id": "https://portal.ogc.org/files/?artifact_id=4700"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report"
+ "@value": "Geography Markup Language (GML) Encoding Specification"
},
{
"@language": "en",
- "@value": "15-050r3"
+ "@value": "03-105r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community\r\n(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0\r\narchitecture through the development, implementations, test, and robust demonstration\r\nmaking use of IC specifications, Geography Markup Language (GML), and NIEM in a\r\nsimulated “real-world” scenario. The demonstration scenario begins with NIEMconformant\r\nInformation Exchange Packages (IEPs) containing operational data and IC\r\nsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)\r\naccess control metadata, and the Trusted Data Format (TDF) for binding assertion\r\nmetadata with data resource(s). Those instance documents are deployed using Open\r\nGeospatial Consortium (OGC) standards enabled Web Services for use by client\r\napplications. Access control is based on attributes of the end-user and the instance data.\r\nRecommendations to update these information exchanges were provided to reflect NIEM\r\n3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment tested\r\nthis data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points\r\n(PEP) accessed by multiple client applications. Results from this task provided a\r\npreliminary architecture that was tested and demonstrated in Testbed 11, and summarized\r\nin other OGC Testbed 11 Engineering Reports. The demonstrations also highlighted how\r\nNIEM and IC data encodings together may support more agile and customer-centric\r\nframeworks driven by collaborative partnerships. This transformation is vital to\r\nconfronting the security challenges of the future."
+ "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16095,35 +16193,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-050r3"
+ "@value": "03-105r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report"
+ "@value": "OpenGIS Geography Markup Language (GML) Encoding Specification"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-154",
+ "@id": "http://www.opengis.net/def/docs/09-046r6",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-08-14"
+ "@value": "2021-09-27"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "David S. Burggraf, Ron Lake, Darko Androsevic"
+ "@value": "Gobe Hobona, Simon Cox"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/pol"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16133,27 +16231,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=19580"
+ "@id": "https://docs.ogc.org/pol/09-046r6.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "WFS Temporal Investigation"
+ "@value": "09-046r6"
},
{
"@language": "en",
- "@value": "06-154"
+ "@value": "OGC Naming Authority - Procedures"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/pol"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The objective of the proposed temporal extensions to the WFS is to enable temporal/geospatial queries using the GML temporal types against GML dynamic features employing either the snapshot or time history model (time slices). "
+ "@value": "The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document describes the framework of documents, registers and other resources required for OGC-NA to execute that role."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16164,35 +16262,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-154"
+ "@value": "09-046r6"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS 4 WFS Temporal Investigation"
+ "@value": "OGC Naming Authority - Procedures"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-075",
+ "@id": "http://www.opengis.net/def/docs/04-084",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-01-14"
+ "@value": "2005-06-27"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf"
+ "@value": "Carl Reed"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16202,27 +16300,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/18-075/18-075.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=7560"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "18-075"
+ "@value": "04-084"
},
{
"@language": "en",
- "@value": "Moving Features Encoding Part I: XML Core"
+ "@value": "Topic 0 - Overview"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange."
+ "@value": "Introduction and roadmap to the Abstract specification. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16233,35 +16331,42 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-075"
+ "@value": "04-084"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Moving Features Encoding Part I: XML Core"
+ "@value": "Topic 0 - Overview"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-036r2",
+ "@id": "http://www.opengis.net/def/docs/06-035r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-08-18"
- }
+ "@value": "2006-07-26"
+ },
+ {
+ "@type": "xsd:date",
+ "@value": "2006-05-02"
+ }
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Stan Tillman"
+ "@value": "Peter Baumann"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/d-bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16271,27 +16376,40 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=40313"
+ "@id": "https://portal.ogc.org/files/?artifact_id=14895"
+ },
+ {
+ "@id": "https://portal.ogc.org/files/?artifact_id=14022"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-7 Motion Video Change Detection"
+ "@value": "06-035r1"
},
{
"@language": "en",
- "@value": "10-036r2"
+ "@value": "Web Coverage Processing Service (WCPS)"
+ },
+ {
+ "@language": "en",
+ "@value": "Web Coverage Processing Service"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/d-bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Engineering Report documents the development effort to build a Web Processing Service (WPS) to perform a change detection algorithm on two motion video streams. It will examine the WPS Motion Video Change Detection architecture from various viewpoints in order to describe its purpose, data models, functional decomposition, and interaction between distinct computational components. "
+ "@value": "The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS uses the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification: coverages are defined as digital geo-spatial information representing space-varying phenomena, currently constrained to equally spaced grids."
+ },
+ {
+ "@value": "The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS grounds on the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification where coverages are defined as digital geospatial information representing space-varying phenomena, currently constrained to equally spaced grids."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16302,35 +16420,39 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-036r2"
+ "@value": "06-035r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-7 Motion Video Change Detection"
+ "@value": "Web Coverage Processing Service"
+ },
+ {
+ "@language": "en",
+ "@value": "Web Coverage Processing Service (WCPS)"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-097",
+ "@id": "http://www.opengis.net/def/docs/99-054",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-03-26"
+ "@value": "1999-06-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff Harrison"
+ "@value": "Peter Ladstaetter"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16340,27 +16462,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=51998"
+ "@id": "https://portal.ogc.org/files/?artifact_id=834"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "12-097"
+ "@value": "Simple Features Implementation Specification for CORBA"
},
{
"@language": "en",
- "@value": "OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)"
+ "@value": "99-054"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document provides a description of the Bulk Data Transfer investigations related to Geography Markup Language (GML) streaming and feature data transportation implemented in the OGC OWS-9 test bed. \r\n\r\nThis document extends the concept of Bulk Data Transfer to the dissemination of large payloads consisting of geospatial data sets and/or collections of data sets between machines that are connected via a network.\r\n\r\nThis document also describes the delivery of large payloads consisting of geospatial data sets and/or collections of data sets to SpatiaLite/SQLite to store the data for use by mobile applications.\r\n"
+ "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16371,35 +16493,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-097"
+ "@value": "99-054"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)"
+ "@value": "OpenGIS Simple Features Implementation Specification for CORBA"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/11-134",
+ "@id": "http://www.opengis.net/def/docs/13-133r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2012-05-15"
+ "@value": "2016-08-22"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Rob Cass, Mark Simms"
+ "@value": "Aaron Braeckel, Lorenzo Bigagli"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16409,27 +16531,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=46372"
+ "@id": "https://docs.ogc.org/is/13-133r1/13-133r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER"
+ "@value": "Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension"
},
{
"@language": "en",
- "@value": "11-134"
+ "@value": "13-133r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The scope of this report is to provide a description of services, data storage and data\r\nmovement within the OWS-8 Tracking sub-thread. The paper outlines the development\r\nof Sensor Observation Services (SOS), a Web Feature Service(WFS), a Notification\r\nService and a Web Processing Service (WPS) for generating track features. Additionally,\r\nimplemented encodings will be discussed as examples and in comparison to the\r\nencodings detailed in (Simonis, 2011)."
+ "@value": "Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers.\r\n\r\nPublish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. \r\n\r\nThis specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16440,70 +16562,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "11-134"
+ "@value": "13-133r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/doc-type/sap/collection",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Collection"
- ],
- "http://www.w3.org/2000/01/rdf-schema#label": [
- {
- "@value": "Documents of type Specification Application Profile - Approved"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
- {
- "@value": "Documents of type Specification Application Profile - Approved"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
- {
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#member": [
- {
- "@id": "http://www.opengis.net/def/docs/06-080r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/09-146r2"
- },
- {
- "@id": "http://www.opengis.net/def/docs/07-045"
- },
- {
- "@id": "http://www.opengis.net/def/docs/01-009"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
- {
- "@value": "Documents of type Specification Application Profile - Approved"
+ "@value": "OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-094r3",
+ "@id": "http://www.opengis.net/def/docs/18-090r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-08-18"
+ "@value": "2019-03-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Micah Brachman"
+ "@value": "Dr. Craig A. Lee"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -16518,17 +16600,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=70051"
+ "@id": "https://docs.ogc.org/per/18-090r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "GeoPackage Elevation Extension Interoperability Experiment Engineering Report"
+ "@value": "Federated Clouds Engineering Report"
},
{
"@language": "en",
- "@value": "16-094r3"
+ "@value": "18-090r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -16538,7 +16620,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "his OGC Engineering Report (ER) describes the setup, experiments, results and issues generated by the GeoPackage Elevation Extension Interoperability Experiment (GPKG-EE IE). The goal of the GPKG-EE IE was to implement and test a proposed elevation extension to the OGC GeoPackage Encoding Standard (12-128r1). The proposed elevation extension was successfully implemented by several IE participants and was demonstrated using both 2-Dimensional (2D) and 3-Dimensional (3D) software clients at the Washington, DC OGC Technical Committee (TC) meeting in [March 9, 2016]. This ER concludes with several recommendations for addressing remaining technical issues that must be resolved in order to complete a candidate GeoPackage Elevation Extension standard."
+ "@value": "The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in OGC Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the OGC Testbed-14 Security Engineering Report (ER) cite:[SecurityER]. This Federated Cloud Engineering Report (ER) dovetails with the Security ER to:\r\n\r\nCoordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks,\r\n\r\nUnderstand the overall federation design space,\r\n\r\nAnalyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14,\r\n\r\nIdentify and prioritize possible incremental development tasks for subsequent testbeds, and\r\n\r\nLiaison with groups external to OGC, such as the National Institute of Standards and Technology (NIST)/Institute of Electrical and Electronics Engineers (IEEE) Joint Working Group on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards.\r\n\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16549,35 +16631,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-094r3"
+ "@value": "18-090r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC GeoPackage Elevation Extension Interoperability Experiment Engineering Report"
+ "@value": "OGC Testbed-14: Federated Clouds Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-054",
+ "@id": "http://www.opengis.net/def/docs/17-069r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2015-11-18"
+ "@value": "2022-05-11"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Stephane Fellah"
+ "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16587,27 +16669,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=64405"
+ "@id": "https://docs.ogc.org/is/17-069r4/17-069r4.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "15-054"
+ "@value": "OGC API - Features - Part 1: Core corrigendum"
},
{
"@language": "en",
- "@value": "Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report"
+ "@value": "17-069r4"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® Engineering Report (ER) summarizes the approaches, findings and the results\r\nof the Linked Data and Semantic Enablement of OGC Web Services sub-thread activities\r\nof the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. This report\r\nprovides an overview of existing standards for geosemantics, outlines the approaches\r\nadopted during the testbed, describes the conceptual semantic models and services\r\ndeveloped during this testbed to leverage Linked Data and semantic enabled OGC web\r\nservices."
+ "@value": "This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.\r\n\r\nDiscovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.\r\n\r\nQuery operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16618,35 +16700,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-054"
+ "@value": "17-069r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report"
+ "@value": "OGC API - Features - Part 1: Core corrigendum"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-014r2",
+ "@id": "http://www.opengis.net/def/docs/02-039r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-04-26"
+ "@value": "2002-10-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Greg Schumann, Josh Lieberman"
+ "@value": "Roland Wagner"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16656,27 +16738,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/16-014r2.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=11500"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report"
+ "@value": "02-039r1"
},
{
"@language": "en",
- "@value": "16-014r2"
+ "@value": "Web Pricing and Ordering"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives.\r\n•\tApply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management. \r\n•\tEmploy an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability. \r\n•\tDevelop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. \r\n•\tPrototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. \r\n"
+ "@value": "This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16687,35 +16769,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-014r2"
+ "@value": "02-039r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report"
+ "@value": "Web Pricing and Ordering"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/03-021",
+ "@id": "http://www.opengis.net/def/docs/16-083r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2003-01-20"
+ "@value": "2017-06-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff Yutzler"
+ "@value": "Eric Hirschorn"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16725,27 +16807,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1328"
+ "@id": "https://docs.ogc.org/is/16-083r2/16-083r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "03-021"
+ "@value": "16-083r2"
},
{
"@language": "en",
- "@value": "Integrated Client for Multiple OGC-compliant Services"
+ "@value": "Coverage Implementation Schema - ReferenceableGridCoverage Extension"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services"
+ "@value": "The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].\r\n\r\nThis OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -16756,35 +16838,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "03-021"
+ "@value": "16-083r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Integrated Client for Multiple OGC-compliant Services"
+ "@value": "OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/99-100r1",
+ "@id": "http://www.opengis.net/def/docs/11-158",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "1999-06-23"
+ "@value": "2011-10-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Cliff Kottman"
+ "@value": "Jim Greenwood"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-as"
+ "@id": "http://www.opengis.net/def/doc-type/isc"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -16794,27 +16876,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=11496"
+ "@id": "https://portal.ogc.org/files/?artifact_id=46436"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "99-100r1"
+ "@value": "11-158"
},
{
"@language": "en",
- "@value": "Topic 0 - Overview"
+ "@value": "Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-as"
+ "@id": "http://www.opengis.net/def/doc-type/isc"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Introduction and roadmap to the Abstract specification."
+ "@value": "This document defines the corrigendum change notes for The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation. \r\n
\r\n\r\nThis document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-‐compliant components are provided by the OpenMI Association and third-‐party software vendors – visit www.openmi.org for further documentation.
\r\n\r\npdf
\r\ndocx\r\n
"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/08-007r1"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/06-121r9"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "11-014r3"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/07-144r4"
+ },
{
- "@language": "en",
- "@value": "OGC Open Modelling Interface Interface Standard"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/12-093",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/18-073r2"
+ },
{
- "@type": "xsd:date",
- "@value": "2013-02-05"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/12-128r14"
+ },
{
- "@value": "Clemens Portele"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/16-120r3"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/07-099r1"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/14-084r2"
+ },
{
- "@id": "https://portal.ogc.org/files/?artifact_id=51784"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/18-000"
+ },
{
- "@language": "en",
- "@value": "OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report"
+ "@id": "http://www.opengis.net/def/docs/15-042r6"
},
{
- "@language": "en",
- "@value": "12-093"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/17-083r2"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/17-069r4"
+ },
{
- "@value": "The main scope of the schema automation activities in the OWS-9 initiative was twofold:\r\n•\tSupport for the SWE Common 2.0 XML Schema encoding rule\r\n•\tDevelopment of and support for an encoding rule for JSON instance data\r\nIn both cases the scope includes implementation of the encoding rules in ShapeChange.\r\nIn addition, an initial analysis of the possibilities for generating SWE Common 2.0 record descriptions from schemas in UML has been conducted and the results are described in this document.\r\nThe approach and results to both work items are described and discussed in this engineering report. This Engineering Report has been prepared as part of the OGC Web Services Phase 9 (OWS-9) initiative.\r\n"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/07-036"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/06-103r4"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-093"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/09-149r1"
+ },
{
- "@language": "en",
- "@value": "OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/doc-type/isx/collection",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Collection"
- ],
- "http://www.w3.org/2000/01/rdf-schema#label": [
+ "@id": "http://www.opengis.net/def/docs/07-068r4"
+ },
{
- "@value": "Documents of type Implementation Standard Extension"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/16-106r2"
+ },
{
- "@value": "Documents of type Implementation Standard Extension"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/10-126r4"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#member": [
+ "@id": "http://www.opengis.net/def/docs/21-006r2"
+ },
{
- "@id": "http://www.opengis.net/def/docs/08-059r4"
+ "@id": "http://www.opengis.net/def/docs/99-050"
},
{
- "@id": "http://www.opengis.net/def/docs/10-135"
+ "@id": "http://www.opengis.net/def/docs/14-083r2"
},
{
- "@id": "http://www.opengis.net/def/docs/11-053r1"
+ "@id": "http://www.opengis.net/def/docs/05-007r7"
},
{
- "@id": "http://www.opengis.net/def/docs/12-040"
+ "@id": "http://www.opengis.net/def/docs/01-009"
},
{
- "@id": "http://www.opengis.net/def/docs/12-039"
+ "@id": "http://www.opengis.net/def/docs/06-121r3"
},
{
- "@id": "http://www.opengis.net/def/docs/13-084r2"
+ "@id": "http://www.opengis.net/def/docs/18-043r3"
},
{
- "@id": "http://www.opengis.net/def/docs/10-092r3"
+ "@id": "http://www.opengis.net/def/docs/17-089r1"
},
{
- "@id": "http://www.opengis.net/def/docs/12-049"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/06-009r6"
+ },
{
- "@value": "Documents of type Implementation Standard Extension"
+ "@id": "http://www.opengis.net/def/docs/07-098r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-065"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-129",
+ "@id": "http://www.opengis.net/def/docs/18-005r8",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-02-16"
+ "@value": "2023-09-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Nadine Alameh"
+ "@value": "Roger Lott"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/as"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26496,27 +25650,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=35634"
+ "@id": "https://docs.ogc.org/as/18-005r8/18-005r8.pdf"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "09-129"
+ "@value": "Topic 02 - Referencing by coordinates"
},
{
"@language": "en",
- "@value": "AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report"
+ "@value": "18-005r8"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/as"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This AIP-2 Engineering Report (ER) describes a set of transverse technology Use Cases developed and applied in the GEOSS Architecture Implementation Pilot Phase 2 (AIP-2). Such Use Cases define reusable activities within a service-oriented architecture, tailored for the GEOSS environment. This report contains the general Use Cases that were specialized by community Working Groups to implement several specific Societal Benefit Area (SBA) Scenarios in AIP-2. The SBA Scenarios and specialized use cases are defined in separate AIP-2 ERs. This AIP-2 ER will be offered for consideration by the GEOSS Best Practice Registry editors and to OGC Technical Committee for consideration as a Best Practice."
+ "@value": "This document is consistent with the third edition (2019) of ISO 19111, Geographic Information - Referencing by coordinates including its amendments 1 and 2. ISO 19111:2019 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics, in close collaboration with the Open Geospatial Consortium (OGC). It replaces the second edition, ISO 19111:2007 and also ISO 19111-2:2009, OGC documents 08-015r2 and 10-020. This OGC document, 18-005r5, incorporates three editorial corrections made in ISO 19111:2019 amendment 1 of 2021."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26527,35 +25681,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-129"
+ "@value": "18-005r8"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report"
+ "@value": "Topic 2 - Referencing by coordinates (Including corrigendum 1 and corrigendum\t2)"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-011r2",
+ "@id": "http://www.opengis.net/def/docs/11-038R2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2016-01-28"
+ "@value": "2012-10-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Panagiotis (Peter) A. Vretanos"
+ "@value": "Ben Domenico"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26565,27 +25719,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=66906"
+ "@id": "https://portal.ogc.org/files/?artifact_id=50294"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-11 Multiple WFS-T Interoperability"
+ "@value": "OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard"
},
{
"@language": "en",
- "@value": "15-011r2"
+ "@value": "11-038R2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document describes the work done in the OGC Testbest-11 to support multiple WFS-T instance interoperability by way of a transaction scenario involving the interaction between clients and multiple WFS-T servers as well as the interaction between the servers themselves, especially in the use case of enterprise-to-enterprise data synchronization.\r\nThe document presents an overview of the transaction scenario, the components used to implement the scenario in the OGC Testbed-11 demo and the new capabilities added to the WFS-T server to support the scenario.\r\n"
+ "@value": "This standard deals with enhancements to the netCDF (Network Common Data Form) data model for array-oriented scientific data..\r\nTwo important data models for netCDF are:\r\n- the “classic” netCDF model, used for netCDF-3 and earlier versions\r\n- an enhanced data model, used in netCDF-4 and later versions.\r\nThe netCDF classic data model is defined in OGC 10-091r3, “NetCDF Core.”\r\nThis document specifies a netCDF extension standard for the enhanced data model. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena.\r\nNetCDF (network Common Data Form) is a data model for array-oriented scientific data. The netCDF classic data model is specified in the netCDF core specification. This standard specifies the enhanced data model. A freely distributed collection of access libraries implementing support for that data model in a machine-independent format are available. Together, the interfaces, libraries, and format support the creation, access, and sharing of multi-dimensional scientific data."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26596,35 +25750,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-011r2"
+ "@value": "11-038R2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-11 Multiple WFS-T Interoperability"
+ "@value": "OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/04-038r1",
+ "@id": "http://www.opengis.net/def/docs/09-112r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2004-10-05"
+ "@value": "2010-10-12"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Uwe Voges, Kristian Senkler"
+ "@value": "Simon Jirka, Arne Bröring, Daniel Nüst"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26634,27 +25788,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=6495"
+ "@id": "https://portal.ogc.org/files/?artifact_id=40571"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "04-038r1"
+ "@value": "Sensor Observable Registry (SOR) Discussion Paper"
},
{
"@language": "en",
- "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0"
+ "@value": "09-112r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS"
+ "@value": "This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26665,35 +25819,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "04-038r1"
+ "@value": "09-112r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0"
+ "@value": "Sensor Observable Registry (SOR) Discussion Paper"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-006",
+ "@id": "http://www.opengis.net/def/docs/09-076r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2009-08-05"
+ "@value": "2009-09-14"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Keith Pomakis"
+ "@value": "Arliss Whiteside"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26703,27 +25857,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=33269"
+ "@id": "https://portal.ogc.org/files/?artifact_id=35042"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "09-006"
+ "@value": "Uses and summary of Topic 02 - Spatial referencing by coordinates"
},
{
"@language": "en",
- "@value": "OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS"
+ "@value": "09-076r3"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the development of SOAP/XML and REST interfaces for the Web Map Tiling Service (WMTS)."
+ "@value": "This document first discusses the uses for data sharing, and then provides a brief summary, of OGC Abstract Specification Topic 2: Spatial referencing by coordinates. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for using Coordinate Reference Systems (CRSs)."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26734,35 +25888,69 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-006"
+ "@value": "09-076r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS"
+ "@value": "Uses and summary of Topic 2 - Spatial referencing by coordinates"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-099r2",
+ "@id": "http://www.opengis.net/def/doc-type/d-atb/collection",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Collection"
+ ],
+ "http://www.w3.org/2000/01/rdf-schema#label": [
+ {
+ "@value": "Documents of type Technical Baseline - deprecated "
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#definition": [
+ {
+ "@value": "Documents of type Technical Baseline - deprecated "
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
+ {
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#member": [
+ {
+ "@id": "http://www.opengis.net/def/docs/03-053r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-014r1"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ {
+ "@value": "Documents of type Technical Baseline - deprecated "
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-100r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-10-07"
+ "@value": "2014-05-28"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Panagiotis (Peter) A. Vretanos"
+ "@value": "Stephan Meissl"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/notes"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26772,27 +25960,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=39852"
+ "@id": "https://portal.ogc.org/files/?artifact_id=54813"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "10-099r2"
+ "@value": "12-100r1"
},
{
"@language": "en",
- "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0"
+ "@value": "GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/notes"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile."
+ "@value": "This Interface Standard is a profile of the OGC® GML Application Schema –Coverages version 1.0 [OC 09-146r2]. This document specifies the usage of the GeoTIFF data format for the encoding of GML coverages. This encoding is used by several OGC services like the Web Coverage Service (WCS) 2.0 Interface Standard – Core [OGC 09-110r4]."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26803,35 +25991,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-099r2"
+ "@value": "12-100r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0"
+ "@value": "OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/05-111r2",
+ "@id": "http://www.opengis.net/def/docs/04-088",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-05-09"
+ "@value": "2004-02-20"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Roland M. Wagner"
+ "@value": "Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/retired"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26841,27 +26029,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=13958"
+ "@id": "https://portal.ogc.org/files/?artifact_id=7561"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "05-111r2"
+ "@value": "04-088"
},
{
"@language": "en",
- "@value": "Access Control & Terms of Use (ToU) \"Click-through\" IPR Management"
+ "@value": "EA-SIG Mediation White Paper"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/retired"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document demonstrats a number of functional capabilities related to rights management (Terms-of-Use, Authentication, content services) that need to be described and chained. "
+ "@value": "*RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise\r\nService."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26872,35 +26060,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "05-111r2"
+ "@value": "04-088"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Access Control & Terms of Use (ToU) \"Click-through\" IPR Management"
+ "@value": "EA-SIG Mediation White Paper"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/17-086r3",
+ "@id": "http://www.opengis.net/def/docs/11-159",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2021-03-22"
+ "@value": "2011-10-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Peter Trevelyan, Paul Hershberg, Steve Olson"
+ "@value": "David Maidment, Ben Domenico, Alastair Gemmell, Kerstin Lehnert, David Tarboton, Ilya Zaslavsky"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/techpaper"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26910,27 +26098,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/17-086r3/17-086r3.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=46471&version=1"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "17-086r3"
+ "@value": "The Open Geospatial Consortium and EarthCube"
},
{
"@language": "en",
- "@value": "MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension"
+ "@value": "11-159"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/techpaper"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The purpose of the GetPolygon operation is to extract data contained within a polygon defined either by a set of points or the radius and position of a circle point. The need for the GetPolygon operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets.\r\n\r\nThis work has been done by members of the OGC MetOcean Domain Working Group."
+ "@value": "EarthCube aims to create an integrated system to access, analyze and share information that is\r\nused by the entire geosciences community. The Open Geospatial Consortium (OGC) is an\r\norganization of which more than four hundred companies and agencies are members, whose\r\npurpose is to create open source standards for sharing geospatial and observational information.\r\nThe authors of this paper are users of OGC standards in our work in hydrology, meteorology,\r\nclimatology, oceanography and in the solid earth sciences, in other words, in key disciplinary\r\nfields that contribute to the Geosciences. Moreover, the OGC has an effective process for\r\nengaging individuals from many countries in standards development and interoperability testing\r\nthat encourages them to set aside the roles they play in their home organizations and instead\r\nfocus just on what is needed to share a particular class of information across the globe. This\r\npaper examines the hypothesis that an OGC-like process could be useful for broader sharing of\r\ninformation in the geosciences."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -26941,35 +26129,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "17-086r3"
+ "@value": "11-159"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension"
+ "@value": "The Open Geospatial Consortium and EarthCube"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/02-028",
+ "@id": "http://www.opengis.net/def/docs/17-084r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2002-04-19"
+ "@value": "2021-04-21"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Tom McCarty"
+ "@value": "Y. Coene, U. Voges, O. Barois"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/ipr"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -26979,27 +26167,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1141"
+ "@id": "https://docs.ogc.org/bp/17-084r1/17-084r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "02-028"
+ "@value": "17-084r1"
},
{
"@language": "en",
- "@value": "Sensor Collection Service"
+ "@value": "EO Collection GeoJSON(-LD) Encoding"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/ipr"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The basic function of the Sensor Collection Service (SCS) is to provide a web-enabled interface to a sensor, collection of sensors or sensor proxy. Sensors are defined as devices that measure physical quantities. "
+ "@value": "JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC Best Practice describes a GeoJSON [NR2] and JSON-LD [NR13] encoding for Earth Observation (EO) metadata for collections (dataset series). This standard can be applied to encode metadata based on the OGC 11-035r1 [OR20] or ISO19139 [OR27], ISO19139-2 [OR28] specifications, or as an encoding of the Unified Metadata Model for Collections (UMM-C) conceptual model [OR2].\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction1 through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12].\r\n\r\nThis document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture.\r\n\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR7] which allows validation of instances against these schemas."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27010,35 +26198,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "02-028"
+ "@value": "17-084r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Sensor Collection Service"
+ "@value": "EO Collection GeoJSON(-LD) Encoding"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-052",
+ "@id": "http://www.opengis.net/def/docs/03-028",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2012-07-12"
+ "@value": "2003-01-17"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Peter Baumann"
+ "@value": "Josh Lieberman, Lou Reich, Peter Vretanos"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/notes"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27048,27 +26236,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=48650"
+ "@id": "https://portal.ogc.org/files/?artifact_id=1317"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "12-052"
+ "@value": "OGC Web Services UDDI Experiment"
},
{
"@language": "en",
- "@value": "WCS 2.0.1 Corrigendum Release Notes"
+ "@value": "03-028"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/notes"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document represents the release notes for the OGC Web Coverage Service (WCS) Interface Standard corrigendum 2.0.1. This corrigendum for WCS supersedes previous WCS versions."
+ "@value": "This document lists the design principles, requirements, and experimental results for future versions of a potential OGC - UDDI (Universal Discovery, Description, and Integration) profile of the OGC Catalog Implementation Specification. Specifically, it describes the usage scenarios, workplan, and experimental results for discovery of OGC services (including registries) through the UDDI interface using SOAP (Simple Object Access Protocol) messaging protocols. The baseline for this experiment is the specification for UDDI version 2 and use of private UDDI implementations. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27079,35 +26267,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-052"
+ "@value": "03-028"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC WCS 2.0.1 Corrigendum Release Notes"
+ "@value": "OGC Web Services UDDI Experiment"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-189",
+ "@id": "http://www.opengis.net/def/docs/21-054",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-08-27"
+ "@value": "2023-01-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Chris Holmes"
+ "@value": "Sergio Taleisnik"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-isc"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27117,27 +26305,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=19208"
+ "@id": "https://docs.ogc.org/per/21-054.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "06-189"
+ "@value": "OGC Disaster Pilot JSON-LD Structured Data Engineering Report"
},
{
"@language": "en",
- "@value": "Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2"
+ "@value": "21-054"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-isc"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document provides the details for a corrigendum for the existing OpenGIS Implementation Specification for the Geography Markup Language version 2.1.2 and does not modify that implementation specification. The current OpenGIS Implementation Specification that this document provides revision notes for is 02-069. "
+ "@value": "This Disaster Pilot JSON-LD Structured Data Engineering Report documents the analysis, discussions, results, and recommendations that emerge from the efforts carried out regarding the use of JSON-LD with OGC APIs to generate structured web page data for search engine optimization of disaster related information.\r\n\r\nThis ER provides the practical experience and lessons learned on the usage of Linked Data within OGC APIs with the objective of enhancing the web search and finding up-to-date conditions, observations, and predictions associated with well-known local geography. Upcoming initiatives should use the findings documented in this ER to further develop applications that make geospatial data and information more easily findable, accessible, interoperable, and reusable, which will increase the efficiency of disaster response. This ER could also be used as a case study of Linked Data to help other industries understand its value and implement it within their domains, or it could serve as a baseline for adding Linked Data support to one or several OGC API standards."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27148,35 +26336,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-189"
+ "@value": "21-054"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2"
+ "@value": "OGC Disaster Pilot JSON-LD Structured Data Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/20-072r2",
+ "@id": "http://www.opengis.net/def/docs/06-054r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2021-08-13"
+ "@value": "2006-07-12"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Hugo Ledoux"
+ "@value": "Arliss Whiteside"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/cs"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27186,27 +26374,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/cs/20-072r2/20-072r2.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=16080"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "CityJSON Community Standard 1.0"
+ "@value": "Image Geopostioning Service"
},
{
"@language": "en",
- "@value": "20-072r2"
+ "@value": "06-054r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/cs"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "CityJSON is a JSON-based encoding for a well-documented subset of the OGC CityGML data model (version 2.0.0). CityJSON defines how to store digital 3D models of cities and landscapes. The aim of CityJSON is to offer an alternative to the GML encoding of CityGML, which can be verbose and complex to read and manipulate. CityJSON aims at being easy-to-use, both for reading datasets and for creating them. It was designed with programmers in mind, so that tools and APIs supporting it can be quickly built."
+ "@value": "This document specifies the interface to an Image Geopositioning Service that adjusts the georeferencing coordinate transformations of multiple images. This adjustment is normally done using a photogrammetric triangulation process, although other methods could be used. Such triangulation adjusts the parameter values of the image georeferencing coordinate transformations using a least-squares fitting process to measured image positions with known error statistics."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27217,35 +26405,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "20-072r2"
+ "@value": "06-054r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC CityJSON Community Standard 1.0"
+ "@value": "OpenGIS Image Geopostioning Service"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-141r6",
+ "@id": "http://www.opengis.net/def/docs/07-018r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2012-01-09"
+ "@value": "2007-08-15"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Daniele Marchionni, Stefania Pappagallo "
+ "@value": "Philippe M"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27255,27 +26443,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=43928"
+ "@id": "https://portal.ogc.org/files/?artifact_id=21465"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "06-141r6"
+ "@value": "Sensor Planning Service Application Profile for EO Sensors"
},
{
"@language": "en",
- "@value": "Ordering Services Framework for Earth Observation Products Interface Standard"
+ "@value": "07-018r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products. "
+ "@value": "This SPS EO profile document specifies at a lower level the interfaces and parameters for requesting information describing the capabilities of a Sensor Planning Service dedicated to the EO Sensor domain, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27286,35 +26474,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-141r6"
+ "@value": "07-018r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Ordering Services Framework for Earth Observation Products Interface Standard"
+ "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/05-019",
+ "@id": "http://www.opengis.net/def/docs/06-103r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2005-02-02"
+ "@value": "2007-01-29"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Udo Quadt, Thomas Kolbe"
+ "@value": "John Herring"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/d-is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27324,27 +26512,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=8869"
+ "@id": "https://portal.ogc.org/files/?artifact_id=18241"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Web 3D Service"
+ "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture"
},
{
"@language": "en",
- "@value": "05-019"
+ "@value": "06-103r3"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/d-is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph. "
+ "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. \r\n\r\nPart 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. \r\n\r\nPart 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) \r\n\r\nThe corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27355,35 +26543,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "05-019"
+ "@value": "06-103r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Web 3D Service"
+ "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/17-002r1",
+ "@id": "http://www.opengis.net/def/docs/17-087r13",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-08-18"
+ "@value": "2020-08-28"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Carl Reed"
+ "@value": "John R. Herring"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/cs"
+ "@id": "http://www.opengis.net/def/doc-type/as"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27393,27 +26581,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/cs/17-002r1/17-002r1.html"
+ "@id": "https://docs.ogc.org/as/17-087r13/17-087r13.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "GeoRSS Encoding Standard"
+ "@value": "17-087r13"
},
{
"@language": "en",
- "@value": "17-002r1"
+ "@value": "Topic 01 - Spatial schema"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/cs"
+ "@id": "http://www.opengis.net/def/doc-type/as"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "GeoRSS is designed as a lightweight, community driven way to extend existing RSS feeds with simple geographic information. The GeoRSS standard provides for encoding location in an interoperable manner so that applications can request, aggregate, share and map geographically tag feeds."
+ "@value": "This document is the ISO 19107:2019 Standard and specifies conceptual schemas for describing the spatial characteristics of geographic entities, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27424,35 +26612,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "17-002r1"
+ "@value": "17-087r13"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC GeoRSS Encoding Standard"
+ "@value": "Topic 1 - Spatial schema"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/03-064r1",
+ "@id": "http://www.opengis.net/def/docs/16-100r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2003-06-12"
+ "@value": "2017-08-16"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Phillip C. Dibner"
+ "@value": "Paul Scarponcini"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27462,27 +26650,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1267"
+ "@id": "https://portal.ogc.org/files/?artifact_id=75117"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "GO-1 Application Objects Report"
+ "@value": "16-100r2"
},
{
"@language": "en",
- "@value": "03-064r1"
+ "@value": "InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-dp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document is a draft of the OpenGIS"
+ "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 0 addresses the Core Requirements Class from LandInfra."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27493,35 +26681,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "03-064r1"
+ "@value": "16-100r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "GO-1 Application Objects Report"
+ "@value": "OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-070r3",
+ "@id": "http://www.opengis.net/def/docs/04-038r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-12-19"
+ "@value": "2004-10-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Carl Reed"
+ "@value": "Uwe Voges, Kristian Senkler"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27531,27 +26719,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/16-070r3"
+ "@id": "https://portal.ogc.org/files/?artifact_id=6495"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage"
+ "@value": "04-038r1"
},
{
"@language": "en",
- "@value": "16-070r3"
+ "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features."
+ "@value": "This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27562,35 +26750,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-070r3"
+ "@value": "04-038r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage"
+ "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/05-087r4",
+ "@id": "http://www.opengis.net/def/docs/06-022r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-10-11"
+ "@value": "2006-04-21"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon Cox"
+ "@value": "James Resler"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-bp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27600,27 +26788,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=17038"
+ "@id": "https://portal.ogc.org/files/?artifact_id=14898"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "05-087r4"
+ "@value": "06-022r1"
},
{
"@language": "en",
- "@value": "Observations and Measurements"
+ "@value": "Temporal Standard Recommendations"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-bp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The general models and XML encodings for observations and measurements, including but not restricted to those using sensors."
+ "@value": "This document summarizes recommendations for extending geospatial standards with regard to time-varying information. These proposals are the result of the National Technology Alliance program called Temporal Evaluation and Assessment (TEA). "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27631,35 +26819,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "05-087r4"
+ "@value": "06-022r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Observations and Measurements"
+ "@value": "Temporal Standard Recommendations"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-062",
+ "@id": "http://www.opengis.net/def/docs/09-166r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-08-14"
+ "@value": "2010-02-01"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Gerhard Gr"
+ "@value": "Benjamin Hagedorn"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-bp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27669,27 +26857,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=22120"
+ "@id": "https://portal.ogc.org/files/?artifact_id=37257"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "City Geography Markup Language"
+ "@value": "Web View Service Discussion Paper"
},
{
"@language": "en",
- "@value": "07-062"
+ "@value": "09-166r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-bp"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "CityGML is designed as an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is implemented as an application schema of the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange and encoding issued by the Open Geospatial Consortium (OGC) and the ISO TC211. "
+ "@value": "The Web View Service (WVS) is an extendable, interactive, image-based portrayal service for complex three-dimensional geodata such as 3D landscape and city models. 3D geodata is delivered as finally rendered images. Besides color images, relevant thematic and geometrical information such as object identity information or depth data is provided. Additionally, the WVS supports interaction with the portrayed 3D environment, e.g., information retrieval, spatial analysis, and 3D navigation. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27700,35 +26888,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-062"
+ "@value": "09-166r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "City Geography Markup Language"
+ "@value": "Web View Service Discussion Paper"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-140r1",
+ "@id": "http://www.opengis.net/def/docs/14-004r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-02-26"
+ "@value": "2014-10-20"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Peter Baumann, Stephan Meissl, Jinsongdi Yu"
+ "@value": "Volker Andres, Simon Jirka , Michael Utech"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/profile"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27738,27 +26926,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=42722"
+ "@id": "https://docs.ogc.org/bp/14-004r1/14-004r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "10-140r1"
+ "@value": "Sensor Observation Service 2.0 Hydrology Profile"
},
{
"@language": "en",
- "@value": "Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile"
+ "@value": "14-004r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/profile"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OGC Web Coverage Service (WCS) Application Profile – Earth Observation (EO-WCS), defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data."
+ "@value": "This OGC document defines an OGC Sensor Observation Service (SOS) 2.0 hydrology profile for SOS 2.0 implementations serving OGC WaterML 2.0. The development of this OGC Best Practice (BP) is based on previous activities and results (i.e. Hydrology Interoperability Experiments[1] as well as the European FP7 project GEOWOW[2]). The work is guided by the need to overcome semantic issues between different SOS instances serving hydrological data and the related client applications. Therefore, this profile focuses on how to use the entities and requests of the standards and defines the necessary technical details to implement the hydrology SOS profile."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27769,120 +26957,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-140r1"
+ "@value": "14-004r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/doc-type/as/collection",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Collection"
- ],
- "http://www.w3.org/2000/01/rdf-schema#label": [
- {
- "@value": "Documents of type OGC Abstract Specification"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
- {
- "@value": "Documents of type OGC Abstract Specification"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
- {
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#member": [
- {
- "@id": "http://www.opengis.net/def/docs/99-110"
- },
- {
- "@id": "http://www.opengis.net/def/docs/04-107"
- },
- {
- "@id": "http://www.opengis.net/def/docs/99-108r2"
- },
- {
- "@id": "http://www.opengis.net/def/docs/00-116"
- },
- {
- "@id": "http://www.opengis.net/def/docs/02-112"
- },
- {
- "@id": "http://www.opengis.net/def/docs/06-004r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/10-030"
- },
- {
- "@id": "http://www.opengis.net/def/docs/99-113"
- },
- {
- "@id": "http://www.opengis.net/def/docs/11-111r1"
- },
- {
- "@id": "http://www.opengis.net/def/docs/18-005r8"
- },
- {
- "@id": "http://www.opengis.net/def/docs/20-040r3"
- },
- {
- "@id": "http://www.opengis.net/def/docs/04-084r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/07-011"
- },
- {
- "@id": "http://www.opengis.net/def/docs/20-082r4"
- },
- {
- "@id": "http://www.opengis.net/def/docs/08-126"
- },
- {
- "@id": "http://www.opengis.net/def/docs/17-087r13"
- },
- {
- "@id": "http://www.opengis.net/def/docs/19-014r3"
- },
- {
- "@id": "http://www.opengis.net/def/docs/00-115"
- },
- {
- "@id": "http://www.opengis.net/def/docs/21-053r1"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
- {
- "@value": "Documents of type OGC Abstract Specification"
+ "@value": "OGC® Sensor Observation Service 2.0 Hydrology Profile"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-115",
+ "@id": "http://www.opengis.net/def/docs/05-007r7",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2015-01-21"
+ "@value": "2007-10-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "George Percivall"
+ "@value": "Peter Schut"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/techpaper"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27892,37 +26995,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=61188"
- },
- {
- "@id": "https://portal.ogc.org/files/61188"
+ "@id": "https://portal.ogc.org/files/?artifact_id=24151"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OGC Smart Cities Spatial Information Framework"
- },
- {
- "@language": "en",
- "@value": "Smart Cities Spatial Information Framework"
+ "@value": "Web Processing Service"
},
{
"@language": "en",
- "@value": "14-115"
+ "@value": "05-007r7"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/techpaper"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This White Paper supports development of a Smart Cities Spatial Information Framework\r\nbased on these themes:\r\nK Smart Cities are high-density generators of innovation and information.\r\nK Location information is a major enabler of Smart City technology benefits.\r\nK Benefits of smart technology must be judged by benefits to residents.\r\nK Reuse and repurpose is vital to urban resilience\r\nK Open standards are needed for interoperability, efficiency, application innovation\r\nand cost effectiveness.\r\nDiscussion of these themes and this white paper will occur at the OGC Smart Cities\r\nLocation Powers Summit in Tokyo on December 2, 2014,\r\n1 the co-located OGC Technical\r\nCommittee meeting, and in many other forums in the future. As described in this paper,\r\nthere are many standards initiatives that focus on Smart Cities. Most Smart Cities use\r\ncases in some way involve indoor and/or outdoor location, and thus communication about\r\nlocation is an issue that cuts across the work programs most of the standards\r\norganizations that are involved with Smart Cities.\r\nThis white paper builds on the OGC - Directions Magazine webinar: “Making Location\r\nWork for Smart Cities – the Case for Location Standards”2."
- },
- {
- "@value": "This White Paper supports development of a Smart Cities Spatial Information Framework\r\nbased on these themes:\r\n- Smart Cities are high-density generators of innovation and information.\r\n- Location information is a major enabler of Smart City technology benefits.\r\n- Benefits of smart technology must be judged by benefits to residents.\r\n- Reuse and repurpose is vital to urban resilience\r\n- Open standards are needed for interoperability, efficiency, application innovation\r\nand cost effectiveness.\r\nDiscussion of these themes and this white paper will occur at the OGC Smart Cities\r\nLocation Powers Summit in Tokyo on December 2, 2014,1 the co-located OGC Technical\r\nCommittee meeting, and in many other forums in the future. As described in this paper,\r\nthere are many standards initiatives that focus on Smart Cities. Most Smart Cities use\r\ncases in some way involve indoor and/or outdoor location, and thus communication about\r\nlocation is an issue that cuts across the work programs most of the standards\r\norganizations that are involved with Smart Cities.\r\nThis white paper builds on the OGC - Directions Magazine webinar: “Making Location\r\nWork for Smart Cities – the Case for Location Standards”2."
+ "@value": "The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -27933,35 +27026,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-115"
+ "@value": "05-007r7"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Smart Cities Spatial Information Framework"
+ "@value": "Web Processing Service"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-097",
+ "@id": "http://www.opengis.net/def/docs/08-001",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-02-11"
+ "@value": "2008-04-29"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "David Blodgett, Byron Cochrane, Rob Atkinson, Sylvain Grellet, Abdelfettah Feliachi, Alistair Ritchi"
+ "@value": "Raj Singh"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -27971,27 +27064,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/18-097.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=26609"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "18-097"
+ "@value": "08-001"
},
{
"@language": "en",
- "@value": "Environmental Linked Features Interoperability Experiment Engineering Report"
+ "@value": "Loosely Coupled Synchronization of Geographic Databases in the CGDI"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Systems that maintain and disseminate information representing and/or related to spatial features often lack mechanisms to describe or discover how features relate to each other, to other kinds of features, and to a wide variety of related information that may be relevant. The Environmental Linked Features Interoperability Experiment (ELFIE) explored Open Geospatial Consortium (OGC) and World Wide Web Consortium (W3C) standards with the goal of establishing a best practice for exposing cross-domain links between environmental domain and sampling features. The Interoperability Experiment (IE) focused on encoding relationships between cross-domain features and linking available observations data to sampled domain features. An approach that leverages the OGC service baseline, W3C data on the web best practices, and JavaScript Object Notation for Linked Data (JSON-LD) contexts was developed and evaluated. Outcomes of the experiment demonstrate that broadly accepted web technologies for linked data can be applied using OGC services and domain data models to fill important gaps in existing environmental data systems' capabilities. While solutions were found to be capable and promising, OGC services and domain model implementations have limited utility for use in linked data applications in their current state and the universe of persistent URIs that form the foundation of a linked data infrastructure is still small. In addition to improvement of the standards baseline and publication of linked data URIs, establishing conventions for URI dereferencing behavior and default content given multiple options for a resource remain for future work."
+ "@value": "This Discussion Paper documents results from the Interoperability Program CGDI Pilot and describes a suite of services that enable the sharing of geographic information across organizations for the purposes of: geographic database synchronization in support of a spatial data infrastructure; geographic database modification suggestions from trusted and un-trusted sources; and the transmission of geographic information in emergency notification events.\r\n\r\nThese services are called the Update Feed Service; Feedback Feed Service; and Emergency Alert Service respectively. Their information encodings are all based on the Atom Syndication Format, extended with GML and WFS Filter encodings to support geospatial requirements, and were implemented in the Canadian Geospatial Data Infrastructure Pilot.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28002,25 +27095,25 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-097"
+ "@value": "08-001"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Environmental Linked Features Interoperability Experiment Engineering Report"
+ "@value": "OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-128r19",
+ "@id": "http://www.opengis.net/def/docs/15-039",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2024-02-06"
+ "@value": "2015-08-19"
}
],
"http://purl.org/dc/terms/creator": [
@@ -28030,7 +27123,7 @@
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28040,27 +27133,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://www.geopackage.org/spec140/index.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=63289"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "12-128r19"
+ "@value": "Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard"
},
{
"@language": "en",
- "@value": "GeoPackage Encoding Standard"
+ "@value": "15-039"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth."
+ "@value": "The GeoPackage Standards Working Group (SWG) presents a vision for storing tiled gridded elevation data in a GeoPackage."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28071,35 +27164,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-128r19"
+ "@value": "15-039"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® GeoPackage Encoding Standard"
+ "@value": "Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/02-023r4",
+ "@id": "http://www.opengis.net/def/docs/05-115",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2003-01-29"
+ "@value": "2006-03-28"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside"
+ "@value": "Joe Lewis"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28109,27 +27202,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=7174"
+ "@id": "https://portal.ogc.org/files/?artifact_id=12899"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "02-023r4"
+ "@value": "Geo Video Web Service"
},
{
"@language": "en",
- "@value": "Geography Markup Language (GML) Encoding Specification"
+ "@value": "05-115"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features."
+ "@value": "A GeoVideo Web Service (GVS) is a web service that facilitates the viewing of live and/or archived feeds from video cameras. The feeds may be composed of:\r\n- A video stream\r\n- Textual data in a caption stream (e.g. GPS data, camera states and characteristics, custom XML data, such as SensorMLTML)\r\n- A combination of a video stream and associated textual data\r\nThe video streams of the feed may be viewed in the Windows Media Player. The textual data is extracted through scripting events that are generated as the caption stream is processed and displayed by the Windows Media Player."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28140,35 +27233,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "02-023r4"
+ "@value": "05-115"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Geography Markup Language (GML) Encoding Specification"
+ "@value": "Geo Video Web Service"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-005r3",
+ "@id": "http://www.opengis.net/def/docs/23-013",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-12-02"
+ "@value": "2023-10-26"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker"
+ "@value": "Tom Kralidis, Mark Burgoyne, Steve Olson, Shane Mill"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28178,27 +27271,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/14-005r3/14-005r3.html"
+ "@id": "https://docs.ogc.org/dp/23-013.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "IndoorGML"
+ "@value": "23-013"
},
{
"@language": "en",
- "@value": "14-005r3"
+ "@value": "Discussion paper for Publish-Subscribe workflow in OGC APIs"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "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."
+ "@value": "OGC APIs provide Web based capabilities which are typically based on polling for collection resource updates (new features/records items, coverages, maps, etc.). Depending on a collection’s temporal resolution or frequency of updates, an event-driven / Publish-Subscribe architecture provides a timely, efficient, and low latency approach for delivery of data updates. This paper provides recommendations on applying Publish-Subscribe architectural patterns to OGC APIs."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28209,35 +27302,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-005r3"
+ "@value": "23-013"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® IndoorGML"
+ "@value": "Discussion paper for Publish-Subscribe workflow in OGC APIs"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-040r1",
+ "@id": "http://www.opengis.net/def/docs/12-081",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-06-30"
+ "@value": "2013-06-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Aleksandar Balaban"
+ "@value": "Simon Cox"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/pol-nts"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28247,27 +27340,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/16-040r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=51856"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-12 Aviation Security Engineering Report"
+ "@value": "12-081"
},
{
"@language": "en",
- "@value": "16-040r1"
+ "@value": "Name type specification – ontology resources"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/pol-nts"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The information security is the state of being protected against the unauthorized use of information and services, or the measures taken to achieve that. This report has ben created as part of OGC Testbed 12 aviation thread and on behalf of sponsors from FAA. It gives the readers an overview into the topic of cyber security in the aviation domain, especially in conjunction with OGC compatible web services, which are today de facto standard for aeronautical traffic System Wide Information Management."
+ "@value": "An OGC name is required for ontology resources published by OGC. This includes OWL\r\nontologies, classes and properties."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28278,35 +27371,39 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-040r1"
+ "@value": "12-081"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Testbed-12 Aviation Security Engineering Report"
+ "@value": "Name type specification – ontology resources"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/21-018",
+ "@id": "http://www.opengis.net/def/docs/14-095",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2022-02-08"
+ "@value": "2015-01-23"
+ },
+ {
+ "@type": "xsd:date",
+ "@value": "2015-01-22"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Panagiotis (Peter) A. Vretanos"
+ "@value": "Lance McKee"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/techpaper"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28316,27 +27413,37 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/21-018.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=60920"
+ },
+ {
+ "@id": "https://portal.ogc.org/files/60920"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Features and Geometries JSON CRS Analysis of Alternatives Engineering Report"
+ "@value": "Information Technology Standards for Sustainable Development"
},
{
"@language": "en",
- "@value": "21-018"
+ "@value": "OGC Information Technology Standards for Sustainable Development"
+ },
+ {
+ "@language": "en",
+ "@value": "14-095"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/techpaper"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "One of the primary requirements for the OGC Testbed-17 Features and Geometries JSON task is to define an extension or profile of GeoJSON that supports encoding spatiotemporal data in Coordinate Reference Systems (CRS) other than the GeoJSON default of the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees (CRS84).\r\n\r\nThis OGC Testbed 17 (TB17) Engineering Report (ER) presents the various alternatives considered for declaring CRS information in a Features and Geometries JSON (JSON-FG) file. JSON-FG is an OGC extension to GeoJSON that, among other things, adds support of coordinate reference systems other than the CRS84 default. One of the alternatives was selected to be the mechanism for declaring CRS information in a JSON-FG document and is fully described in the “OGC Testbed-17: OGC Features and Geometries JSON Engineering Report” (OGC 21-017r1).\r\n\r\nThis ER was submitted to the OGC Features and Geometries JSON Standards Working Group so that the work in TB17 can inform their task of developing and documenting a Features and Geometries JSON standard."
+ "@value": "Sustainable development, meeting the needs of the present without compromising the\r\nability of future generations to meet their own needs,1\r\n will be accomplished by\r\nbalancing social, economic and environmental objectives. In this paper the authors\r\nexplain that rigorous standards for communicating environmental data are absolutely\r\nessential to enable social and economic progress in the Age of the Environment2 – the\r\nAnthropocene Epoch3 – in which humanity's expanding footprint has become the main\r\ncause of change in the planet's geology, water bodies, atmosphere and biosphere. The\r\nauthors argue for a concerted and ongoing global effort to 1) define data communication\r\nand system interoperability requirements for environmental science, business and policy,\r\nand then 2) develop and implement consensus-derived, free and open environmental\r\nInformation Technology (IT) standards that meet those requirements and that co-evolve\r\nwith the larger IT standards framework and advances in IT."
+ },
+ {
+ "@value": "Sustainable development, meeting the needs of the present without compromising the ability of future generations to meet their own needs, will be accomplished by balancing social, economic and environmental objectives. In this paper the authors explain that rigorous standards for communicating environmental data are absolutely essential to enable social and economic progress in the Age of the Environment – the Anthropocene Epoch – in which humanity's expanding footprint has become the main cause of change in the planet's geology, water bodies, atmosphere and biosphere. The authors argue for a concerted and ongoing global effort to 1) define data communication and system interoperability requirements for environmental science, business and policy, and then 2) develop and implement consensus-derived, free and open environmental Information Technology (IT) standards that meet those requirements and that co-evolve with the larger IT standards framework and advances in IT."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28347,35 +27454,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "21-018"
+ "@value": "14-095"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-17: Features and Geometries JSON CRS Analysis of Alternatives Engineering Report"
+ "@value": "OGC Information Technology Standards for Sustainable Development"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/14-003",
+ "@id": "http://www.opengis.net/def/docs/02-066r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-12-02"
+ "@value": "2002-08-29"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon J D Cox, Bruce A Simons"
+ "@value": "Jean-Philippe Humblet"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/d-rp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28385,27 +27492,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/bp/14-003/14-003.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=1181"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "14-003"
+ "@value": "02-066r1"
},
{
"@language": "en",
- "@value": "WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data"
+ "@value": "Web Map Context Documents"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/d-rp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Best Practice describes how to configure XML documents for single and time series water quality measurements. In addition to stating the rules for using the O&M and WML 2 standards, along with the appropriate content ontologies, this Best Practice provides guidance through examples. This document is intended to complement WaterML 2.0 as part of a suite of standards for water observation data."
+ "@value": "States how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent manner."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28416,35 +27523,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "14-003"
+ "@value": "02-066r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data"
+ "@value": "Web Map Context Documents"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-001",
+ "@id": "http://www.opengis.net/def/docs/14-044",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2011-03-21"
+ "@value": "2015-02-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Johannes Echterhoff"
+ "@value": "Lew Leinenweber"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28454,27 +27561,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=38476"
+ "@id": "https://portal.ogc.org/files/?artifact_id=61108"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "SWE Service Model Implementation Standard"
+ "@value": "Testbed 10 Summary Engineering Report"
},
{
"@language": "en",
- "@value": "09-001"
+ "@value": "14-044"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard."
+ "@value": "The OGC Testbed 10 was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for Testbed 10 was conducted between October 2013 and April 2014."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28485,30 +27592,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-001"
+ "@value": "14-044"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS® SWE Service Model Implementation Standard"
+ "@value": "OGC® Testbed 10 Summary Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/04-052",
+ "@id": "http://www.opengis.net/def/docs/05-102r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2004-09-26"
+ "@value": "2006-05-09"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Arliss Whiteside"
+ "@value": "David Burggraf, Stan Tillman"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -28523,17 +27630,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=6660"
+ "@id": "https://portal.ogc.org/files/?artifact_id=14337"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS1.2 Image Handling Requirements"
+ "@value": "OWS3 GML Topology Investigation"
},
{
"@language": "en",
- "@value": "04-052"
+ "@value": "05-102r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -28543,7 +27650,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document was developed as part of the Image Handling Thread of the OGC Web Services Initiative Phase 1 Thread Set 2 (OWS 1.2). This document specified the requirements for the image handling functions to be supported by draft specifications prepared under that thread. "
+ "@value": "Part 1 of this investigation is conducted by Galdos Systems. In this part, the OWS3 MSD3 geometric description is extended to include a topology encoding as defined by the MSD3 schema. Part 2 (Clause 6.2) of this investigation is conducted by Intergraph Corp. and describes and discusses the impacts of encoding topology within the GML data. \r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28554,35 +27661,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "04-052"
+ "@value": "05-102r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS1.2 Image Handling Requirements"
+ "@value": "OWS3 GML Topology Investigation"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-144r2",
+ "@id": "http://www.opengis.net/def/docs/09-034",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2008-03-11"
+ "@value": "2009-07-29"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Richard Martell"
+ "@value": "Genong (Eugene) Yu, Liping Di"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28592,27 +27699,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=27093"
+ "@id": "https://portal.ogc.org/files/?artifact_id=33925"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-144r2"
+ "@value": "OWS-6 Georeferencable Imagery Engineering Report"
},
{
"@language": "en",
- "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package"
+ "@value": "09-034"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® document is a companion to the CSW-ebRIM catalogue profile (OGC 07-110r2). It specifies the content of the Basic extension package that shall be supported by all conforming services. The package includes extension elements of general utility that may be used to characterize a wide variety of geographic information resources, with a focus on service-oriented metadata management."
+ "@value": "This document discusses considerations about and recommendations for approaches for georeferenceable imagery under the Sensor Web Enablement thread during OGC Web Services Phase 6. This is an extension to the work described in the previous engineering report number OGC 08-071 . Georeferencealbe imagery is “a referenceable grid that has information that can be used to transform grid coordinates to external coordinates, but the transformation shall not be required to be an affine transformation”. Geolocation of georeferenceable imagery refers to the techniques described in ISO 19130, such as sensor models, functional fit models, and spatial registration using control points."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28623,35 +27730,91 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-144r2"
+ "@value": "09-034"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package"
+ "@value": "OWS-6 Georeferencable Imagery Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/11-097",
+ "@id": "http://www.opengis.net/def/doc-type/notes",
+ "http://www.w3.org/2004/02/skos/core#narrower": [
+ {
+ "@id": "http://www.opengis.net/def/docs/11-044"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-126r8"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-061"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-099r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-016r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-066r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-052"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-123r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-024r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-066r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-004"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/23-018r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/19-034r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/22-032r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-066r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/20-006"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-111"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-084r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2011-12-19"
+ "@value": "2009-10-13"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jérôme JANSOU, Thibault DACLA"
+ "@value": "Jo Walsh, Pedro Gonçalves, Andrew Turner"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28661,27 +27824,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=46394"
+ "@id": "https://portal.ogc.org/files/?artifact_id=35983"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-8 AIXM 5.1 Compression Benchmarking"
+ "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard"
},
{
"@language": "en",
- "@value": "11-097"
+ "@value": "09-084r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. With version 5.1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year.\r\nIn a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services. This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link. Today, datalink communications lack bandwidth and future datalink will still have a limited capacity.\r\n"
+ "@value": "The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28692,35 +27855,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "11-097"
+ "@value": "09-084r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-8 AIXM 5.1 Compression Benchmarking"
+ "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-003r1",
+ "@id": "http://www.opengis.net/def/docs/14-084r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-06-04"
+ "@value": "2015-02-17"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Louis Hecht, Jr., Raj Singh"
+ "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28730,27 +27893,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=37223"
+ "@id": "https://docs.ogc.org/is/14-084r2/14-084r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "10-003r1"
+ "@value": "14-084r2"
},
{
"@language": "en",
- "@value": "Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed"
+ "@value": "Moving Features Encoding Extension: Simple Comma Separated Values (CSV)"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Architecture, Engineering, Construction, Owner Operator, Phase 1 (AECOO-1) Testbed developed and implemented methods to streamline communications between parties in the conceptual design phase to get an early understanding of the tradeoffs between construction cost and energy efficiency. To that end, the project developed the interoperability components required for these analyses in collaborative team settings. These were Information Delivery Manuals (IDMs) for quantity takeoffs and energy analysis business processes, and used these to define Model View Definitions (MVDs)—standards-based subsets of Industry Foundation Classes (IFCs). AECOO-1 was conducted in response the felt need that overall productivity loss and fragmentation in the capital facilities development industries is no longer tolerable. All stakeholders need to practice the best way they know, and practice profitably; software interoperability problems must not hold them back. Non-interoperable software and data is cause for loss of competition across the market."
+ "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28761,35 +27924,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-003r1"
+ "@value": "14-084r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed"
+ "@value": "OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/03-064r5",
+ "@id": "http://www.opengis.net/def/docs/10-099r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2004-06-25"
+ "@value": "2010-10-07"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Eric Bertel"
+ "@value": "Panagiotis (Peter) A. Vretanos"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rp"
+ "@id": "http://www.opengis.net/def/doc-type/notes"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28799,27 +27962,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=5936"
+ "@id": "https://portal.ogc.org/files/?artifact_id=39852"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "03-064r5"
+ "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0"
},
{
"@language": "en",
- "@value": "GO-1 Application Objects"
+ "@value": "10-099r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rp"
+ "@id": "http://www.opengis.net/def/doc-type/notes"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The GO-1 Application Objects specification defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics."
+ "@value": "This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28830,38 +27993,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "03-064r5"
+ "@value": "10-099r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "GO-1 Application Objects"
+ "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-165r1",
+ "@id": "http://www.opengis.net/def/docs/17-014r9",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-04-02"
+ "@value": "2023-01-11"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Carl Reed, Mike Botts, George Percivall, John Davidson"
- },
- {
- "@value": "Mike Botts, George Percivall, Carl Reed, John Davidson"
+ "@value": "Carl Reed, Tamrat Belayneh"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/techpaper"
+ "@id": "http://www.opengis.net/def/doc-type/cs"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -28871,34 +28031,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/wp/07-165r1/"
+ "@id": "https://docs.ogc.org/cs/17-014r9/17-014r9.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-165r1"
- },
- {
- "@language": "en",
- "@value": "OGC Sensor Web Enablement: Overview and High Level Architecture"
+ "@value": "17-014r9"
},
{
"@language": "en",
- "@value": "Sensor Web Enablement: Overview And High Level Architecture"
+ "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/techpaper"
+ "@id": "http://www.opengis.net/def/doc-type/cs"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "A sensor network is a computer accessible network of many, spatially distributed devices using sensors to monitor conditions at different locations, such as temperature, sound, vibration, pressure, motion or pollutants[1]. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs)."
- },
- {
- "@value": "This OGC White Paper provides a high-level overview of and architecture for the Open Geospatial\r\nConsortium (OGC) standards activities that focus on sensors, sensor networks, and a concept called the\r\n“Sensor Web”. This OGC focus area is known as Sensor Web Enablement (SWE)."
+ "@value": "The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers.\r\n\r\nA single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28909,34 +28062,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-165r1"
+ "@value": "17-014r9"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Sensor Web Enablement: Overview And High Level Architecture"
- },
- {
- "@language": "en",
- "@value": "OGC Sensor Web Enablement: Overview and High Level Architecture"
+ "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/19-010r2",
+ "@id": "http://www.opengis.net/def/docs/12-154",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-12-12"
+ "@value": "2013-02-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Clemens Portele"
+ "@value": "Darko Androsevic"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -28951,17 +28100,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/19-010r2.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=51889"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "19-010r2"
+ "@value": "OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report "
},
{
"@language": "en",
- "@value": "OGC Testbed-15: Styles API Engineering Report"
+ "@value": "12-154"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -28971,7 +28120,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document is a proof of concept of a draft specification of the OGC Styles Application Programming Interface (API) that defines a Web API that enables map servers and clients as well as visual style editors to manage and fetch styles.\r\n\r\nWeb APIs are software interfaces that use an architectural style that is founded on the technologies of the Web. Styles consist of symbolizing instructions that are applied by a rendering engine on features and/or coverages.\r\n\r\nThe Styles API supports several types of consumers, mainly:\r\n\r\nVisual style editors that create, update and delete styles for datasets that are shared by other Web APIs implementing the OGC API - Features - Part 1: Core standard or the draft OGC API - Coverages or draft OGC API - Tiles specifications;\r\n\r\nWeb APIs implementing the draft OGC API - Maps specification fetch styles and render spatial data (features or coverages) on the server;\r\n\r\nMap clients that fetch styles and render spatial data (features or coverages) on the client.\r\n\r\nFeature data is either accessed directly or organized into spatial partitions such as a tiled data store (aka vector tiles).\r\n\r\nThe Styles API is consistent with the emerging OGC API family of standards.\r\n\r\nThe Styles API implements the conceptual model for style encodings and style metadata as documented in chapter 6 of the OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report.\r\n\r\nThe model defines three main concepts:\r\n\r\nThe style is the main resource.\r\n\r\nEach style is available in one or more stylesheets - the representation of a style in an encoding like OGC SLD 1.0 or Mapbox Style. Clients will use the stylesheet of a style that fits best based on the capabilities of available tools and their preferences.\r\n\r\nFor each style there is style metadata available, with general descriptive information about the style, structural information (e.g., layers and attributes), and so forth to allow users to discover and select existing styles for their data."
+ "@value": "This OGC® document provides mapping of the national imagery transmission format (NITF) version 2.1 format and NITF tagged record extensions (TRE) to GMLJP2 v2.0 (draft) format.\r\nThis Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative. \r\nThis document further describes study results of analyses of NITF and NITF extensions (TRE) capabilities and how they can be supported by GMLJP2 2.0 (draft). This activity was a part of the OGC OWS-9 Innovations thread.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -28982,35 +28131,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-010r2"
+ "@value": "12-154"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15: Styles API Engineering Report"
+ "@value": "OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report "
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/11-062r2",
+ "@id": "http://www.opengis.net/def/docs/07-012",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2011-11-17"
+ "@value": "2007-09-04"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "David Burggraf, Ron Lake"
+ "@value": "Jennifer Marcus, Chuck Morris"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29020,27 +28169,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=46548"
+ "@id": "https://portal.ogc.org/files/?artifact_id=20582"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-8 CCI Portrayal Registries Engineering Report"
+ "@value": "07-012"
},
{
"@language": "en",
- "@value": "11-062r2"
+ "@value": "Compliance Test Engine Interoperability Program Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OWS-8 Cross Community Interoperability (CCI) thread was built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artifacts. This OGC engineering report aims to present findings from the portrayal registries as part of the CCI subthread"
+ "@value": "As a work item in the OWS4/Conformance and Interoperability Test and Evaluation (CITE) project, Northrop Grumman Information Technology (NGIT) provided an open source web services compliance engine. NGIT refers to this engine as the Test Evaluation And Measurement (TEAM) Engine. It executes scripts written in Compliance Test Language (CTL), a grammar also developed by NGIT. This IPR describes TEAM Engine in detail and provides information on how it was used in OWS-4/CITE."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29051,35 +28200,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "11-062r2"
+ "@value": "07-012"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-8 CCI Portrayal Registries Engineering Report"
+ "@value": "Compliance Test Engine Interoperability Program Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-113r5",
+ "@id": "http://www.opengis.net/def/docs/06-010r6",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-12-19"
+ "@value": "2007-07-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Carl Reed"
+ "@value": "Steve Havens"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/retired"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29089,27 +28238,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/15-113r5"
+ "@id": "https://portal.ogc.org/files/?artifact_id=19371"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "15-113r5"
+ "@value": "06-010r6"
},
{
"@language": "en",
- "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure"
+ "@value": "Transducer Markup Language"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/retired"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time."
+ "@value": "*THIS STANDARD HAS BEEN RETIRED* \r\n\r\nThe OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system.\r\n \r\nThe protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations.\r\n \r\nThe sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion.\r\n\r\nThis is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29120,35 +28269,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-113r5"
+ "@value": "06-010r6"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure"
+ "@value": "OpenGIS Transducer Markup Language *RETIRED*"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-007r1",
+ "@id": "http://www.opengis.net/def/docs/19-025r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-06-06"
+ "@value": "2019-08-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Paul Watson"
+ "@value": "Robert Thomas, Terry Idol"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29158,27 +28307,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=21821"
+ "@id": "https://portal.ogc.org/files/?artifact_id=88037"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS4 - Topology Quality Assessment Interoperability Program Report"
+ "@value": "19-025r1"
},
{
"@language": "en",
- "@value": "07-007r1"
+ "@value": "Development of Spatial Data Infrastructures for Marine Data Management"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document describes the purpose and function of the Topology Quality Assessment Service developed and deployed within the Geo-processing workflow thread of the OWS4 interoperability testbed."
+ "@value": "This engineering report presents the results of a concept development study on a\r\nMarine Spatial Data Infrastructure (SDI), sponsored by the National Geospatial-\r\nIntelligence Agency (NGA) - Maritime Safety Office (MSO), on behalf of the\r\nInternational Hydrographic Organization (IHO) and the IHO MSDI Working Group\r\n(MSDIWG), and executed by the Open Geospatial Consortium (OGC). The goal of\r\nthis study was to demonstrate to stakeholders the diversity, richness and value of a\r\nMarine SDI – specifically data, analysis, interoperability and associated IT services\r\n- including web services - in addressing needs of the marine domain."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29189,35 +28338,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-007r1"
+ "@value": "19-025r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS4 - Topology Quality Assessment Interoperability Program Report"
+ "@value": "Development of Spatial Data Infrastructures for Marine Data Management"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-026",
+ "@id": "http://www.opengis.net/def/docs/18-008r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2015-10-30"
+ "@value": "2019-02-12"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Thomas Forbes, Alberto Olivares, Richard Rombouts"
+ "@value": "Christiaan Lemmen, Peter van Oosterom, Mohsen Kalantari, Eva-Maria Unger, Cornelis de Zeeuw"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/techpaper"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29227,27 +28376,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=63306"
+ "@id": "https://docs.ogc.org/wp/18-008r1/18-008r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-11 Aviation Feature Schema Recommendations Engineering Report"
+ "@value": "White Paper on Land Administration"
},
{
"@language": "en",
- "@value": "15-026"
+ "@value": "18-008r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/techpaper"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Developed by EUROCONTROL, the Aviation Feature Schema (AFX) is a template for\r\napplication schemas to implement by adding their operational attributes. For example, the\r\nAirport Mapping format can be implemented by extending AFX. The AFX defines\r\nconcepts of geometry and temporality through predefined classes and properties.\r\nTherefore, these elements need not be redefined by application schemas. This means\r\nimplementations of the AFX abide by the same structure, therefore aiding interoperability\r\nand allowing the rapid development of schemas. The AFX schema is designed to be\r\ngeneric and easily reusable and it is not intended to replace the standard aviation models\r\nsuch as WXXM and AIXM.\r\nThis Engineering Report assesses the suitability of the AFX as a template for lowering\r\nthe GIS entry level for aviation data, providing recommendations of suitability and areas\r\nof improvement. The report is aimed at system and client developers that shall use AFX."
+ "@value": "This white paper provides an overview of the land administration domain and proposes actions needed for design and develop implementation standards this domain. A close cooperation between the Open Geospatial Consortium (OGC) and ISO is expected to accelerate those developments.\r\n\r\nA huge task is waiting: the establishment of land rights for all: young and old, rich and poor, male and female. Data on many millions of parcels, spatial units, (use-) rights, persons, and parties have to be collected, linked, maintained, and published. Land Administration Systems (LAS) should be designed for maintenance of the dynamic relations between people and land. Existing land administrations require extensions: such as 3D and 4D functionality and datasets, blockchain for transparent transactions, generic processes and integration with remote sensing, and processes to support conversion from social to legal tenure.\r\n\r\nA broad range of geospatial technologies and applications are available. They range from satellite and drone imaging and mapping, to geodesy, precise positioning, geo‐information science, cartography, spatial data infrastructure, and many surveying sub‐disciplines. The scientific and professional disciplines in the geospatial community design, develop, and apply those technologies. Apart from this technical component, a land administration also has a social and legal component. This makes land administration an arena where, apart from the geospatial community, many different scientific and professional disciplines meet. Depending on the stage of development and the level of societal acceptance of the land administration, those disciplines involved may be different."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29258,30 +28407,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-026"
+ "@value": "18-008r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Testbed-11 Aviation Feature Schema Recommendations Engineering Report"
+ "@value": "OGC White Paper on Land Administration"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-002",
+ "@id": "http://www.opengis.net/def/docs/12-095",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-04-28"
+ "@value": "2013-06-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Raj Singh"
+ "@value": "James Gallagher, Peter Baumann"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -29296,17 +28445,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=37839"
+ "@id": "https://portal.ogc.org/files/?artifact_id=52783"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "10-002"
+ "@value": "OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study"
},
{
"@language": "en",
- "@value": "Climate Challenge Integration Plugfest 2009 Engineering Report"
+ "@value": "12-095"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -29316,7 +28465,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Engineering Report (ER) documents findings of the CCIP 2009 Plugfest, which was conducted via the public Internet to address requirements stated in the CCIP Call for Participation . It addresses concept development, specifications tested, and interoperability experiments conducted. The ER concludes with issues that arose, and provides recommendations for the refinement of OGC Specifications and the Plugfest process. Recommendations in this ER will be considered in the planning of future activities.\r\nOGC expresses thanks to the Australian Bureau of Meteorology and to CSIRO for sponsoring CCIP 2009.\r\n"
+ "@value": "This document represents the OWS-9 OWS Innovations Coverage Access Study\r\nEngineering Report. It contributes knowledge based on the experience prototyping the\r\nWCS 2.0 Service – Access Innovations component, established in close collaboration\r\nwith the OPeNDAP group. To this end, accessing a variety of coverage data types\r\nconsidering WCS 2.0 and DAP 2.0 interfaces have been implemented and demonstrated.\r\nThe final result is a WCS 2.0 interface for the DAP 2.0 suite."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29327,43 +28476,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-002"
+ "@value": "12-095"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Climate Challenge Integration Plugfest 2009 Engineering Report"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/doc-type/cp",
- "http://www.w3.org/2004/02/skos/core#narrower": [
- {
- "@id": "http://www.opengis.net/def/docs/18-095r7"
+ "@value": "OGC® OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/19-023r1",
+ "@id": "http://www.opengis.net/def/docs/07-023r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-12-11"
+ "@value": "2007-05-16"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Andrea Aime"
+ "@value": "Paul Cote"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29373,27 +28514,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/19-023r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=21622"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report"
+ "@value": "07-023r2"
},
{
"@language": "en",
- "@value": "19-023r1"
+ "@value": "OGC Web Services Architecture for CAD GIS and BIM"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Testbed 15 Engineering Report (ER) describes a style encoding and metadata conceptual model that provides information for understanding styles intended usage, availability, compatibility with existing layers, and supporting style search. A style is a sequence of rules of symbolizing instructions to be applied by a rendering engine on one or more features and/or coverages"
+ "@value": "This document lists the design principles and requirements for future versions of a potential architecture for integrating workflows and information models from Computer Aided Design and Building Information Modelling with the principles of the OGC Web Services Architecture. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29404,35 +28545,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-023r1"
+ "@value": "07-023r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report"
+ "@value": "OGC Web Services Architecture for CAD GIS and BIM"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/05-050",
+ "@id": "http://www.opengis.net/def/docs/14-049",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-05-02"
+ "@value": "2014-07-16"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Craig Bruce"
+ "@value": "Ingo Simonis, Stephane Fellah"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29442,27 +28583,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=12983"
+ "@id": "https://portal.ogc.org/files/?artifact_id=58974"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "05-050"
+ "@value": "Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report"
},
{
"@language": "en",
- "@value": "GML Performance Investigations by CubeWerx"
+ "@value": "14-049"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways."
+ "@value": "Testbed 10 ontology work focused on:\r\n•\tA general examination of ontologies in the context of OGC data modeling, handling, and organization. Testbed-10 has started to define a consistent set of ontologies implementing solid theoretical foundations and semantics. \r\n•\tThe definition of a core ontologies for representing incident information used by Incident Management Systems (IMS) and mapping symbologies used in the emergency and disaster management domain with the goal to improve interoperability between different IMS symbology sets used across multi-level jurisdiction. \r\n•\tAddressed ontology mapping between hydrology feature models using SPARQL and OWL2.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29473,35 +28614,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "05-050"
+ "@value": "14-049"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "GML Performance Investigations by CubeWerx"
+ "@value": "OGC® Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/17-020r1",
+ "@id": "http://www.opengis.net/def/docs/06-126",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-01-26"
+ "@value": "2006-10-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Johannes Echterhoff, Clemens Portele"
+ "@value": "Chuck Morris"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29511,27 +28652,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/17-020r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=16860"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "17-020r1"
+ "@value": "06-126"
},
{
"@language": "en",
- "@value": "Testbed-13: NAS Profiling Engineering Report"
+ "@value": "Compliance Test Language (CTL) Discussion Paper"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The National System for Geospatial-Intelligence (NSG) Application Schema (NAS) is an ISO 19109 compliant application schema that defines the conceptual model for identifying and encoding feature data in the U.S. National System for Geospatial-Intelligence (NSG). NGA utilizes the open source software tool ShapeChange as an integral piece in NAS development. This tool is used to take NAS-based UML models and create Extensible Markup Language (XML) and Resource Description Framework (RDF) based schemas. Testbed-12 began development of capabilities for extracting profiles supporting specific mission functions from the full NAS content. Testbed-13 further refined the approach to NAS Profiling by investigating how a specific profile (Urban Military Profile) can be processed in an automated way and used to derive implementation schemas for the OGC standards CDB and CityGML.\r\n\r\nThis OGC Engineering Report describes:\r\n\r\nThe specification of a NAS-based Military Urban Profile as a Unified Modeling Language (UML) model (chapter 5);\r\n\r\nHow mission-specific sub-profiles can be specified and maintained using ShapeChange and the new ShapeChange Profile Management Tool (chapter 6); and\r\n\r\nHow the model and profile information are processed to derive output for\r\n\r\na CDB data store (chapter 7, chapter 8) and\r\n\r\na CityGML Application Domain Extension (chapter 9).\r\n\r\nThis work provides insights into:\r\n\r\nThe requirements and constraints on managing profiles of complex ISO 19109 compliant application schemas such as the NAS; and\r\n\r\nUsing a model-driven approach to generate implementation schemas of an ISO 19109 compliant application schema profile for different environments.\r\n\r\nThe target audience of this document is anyone interested in these topics. The implementation environments discussed in this report are the OGC standards CDB and CityGML. The profiled application schema is the NAS.\r\n\r\nThis report assumes that readers are familiar with the key concepts and technologies discussed in this document. This document does not provide an introduction to them, but the table below provides a brief summary and pointers to more information."
+ "@value": "This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29542,35 +28683,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "17-020r1"
+ "@value": "06-126"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-13: NAS Profiling Engineering Report"
+ "@value": "Compliance Test Language (CTL) Discussion Paper"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/19-045r3",
+ "@id": "http://www.opengis.net/def/docs/15-028",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2020-05-21"
+ "@value": "2015-08-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Kyoung-Sook KIM, Nobuhiro ISHIMARU"
+ "@value": "Daniel Balog"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29580,27 +28721,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/19-045r3/19-045r3.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=63281"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "19-045r3"
+ "@value": "Testbed 11 Data Broker Specifications Engineering Report"
},
{
"@language": "en",
- "@value": "Moving Features Encoding Extension - JSON"
+ "@value": "15-028"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This standard defines how to encode and share the various movements of geographic features by using JavaScript Object Notation (JSON). It provides an alternative encoding for OGC Moving Features instead of that provided in the XML Core [OGC 14-083r2] and Simple CSV [OGC 14-084r2] standards. A moving feature, for instance a vehicle or a pedestrian, contains a temporal geometry whose location continuously changes over time and dynamic non-spatial attributes whose values vary with time. This Moving Features JSON encoding defines a set of keywords to implement the conceptual schema of moving features defined in ISO 19141:2008 [ISO 19141:2008], accompanied with IETF GeoJSON Format [IETF RFC 7946]."
+ "@value": "This document is a deliverable of the OGC Testbed 11 Interoperability initiative. The report’s contents cover the summary of the interoperability work regarding the Aviation Data Broker concept. This data broker concept enables the setup of cascading OGC Web Feature Server (WFS) servers to form a data source chain, in which one service is capable of providing information coming from one or more other services. The objectives of this document are to research the feasibility of this concept and to investigate a number of specific Data Broker responsibilities and use cases, such as provenance and lineage, conflation, caching, scalability and flexible management of data sources."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29611,30 +28752,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-045r3"
+ "@value": "15-028"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Moving Features Encoding Extension - JSON"
+ "@value": "OGC® Testbed 11 Data Broker Specifications Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/16-034",
+ "@id": "http://www.opengis.net/def/docs/17-048",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-03-09"
+ "@value": "2017-08-31"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon Jirka, Arne de Wall, Christoph Stasch"
+ "@value": "Josh Lieberman, Andy Ryan"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -29649,17 +28790,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/16-034.html"
+ "@id": "https://docs.ogc.org/per/17-048.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-12 LiDAR Streaming Engineering Report"
+ "@value": "Underground Infrastructure Concept Study Engineering Report"
},
{
"@language": "en",
- "@value": "16-034"
+ "@value": "17-048"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -29669,7 +28810,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Engineering Report describes how developments of the Community Sensor Model Working Group (CSMW) can be harmonized with the latest SWE specifications and developments in order to support streaming of LiDAR data with SWE technologies. The report will therefore provide an overview on both initiatives and then describe different options how to integrate LiDAR data streams and SWE technologies. In particular, the ER will consider the results of the activities SOS Compression (LiDAR) Server (A012) and LiDAR Streaming Client (A010) and infer recommendations for future developments."
+ "@value": "This report documents the progress made to date by OGC and its members to build a complete picture of the present situation and develop a conceptual framework for action to improve underground infrastructure data interoperability. The report also identifies the most important steps to be taken next in order to develop the necessary data standards and foster their adoption."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29680,35 +28821,112 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "16-034"
+ "@value": "17-048"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Testbed-12 LiDAR Streaming Engineering Report"
+ "@value": "OGC Underground Infrastructure Concept Study Engineering Report"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/isc",
+ "http://www.w3.org/2004/02/skos/core#narrower": [
+ {
+ "@id": "http://www.opengis.net/def/docs/07-036r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-091r6"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-146r8"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-083r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-005r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-010r11"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-158"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-005r5"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-045r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-075"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-157"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-065r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-026r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-010"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-128r15"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-050"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-147r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-027r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-065r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-094r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-128r12"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-083r4"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-122r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-045r2"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/22-049r1",
+ "@id": "http://www.opengis.net/def/docs/04-046r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2023-09-21"
+ "@value": "2004-02-11"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Andreas Matheus"
+ "@value": "Roger Lott"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29718,27 +28936,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/22-049r1/22-049r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=6716"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "22-049r1"
+ "@value": "04-046r3"
},
{
"@language": "en",
- "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0"
+ "@value": "Topic 02 - Spatial Referencing by Coordinates"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/d-as"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 defines a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 Standard. GeoXACML 3.0 supports the interoperable definition of access rights including geographic conditions based on the XACML 3.0 language, processing model and policy schema. GeoXACML 3.0 provides improvements based on enhancements to the XACML Standard, primarily the support of access conditions spanning different XACML categories. This enhancement empowers GeoXACML 3.0 to be a powerful decision engine with support for spatiotemporal access conditions.\r\n\r\nAs a result of the XACML 3.0 deployment model and corresponding implementation flexibility, GeoXACML 3.0 can be operated as a traditional Policy Decision Point or as a cloud-native API gateway.\r\n\r\nThe OGC GeoXACML 3.0 Standard defines different conformance classes that supports flexible implementation conformance. Implementation of the Core conformance class supports the ISO 19125 geometry model including topological test (spatial relations) functions which enables the indexing of access conditions-based geometry. The Spatial Analysis conformance class extends the topological test functions for defining access conditions including the processing of geometries. To support condition evaluation for geometries encoded in different Coordinate Reference System (CRS), the CRS Transformation conformance class enables a compliant implementation to undertake dynamic CRS transformation during decision-making unless prohibited per request. Finally, the API conformance class enables operating a GeoXACML 3.0 compliant implementation as an OGC API conformant service (Policy Decision Point)."
+ "@value": "Describes modelling requirements for spatial referencing by coordinates."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29749,35 +28967,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "22-049r1"
+ "@value": "04-046r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0"
+ "@value": "Topic 2 - Spatial Referencing by Coordinates"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/02-019r1",
+ "@id": "http://www.opengis.net/def/docs/18-091r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2002-02-28"
+ "@value": "2019-02-04"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff Lansing"
+ "@value": "Johannes Echterhoff"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/ipr"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29787,27 +29005,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1121"
+ "@id": "https://docs.ogc.org/per/18-091r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Coverage Portrayal Service"
+ "@value": "18-091r2"
},
{
"@language": "en",
- "@value": "02-019r1"
+ "@value": "Application Schemas and JSON Technologies Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/ipr"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The Coverage Portrayal Service (CPS) IPR proposes a standard interface for producing visual pictures from coverage data."
+ "@value": "This Engineering Report (ER) enhances the understanding of the relationships between data exchange based on Geography Markup Language (GML), JavaScript Object Notation (JSON), and Resource Description Framework (RDF) for future web services, e.g. Web Feature Service (WFS) 3.0. The work documented in this report:\r\n\r\ncontributes to the ability to bridge between technology-dependent alternate representations of “features” (real-world objects), and to consistently employ alternate encoding technologies (Extensible Markup Language (XML), JSON, RDF) to exchange information about “features”; and\r\n\r\ndetermines principled techniques for the development of JSON-based schemas from ISO 19109-conformant application schemas.\r\n\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29818,35 +29036,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "02-019r1"
+ "@value": "18-091r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Coverage Portrayal Service"
+ "@value": "OGC Testbed-14: Application Schemas and JSON Technologies Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/03-109r1",
+ "@id": "http://www.opengis.net/def/docs/20-057",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2004-02-18"
+ "@value": "2022-11-10"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff de La Beaujardiere"
+ "@value": "Joan Masó, Jérôme Jacovella-St-Louis"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29856,27 +29074,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=4756"
+ "@id": "https://docs.ogc.org/is/20-057/20-057.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "03-109r1"
+ "@value": "OGC API - Tiles - Part 1: Core"
},
{
"@language": "en",
- "@value": "Web Map Service (Recommendation Paper)"
+ "@value": "20-057"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Provides three operations (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. "
+ "@value": "OGC API — Tiles is a standard defining building blocks for creating Web APIs that support the retrieval of geospatial information as tiles. Different forms of geospatial information are supported, such as tiles of vector features (“vector tiles”), coverages, maps (or imagery) and other types of geospatial information. Although it can be used independently, the OGC API — Tiles building blocks can be combined with other OGC API Standards and draft specifications for additional capabilities or increasing interoperability for specific types of data. The OGC API — Tiles standard references the OGC Two Dimensional Tile Matrix Set (TMS) and Tileset Metadata standard, which defines logical models and encodings for specifying tile matrix sets and describing tile sets. A tile matrix set is a tiling scheme that enables an application to partition and index space based on a set of regular grids defined for multiple scales in a Coordinate Reference System (CRS).\r\n\r\nThis specification is a successor to the OGC’s Web Map Tile Service (WMTS) standard, focusing on simple reusable REST API building blocks which can be described using the OpenAPI specification. Whereas WMTS focused on map tiles, the OGC API — Tiles standard has been designed to support any form of tiled data."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29887,30 +29105,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "03-109r1"
+ "@value": "20-057"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Web Map Service"
+ "@value": "OGC API - Tiles - Part 1: Core"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-027r1",
+ "@id": "http://www.opengis.net/def/docs/04-010r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2007-05-25"
+ "@value": "2004-05-04"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Clemens Portele"
+ "@value": "Peter Schut"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -29925,17 +29143,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=21702"
+ "@id": "https://portal.ogc.org/files/?artifact_id=5858"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-027r1"
+ "@value": "Geolinked Data Access Service"
},
{
"@language": "en",
- "@value": "Local MSD Implementation Profile (GML 3.2.1)"
+ "@value": "04-010r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -29945,7 +29163,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO/DIS 19131 (Geographic Information "
+ "@value": "A Geolinked Data Access Service (GDAS) provides a way to publish and access data that refers to spatial features (e.g. population data for countries). A GDAS can expose data from non-GIS databases so that it can be manipulated and mapped with the aid of a Geolinking Service."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -29956,35 +29174,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-027r1"
+ "@value": "04-010r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Local MSD Implementation Profile (GML 3.2.1)"
+ "@value": "Geolinked Data Access Service"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/06-050r3",
+ "@id": "http://www.opengis.net/def/docs/08-085r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-07-19"
+ "@value": "2014-09-23"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Carl Reed"
+ "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/can"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -29994,27 +29212,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=15755"
+ "@id": "https://docs.ogc.org/is/08-085r4/08-085r4.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "GeoRSS, An Introduction to"
+ "@value": "GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core "
},
{
"@language": "en",
- "@value": "06-050r3"
+ "@value": "08-085r4"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/can"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "GeoRSS is simple proposal for geo-enabling, or tagging, really simple syndication (RSS) feeds with location information. GeoRSS proposes a standardized way in which location is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. GeoRSS may not work for every use, but it should serve as an easy-to-use geotagging encoding that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated encoding standards such as the OGC (Open Geospatial Consortium) GML (Geography Markup Language)."
+ "@value": "This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.\r\n\r\nThis document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -30025,35 +29243,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "06-050r3"
+ "@value": "08-085r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "GeoRSS, An Introduction to"
+ "@value": "OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core "
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-018r2",
+ "@id": "http://www.opengis.net/def/docs/17-066r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2008-01-21"
+ "@value": "2022-05-02"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Philippe M"
+ "@value": "Carl Reed"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -30063,27 +29281,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=25199"
+ "@id": "https://docs.ogc.org/is/17-066r2/17-066r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-018r2"
+ "@value": "17-066r2"
},
{
"@language": "en",
- "@value": "Sensor Planning Service Application Profile for EO Sensors"
+ "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/bp"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The SPS configuration proposed in this profile is intended to support the programming process of Earth Observation (EO) sensors system. This profile describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests."
+ "@value": "The GeoPackage Extension for Tiled Gridded Coverage Data” (TGCE) extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. The tiles contain values, such as elevation, temperature or pressure, and the extension defines two encodings. The PNG encoding uses PNG files to store 16-bit integer values and a scale and offset may be applied to fine-tune the coverage range. To support 32-bit floating point data or binary data, the extension also defines a TIFF encoding. In this encoding, TIFF files are used to store IEEE floating point or a binary data type where the SampleFormat has a value of either 1 (unsigned integer) or 2 (signed integer) AND the BitsPerSample is either 8, 16, or 32. To simplify development, this encoding constrains many of the TIFF options to the minimal set needed to meet the floating-point requirement. The extension also defines two ancillary data tables: one for regular gridded coverages and one for tiles.\r\n\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -30094,35 +29312,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-018r2"
+ "@value": "17-066r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors"
+ "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-026r1",
+ "@id": "http://www.opengis.net/def/docs/03-002r9",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-03-05"
+ "@value": "2006-01-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Juan José Doval, Héctor Rodríguez"
+ "@value": "Craig Bruce"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -30132,27 +29350,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/18-026r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=13636"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Security Engineering Report"
+ "@value": "03-002r9"
},
{
"@language": "en",
- "@value": "18-026r1"
+ "@value": "Binary Extensible Markup Language (BXML) Encoding Specification"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Security Engineering Report (ER) covers several OGC Testbed-14 topics:\r\n\r\nBest practices for the integration of OAuth2.0/OpenID Connect services\r\n\r\nMediation services for different security environments\r\n\r\nFederated identity management\r\n\r\nSecuritization of workflows\r\n\r\nThe first two topics are the main focus of this ER. During this Testbed, a server that provides OAuth2.0 and OpenID Connect capabilities was extended with a mediation service that allows for a centralized security authority with users/clients that implement different security standards.\r\n\r\nThe remaining two topics will expand on the close relationship between Security, Workflows and Federated Clouds and the respective implementation challenges. On these specific topics, this ER also outlines and provides a proof-of-concept for a simplistic architecture approach that explores one of several Federated Clouds architectures."
+ "@value": "This OGC Best Practices document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -30163,587 +29381,588 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-026r1"
+ "@value": "03-002r9"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-14: Security Engineering Report"
+ "@value": "Binary Extensible Markup Language (BXML) Encoding Specification"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-029",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/doc-type/techpaper",
+ "http://www.w3.org/2004/02/skos/core#narrower": [
{
- "@type": "xsd:date",
- "@value": "2012-04-04"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/15-002r5"
+ },
{
- "@value": "Bastian Schäffer"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/10-124r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/18-004r1"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/11-159"
+ },
{
- "@id": "https://portal.ogc.org/files/?artifact_id=47860"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/20-085r1"
+ },
{
- "@language": "en",
- "@value": "Web Processing Service Best Practices Discussion Paper"
+ "@id": "http://www.opengis.net/def/docs/18-008r1"
},
{
- "@language": "en",
- "@value": "12-029"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/19-078r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/16-019r4"
+ },
{
- "@value": "The following document contains best practices for identifying input data formats for the OGC WPS 1.0.0. It was created due to a lack of interoperability between different WPS implementation based on non-standardized input identifiers."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/11-110"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/11-036"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-029"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/14-095"
+ },
{
- "@language": "en",
- "@value": "Web Processing Service Best Practices Discussion Paper"
+ "@id": "http://www.opengis.net/def/docs/16-131r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/19-076"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-165r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-145"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-044r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-026"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-128"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-115"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-099r1",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/doc-type/dp",
+ "http://www.w3.org/2004/02/skos/core#narrower": [
{
- "@type": "xsd:date",
- "@value": "2008-02-23"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/09-163r2"
+ },
{
- "@value": "Andreas Matheus"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/09-104r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/07-169"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/09-166r2"
+ },
{
- "@id": "https://portal.ogc.org/files/?artifact_id=25220"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/07-166r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-012"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-171"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-012r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-039"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-184r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/02-017r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-125"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-172r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-077r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-073r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-011r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-100"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/01-061"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/03-028"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/16-114r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-124r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-117"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/20-092"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-041r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/17-049"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-002"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/13-100"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-039r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-010r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-163"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-050"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-001r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-002r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/20-088"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/20-054r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-116"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-076"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-077"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-015"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-023r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-041r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-095r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/19-047"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-140"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/13-099"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-079"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-118"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-133"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-071"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/14-121r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-001"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-112r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-187r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-037"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-173r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/21-010r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/10-191r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/19-090r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/03-029"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-155"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/23-013"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/12-029"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-056"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-082"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-122"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-084r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-017"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-138r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/04-052"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/05-116"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/03-025"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/07-007r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/23-056"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-078r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/09-076r3"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/13-068"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/08-132"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/19-042r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-074r2"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/18-037r1"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/06-079r1"
+ },
{
- "@language": "en",
- "@value": "GeoXACML Implementation Specification - Extension B (GML3) Encoding"
+ "@id": "http://www.opengis.net/def/docs/06-107r1"
},
{
- "@language": "en",
- "@value": "07-099r1"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/07-027r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/09-085r2"
+ },
{
- "@value": "This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/09-042"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/03-026"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-099r1"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/16-145"
+ },
{
- "@language": "en",
- "@value": "GeoXACML Implementation Specification - Extension B (GML3) Encoding"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/21-026",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/08-058r1"
+ },
{
- "@type": "xsd:date",
- "@value": "2023-07-14"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/11-018"
+ },
{
- "@value": "Joan Maso"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/08-077"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/15-096"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/11-163"
+ },
{
- "@id": "https://docs.ogc.org/is/21-026/21-026.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/05-102r1"
+ },
{
- "@language": "en",
- "@value": "21-026"
+ "@id": "http://www.opengis.net/def/docs/16-079"
},
{
- "@language": "en",
- "@value": "OGC Cloud Optimized GeoTIFF Standard"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/15-100r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/08-001"
+ },
{
- "@value": "The Cloud Optimized GeoTIFF (COG) relies on two characteristics of the TIFF v6 format (tiles and reduced resolution subfiles), GeoTIFF keys for georeference, and the HTTP range, which allows for efficient downloading of parts of imagery and grid coverage data on the web and to make fast data visualization of TIFF or BigTIFF files and fast geospatial processing workflows possible. COG-aware applications can download only the information they need to visualize or process the data on the web. Numerous remote sensing datasets are available in cloud storage facilities that can benefit from optimized visualization and processing. This standard formalizes the requirements for a TIFF file to become a COG file and for the HTTP server to make COG files available in a fast fashion on the web.\r\n\r\nThe key work for crafting this OGC Standard was undertaken in the Open-Earth-Monitor Cyberinfrastructure (OEMC) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101059548 and in the All Data 4 Green Deal - An Integrated, FAIR Approach for the Common European Data Space (AD4GD) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101061001."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/07-004"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/12-027r3"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "21-026"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/19-077"
+ },
{
- "@language": "en",
- "@value": "OGC Cloud Optimized GeoTIFF Standard"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/19-032",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/07-152"
+ },
{
- "@type": "xsd:date",
- "@value": "2020-07-30"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/13-101"
+ },
{
- "@value": "Steven Chau & Mohsen Kalantari"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/07-056r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/15-039"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/06-045r1"
+ },
{
- "@id": "https://docs.ogc.org/per/19-032.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/12-117r1"
+ },
{
- "@language": "en",
- "@value": "19-032"
+ "@id": "http://www.opengis.net/def/docs/18-001r1"
},
{
- "@language": "en",
- "@value": "Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/13-021r3"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/04-051"
+ },
{
- "@value": "This document defines an Application Domain Extension (ADE) of CityGML for public safety use cases. The ADE has been developed as part of OGC’s Indoor Mapping and Modeling Pilot project sponsored by the National Institute of Standards and Technology (NIST), Communications Technology Laboratory (CTL), Public Safety Communications Research (PSCR) Division. The ADE has been developed primarily based on reference preplan symbology created by the National Alliance for Public Safety GIS (NAPSG) Foundation. NAPSG is a 501 (C) (3) not-for-profit organization that was established in 2005 to overcome challenges faced by Federal, tribal, state, and local public safety agencies in the United States. NAPSG focuses on using GIS technology to resolve challenges that occur. In the definition of the ADE, public safety requirements that were not explicit in NAPSG have also been considered. This Engineering Report (ER) provides the methodology of the ADE development, details the implementation of the ADE and its structure and the application of the ADE in the context of public safety use cases.\r\n\r\nThe findings include:\r\n\r\nA methodology to transform NAPSG symbology to data elements;\r\n\r\nA need for an extension of a reference to four existing CityGML classes; and\r\n\r\nThe creation of seven new CityGML classes that are critical for public safety use cases."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/12-028r1"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/08-054r1"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-032"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/21-067"
+ },
{
- "@language": "en",
- "@value": "OGC Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/18-062r2",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/08-122r2"
+ },
{
- "@type": "xsd:date",
- "@value": "2021-12-20"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/07-009r3"
+ },
{
- "@value": "Benjamin Pross, Panagiotis (Peter) A. Vretanos"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/05-084"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/16-129"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/16-142"
+ },
{
- "@id": "https://docs.ogc.org/is/18-062r2/18-062r2.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/21-041r2"
+ },
{
- "@language": "en",
- "@value": "OGC API - Processes - Part 1: Core"
+ "@id": "http://www.opengis.net/def/docs/08-127"
},
{
- "@language": "en",
- "@value": "18-062r2"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/09-132r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/10-196r1"
+ },
{
- "@value": "The OGC API — Processes — Part 1: Core Standard supports the wrapping of computational tasks into executable processes that can be offered by a server through a Web API and be invoked by a client application. The standard specifies a processing interface to communicate over a RESTful protocol using JavaScript Object Notation (JSON) encodings. The standard leverages concepts from the OGC Web Processing Service (WPS) 2.0 Interface Standard but does not require implementation of a WPS.\r\n\r\nBy way of background and context, in many cases geospatial or location data, including data from sensors, must be processed before the information can be effectively used. The WPS Standard provides a standard interface that simplifies the task of making simple or complex computational geospatial processing services accessible via web services. Such services include well-known processes found in Geographic Information Systems (GIS) as well as specialized processes for spatiotemporal modeling and simulation. While the WPS standard was designed with spatial processing in mind, the standard could also be used to readily insert non-spatial processing tasks into a web services environment.\r\n\r\nThe OGC API — Processes Standard is a newer and more modern way of programming and interacting with resources over the web while allowing better integration into existing software packages. The OGC API — Processes Standard addresses all of the use cases that were addressed by the WPS Standard, while also leveraging the OpenAPI specification and a resource-oriented approach.\r\n\r\nThe resources that are provided by a server implementing the OGC API — Processes Standard are listed in Table 1 below and include information about the server, the list of available processes (Process list and Process description), jobs (running processes) and results of process executions."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/09-010"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/05-115"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-062r2"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/23-022r1"
+ },
{
- "@language": "en",
- "@value": "OGC API - Processes - Part 1: Core"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/07-056r1",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/12-031r2"
+ },
{
- "@type": "xsd:date",
- "@value": "2007-07-23"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/04-050r1"
+ },
{
- "@value": "John Herring, OAB, Architecture WG"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/08-009r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/09-124r2"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/09-084r1"
+ },
{
- "@id": "https://portal.ogc.org/files/?artifact_id=21976"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/06-154"
+ },
{
- "@language": "en",
- "@value": "07-056r1"
+ "@id": "http://www.opengis.net/def/docs/15-075r1"
},
{
- "@language": "en",
- "@value": "The Specification Model -- Structuring an OGC specification to encourage implementation"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/05-014"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/07-055r1"
+ },
{
- "@value": "This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. "
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/03-014"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/11-058r1"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-056r1"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/07-032"
+ },
{
- "@language": "en",
- "@value": "The Specification Model -- Structuring an OGC specification to encourage implementation"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/20-054r1",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/05-101"
+ },
{
- "@type": "xsd:date",
- "@value": "2021-01-19"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/09-018"
+ },
{
- "@value": "Kyoung-Sook Kim, Jiyeong Lee"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/19-004"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/20-000r1"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/06-182r1"
+ },
{
- "@id": "https://docs.ogc.org/dp/20-054r1.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/15-122r1"
+ },
{
- "@language": "en",
- "@value": "20-054r1"
+ "@id": "http://www.opengis.net/def/docs/05-029r4"
},
{
- "@language": "en",
- "@value": "An Extension Model to attach Points of Interest into IndoorGML"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/16-012r1"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/10-134"
+ },
{
- "@value": "The scope of this discussion paper is to investigate types of Point of Interest (POI) data in indoor space and propose a conceptual model to harmonize the POI information with the IndoorGML core and navigation modules. In particular, this document focuses on the management of spatial (and non-spatial) history of indoor POI features. The paper covers the following scope:\r\n\r\nPoints of Interest Feature Types;\r\n\r\nA Conceptual model to extend IndoorGML schema for indoor POI; and\r\n\r\nUse cases in home navigation and hospital facility management."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/15-074"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/05-140"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "20-054r1"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/06-022r1"
+ },
{
- "@language": "en",
- "@value": "An Extension Model to attach Points of Interest into IndoorGML"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/02-009",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/docs/08-071"
+ },
{
- "@type": "xsd:date",
- "@value": "2002-01-14"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/docs/10-195"
+ },
{
- "@value": "Ron Lake"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/docs/17-059"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/docs/07-160r1"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/docs/16-084"
+ },
{
- "@id": "https://portal.ogc.org/files/?artifact_id=1108"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/docs/11-088r1"
+ },
{
- "@language": "en",
- "@value": "02-009"
+ "@id": "http://www.opengis.net/def/docs/07-158"
},
{
- "@language": "en",
- "@value": "Geography Markup Language"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/docs/05-111r2"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/docs/19-091r2"
+ },
{
- "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/docs/04-060r1"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/docs/09-112"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "02-009"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/docs/09-123"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/01-019"
+ },
{
- "@language": "en",
- "@value": "Geography Markup Language"
+ "@id": "http://www.opengis.net/def/docs/08-000"
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/11-094"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-126r4",
+ "@id": "http://www.opengis.net/def/docs/02-007r4",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2014-02-24"
+ "@value": "2002-08-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Peter Taylor"
+ "@value": "John Bobbitt"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -30753,27 +29972,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=57222"
+ "@id": "https://portal.ogc.org/files/?artifact_id=11498"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "WaterML 2.0: Part 1- Timeseries"
+ "@value": "Units of Measure Recommendation"
},
{
"@language": "en",
- "@value": "10-126r4"
+ "@value": "02-007r4"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document."
+ "@value": "Common semantic for units of measurement to be used across all OGC specifications."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -30784,35 +30003,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-126r4"
+ "@value": "02-007r4"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® WaterML 2.0: Part 1- Timeseries"
+ "@value": "Units of Measure Recommendation"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/04-021r3",
+ "@id": "http://www.opengis.net/def/docs/12-075",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2004-08-02"
+ "@value": "2012-08-22"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Doug Nebert"
+ "@value": "Arne Schilling, Benjamin Hagedorn, Volker Coors "
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -30822,31 +30041,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=5929"
+ "@id": "https://portal.ogc.org/files/?artifact_id=49068"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Catalogue Service Implementation Specification [Catalogue Service for the Web]"
- },
- {
- "@language": "en",
- "@value": "04-021r3"
+ "@value": "3D Portrayal Interoperability Experiment FINAL REPORT "
},
{
"@language": "en",
- "@value": "Catalogue Service Implementation Specification"
+ "@value": "12-075"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources."
+ "@value": "This document describes the results of an OGC Interoperability Experiment (IE) on the portrayal of 3D geospatial information. It contains technical details on processing 3D information in an OGC service environment as well as best practices on how to portray large data sets in urban planning scenarios, taking into account architectures and capabilities of interactive 3D graphics. Especially Web 3D Service and Web View Service, two draft standards (published as OGC discussions paper), have been in the focus of 3DPIE. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -30857,246 +30072,162 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "04-021r3"
+ "@value": "12-075"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]"
- },
- {
- "@language": "en",
- "@value": "OpenGIS Catalogue Service Implementation Specification"
+ "@value": "OGC 3D Portrayal Interoperability Experiment FINAL REPORT "
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-047r3",
+ "@id": "http://www.opengis.net/def/docs/",
"@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
+ "http://www.w3.org/2004/02/skos/core#Collection"
],
- "http://purl.org/dc/terms/created": [
+ "http://purl.org/dc/terms/provenance": [
{
- "@type": "xsd:date",
- "@value": "2019-02-07"
+ "@value": "Generated by the OGC Definitions Server to support integration of the elements of this ConceptScheme into bigger collections. ogc_skos_profile_entailements.ttl"
}
],
- "http://purl.org/dc/terms/creator": [
+ "http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Eugene Genong Yu, Liping Di"
+ "@value": "Collection hierarchy for this ConceptScheme"
}
],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/docs"
}
],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "http://www.w3.org/2004/02/skos/core#member": [
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/doc-type/per/collection"
+ },
{
- "@id": "https://docs.ogc.org/per/18-047r3.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/doc-type/d-isc/collection"
+ },
{
- "@language": "en",
- "@value": "Swath Coverage Engineering Report"
+ "@id": "http://www.opengis.net/def/doc-type/rfc/collection"
},
{
- "@language": "en",
- "@value": "18-047r3"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/doc-type/bp/collection"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/per"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/doc-type/ipr/collection"
+ },
{
- "@value": "This Engineering Report (ER) presents a summary, description and findings of the Swath Coverage task conducted by the OGC Testbed-14 initiative."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/doc-type/as/collection"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/doc-type/d-rp/collection"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-047r3"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/doc-type/d-is/collection"
+ },
{
- "@language": "en",
- "@value": "OGC Testbed-14: Swath Coverage Engineering Report"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/02-069",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/doc-type/isc/collection"
+ },
{
- "@type": "xsd:date",
- "@value": "2002-08-19"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/doc-type/dp/collection"
+ },
{
- "@value": "Ron Lake"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/doc-type/dp-draft/collection"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/doc-type/d-as/collection"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/doc-type/d-rfc/collection"
+ },
{
- "@id": "https://portal.ogc.org/files/?artifact_id=11339"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/doc-type/ts/collection"
+ },
{
- "@language": "en",
- "@value": "02-069"
+ "@id": "http://www.opengis.net/def/doc-type/d-profile/collection"
},
{
- "@language": "en",
- "@value": "Geography Markup Language"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/doc-type/is-draft/collection"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/d-is"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/doc-type/retired/collection"
+ },
{
- "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/doc-type/d-dp/collection"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/doc-type/pol/collection"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "02-069"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#prefLabel": [
+ "@id": "http://www.opengis.net/def/doc-type/sap/collection"
+ },
{
- "@language": "en",
- "@value": "Geography Markup Language"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/docs/19-011r4",
- "@type": [
- "http://www.w3.org/2004/02/skos/core#Concept"
- ],
- "http://purl.org/dc/terms/created": [
+ "@id": "http://www.opengis.net/def/doc-type/cs/collection"
+ },
{
- "@type": "xsd:date",
- "@value": "2020-11-05"
- }
- ],
- "http://purl.org/dc/terms/creator": [
+ "@id": "http://www.opengis.net/def/doc-type/pol-nts/collection"
+ },
{
- "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker, Hye-Young Kan"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
+ "@id": "http://www.opengis.net/def/doc-type/pc/collection"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.opengis.net/def/metamodel/ogc-na/status": [
+ "@id": "http://www.opengis.net/def/doc-type/d-atb/collection"
+ },
{
- "@id": "http://www.opengis.net/def/status/valid"
- }
- ],
- "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
+ "@id": "http://www.opengis.net/def/doc-type/orm/collection"
+ },
{
- "@id": "https://docs.ogc.org/is/19-011r4/19-011r4.html"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#altLabel": [
+ "@id": "http://www.opengis.net/def/doc-type/"
+ },
{
- "@language": "en",
- "@value": "OGC® IndoorGML 1.1"
+ "@id": "http://www.opengis.net/def/doc-type/ug/collection"
},
{
- "@language": "en",
- "@value": "19-011r4"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#broader": [
+ "@id": "http://www.opengis.net/def/doc-type/notes/collection"
+ },
{
- "@id": "http://www.opengis.net/def/doc-type/is"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#definition": [
+ "@id": "http://www.opengis.net/def/doc-type/is/collection"
+ },
{
- "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema of 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 modeling indoor spaces for navigation purposes."
- }
- ],
- "http://www.w3.org/2004/02/skos/core#inScheme": [
+ "@id": "http://www.opengis.net/def/doc-type/isx/collection"
+ },
{
- "@id": "http://www.opengis.net/def/docs"
- }
- ],
- "http://www.w3.org/2004/02/skos/core#notation": [
+ "@id": "http://www.opengis.net/def/doc-type/d-sap/collection"
+ },
{
- "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-011r4"
+ "@id": "http://www.opengis.net/def/doc-type/profile/collection"
+ },
+ {
+ "@id": "http://www.opengis.net/def/doc-type/d-bp/collection"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@language": "en",
- "@value": "OGC® IndoorGML 1.1"
+ "@value": "Concepts in OGC Documents"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/07-158",
+ "@id": "http://www.opengis.net/def/docs/05-088r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2008-01-02"
+ "@value": "2006-01-18"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "R"
+ "@value": "Arthur Na, Mark Priest"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31106,27 +30237,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=25280"
+ "@id": "https://portal.ogc.org/files/?artifact_id=12846"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "07-158"
+ "@value": "05-088r1"
},
{
"@language": "en",
- "@value": "Wrapping OGC HTTP-GET/POST Services with SOAP"
+ "@value": "Sensor Observation Service"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/d-dp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP"
+ "@value": "A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. "
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31137,35 +30268,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "07-158"
+ "@value": "05-088r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Wrapping OGC HTTP-GET/POST Services with SOAP"
+ "@value": "Sensor Observation Service"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/05-094r1",
+ "@id": "http://www.opengis.net/def/docs/11-014r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2006-07-18"
+ "@value": "2014-05-26"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Arliss Whiteside"
+ "@value": "Stanislav Vanecek, Roger Moore"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/profile"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31175,27 +30306,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=13203"
+ "@id": "https://portal.ogc.org/files/?artifact_id=59022"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "GML 3.1.1 CRS support profile"
+ "@value": "11-014r3"
},
{
"@language": "en",
- "@value": "05-094r1"
+ "@value": "Open Modelling Interface Interface Standard"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/profile"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document."
+ "@value": "The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation. \r\n
\r\n\r\nThis document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-‐compliant components are provided by the OpenMI Association and third-‐party software vendors – visit www.openmi.org for further documentation.
\r\n\r\npdf
\r\ndocx\r\n
"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31206,35 +30337,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "05-094r1"
+ "@value": "11-014r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "GML 3.1.1 CRS support profile"
+ "@value": "OGC Open Modelling Interface Interface Standard"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-128r15",
+ "@id": "http://www.opengis.net/def/docs/18-090r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-09-06"
+ "@value": "2019-10-23"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jeff Yutzler"
+ "@value": "Craig A. Lee"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31244,27 +30375,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=80678"
+ "@id": "https://docs.ogc.org/per/18-090r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OGC® GeoPackage Encoding Standard - with Corrigendum"
+ "@value": "Testbed-14: Federated Clouds Engineering Report"
},
{
"@language": "en",
- "@value": "12-128r15"
+ "@value": "18-090r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth."
+ "@value": "The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the Security Engineering Report (ER) [1]. This Federated Cloud ER will dovetail with the Security ER to:\r\n\r\nCoordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks,\r\n\r\nUnderstand the overall federation design space,\r\n\r\nAnalyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14,\r\n\r\nIdentify and prioritize possible incremental development tasks for subsequent testbeds, and\r\n\r\nLiaison with groups external to OGC, such as the NIST/IEEE Joint WG on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31275,30 +30406,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-128r15"
+ "@value": "18-090r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® GeoPackage Encoding Standard - with Corrigendum"
+ "@value": "OGC Testbed-14: Federated Clouds Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-158",
+ "@id": "http://www.opengis.net/def/docs/16-034",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-06-18"
+ "@value": "2017-03-09"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Matthes Rieke"
+ "@value": "Simon Jirka, Arne de Wall, Christoph Stasch"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -31313,17 +30444,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=51817"
+ "@id": "https://docs.ogc.org/per/16-034.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "12-158"
+ "@value": "16-034"
},
{
"@language": "en",
- "@value": "OWS-9 Report on Aviation Performance Study"
+ "@value": "Testbed-12 LiDAR Streaming Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -31333,7 +30464,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). The report summarizes the work carried out regarding performance and endurance testing of data provision services, namely Web Feature Service and Event Service. More specifically, the report deals with the performance and endurance testing of data provision services commonly used within OWS Aviation testbeds. Test runs have been evaluated on the basis of well-defined, service-specific test models and the results are documented in detail. Furthermore, a description of the service test environment is documented in alignment with the overall OWS-9 service architecture"
+ "@value": "This Engineering Report describes how developments of the Community Sensor Model Working Group (CSMW) can be harmonized with the latest SWE specifications and developments in order to support streaming of LiDAR data with SWE technologies. The report will therefore provide an overview on both initiatives and then describe different options how to integrate LiDAR data streams and SWE technologies. In particular, the ER will consider the results of the activities SOS Compression (LiDAR) Server (A012) and LiDAR Streaming Client (A010) and infer recommendations for future developments."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31344,35 +30475,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-158"
+ "@value": "16-034"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® OWS-9 Report on Aviation Performance Study"
+ "@value": "Testbed-12 LiDAR Streaming Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-144",
+ "@id": "http://www.opengis.net/def/docs/08-022r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-06-18"
+ "@value": "2008-05-12"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "David Burggraf"
+ "@value": "Simon Cox"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/cr"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31382,27 +30513,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=53255"
+ "@id": "https://portal.ogc.org/files/?artifact_id=27697"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "12-144"
+ "@value": "Change Request - O&M Part 1 - Move extensions to new namespace"
},
{
"@language": "en",
- "@value": "OWS-9 Architecture - Registry Engineering Report"
+ "@value": "08-022r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/cr"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC® Engineering Report provides guidelines for the harvest, registration and retrieval of aviation resources from an OGC web catalogue/registry service (OGC CSW-ebRIM), with particular emphasis on ISO metadata resources. Alternatives for selective and efficient retrieval of such resources are also described along with lessons learned. The OGC CSW-ebRIM registry interface is evaluated against SESAR registry requirements, documented as a gap analysis, to assess whether there are any obstacles to implementing SESAR registry with an OGC CSW-ebRIM interface."
+ "@value": "The XML Schema implementation of optional/informative elements of the Observation Schema was published in the om/1.0.0/extensions directory, in the same XML namespace as the base schema. Those OGC implementations that have a dependency on the Observation Schema (i.e. Sampling Features, SOS) the “all-components” document om.xsd. However, the all-components stub-schema document “om.xsd” does not include the extensions. Thus, any application which requires one of the dependent OGC schemas (Sampling Features, SOS) may not access the Observation Schema Extensions, since the of om.xsd clashes with any attempt to om_extended.xsd. This problem is a consequence of an error in the modularization strategy for optional elements, combined with the rules for schema document resolution used by standard processing environments."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31413,35 +30544,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-144"
+ "@value": "08-022r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® OWS-9 Architecture - Registry Engineering Report"
+ "@value": "Change Request - O&M Part 1 - Move extensions to new namespace"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-182r1",
+ "@id": "http://www.opengis.net/def/docs/20-072r2",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-02-16"
+ "@value": "2021-08-13"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Josh Lieberman"
+ "@value": "Hugo Ledoux"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/cs"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31451,27 +30582,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=36889"
+ "@id": "https://docs.ogc.org/cs/20-072r2/20-072r2.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "09-182r1"
+ "@value": "CityJSON Community Standard 1.0"
},
{
"@language": "en",
- "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2"
+ "@value": "20-072r2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/cs"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. End-to-end here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end."
+ "@value": "CityJSON is a JSON-based encoding for a well-documented subset of the OGC CityGML data model (version 2.0.0). CityJSON defines how to store digital 3D models of cities and landscapes. The aim of CityJSON is to offer an alternative to the GML encoding of CityGML, which can be verbose and complex to read and manipulate. CityJSON aims at being easy-to-use, both for reading datasets and for creating them. It was designed with programmers in mind, so that tools and APIs supporting it can be quickly built."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31482,35 +30613,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-182r1"
+ "@value": "20-072r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2"
+ "@value": "OGC CityJSON Community Standard 1.0"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/09-007",
+ "@id": "http://www.opengis.net/def/docs/21-074",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2009-10-09"
+ "@value": "2022-05-06"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Scott Fairgrieve"
+ "@value": "Samantha Lavender, Andrew Lavender"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/ug"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31520,27 +30651,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=33355"
+ "@id": "https://docs.ogc.org/guides/21-074.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report"
+ "@value": "21-074"
},
{
"@language": "en",
- "@value": "09-007"
+ "@value": "OGC Disaster Pilot: User Readiness Guide"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/ug"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document outlines the concepts, best practices, and lessons learned gathered from integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC Sensor Web Enablement (SWE)-based architecture. The document also specifies a web service interface for interacting with CCSI sensors and defines the basis for a profile that can be used to represent CCSI sensor definitions, data, and commands in SWE formats. "
+ "@value": "The OGC Disaster Pilot 2021 initiative brought differing technologies together through multiple participants, allowing the future development of a robust solution with no single-point weaknesses. This Guide supports data providers in preparing and coordinating with others to leverage standards-based cloud computing platforms to support disaster management and response efforts. Geospatial data is acquired from multiple sources, including Earth Observation satellites, and converted to Decision Ready Information and indicators (DRI) from Analysis Ready Data and datasets (ARD) alongside recipes."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31551,35 +30682,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "09-007"
+ "@value": "21-074"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report"
+ "@value": "OGC Disaster Pilot: User Readiness Guide"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-030",
+ "@id": "http://www.opengis.net/def/docs/21-057",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-03-06"
+ "@value": "2022-10-14"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Sara Saeedi"
+ "@value": "Jeff Yutzler"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31589,27 +30720,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/18-030.html"
+ "@id": "https://docs.ogc.org/is/21-057/21-057.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "18-030"
+ "@value": "OGC GeoPackage WKT for Coordinate Reference Systems Extension"
},
{
"@language": "en",
- "@value": "Secure Client Test Engineering Report"
+ "@value": "21-057"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Engineering Report (ER) describes the development of compliance tests and their implementation in the OGC Test, Evaluation, And Measurement (TEAM) Engine to validate a client’s ability to make secure requests according to the OGC Web Services Security Candidate Standard. The goal of the candidate standard is to allow the implementation of Information Assurance (IA) controls and to advertise their existence in an interoperable way with minimal impact to existing implementations using a backward-compatible approach.\r\n\r\nThis ER covers the following topics from OGC Testbed-14 Compliance Interoperability & Testing Evaluation (CITE) thread:\r\n\r\ndeveloping a client validator to test compliance of client software with the OGC Web Services Security Candidate Standard\r\n\r\ncapturing the results of two use cases with different authentication methods\r\n\r\nmaking recommendations to the OGC Web Services Security Standards Working Group (SWG) based on the experiences made while developing the validator\r\n\r\n"
+ "@value": "This document is a revision to the GeoPackage WKT for Coordinate Reference Systems Extension that previously was published as Annex F.10 of the GeoPackage Encoding Standard 1.3.0 (OGC 12-128r17). This document replaces Annex F.10. The extension defines how to encode coordinate reference systems (CRS) in GeoPackages using the ISO/OGC Well-known text representation of coordinate reference systems [2019] (CRS WKT2) Standard. Specifically, this revision adds coordinate epochs to the encoding of coordinate reference systems in a GeoPackage."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -31620,35 +30751,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-030"
+ "@value": "21-057"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-14: Secure Client Test Engineering Report"
+ "@value": "OGC GeoPackage WKT for Coordinate Reference Systems Extension"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/11-158",
+ "@id": "http://www.opengis.net/def/docs/13-053r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2011-10-18"
+ "@value": "2014-02-24"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jim Greenwood"
+ "@value": "Panagiotis (Peter) A. Vretanos"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -31658,27 +30789,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=46436"
+ "@id": "https://portal.ogc.org/files/?artifact_id=55244"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "11-158"
+ "@value": "CHISP-1 Engineering Report"
},
{
"@language": "en",
- "@value": "Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report"
+ "@value": "13-053r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/isc"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document defines the corrigendum change notes for NOTE: WMS 1.3 and ISO 19128 are the same documents."
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/docs/13-080r3"
- },
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#notation": [
{
- "@id": "http://www.opengis.net/def/docs/09-064r2"
- },
+ "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
+ "@value": "06-042"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@id": "http://www.opengis.net/def/docs/08-176r1"
- },
+ "@language": "en",
+ "@value": "OpenGIS Web Map Service (WMS) Implementation Specification"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.opengis.net/def/docs/15-073r2",
+ "@type": [
+ "http://www.w3.org/2004/02/skos/core#Concept"
+ ],
+ "http://purl.org/dc/terms/created": [
{
- "@id": "http://www.opengis.net/def/docs/18-090r2"
- },
+ "@type": "xsd:date",
+ "@value": "2015-11-18"
+ }
+ ],
+ "http://purl.org/dc/terms/creator": [
{
- "@id": "http://www.opengis.net/def/docs/17-018"
- },
+ "@value": "E. Devys, L.Colaiacomo, P. Baumann"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/docs/17-046"
- },
+ "@id": "http://www.opengis.net/def/doc-type/per"
+ }
+ ],
+ "http://www.opengis.net/def/metamodel/ogc-na/status": [
{
- "@id": "http://www.opengis.net/def/docs/16-094r3"
- },
+ "@id": "http://www.opengis.net/def/status/valid"
+ }
+ ],
+ "http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "http://www.opengis.net/def/docs/12-139"
- },
+ "@id": "https://portal.ogc.org/files/?artifact_id=65887"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#altLabel": [
{
- "@id": "http://www.opengis.net/def/docs/15-027r1"
+ "@language": "en",
+ "@value": "Testbed-11 DGIWG GMLJP2 testing results Engineering Report"
},
{
- "@id": "http://www.opengis.net/def/docs/16-062"
- },
+ "@language": "en",
+ "@value": "15-073r2"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/docs/09-034"
- },
+ "@id": "http://www.opengis.net/def/doc-type/per"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#definition": [
{
- "@id": "http://www.opengis.net/def/docs/17-037"
- },
+ "@value": "This OGC Engineering Report (ER) describes work done in OGC Testbed 11 to test\r\nGMLJP2 in terms of defining a DGIWG GMLJP2 version 1 profile.\r\nThe requirements for a DGIWG profile of GMLJP2 have been documented in the\r\nDGIWG GMLJP2 version 1 profile. The Imagery WG inside DGIWG has developed a\r\nfilter to map the files produced using the previous GMLJP2 schema into the GMLJP2\r\nversion 2 schema and is about to submit a GMLJP2 2.0 profile to DGIWG.\r\nThe DGIWG implementation of the GMLJP2 profile is based on the OGC GMLJP2 v2\r\nand other requirements are coming directly from the adoption inside the DGIWG of the\r\nnew OGC GMLJP2 version 2.\r\nThis Testbed 11 activity is a response to the need of harmonization between DGIWG and\r\nOGC."
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#inScheme": [
{
- "@id": "http://www.opengis.net/def/docs/19-088r2"
- },
+ "@id": "http://www.opengis.net/def/docs"
+ }
+ ],
+ "http://www.w3.org/2004/02/skos/core#notation": [
{
- "@id": "http://www.opengis.net/def/docs/12-155"
+ "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
+ "@value": "15-073r2"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
- "@value": "Documents of type Public Engineering Report"
+ "@language": "en",
+ "@value": "OGC® Testbed-11 DGIWG GMLJP2 testing results Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/03-006r3",
+ "@id": "http://www.opengis.net/def/docs/14-106",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2004-01-16"
+ "@value": "2015-01-30"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Marwa Mabrouk"
+ "@value": "Carl Reed, Jennifer Harne"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rfc"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -45027,27 +44703,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=3418"
+ "@id": "https://docs.ogc.org/bp/14-106/14-106.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "03-006r3"
+ "@value": "Unified Geo-data Reference Model for Law Enforcement and Public Safety"
},
{
"@language": "en",
- "@value": "Location Services (OpenLS): Core Services [Parts 1-5]"
+ "@value": "14-106"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-rfc"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. "
+ "@value": "This document provides an overview of the Unified Geo-data Reference Model for Law Enforcement and Public Safety (Unified Model). The Unified Model was originally developed by the GIS Center for Security (GIS CS), Abu Dhabi Police. The GIS CS was initiated based on a UAE Ministry of Interior issued decree to establish GIS CS with the core mission: “To geo-enable police services and applications using International standards and best practices.” In 2010, the GIS SC initiated a program to develop a Standardized GIS Environment (SGA). Part of this effort was to define and implement a standard data model for sharing Law Enforcement and Public Safety data."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45058,35 +44734,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "03-006r3"
+ "@value": "14-106"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]"
+ "@value": "Unified Geo-data Reference Model for Law Enforcement and Public Safety"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/10-171",
+ "@id": "http://www.opengis.net/def/docs/20-089r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2010-10-12"
+ "@value": "2021-12-14"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Simon Jirka, Daniel Nüst"
+ "@value": "Pedro Gonçalves"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -45096,27 +44772,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=40609"
+ "@id": "https://docs.ogc.org/bp/20-089r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "10-171"
+ "@value": "Best Practice for Earth Observation Application Package"
},
{
"@language": "en",
- "@value": "Sensor Instance Registry Discussion Paper "
+ "@value": "20-089r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/dp"
+ "@id": "http://www.opengis.net/def/doc-type/bp"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This Discussion paper introduces the Sensor Instance Registry (SIR), a web service interface for managing the metadata and status information of sensors. Furthermore this service is capable of automatically harvesting sensor metadata, transforming the collected metadata sets into a data model compatible to OGC Catalogs and to push harvested metadata into OGC Catalog instances."
+ "@value": "Platforms for the exploitation of Earth Observation (EO) data have been developed by public and private companies in order to foster the usage of EO data and expand the market of Earth Observation-derived information. A fundamental principle of the platform operations concept is to move the EO data processing service’s user to the data and tools, as opposed to downloading, replicating, and exploiting data ‘at home’. In this scope, previous OGC activities initiated the development of an architecture to allow the ad-hoc deployment and execution of applications close to the physical location of the source data with the goal to minimize data transfer between data repositories and application processes.\r\n\r\nThis document defines the Best Practice to package and deploy Earth Observation Applications in an Exploitation Platform. The document is targeting the implementation, packaging and deployment of EO Applications in support of collaborative work processes between developers and platform owners.\r\n\r\nThe Best Practice includes recommendations for the application design patterns, package encoding, container and data interfaces for data stage-in and stage-out strategies focusing on three main viewpoints: Application, Package and Platform."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45127,35 +44803,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "10-171"
+ "@value": "20-089r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Sensor Instance Registry Discussion Paper "
+ "@value": "OGC Best Practice for Earth Observation Application Package"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/15-104r5",
+ "@id": "http://www.opengis.net/def/docs/05-047r3",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2017-08-01"
+ "@value": "2006-01-20"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Matthew Purss"
+ "@value": "Martin Kyle, David Burggraf, Sean Forde, Ron Lake"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-as"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -45165,27 +44841,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/as/15-104r5/15-104r5.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=13252"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "15-104r5"
+ "@value": "GML in JPEG 2000 for Geographic Imagery Encoding Specification"
},
{
"@language": "en",
- "@value": "Topic 21 - Discrete Global Grid Systems Abstract Specification"
+ "@value": "05-047r3"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/d-as"
+ "@id": "http://www.opengis.net/def/doc-type/is"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This document specifies the core Abstract Specification and extension mechanisms for Discrete Global Grid Systems (DGGS). A DGGS is a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo-encoding, quantization strategy and associated mathematical functions.The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services."
+ "@value": "The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard http://www.opengeospatial.org/standards/gml is used within JPEG 2000 http://www.jpeg.org/jpeg2000/ images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file. \r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45196,35 +44872,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "15-104r5"
+ "@value": "05-047r3"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Topic 21 - Discrete Global Grid Systems Abstract Specification"
+ "@value": "OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/13-133r1",
+ "@id": "http://www.opengis.net/def/docs/17-024",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2016-08-22"
+ "@value": "2018-01-11"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Aaron Braeckel, Lorenzo Bigagli"
+ "@value": "Pedro Gonçalves"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -45234,27 +44910,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/is/13-133r1/13-133r1.html"
+ "@id": "https://docs.ogc.org/per/17-024.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension"
+ "@value": "Testbed-13: Application Deployment and Execution Service Engineering Report"
},
{
"@language": "en",
- "@value": "13-133r1"
+ "@value": "17-024"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/is"
+ "@id": "http://www.opengis.net/def/doc-type/per"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers.\r\n\r\nPublish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. \r\n\r\nThis specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol."
+ "@value": "The Testbed-13 Earth Observation Clouds (EOC) effort supports the development of ESA’s Thematic Exploitation Platforms (TEP) by exercising envisioned workflows for data integration and processing that are deployed in multiple clouds. The Application Deployment & Execution Service OGC Engineering Report (ER) identifies the Application Programming Interface (API) for delivering all functionality provided to realize the testbed scenario.\r\n\r\nThis ER will list the requirements fulfilled by Cloud APIs in order to allow an automation of the application package deployment and execution workflow and capture implementation process experiences.\r\n\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45265,30 +44941,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "13-133r1"
+ "@value": "17-024"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension"
+ "@value": "OGC Testbed-13: Application Deployment and Execution Service Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/12-139",
+ "@id": "http://www.opengis.net/def/docs/19-018",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2013-02-05"
+ "@value": "2020-02-06"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jan Herrmann, Andreas Matheus"
+ "@value": "Martin Klopfer"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -45303,17 +44979,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://portal.ogc.org/files/?artifact_id=51833"
+ "@id": "https://docs.ogc.org/per/19-018.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OWS-9: SSI Security Rules Service Engineering Report"
+ "@value": "19-018"
},
{
"@language": "en",
- "@value": "12-139"
+ "@value": "OGC Testbed-15: Open Portrayal Framework Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -45323,7 +44999,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "In this engineering report we describe how to administrate XACML v2.0, XACML v3.0 and GeoXACML v1.0.1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS). \r\nAfter introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.g. OGC XACML PAWS) specification.\r\n"
+ "@value": "This Engineering Report (ER) describes the OGC Testbed-15 Open Portrayal Framework (OPF) Thread requirements, scenario, high-level architecture, and solutions. Main topics addressed in the OPF Thread include style changing and sharing, converting style encodings, client- / server-side rendering of vector- and raster data and data provision in denied, disrupted, intermittent, and limited bandwidth (DDIL) infrastructure situations. The work in the OPF Thread was focused on an OGC Application Programming Interface (API) oriented approach."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45334,35 +45010,35 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "12-139"
+ "@value": "19-018"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OWS-9: SSI Security Rules Service Engineering Report"
+ "@value": "OGC Testbed-15: Open Portrayal Framework Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/19-012r1",
+ "@id": "http://www.opengis.net/def/docs/19-034r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-12-17"
+ "@value": "2023-03-13"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Benjamin Pross"
+ "@value": "Carl Reed, Tamrat Belayneh"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/notes"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/status": [
@@ -45372,27 +45048,27 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/19-012r1.html"
+ "@id": "https://docs.ogc.org/cs/17-014r7/19-034r1.pdf"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15: Delta Updates Engineering Report"
+ "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes "
},
{
"@language": "en",
- "@value": "19-012r1"
+ "@value": "19-034r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
{
- "@id": "http://www.opengis.net/def/doc-type/per"
+ "@id": "http://www.opengis.net/def/doc-type/notes"
}
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Testbed 15 Engineering Report (ER) documents the design of a service architecture that allows the delivery of prioritized updates of features to a client, possibly acting in a DDIL (Denied, Degraded, Intermitted or Limited Bandwidth) environment. Two different technical scenarios were investigated and tested:\r\n\r\nThe enhancement of Web Feature Service (WFS) instances to support updates on features sets.\r\n\r\nUtilizing a Web Processing Service (WPS) instance to access features, without the need to modify the downstream data service."
+ "@value": "This document provides the set of revision notes for OGC I3S Community Standard [OGC 17-014r5] and does not modify that standard.\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45403,30 +45079,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "19-012r1"
+ "@value": "19-034r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-15: Delta Updates Engineering Report"
+ "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes "
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-025",
+ "@id": "http://www.opengis.net/def/docs/19-021",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-03-07"
+ "@value": "2019-12-17"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Jérôme Jacovella-St-Louis"
+ "@value": "Esther Kok, Stephane Fellah"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -45441,17 +45117,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/18-025.html"
+ "@id": "https://docs.ogc.org/per/19-021.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "18-025"
+ "@value": "OGC Testbed-15: Semantic Web Link Builder and Triple Generator"
},
{
"@language": "en",
- "@value": " CityGML and AR Engineering Report"
+ "@value": "19-021"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -45461,7 +45137,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Testbed-14 Engineering Report (ER) describes the results of the Augmented Reality (AR) work performed in the Testbed-14 CityGML and Augmented Reality work package which was part of the Next Generation Services thread.\r\n\r\nBy integrating information available from urban models within a view of the real world through a mobile device, this testbed activity explored the possibilities offered by AR in a geospatial context. The ER additionally discusses the approach used to bring in these urban models from various data sources. The experiments also covered to some extent Virtual Reality (VR) where any city can be explored freely from a computer display or potentially within a VR headset.\r\n\r\nA continuation of these experiments would have looked at a combination of Augmented and Virtual Reality (Mixed Reality). The portrayal of AR and three-dimensional (3D) content through extending a common conceptual model to style classic geospatial features (as explored in the Testbed-14 Portrayal work) is also touched upon. The efficient transmission of 3D content is also a subject of this document through the use of a simple 3D transmission format developed during the initiative.\r\n\r\nThis ER provides many insights that showcase what is now made possible by the combination of AR, VR and integrated urban models.\r\n\r\nThe testbed work shines light on the benefits of applying a common portrayal approach to AR, bridging the gap between AR applications and traditional Geographic Information Systems and services.\r\n\r\nThe ER introduces a new, simple approach and conceptual model for transmitting 3D geospatial content which could be the basis to define simple profiles for the I3S and 3D Tiles community standards. It could also inform enhancements to the 3D Portrayal Service (3DPS) and/or next generation services (e.g., WFS 3.0) for delivering 3D contents in a format agnostic manner.\r\n\r\nFinally, the ER covers methods to bring in different types of geospatial content from various sources for integration into AR applications.\r\n\r\nDuring Testbed-14, the participants demonstrated AR experiences with geospatial datasets providing integrated views of urban spaces. Two clients and two services were shown to be interoperable, streaming AR content through a simple 3D transmission format, leveraging either GeoJSON or GNOSIS Map Tiles, as well as E3D 3D model specifications.\r\n\r\nThe feasibility of extending a classic portrayal conceptual model for AR was also shown. In order to serve them to the clients in the supported transmission formats, geospatial data sets of various types and in various formats were successfully imported for consumption by the services."
+ "@value": "This OGC Testbed 15 Engineering Report (ER) describes a generalized approach towards performing data fusion from multiple heterogeneous geospatial linked data sources. The specific use case is semantic enrichment of hydrographic features provided by Natural Resources Canada (NRCan). The ER attempts to define and formalize the integration pipeline necessary to perform a fusion process for producing semantically coherent fused entities."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45472,30 +45148,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-025"
+ "@value": "19-021"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Testbed-14: CityGML and AR Engineering Report"
+ "@value": "OGC Testbed-15: Semantic Web Link Builder and Triple Generator"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/17-088r1",
+ "@id": "http://www.opengis.net/def/docs/12-139",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2018-02-07"
+ "@value": "2013-02-05"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Luis Bermudez"
+ "@value": "Jan Herrmann, Andreas Matheus"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -45510,17 +45186,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/17-088r1.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=51833"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "17-088r1"
+ "@value": "12-139"
},
{
"@language": "en",
- "@value": "Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report"
+ "@value": "OWS-9: SSI Security Rules Service Engineering Report"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -45530,7 +45206,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "Disasters are responsible for major socioeconomic damages. Global initiatives call for the improvement of information technology infrastructure to better share data and advance multinational collaboration.\r\n\r\nThe Strengthening Disaster Risk Reduction Across the Americas: A Regional Summit on the Contributions of Earth Observations held on September 3-8 in 2017 in Buenos Aires, Argentina strengthened the collective ability to share the many challenges of disaster risk reduction in Latin America and the Caribbean (LAC) while promoting the awareness and better use of earth observations (EO).\r\n\r\nA simulation exercise took place during the summit. The exercise brought together government, emergency managers, earth observation data providers, academics, non-governmental organizations, and commercial companies. The participants assessed the capabilities and needs of policymakers, regional and on-the-ground decision makers, and learned what information products can be produced, and when and how such products are available.\r\n\r\nThis ER describes the description and results of the simulated scenario including the post-exercise activity that captured the lessons learned from the participants.\r\n\r\n"
+ "@value": "In this engineering report we describe how to administrate XACML v2.0, XACML v3.0 and GeoXACML v1.0.1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS). \r\nAfter introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.g. OGC XACML PAWS) specification.\r\n"
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45541,30 +45217,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "17-088r1"
+ "@value": "12-139"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report"
+ "@value": "OWS-9: SSI Security Rules Service Engineering Report"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/22-041",
+ "@id": "http://www.opengis.net/def/docs/09-182r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2023-08-16"
+ "@value": "2010-02-16"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Leigh St. Hilaire, Aidan Brookson"
+ "@value": "Josh Lieberman"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -45579,17 +45255,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/22-041.html"
+ "@id": "https://portal.ogc.org/files/?artifact_id=36889"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Testbed-18: Building Energy Data Interoperability Engineering Report"
+ "@value": "09-182r1"
},
{
"@language": "en",
- "@value": "22-041"
+ "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -45599,7 +45275,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Testbed-18 Engineering Report (ER) represents deliverable D012 and D013 for the Building Energy Data Interoperability task."
+ "@value": "This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. End-to-end here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45610,30 +45286,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "22-041"
+ "@value": "09-182r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "Testbed-18: Building Energy Data Interoperability Engineering Report"
+ "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-086r1",
+ "@id": "http://www.opengis.net/def/docs/19-016r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-02-15"
+ "@value": "2019-12-19"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Sam Meek"
+ "@value": "Michael A. Leedahl"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -45648,17 +45324,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/18-086r1.html"
+ "@id": "https://docs.ogc.org/per/19-016r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "18-086r1"
+ "@value": "19-016r1"
},
{
"@language": "en",
- "@value": "OGC Vector Tiles Pilot: Summary Engineering Report"
+ "@value": "OGC Testbed-15: Data Centric Security"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -45668,7 +45344,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "This OGC Engineering Report (ER) provides the summary findings resulting from completion of the OGC Vector Tiles Pilot (VTP or Pilot). The requirements for the Pilot were generated from a combination of sponsor input and analysis of typical use cases for tiling of vector feature data across the OGC Standards Baseline and related standards. The driving use case for this activity was the visualization of feature data on a client. The three main scenarios considered were consumption of tiled feature data by a web client, a desktop client and a mobile client. As a standards body, the OGC already has standards that fit these use cases. These are; Web Map Tile Service 1.0 (WMTS) for a web client, and GeoPackage 1.2 for a mobile client. Web Feature Service (WFS) 3.0 is suitable for a desktop client and has an in-built method to support tiling, but not specifically for tiled feature data such as that explored in the VTP. One of the purposes of the Pilot was to produce demonstration implementations to support tiled feature data using WFS 3.0, WMTS 1.0 and GeoPackage 1.2 that can be validated by Technology Integration Experiments (TIEs). The draft extension to these standards helped define a draft Conceptual Model for tiled feature data in support of visualization. The Conceptual Model formally captures the requirements for component implementations and rationalizes them into a model documented in the Unified Modeling Language (UML).\r\n\r\nThe ER provides an overview of each of the components, their implementation decisions and the challenges faced. The components are presented as draft extensions to existing standards. The WFS standard is currently in a major revision cycle and is transitioning away from services to a resource-oriented architecture. This transition has implications for access to tiled feature data. This offers options of access to pre-rendered tiles, or to tiles created using WFS 3.0 query functionality. The current WMTS standard only offers access to the pre-rendered tiles and much of the work is therefore about defining and supporting tiled feature data as a media type. The OGC GeoPackage standard is more complex as it attempts to ship all of the tiled feature data in a self-contained package aimed at environments that have Denied, Degraded, Intermittent or Limited (DDIL) bandwidth. DDIL is an important use case for GeoPackage as most normal web services do not function without connectivity. The military, first responders and other groups who work in challenging operational environments require a capability to ship, store and distribute geospatial data in an efficient, modern manner. The combination of GeoPackage and tiled feature data offers the means to supply detailed geospatial data in a portable fashion to satisfy many DDIL use cases. GeoPackage also offers the majority of the future work as it attempts to store information such as styling and attribution separately to the geometries to take advantage of a relational database structure.\r\n\r\nWhen this project was initiated, the term vector tiles was used throughout. However, as the project progressed, the participants agreed that the term tiled feature data was more appropriate than the colloquial term of vector tiles. This engineering report therefore interchangeably uses both tiled feature data and vector tiles to refer to the approach of tiling vector feature data.\r\n\r\n"
+ "@value": "The OGC Testbed-15 Data Centric Security Engineering Report (ER) discusses the current state of security in protecting data in a geospatial environment. The ER examines the use of encrypted container formats such as NATO STANAG 4778 Information on standard Metadata Binding with metadata as defined in NATO STANAG 4774 Confidentiality Metadata Label Syntax in combination with geospatial data using the encoding for an OGC Web Feature Service (WFS) FeatureCollection structure. This report also makes a recommendation for the creation of new media types to support output container formats such as STANAG 4778. The report then discusses various implementation scenarios in which a STANAG 4778 (eXtensible Markup Language (XML) container maintains encrypted data from author to service to viewer. These implementations use the new OGC API - Features - Part 1: Core with features encrypted using keys supplied by feature authors and users."
}
],
"http://www.w3.org/2004/02/skos/core#inScheme": [
@@ -45679,38 +45355,30 @@
"http://www.w3.org/2004/02/skos/core#notation": [
{
"@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no",
- "@value": "18-086r1"
+ "@value": "19-016r1"
}
],
"http://www.w3.org/2004/02/skos/core#prefLabel": [
{
"@language": "en",
- "@value": "OGC Vector Tiles Pilot: Summary Engineering Report"
- }
- ]
- },
- {
- "@id": "http://www.opengis.net/def/doc-type/d-per",
- "http://www.w3.org/2004/02/skos/core#narrower": [
- {
- "@id": "http://www.opengis.net/def/docs/22-020"
+ "@value": "OGC Testbed-15: Data Centric Security"
}
]
},
{
- "@id": "http://www.opengis.net/def/docs/18-029",
+ "@id": "http://www.opengis.net/def/docs/18-023r1",
"@type": [
"http://www.w3.org/2004/02/skos/core#Concept"
],
"http://purl.org/dc/terms/created": [
{
"@type": "xsd:date",
- "@value": "2019-03-15"
+ "@value": "2019-03-06"
}
],
"http://purl.org/dc/terms/creator": [
{
- "@value": "Sara Saeedi"
+ "@value": "Joan Masó"
}
],
"http://www.opengis.net/def/metamodel/ogc-na/doctype": [
@@ -45725,17 +45393,17 @@
],
"http://www.w3.org/2000/01/rdf-schema#seeAlso": [
{
- "@id": "https://docs.ogc.org/per/18-029.html"
+ "@id": "https://docs.ogc.org/per/18-023r1.html"
}
],
"http://www.w3.org/2004/02/skos/core#altLabel": [
{
"@language": "en",
- "@value": "Symbology Engineering Report"
+ "@value": "MapML Engineering Report"
},
{
"@language": "en",
- "@value": "18-029"
+ "@value": "18-023r1"
}
],
"http://www.w3.org/2004/02/skos/core#broader": [
@@ -45745,7 +45413,7 @@
],
"http://www.w3.org/2004/02/skos/core#definition": [
{
- "@value": "The portrayal and visualization of geospatial information is a critical task for facilitating decision making, situational awareness, and spatial analysis. However, despite its importance, various local, national, and international agencies continue to use different symbols and terminology for the same event, feature, or entity. This approach prevents interoperability from being extended to the semantic level, which in turn makes it difficult to share, reuse, and mediate unambiguous portrayal information between agencies.\r\n\r\nThis Engineering Report (ER) captures the requirements, solutions, models, and implementations of the Open Geospatial Consortium (OGC) Testbed-14 Portrayal thread. This effort leverages the work of the Portrayal Ontology development and the Semantic Portrayal Service conducted during Testbed 10, 11, 12 and 13. Thus far the emphasis for developing the portrayal ontologies (Testbeds 12 and 13) has been on modeling and representing portrayal information for feature data. The objective of Testbed-14 is to extend the portrayal ontology to accommodate more complex symbols (e.g., composite symbols) and to provide clear recommendations on how to best proceed with portrayal information encodings."
+ "@value": "This is the second Engineering Report (ER) about the Map Markup Language (MapML) cite:[Rushforth2018] resulting from OGC Testbed initiatives. To find an introduction of MapML and how it works, please, refer to the previous ER OGC 17-019 cite:[Maso2018]. MapML is a new media type that can be included in a element of a