Introduction System context Structure and format

11.5 Structure and format

11.5.1 Introduction

All application profiles shall be structured as shown in Table 71. This organization complies with clause 12.3 of ISO 19106 Geographic information – Profiles. A profile may introduce additional subclauses as required. Table 70 — Structure of an application profile Clause Title Preface Submitting organizations Revision history Changes to the OpenGIS Catalogue Services Specification Future work Forward front matter Introduction 1 Scope 2 Conformance 3 Normative references 4 Terms and definitions 5 Symbols and abbreviations 6 System context 6.1 Application domain 6.2 Essential use cases 7 Information models 7.1 Capability classes 7.2 Catalogue information model 7.3 Supported data bindings 7.4 Service information model 7.5 Native language support 8 External interfaces 8.1 Imported protocol bindings 8.2 Interface A 8.3 Interface B . . . 8.i Query facilities 8.j General implementation guidance 8.k Security considerations Annex A Abstract test suite normative Annex B Design rationale informative Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 181 Clauses 6 through 8 convey the particulars of the application profile in terms of three ‘views’ these correspond to the following standard ODP viewpoints: Enterprise, Information, and Computational. The three views describe various aspects of the catalogue service with respect to the base specifications; taken together they constitute the basic application architecture. The essential content of these views is summarized in the following subclauses; additional guidance can be found in the annotated profile template OGC Document 03-101.

11.5.2 System context

This view focuses on the purpose, scope, and policies of the catalogue service i.e., what is the system used for. It documents special requirements 10 and describes the context of use as suggested in Table 71. Table 71 — System context: required subclauses Subclause Topical content Application domain The subject domain being addressed—identify whether this profile has a specific disciplinary focus e.g. oceanography, or is of interest to a broader community e.g. research, public access, or libraries The prospective stakeholders or community of practice Essential use cases What the system should be able to do, what it will be used for, who will use it Typical scenarios that encompass a series of interactions between users and the catalogue system being described in order to fulfill the needs of stakeholders. The inclusion of narrative use cases with accompanying interaction andor sequence diagrams is recommended

11.5.3 Information models