Conceptio › Archive › Open Geospatial Consortium (OGC)

Open Geospatial Consortium (OGC)open access

OGC OWS Context Conceptual Model (version 1.0) — OGC 12-080r2

Open Geospatial Consortium · Open Geospatial Consortium (OGC)

Open Geospatial Consortium (OGC) · Standards · License: Open Access

conceptual context geospatial model ogc ogc12 opengeospatialconsortium

ogc, geospatial, standard, open geospatial consortium, owc, ogc owc, 12-080r2, ogc 12-080r2, 1.0, ows, context, conceptual, model

Open Geospatial Consortium Publication Date: 2014-01-22 Approval Data: 2013-12-05 Submission Date: 2013-09-01 Reference URL for this document: www.opengeospatial.net/doc/IS/owc-conceptual/1.0

Internal reference number of this OGC® document:

12-080r2

Version: 1.0 Category: OGC® Implementation Standard Editor(s): Roger Brackin, Pedro Gonçalves

Warning This document is an OGC Member approved international standard. This document is available on a royalty free, non-discriminatory basis. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

Document type: Document subtype: Document stage: Document language:

OGC® Implementation Standard Conceptual Model Approved for Public Release English

Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement. If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR. THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT MAY BE IN FORCE ANYWHERE IN THE WORLD. THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE INTELLECTUAL PROPERTY WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR FREE. ANY USE OF THE INTELLECTUAL PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THE INTELLECTUAL PROPERTY BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION OR PERFORMANCE OF THIS INTELLECTUAL PROPERTY. This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by any third party. Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or specifications. This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.

OGC 12-080r2

Contents 1. Scope ............................................................................................................................ 7 2. Conformance ................................................................................................................ 7 3. References .................................................................................................................... 7 4. Terms and Definitions.................................................................................................. 7 4.1 Common Operating Picture ................................................................................... 8 4.2 Context Document ................................................................................................. 8 4.3 Resource................................................................................................................. 8 4.4 Area of Interest ...................................................................................................... 8 5. Conventions ................................................................................................................. 8 5.1 Abbreviated Terms................................................................................................. 8 5.2 UML notation......................................................................................................... 8 5.3 Data dictionary tables ............................................................................................ 9 5.4 Core and Extension Breakdown............................................................................. 9 6. Use Cases and Requirements ..................................................................................... 11 6.1 Use Cases ............................................................................................................. 11 6.2 Overview of Key Requirements........................................................................... 11 6.2.1 Definition of Geographic Area ..................................................................... 11 6.2.2 Definition of Temporal Interval .................................................................... 11 6.2.3 Support a series of Configured Resources .................................................... 12 6.2.4 Order of Configured Resources .................................................................... 12 6.2.5 Support Multiple Service Types and Parameters .......................................... 12 6.2.6 Allow Clients to decide if service is supported ............................................ 12 6.2.7 Support for visualization and other client types ........................................... 12 6.2.8 Allow resources to be enabled or disabled ................................................... 12 6.2.9 Association of Information with embedded Content .................................... 12 6.2.10 Support for In-line Content ......................................................................... 12 6.2.11 Support for External Content ...................................................................... 13 6.2.12 Support for Chained Services ..................................................................... 13 6.2.13 Support for capturing Resource Parameters ............................................... 13 7. OWS Context Conceptual Model ................................................................................ 1 7.1 Overview ................................................................................................................ 1 2

OGC 12-080r2 7.2 Core Conceptual Model ......................................................................................... 1 7.2.1 Class ows:Context........................................................................................... 3 7.2.2 Class owc:Resource ........................................................................................ 5 7.2.3 Datatype owc:Offering.................................................................................... 8 7.2.4 Datatype owc:Operation ................................................................................. 9 7.2.5 Datatype owc:Content................................................................................... 10 7.2.6 Datatype owc:StyleSet .................................................................................. 10 7.2.7 Datatype owc:Creator ................................................................................... 11 7.2.8 Datatype owc:CreatorApplication ................................................................ 12 7.2.9 Datatype owc:CreatorDisplay ....................................................................... 13 7.3 owc:WMS Offering Extension ............................................................................ 14 7.3.1 Summary of Valid Attributes ........................................................................ 15 7.3.2 Supported Standards Within This Extension ................................................ 15 7.4 owc:WFS Offering Extension .............................................................................. 15 7.4.1 Summary of Valid Attributes ........................................................................ 16 7.4.2 Supported Standards Within This Extension ................................................ 16 7.5 owc:WCS Offering Extenstion ............................................................................ 16 7.5.1 Summary of Valid Attributes ........................................................................ 16 7.5.2 Supported Standards Within This Extension ................................................ 17 7.6 owc:WPS Offering Extension .............................................................................. 17 7.6.1 Summary of Valid Attributes ........................................................................ 17 7.6.2 Supported Standards Within This Extension ................................................ 18 7.7 owc:CSW Offering Extenstion ............................................................................ 18 7.7.1 Summary of Valid Attributes ........................................................................ 18 7.7.2 Supported Standards Within This Extension ................................................ 19 7.8 owc:WMTS Offering Extension .......................................................................... 19 7.8.1 Summary of Valid Attributes ........................................................................ 19 7.8.2 Supported Standards Within This Extension ................................................ 20 7.9 owc:GML Offering Extension ............................................................................. 20 7.9.1 Summary of Valid Attributes ........................................................................ 20 7.9.2 Supported Standards Within This Extension ................................................ 20 7.10 owc:KML Offering Extension ........................................................................... 21 7.10.1 Summary of Valid Attributes ...................................................................... 21 7.10.2 Supported Standards Within This Extension .............................................. 21 3

OGC 12-080r2 7.11 owc:GeoTIFF Offering Extension ..................................................................... 21 7.11.1 Summary of Valid Attributes ...................................................................... 22 7.11.2 Supported Standards Within This Extension .............................................. 22 7.12 owc:GMLJP2 Offering Extension ..................................................................... 22 7.12.1 Summary of Valid Attributes ...................................................................... 23 7.12.2 Supported Standards Within This Extension .............................................. 23 7.13 owc:GMLCOV Offering Extension ................................................................... 23 7.13.1 Summary of Valid Attributes ...................................................................... 24 7.13.2 Supported Standards Within This Extension .............................................. 24 A.1 Conformance Test Class: core ............................................................................ 25 A.1.1 Fully Implements the Content Class ............................................................ 26 A.1.2 Fully Implements the CreatorDisplay Class ................................................ 27 A.2 Conformance Test Class: WFS Extension .......................................................... 28 A.3 Conformance Test Class: WCS Extension.......................................................... 28 A.4 Conformance Test Class: WPS Extension .......................................................... 29 A.5 Conformance Test Class: CSW Extension.......................................................... 29 A.6 Conformance Test Class: WMTS Extension ...................................................... 29 A.7 Conformance Test Class: GML Extension ......................................................... 30 A.8 Conformance Test Class: KML Extension ......................................................... 30 A.9 Conformance Test Class: GeoTIFF Extension ................................................... 30 A.10 Conformance Test Class: GMLJP2 Extension.................................................. 31 A.11 Conformance Test Class: GMLCOV Extension ............................................... 31

OGC 12-080r2

Abstract This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard. The OGC Web Services Context Document (OWS Context) was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is developed to support in-line content as well. The goal is to support use cases such as the distribution of search results, the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes. OWS Context is aimed at replacing previous OGC attempts at providing such a capability (the Web Map Context WMC) which was reasonably successful but limited to WMS. Other work on the ‘Location Organizer Folder (LOF)’ was also taken into consideration. The concept of OWS Context, and the first prototype document was produced as part of OGC testbed OWS-7. See OGC 10-035r1, Information Sharing Engineering Report. In order to achieve mass market appeal, as well as being useful to a wider community, the use of OWS Context support to other existing standards was considered. Multiple encoding formats for OWS Context have been developed (ATOM, JSON). Each of these is described in a separate OWS Context Extensions to the Core model. This document concentrates on describing the OWS Context Model in abstract terms using UML. The document defines requirements and use cases. It also includes an abstract test suite to verify that encodings are compliant with the core specification. The intent of OWS Context is to allow many types of OGC Data Delivery service to be referenced and therefore exploited (for example, not just WMS but also WFS, WCS and WPS) but it does not explicitly define the encoding of these services in the core (only the general approach to be used for different types of service interface). Service explicit encodings are defined within the extension documents for ATOM and JSON. The abbreviation owc is used throughout this document for OWS Context.

OGC 12-080r2

ii.

Keywords The following are keywords to be used by search engines and document catalogues Ogcdoc, COP, Common Operating Picture, OWC, Context, OWS Context

iii.

Preface Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation when possible.

iv.

Submitting organizations The following organizations submitted this Implementation Standard to the Open Geospatial Consortium as an Implementation Standard: Envitia Intergraph ImageMatters NGA Terradue USGS

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

Company

Roger Brackin

Envitia

Pedro Gonçalves

Terradue

Joan Maso

Universitat Autònoma de Barcelona

David Rosinger

Intergraph

Raj Singh

OGC

Matt Tricomi

USGS

David Wesloh

NGA

Jeff Yutzler

Image Matters Inc.

OGC 12-080r2

1. Scope This document defines the conceptual model of the OWS Context document and the intended semantics of each element of the document. It also defines the requirements and the abstract test cases against which encoding specifications using specific carrier standards can be validated as compliant with OWS Context.

2. Conformance This document defines a standardisation target for encodings which implement the OWS Context conceptual model in order to allow different encodings to have equivalent content and semantics so that they can be interoperable; it establishes a core requirements class: http://www.opengis.net/spec/owc/1.0/req/core with URI of http://www.opengis.net/spec/owc/1.0/req/core as well as a number of extensions, one per chosen service type. Requirements and conformance test URIs defined in this document are relative to http://www.opengis.net/spec/owc/1.0. All requirements in this specification are part of the core requirement stated above. Conformance with this standard shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site. In order to conform to this OGC® interface standard, an encoding standard shall choose to implement any one of the conformance levels specified in Annex A (normative).

3. References The following normative documents contain provisions that, through reference in this text, constitute provisions of this document. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies. 1. ISO19115:2003 Metadata Standard for Geographic Information. 2. OGC 08-131r3 - The Specification Model — A Standard for Modular specifications

4. Terms and Definitions The following terms and definitions are used throughout this document:

OGC 12-080r2 4.1 Common Operating Picture A COP is a single identical display of relevant information shared by more than one command. A common operational picture facilitates collaborative planning and assists all echelons to achieve situational awareness. 4.2 Context Document A context document is a document describing the set of resources and their configuration, and ancillary information (area of interest, etc.) which defines the information representation of a common operating picture. 4.3 Resource A resource is a configured set of information which is uniquely identifiable to a user. This can be realised as in-line or external content or by one or more configured web services. 4.4 Area of Interest An area of interest is a geographic area which is significant to a user.

5. Conventions This sections provides details and examples for any conventions used in the document. Examples of conventions are symbols, abbreviations, use of XML schema, or special notes regarding how to read the document. 5.1 Abbreviated Terms owc - OGC Web Services Context 5.2 UML notation Unified Modeling Language (UML) static structure diagrams appearing in this specification are used as described in Sub clause 5.2 of OGC Web Service Common [OGC 06-121r9]. Further, the following conventions hold: UML elements having a package name of “OWS Common” are those defined in the UML model of OWS Common [OGC 06-121r9]. UML elements having a package name of GML are those defined in the UML model of GML [OGC 07-036].

OGC 12-080r2 UML elements not qualified with a package name are those defined in this Standard. UML data type Any is used here as an equivalence to XML’s xsd:any. 5.3 Data dictionary tables The UML model data dictionary is specified herein in a series of tables. The contents of the columns in these tables are described in Sub clause 5.5 of [OGC 06-121r9]. The contents of these data dictionary tables are normative, including any table footnotes. For the reader’s convenience, table rows describing inherited components are shaded. 5.4 Core and Extension Breakdown The OWS context standard follows the modular specification design pattern identified in REF 3. It was decided that the requirements would be split both on the basis of core and then specific service types (WMS, WFS etc.) and also on the basis of specific encoding of the document.

OGC 12-080r2

Figure 1 - OWS Context Requirement Class and Document Breakdown

The core context document is largely agnostic of any particular resource type, covering the basic structure and the extension model. A requirement class is then defined for each resource offering. This document covers all of the requirement classes for the conceptual model (the left grey box in figure 1 above). These standardization target resources include services (WMS, WFS), encodings for in-line content (GML, GeoTiff) and storage for external content (GeoPackage). Various potential OWS Context encodings have been considered, in particular there are clear requirements for both an XML (Atom) encoding and a JSON Encoding. These are the subject of separate documents (Implementation Specifications). This standard recommends that any implementer of an application profile which defines an extensions conceptual model should define both an XML (Atom) and a JSON Encoding of the extension.

OGC 12-080r2

6. Use Cases and Requirements The Context Document goal is to support the exchange of a common operating picture or view between human users or applications such that the area of interest, time range, resources and their configuration is unambiguously exchanged between applications. 6.1 Use Cases The OWS Context document is aimed at meeting a range of user context exchange requirements around shared situational awareness. Possible uses of the context document include: 1. Exchange of a common view or common operating picture for shared situational awareness. 2. Exchange of discovery results from various catalogue searches, to avoid duplication of effort. 3. Exchange of configuration and/or results of an analysis or processing activity The exchange of a common operating picture is recognized as the most important usage of the OWS Context Document. As part of this there is the recognition that in some cases the services referenced may not be available.Therefore information outputs from services may be included as in-line content or referenced as external content in a container such as a GeoPackage, andsome descriptive information (for example overlays or thumbnails) may need to be carried in the context document itself or alongside it. 6.2 Overview of Key Requirements The above use cases lead to the following general requirements for an OWS Context document. All of these requirements are implicit in the core requirement class http://www.opengis.net/spec/owc/1.0/req/core shown (and detailed in section 7).

6.2.1 Definition of Geographic Area The Context Document shall provide the capability to identify the geographic area of interest of the common operating picture. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ContextClass 6.2.2 Definition of Temporal Interval The Context Document shall provide the capability to identify the temporal extent of the COP (one or more time envelopes). Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ContextClass

OGC 12-080r2 6.2.3 Support a series of Configured Resources The Context Document shall provide the capability to define a series of configured resources together which provide relevant information to the COP User. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ContextClass 6.2.4 Order of Configured Resources The Context Document shall define the order of precedence of the resources included (this could be interpreted as, for example, the order of display by visualization clients) Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ContextClass. 6.2.5 Support Multiple Service Types and Parameters The Context Document shall allow any service type to be specified and any rules to be specified. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass 6.2.6 Allow Clients to decide if service is supported The Context Document shall provide information to allow clients to test if a service matches a supported profile in order to understand if they can interpret it. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/OfferingClass 6.2.7 Support for visualization and other client types The Context Document shall allow information targeted at different representations to be included (i.e. not just targeted at geographic visualization or just visualization). Requirement: http://www.opengis.net/spec/owc/1.0/req/core/StyleSet 6.2.8 Allow resources to be enabled or disabled The Context Document shall allow information to be marked as enabled or disabled, i.e. it is to be presented to the user when the context is opened or it isn’t. Source: WMC Specification: which has an on/off option (layer displayed or not when loaded). Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass 6.2.9 Association of Information with embedded Content It shall be possible to associate information (e.g. styling) with embedded content, e.g. GML. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass 6.2.10 Support for In-line Content The Context Document should allow the in-line inclusion of a resource (literal value of a resource) in the context document. 12

OGC 12-080r2 Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass 6.2.11 Support for External Content The Context Document should allow reference to a literal value of a resource in a container external to the context document. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass 6.2.12 Support for Chained Services The Context Document should allow the definition of a chain of processing services in order to define a resource. Not included in version 1 of the specification. 6.2.13 Support for capturing Resource Parameters The Context Document should allow the parameters which define the resource or processing service steps to be captured. Requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass

7. OWS Context Conceptual Model 7.1 Overview This clause specifies the underlying OWS Context conceptual model for which an encoding can be created. It defines the mandatory requirements for context encoding and the necessary semantics of how that encoding should be interpreted. The conceptual model is broken down into various packages. These are shown in Figure 1 below.

Figure 2 – OWS Context Standard Packages

7.2 Core Conceptual Model The requirements within this section fall within the ows context core requirement class. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/core

Scope:

All requirements in this subsection relate to the above requirement class.

Dependencies:

None

Description:

The OWS Context conceptual model is shown in the UML Diagram below.

OGC 12-080r2

class OWC Core Model «DataType» CreatorApplication

«DataType» Creator

Context + + + + + + + + + + + + + +

specReference :URI language :CharacterString id :CharacterString title :CharacterString abstract :CharacterString [0..1] updateDate :CharacterString [0..1] author :CharacterString [0..*] publisher :CharacterString [0..1] creator :Creator [0..1] rights :CharacterString [0..1] areaOfInterest :GM_Envelope [0..1] timeIntervalOfInterest :TM_GeometricPrimitive [0..1] keyword :CharacterString [0..*] extension :Any [0..*]

+ + +

title :CharacterString [0..1] uri :URI [0..1] version :Version [0..1]

«DataType» CreatorDisplay + + + +

pixelWidth :int [0..1] pixelHeight :int [0..1] mmPerPixel :double [0..1] extension :Any [0..*]

«DataType» Offering

resource

+ + + + +

0..* {ordered} Resource + + + + + + + + + + + + + + + + + + +

+ + +

creatorApplication :CreatorApplication [0..1] creatorDisplay :CreatorDisplay [0..1] extension :Any [0..*]

id :CharacterString title :CharacterString abstract :CharacterString [0..1] updateDate :TM_Date [0..1] author :CharacterString [0..*] publisher :CharacterString [0..1] rights :CharacterString [0..1] geospatialExtent :GM_Envelope [0..1] temporalExtent :TM_GeometricPrimitive [0..1] contentDescription :Any [0..1] preview :URI [0..*] contentByRef :URI [0..*] offering :Offering [0..*] active :Boolean [0..1] keyword :CharacterString [0..*] maxScaleDenominator :double [0..1] minScaleDenominator :double [0..1] folder :CharacterString [0..1] extension :Any [0..*]

code :URI operation :Operation [0..*] content :Content [0..*] styleSet :StyleSet [0..*] extension :Any [0..*]

«DataType» Operation

+resourceMetadata +contextMetadata 0..*

0..*

+ + + + + + +

code :CharacterString method :CharacterString type :CharacterString requestURL :URI request :Content [0..1] result :Any [0..1] extension :Any [0..*]

MD_Metadata

«DataType» Content + + + +

type :CharacterString URL :URI [0..1] content :Any [0..1] extension :Any [0..*]

«DataType» StyleSet + + + + + + +

name :CharacterString title :CharacterString abstract :CharacterString [0..1] default :Boolean [0..1] legendURL :URI [0..*] content :Content [0..1] extension :Any [0..*]

Figure 3 – UML Class Diagram of OWS Context

The role of each class and attribute in the model above is described in the tables below.

OGC 12-080r2 7.2.1 Class ows:Context Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/ContextClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the Context Class and meet all of the tabulated constraints and notes

This class is the overall container class for the context document. Its properties are documented below. Name

specReference

Data type and Value

Definition

Specification Reference identifying

Multiplicity and Use

URI

One (mandatory)

CharacterString

One (mandatory)

CharacterString

One (mandatory)

CharacterString

One (mandatory)

CharacterString

Zero or one

that this is an owc Context document language

Language used in the owc Context document

Unique Identifier assigned to the OWS Context Document

title

A Human Readable Title for the OWS Context Document

abstract

Description of the Context

(optional)

Document Purpose/Content updateDate

Date when the Context Document

CharacterString

Zero or one (optional)

CharacterString

Zero or more (optional)

CharacterString

Zero or one (optional)

Creator

Zero or one (optional)

was updated author

Identifier for the author of the document

publisher

Identifier for the publisher of the document

creator

The tool/application used to create the context document and its properties

OGC 12-080r2 Definition

Data type and Value

Rights which apply to the context

CharacterString

Zero or one (optional)

GM_Envelope

Zero or one

Name

rights

document areaOfInterest

Geographic area of interest of the users of the context document

timeIntervalOfInterest

keyword

(optional)

b,c

A date/time interval relevant to the

Multiplicity and Use

TM_GeometricPri

Zero or one (optional)

context document .

mitive

Keyword related to this context

CharacterString Zero or more

(optional)

document. Shall support an optional codelist parameter. resource

The description of a resource and

owc:Resource

Zero or more (optional)

its access parameters and d

configuration . contextMetadata

Additional metadata describing the

Association

Zero or more (optional)

n/a

Zero or more (optional)

context document itself. The format recommendation is ISO19115 complaint metadata. The metadata standard used should be specified extension

Any encoding should allow the user to extend the context content to include custom items

Table 1- Context Class Properties a

The rights described apply to the Context Document itself not to any of its contents.

These properties define the geographic area of interest and date/time interval of interest to the context user. They do not define the bounding extent (either in geographic area or time) of the referenced resources. The intention is not to provide the overall bounds or clipping extent but simply to indicate to a Context Document client the expected view of the information in area and time.

OGC 12-080r2 c

The Coordinate Reference System shall be unambiguous. It should either be implicit in the choice of encoding of an area of interest or explicitly defined. d

Resources are ordered. Clients would normally interpret this in terms of display order. How the encoding defines the order of layers in relation to display shall be defined in the encoding specification. 7.2.2 Class owc:Resource Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the Resource Class and meet all of the tabulated constraints and notes

This class describes the resource elements which supply the information layers used in the Context Document. Resource, while it can be used bare, is typically classified by owc:MediaCode indicating the type of information encoded in the resource. The resource offers multiple ways to pass a configured resource, in-line content, by absolute URI and by service Content which needs to be interpreted by an intelligent client. While there may be limitations in the individual encoding, each of these types shall be semantically equivalent, i.e. alternative representations of the same information (they can for example have different resolutions but should not show fundamentally different information). Name

Definition

Data type and Value

Multiplicity and Use

Unique Identifier assigned to the

CharacterString

One (mandatory)

CharacterString

One (mandatory)

CharacterString

Zero or one (optional)

Date when the resource definition CharacterString

Zero or one (optional)

owc Resource. Used to reference a resource from other resources title

A Human Readable Title for the owc Resource.

abstract

Description of the Context Document Purpose/Content

updateDate

was updated author

Identifier for the author of the

CharacterString

Zero or more

OGC 12-080r2 Name

Data type and Value

Definition

(optional)

resource definition publisher

Identifier for the publisher of the

CharacterString

Zero or one (optional)

CharacterString

Zero or one (optional)

GM_Envelope

Zero or one

resource definition rights

Rights which apply to the resource definitiona

geospatialExtent

The geographic extent of the resource

temporalExtent

contentDescription

(optional)

TM_GeometricP Zero or one

The temporal extent of the content of the resource

Multiplicity and Use

rimitive

A reference to a description of the Any Context resource in alternative

(optional) Zero or one (optional)

format. preview

A URI identifying a preview of

URI

(optional)

the resource contentByRef

Zero or more

URI

Zero or more (optional)

Service or inline content offering

owc:OfferingTy

for the resource targeted at OGC

Zero or more (optional)

A URI identifying a service which will return an immediately exploitable result by simply requesting based on the URI. The expectation is that the return type of this call will be a well-known format

offering

compliant clients active

This flag indicates the state of the Boolean resource within the context

Default=TRUE

Zero or one (optional)

document. It can be interpreted by the caller as required (this may be defined in a profile or in the

OGC 12-080r2 Name

Definition

Data type and Value

Multiplicity and Use

CharacterString

Zero or more (optional)

specific service extensions) keyword

Keyword related to this resource definition. Shall support an optional codelist parameter.

tor

the layer .

Zero or one (optional)

maxScaleDenomin

Maximum scale for the display of double

Zero or one

minScaleDenomina

Minimum scale for the display of double d

ator

the layer .

(optional)

resourceMetadata

Metadata about the resource itself Association

Zero or more (optional)

folder

Definition of the folder structure

CharacterString

Zero or one (optional)

n/a

Zero or more

in which the resource is placed. extension

Any encoding should allow the

(optional)

user to extend the resource content to include custom items Table 2- Resource Class Properties

The semantics of rights is not defined here and needs to be defined in extension packages. b

The geospatial extent indicates to a client that data that intersects with this area needs to be retrieved and, if relevant portrayed. There is no specific requirement to hard clip the data to this boundary. c

The temporal extent indicates to a client that data that intersects with this time interval needs to be retrieved, and, if relevant, portrayed. There is no specific requirement to hard clip the data to this boundary. d

OGC 12-080r2 of 0.28 mm × 0.28 mm (millimeters). The definition is the same used in WMS 1.3.0 [OGC 06-042] and in Symbology Encoding Implementation Specification 1.1.0 [05077r4]. Frequently, the true pixel size is unknown and 0.28 mm is a common actual size for current displays. 7.2.3 Datatype owc:Offering Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/OfferingClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the Offering Class and meet all of the tabulated constraints and notes

This datatype class defines the properties of a specific service binding or inline content for an offering. The service binding is primarily characterized by a series of parameters. The parameters valid for a specific type of service binding, e.g. WFS are defined outside of the OWS Context core specification. Each specific service binding is defined by a URI which references a requirement class. Name

code

Code identifying the type of service offering

operation

Data Type and Values

Definition

URI

One (mandatory)

owc:Operation

Zero or more (optional)

Operations used to invoke the service

Multiplicity and Use

content

inline content

owc:Content

Zero or more (optional)

styleSet

Style sets to style the in-line

owc:StyleSet

Zero or more (optional)

content extension

Application specific content

n/a

Zero or more (optional)

Table 3- Offering Class Properties

Operations of a specific service request should be defined in a separate extension of this document. Additional, custom additions are supported on an ad-hoc basis without 8

OGC 12-080r2 changing the core service offering type. Any modification of the parameter field types or semantics would require a new service offering code value. 7.2.4 Datatype owc:Operation Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/OperationClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the Operation Class and meet all of the tabulated constraints and notes

Definition of the operation either to get the information or to get the capabilities. Note that service specific extension requirements may mandate more than one owc:operation. Name

code

Code identifying the type of Operation

method

Data Type and Values

Definition

Multiplicity and Use

CharacterString

One (mandatory)

CharacterString

One (mandatory)

Name of operation method request

type

MIMEType of the return result

CharacterString

One (mandatory)

requestURL

Service Request URLb

URI

One (mandatory)

request

Optional request body contentc

Owc:Content

Zero or one (optional)

result

result of the operation (optional)

Any

Zero or one (optional)

extension

Application specific content

n/a

Zero or more (optional)

Table 4- Operation Class Properties

a Typically the OGC Service request type, e.g. "GetCapabilities" or "GetMap". b Full request URL for an http:get, and request URL http:post. 9

OGC 12-080r2 c Note not necessarily XML (defined by MIMEType).

7.2.5 Datatype owc:Content Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/ContentClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the Content Class and meet all of the tabulated constraints and notes

Definition

Data Type and Values

Multiplicity and Use

type

Type of the inline content

CharacterString

One (mandatory)

URL

Referenced Content

URL

Zero or One

Name

(optional) content

Actual content in the content element

Any

extension

Zero or One (optional)

Application specific content

n/a

Zero or more (optional)

Table 5- Content Class Properties a:

URL and content elements are mutually exclusive, and the provision of one is mandatory. One and only one of URL or content should be populated in a specific content element (i.e a content element must either have content or reference content). 7.2.6 Datatype owc:StyleSet Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/StyleSetClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the StyleSet Class and meet all of the tabulated constraints and notes

OGC 12-080r2 This datatype class defines a portrayal style for a resource content or serviceContent element. It can be specified at a resource level or at a service offering level (when it only applies to the offering. Name

name

Data Type and Values

Definition

Unique name of the styleSet within

Multiplicity and Use

CharacterString

One (mandatory)

CharacterString

One (mandatory)

CharacterString

Zero or one

a given offering title

A Human Readable Title for the OWS Context Document

abstract

Description of the Style

(optional) default

Whether this Styleset is the one to

Boolean Default=FALSE

Zero or one (optional)

URL

Zero or one (optional)

URI

Zero or one

be used as default (initial display) legendURL

URL of a legend image for the style

content

The in-line or an external

(optional)

reference to the style definition extension

Any encoding should allow the

n/a

user to extend the style definition

Zero or more (optional)

to include custom items

Table 6- StyleSet Class Properties

Note: StyleSet cannot be derived from the service request, and it is a list of relevant styles which could be applied if the service supports dynamic styling, for example if the WMS is an FPS and supports SLD. The intention is that the client could visualize the layer using the getMap Call (which would have a defined styling) but could also offer the user a selection of alternative styles for the layer. These would be derived from the style list parameter. 7.2.7 Datatype owc:Creator Requirement ID:

OGC 12-080r2 Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the Creator Class and meet all of the tabulated constraints and notes

This datatype class provides place to encode information related to the creator of the con text document. It includes the creator application and any relevant properties or settings for the application. Name

Definition

Data Type and Values

creatorApplication

The name, reference and version

CreatorApplication

Zero or one (optional)

CreatorDisplay

Zero or one (optional)

n/a

Zero or more

of the creator application used to

Multiplicity and Use

create the context document creatorDisplay

Properties of the display in use when the context document was created (for display based applications only).

extension

Any encoding should allow the

(optional)

user to extend the Creator information to include custom items

Table 7- Creator Class Properties

7.2.8 Datatype owc:CreatorApplication Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/CreatorApplication Class Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the CreatorDisplay Class and meet all of the tabulated constraints and notes

OGC 12-080r2 This datatype class provides place to encode information related to the creator context when the document was produced. It includes the creator application and relevant properties or settings for the application.

Name

title

Data Type and Values

Definition

Title or name of the application (for

CharacterString

Zero or one (optional)

URI

Zero or one

display purposes) uri

URI describing the creator

(optional)

application. version

Multiplicity and Use

Version of the application.

CharacterString

Zero or one (optional)

Table 8- CreatorApplication Class Properties

7.2.9 Datatype owc:CreatorDisplay Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/core/CreatorDisplayClass

Requirement Txt:

Implementations shall support the encoding of all of the mandatory and optional parameters of the CreatorDisplay Class and meet all of the tabulated constraints and notes

This datatype class provides place to encode information related to the display area used in the creator application when the OWS Context document was produced. This set of properties only applies to creator applications which are using a geographic display and is supporting information to the exploiter of the OWS Context document. Note the elements within creator display are intended as supporting information (metadata) for clients and not properties which should control the display size of the client opening the document. Name

pixelWidth

Definition

Pixel width of the display specified by Area of Interest.

Data Type and Values Integer

Multiplicity and Use

Zero or one (optional)

OGC 12-080r2 Name

pixelHeight

Data Type and Values

Definition

Pixel height of the display

Integer

Zero or one (optional)

Double

Zero or one

specified by Area of Interest. mmPerPixel

The number of mm per pixel for

Multiplicity and Use

(optional)

the display. If no value is available the field should be set to NULL. extension

Any encoding should allow the

n/a

user to extend the display

Zero or more (optional)

information to include custom items

Table 9- CreatorDisplay Class Properties

7.3 owc:WMS Offering Extension This class describes the extension to the OWS Context Core which supports Web Map Service Extensions (WMS) offerings. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/wms

Scope:

All requirements in this subsection relate to the above requirement class)

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Description: This class describes the extension to the OWS Context Core which supports Web Map Service (WMS) Service offerings. Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wms/GetCapabilities

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of only one GetCapabilities request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wms/GetMap

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of one and only one GetMap request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wms/content

Requirement Txt: Encodings of OWS Context for this extension will exclude the encoding of owc:content in an offering.

OGC 12-080r2 Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wms/styles

Requirement Txt:

Where additional styles are provided the client shall treat these as alternatives to any style specifically encoded in the GetMap call (e.g SLD reference). There is no specific requirement for the client to use these.

7.3.1 Summary of Valid Attributes

Attribute

Value

Constraint

operation

GetCapabilities

One (mandatory)

operation

GetMap

One (mandatory)

content

Zero (forbidden)

style

SLD or Txt

Zero or more (optional)

7.3.2 Supported Standards Within This Extension 1. WMS 1.3.0 2. WMS 1.1.1 3. SLD-WMS 1.1.0

Web Map Service (06-042) Web Map Service (01-068r3) Styled Layer Descriptor Profile (05-078r4)

7.4 owc:WFS Offering Extension This class describes the extension to the OWS Context Core which supports Web Feature Service (WFS) Service offerings. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/wfs

Scope:

All requirements in this subsection relate to the above requirement class)

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wfs/GetCapabilities

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of a one and only one GetCapabilities request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wfs/GetFeature

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of one and only one GetFeature request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wfs/content

Requirement Txt:

Encodings of OWS Context for this extension will exclude the encoding of owc:content in an offering.

OGC 12-080r2 7.4.1 Summary of Valid Attributes

Attribute

Value

Multiplicity

operation

GetCapabilities

One (mandatory)

operation

GetFeature

One (mandatory)

content

Zero (forbidden)

style

SLD or Txt

Zero or more (optional)

7.4.2 Supported Standards Within This Extension 4. WFS 2.0 5. WFS 1.1.0 6. WFS 1.0.0

Web Feature Service 2.0 (also ISO 19142) (09-025r1) Web Feature Service (04-094) Web Feature Service (02-058)

7.5 owc:WCS Offering Extenstion This class describes the extension to the OWS Context Core which supports Web Coverage Service (WCS) offerings. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/wcs

Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wcs/GetCapabilities

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of a one and only one GetCapabilities request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wcs/GetCoverage

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of one and only one GetCoverage request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wcs/content

Requirement Txt:

Encodings of OWS Context for this extension will exclude the encoding of owc:content in an offering.

7.5.1 Summary of Valid Attributes

OGC 12-080r2

Attribute

Value

Multiplicity

operation

GetCapabilities

One (mandatory)

operation

GetCoverage

One (mandatory)

content

Zero (forbidden)

style

SLD or Txt

Zero or more (optional)

7.5.2 Supported Standards Within This Extension 1. WCS 2.0 2. WCS 1.1.0 3. WCS 1.0

Web Coverage Standard 2.0 - Core (09-110r3) Web Coverage Service (WCS) (06-083r8) Web Coverage Service (WCS) (03-065r6)

7.6 owc:WPS Offering Extension This class describes the extension to the OWS Context Core which supports Web Processing Service (WPS) offerings. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/wps

Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wps/GetCapabilities

Requirement Txt:

Encoding of OWS Context for this extension will require the encoding of a one and only one GetCapabilities request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wps/Execute

Requirement Txt:

Encoding of OWS Context for this extension will require the encoding of one and only one Execute request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wps/content

Requirement Txt:

Encoding of OWS Context for this extension will exclude the encoding of owc:content in an offering.

7.6.1 Summary of Valid Attributes

Attribute

Value

Multiplicity

operation

GetCapabilities

One (mandatory)

operation

Execute

One (mandatory)

OGC 12-080r2

Attribute

Value

Multiplicity

content

Zero (forbidden)

style

SLD or Txt

Zero or more (optional)

7.6.2 Supported Standards Within This Extension 1. WPS 1.0.0

Web Processing Service (05-007r7)

7.7 owc:CSW Offering Extenstion This class describes the extension to the OWS Context Core which supports Catalogue Services (CSW) offerings. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/csw

Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/csw/GetCapabilities

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of a one and only one GetCapabilities request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/csw/GetRecords

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of one and only one GetRecords request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/csw/content

Requirement Txt:

Encodings of OWS Context for this extension will exclude the encoding of owc:content in an offering.

7.7.1 Summary of Valid Attributes Attribute

Value

Multiplicity

operation

GetCapabilities

One (mandatory)

operation

GetRecords

One (mandatory)

content

Zero (forbidden)

style

SLD or Txt

Zero or more (optional)

OGC 12-080r2 7.7.2 Supported Standards Within This Extension 1. CSW 2.0.2

Catalogue Service IS (07-006r1)

7.8 owc:WMTS Offering Extension This class describes the extension to the OWS Context Core which supports Web Map Tiling Service Extensions (WMTS) offerings. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/wmts

Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wmts/GetCapabilities

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of a one and only one GetCapabilities request in an offering.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wmts/GetTile

Requirement Txt:

Encodings of OWS Context for this extension will require the encoding of one or more GetTile requests in an offering to satisfy one information request.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/wmts/content

Requirement Txt:

Encodings of OWS Context for this extension will exclude the encoding of owc:content in an offering.

7.8.1 Summary of Valid Attributes

Attribute

Value

Multiplicity

operation

GetCapabilities

One (mandatory)

operation

GetTile

One (mandatory)

content

Zero (forbidden)

style

Txt

Zero or more (optional)

The WMTS requires multiple tiles to satisfy one viewing request. However the purpose of GetTile here is to pass relevant parameters which the client can use to prepare the specific tile requests (for example defining the layer(s) to access).

OGC 12-080r2 7.8.2 Supported Standards Within This Extension 1. WMTS 1.0.0

Web Map Tile Service (07-057r7)

7.9 owc:GML Offering Extension This class describes the extension to the OWS Context Core which supports inline or referenced GML offerings; this can include referencing local files or into databases. Requirement Class: http://www.opengis.net/spec/owc/1.0/req/gml Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/gml/content

Requirement Txt:

An encoding of this extension shall use the content element to capture the GML content. No operation elements should be present.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/gml/style

Requirement Txt:

An encoding of this content shall allow the encoding of associated style information, including specification of a default.

7.9.1 Summary of Valid Attributes

Attribute

Value

Multiplicity

operation

Zero (forbidden)

content

GML Content in-line or local

One (mandatory)

reference style

SLD or Txt

Zero or more (optional)

7.9.2 Supported Standards Within This Extension 1. 2. 3. 4. 5. 6.

GML 3.3 GML 3.2.1 GML 3.1.1 GML 3.0 GML 2.1.2 GML 2.1.1

Geography Markup Language (GML) (10-129r1) Geography Markup Language (GML) (07-036) Geography Markup Language (GML) (03-105r1) Geography Markup Language (GML) (02-023r4) Geography Markup Language (02-069) Geography Markup Language (02-009)

OGC 12-080r2 7.10 owc:KML Offering Extension This class describes the extension to the OWS Context Core which supports in-line or referenced KML offerings ; this can include referencing local files or into databases. Requirement Class: http://www.opengis.net/spec/owc/1.0/req/kml Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/kml/content

Requirement Txt:

An encoding of this extension shall use the content element to capture the KML content. No operation elements should be present.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/kml/style

Requirement Txt:

An encoding of this content shall not allow the encoding of associated style information as it is present within the KML Document body.

7.10.1 Summary of Valid Attributes Attribute

Value

Multiplicity

operation

Zero (forbidden)

content

KML Content in-line or local

One (mandatory)

reference style

Zero (forbidden)

7.10.2 Supported Standards Within This Extension 1. KML 2.2.0

OGC KML (07-147r2)

7.11 owc:GeoTIFF Offering Extension This class describes the extension to the OWS Context Core which supports in-line or referenced GeoTIFF offerings. ; this can include referencing local files or into databases. Requirement Class: http://www.opengis.net/spec/owc/1.0/req/geotiff Scope:

OGC 12-080r2 Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/geotiff/content

Requirement Txt:

An encoding of this extension shall use the content element to reference a GeoTIFF file. No operation elements should be present.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/GeoTIFF/style

Requirement Txt:

An encoding of this content shall not allow the encoding of associated style information, as none is required to visualize a GeoTIFF image.

7.11.1 Summary of Valid Attributes

Attribute

Value

Multiplicity

operation

Zero (forbidden)

content

Local reference to a GeoTIFF

One (mandatory)

File style

Zero (forbidden)

7.11.2 Supported Standards Within This Extension GeoTIFF Revision 1.0 ( www.pubdoc.org/fileformat/rasterimage/tiff/geotiff.pdf)

7.12 owc:GMLJP2 Offering Extension This class describes the extension to the OWS Context Core which supports in-line and referenced GMLJP2 offerings; this can include referencing local files or into databases. Requirement Class: http://www.opengis.net/spec/owc/1.0/req/gmljp2 Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/gmljp2/content

Requirement Txt:

An encoding of this extension shall use the content element to reference a GMLJP2 file. No operation elements should be present.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/GMLJP2/style

OGC 12-080r2 Requirement Txt:

An encoding of this content shall not allow the encoding of associated style information, as none is required to visualize a GMLJP2 image.

7.12.1 Summary of Valid Attributes Attribute

Value

Multiplicity

operation

Zero (forbidden)

content

Local reference to a GMLJP2

One (mandatory)

File style

Zero (forbidden)

7.12.2 Supported Standards Within This Extension 1. GMLJP2 1.0.0

GML in JPEG 2000 for Geographic Imagery (05-047r3)

7.13 owc:GMLCOV Offering Extension This class describes the extension to the OWS Context Core which supports in-line or referenced GMLCOV offerings. This can include references into databases. Requirement Class:

http://www.opengis.net/spec/owc/1.0/req/gmlcov

Scope:

All requirements in this subsection relate to the above requirement class

Dependencies:

http://www.opengis.net/spec/owc/1.0/req/core

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/gmlcov/content

Requirement Txt:

An encoding of this extension shall use the content element to contain or reference GML which will then reference coverage image files. No operation elements should be present.

Requirement ID:

http://www.opengis.net/spec/owc/1.0/req/GMLCOV/style

Requirement Txt:

An encoding of this content shall not allow the encoding of associated style information, as none is required to visualize a GMLCOV image.

OGC 12-080r2 7.13.1 Summary of Valid Attributes Attribute

Value

Multiplicity

operation

Zero (forbidden)

content

Inline content or Local

One (mandatory)

reference to a GML File style

Zero (forbidden)

7.13.2 Supported Standards Within This Extension TBD

OGC 12-080r2

Annex A: Conformance Class Abstract Test Suite (Normative) An OWS Context Encoding implementation shall satisfy the following characteristics to be conformant with this specification. A.1

Conformance Test Class: core

The OGC URI identifier of this conformance class is: http://www.opengis.net/spec/owc/1.0/conf/core. Tests identifiers below are shown in full but all relate to http://www.opengis.net/spec/owc/1.0/. Fully Implements the Context Class. Test id: http://www.opengis.net/spec/owc/1.0/conf/core/ContextClass Test Purpose: To test requirement http://www.opengis.net/spec/owc/1.0/req/core/ContextClass: Test Method: Review all rows of the owc: Context Class and confirm that an encoding rule is defined for each element in the encoding specification. Fully Implements the Resource Class Test id: http://www.opengis.net/spec/owc/1.0/conf/core/ResourceClass Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/ResourceClass Test Method: Review all rows of the owc: Resource Class and confirm that an encoding rule is defined for each element in the encoding specification. Fully Implements the Offering Class Test id: http://www.opengis.net/spec/owc/1.0/conf/core/OfferingClass

OGC 12-080r2 Test Purpose: To test requirement http://www.opengis.net/spec/owc/1.0/req/core/OfferingClass | Test Method: Review all rows of the owc:Offering Class and confirm that an encoding rule is defined for each element in the encoding specification. Fully Implements the Operation Class Test id: http://www.opengis.net/spec/owc/1.0/conf/core/OperationClass Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/OperationClass Test Method: Review all rows of the owc:Operation class and confirm that an encoding rule is defined for each element in the encoding specification. A.1.1

Fully Implements the Content Class

Test id: http://www.opengis.net/spec/owc/1.0/conf/core/ContentClass Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/ContentClass Test Method: Review all rows of the owc:Content class and confirm that an encoding rule is defined for each element in the encoding specification.

Fully Implements the StyleSet Classes Test id: http://www.opengis.net/spec/owc/1.0/conf/core/StyleSetClass Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/StyleSetClass Test Method: 26

OGC 12-080r2 Review all rows of the owc:StyleSet class and confirm that an encoding rule is defined for each element in the encoding specification. Fully Implements the Creator Class Test Id: http://www.opengis.net/spec/owc/1.0/conf/core/CreatorClass Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/CreatorClass Test Method: Review all rows of the owc: Creator Class and confirm that an encoding rule is defined for each element in the encoding specification. Fully Implements the CreatorApplication Class Test Id: http://www.opengis.net/spec/owc/1.0/conf/core/CreatorApplicationClass Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/ CreatorApplicationClass Test Method: Review all rows of the owc: CreatorApplication Class and confirm that an encoding rule is defined for each element in the encoding specification.

A.1.2

Fully Implements the CreatorDisplay Class

Test id: http://www.opengis.net/spec/owc/1.0/conf/core/CreatorDisplay Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/core/CreatorDisplay Test Method:

OGC 12-080r2 Review all rows of the owc:CreatorDisplay class and confirm that an encoding rule is defined for each element in the encoding specification.Conformance Test Class: WMS Extension Fully Implements the WMSOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/wmsOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/wmsOffering, Test Method: Review all rows of the WMSOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.2

Conformance Test Class: WFS Extension

Fully Implements the WFSOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/wfsOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/wfsOffering Test Method: Review all rows of the WFSService Class and confirm that an encoding rule is defined for each element in the encoding specification. A.3

Conformance Test Class: WCS Extension

Fully Implements the WCSOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/wcsOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/wcsOffering Test Method: 28

OGC 12-080r2 Review all rows of the WCSOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.4

Conformance Test Class: WPS Extension

Fully Implements the WPSOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/wpsOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/wpsOffering Test Method: Review all rows of the WPSOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.5

Conformance Test Class: CSW Extension

Fully Implements the CSWOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/cswOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/cswOffering Test Method: Review all rows of the CSWOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.6

Conformance Test Class: WMTS Extension

Fully Implements the WMTSOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/wmtsOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/wmtsOffering 29

OGC 12-080r2 Test Method: Review all rows of the WMTSOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.7

Conformance Test Class: GML Extension

Fully Implements the GMLOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/gmlOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/gmlOffering Test Method: Review all rows of the GMLOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.8

Conformance Test Class: KML Extension

Fully Implements the KMLOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/kmlOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/kmlOffering Test Method: Review all rows of the KML Offering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.9

Conformance Test Class: GeoTIFF Extension

Fully Implements the GeoTIFFOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/geotiffOffering Test Purpose: 30

OGC 12-080r2 To test requirement: http://www.opengis.net/spec/owc/1.0/req/geotiffOffering Test Method: Review all rows of the GeoTIFFOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.10 Conformance Test Class: GMLJP2 Extension

Fully Implements the GMLJP2Offering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/gmljp2Offering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/gmljp2Offering Test Method: Review all rows of the GMLOffering Class and confirm that an encoding rule is defined for each element in the encoding specification. A.11 Conformance Test Class: GMLCOV Extension

Fully Implements the GMLCOVOffering Class. Test Id: http://www.opengis.net/spec/owc/1.0/conf/gmlcovOffering Test Purpose: To test requirement: http://www.opengis.net/spec/owc/1.0/req/gmlcovOffering Test Method: Review all rows of the GMLCOVOffering Class and confirm that an encoding rule is defined for each element in the encoding specification.

OGC 12-080r2

Annex B: Revision history

Date

Release

3rd October Draft 10 2012 28th Draft 13 December 2012 31st May Draft 14 2013 4th June Draft 15 2013 30th June Draft 16 2013 31st August Draft 17 2013

Author(s)

Paragraph modified

Description

Roger Brackin, Initial Document Release Approved Draft Release for use in Pedro Gonçalves outside of SWG OWS-9 Roger Brackin, Document Release for Approved for release under TC 3 Pedro Gonçalves TC/OpenGeo week rule /OAB/Open Geo Roger Brackin, Figure 3, Table 2, Table UML Model corrections, various Pedro Gonçalves 3, Section 7.8.1 minor table corrections, WMTS Operation Multiplicity. Roger Brackin, Figure 2, Table 2,4,5 UML and Table corrections noted by Joan Maso Roger Brackin, Section 7.2.4 Remove comment accidently left in D15 Roger Brackin, Section A11 removed Erroneous Conformance test.

OGC 12-080r2

Annex C: Bibliography

1. [ISO19115:2003] -

Metadata Standard for Geographic Information.

2. [OGC 05-005] -

Web Map Context Documents Implementation Specification

3. [OGC 08-131r3] -

The Specification Model — A Standard for Modular specifications

4. [OGC 10-035r1] -

OWS Context Engineering Report

OGC OWS Context Conceptual Model (version 1.0) — OGC 12-080r2

Related documents