Note
Preface

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

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

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

Abstract

<Insert Abstract Text here>

Scope

Note

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

Conformance

This standard defines XXXX.

Requirements for N standardization target types are considered:

  • AAAA

  • BBBB

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

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

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

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

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

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.

Note

Insert References here. If there are no references, leave this section empty.

References are to follow the Springer LNCS style, with the exception that optional information may be appended to references: DOIs are added after the date and web resource references may include an access date at the end of the reference in parentheses. See examples from Springer and OGC below.

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

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

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

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

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

  • [NCBI], National Center for Biotechnology Information, http://www.ncbi.nlm.nih.gov

  • [ISO 19101-1:2014], Geographic information — Reference model — Part 1: Fundamentals

  • [ISO 19115-1:2014], Geographic information — Metadata — Part 1: Fundamentals

  • [ISO 19157:2013], Geographic information — Data quality

  • [ISO 19139:2007], Geographic information — Metadata — XML schema implementation

  • [ISO 19115-3], Geographic information — Metadata — Part 3: XML schemas (2016)

  • [OGC 15-097], OGC Geospatial User Feedback Standard: Conceptual Model (2016)

  • [OGC 12-019], OGC City Geography Markup Language (CityGML) Encoding Standard (2012)

  • [OGC 14-005r3], OGC IndoorGML (2014)

  • [OGC 06-121r9], OGC Web Service Common Implementation Specification, April 7, 2010. http://portal.opengeospatial.org/files/?artifact_id=38867

Terms and definitions

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

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

example term

term used for exemplary purposes

[ISO 19101-1:2014]

Note
 An example note.
Here’s an example of an example term.

Conventions

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

Identifiers

The normative provisions in this standard are denoted by the URI

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

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

Clauses not Containing Normative Material

Paragraph

Clauses not containing normative material sub-clause 1

Paragraph

Clauses not containing normative material sub-clause 2

Clause containing normative material

Paragraph

Requirement Class A or Requirement A Example

Paragraph – intro text for the requirement class.

Use the following table for Requirements Classes.

Requirements Class

requirement description

requirement description

requirement description

Requirement 1

Paragraph - intro text for the requirement.

Use the following table for Requirements, number sequentially.

Requirement 'shall' statement

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

Names Definition Data types and values Multiplicity and use

name 1

definition of name 1

float

One or more (mandatory)

name 2

definition of name 2

character string type, not empty

Zero or one (optional)

name 3

definition of name 3

GML:: Point PropertyType

One (mandatory)

Media Types for any data encoding(s)

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

Appendix A: Conformance Class Abstract Test Suite (Normative)

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

Conformance Class A

Requirement 1

Test purpose

Verify that…​

Test method

Inspect…​

Requirement 2

Appendix B: Title

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

Appendix C: Revision History

Date Release Editor Primary clauses modified Description

2021-05-17

0.1

Matthew Purss

all

initial version

Bibliography

Note
Example Bibliography (Delete this note).

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

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

  • For citations in the text please use square brackets and consecutive numbers: [1], [2], [3]

– Actual References:

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

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

  • [OGCTB12], OGC: OGC Testbed 12 Annex B: Architecture (2015).