CSW FGDC Application Profile
Open Geospatial Consortium Inc.
Date: 18 October 2006
Reference number of this OpenGIS® project document: OGC 06-129r1
Version: 0.0.12
Category: OpenGIS® Catalogue Service Application Profile
Editors: Patrick Neal, John Davidson, Bruce Westcott

OpenGIS® Catalogue Service Implementation Specification
2.0.1 -

FGDC CSDGM Application Profile for CSW 2.0
Copyright notice
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/.

Warning
This proposed document is not yet an OGC Standard. It is distributed for review
and comment. It is subject to change without notice and may not be referred to as
an OGC Standard.

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

Candidate Specification
Best Practices Document
Candidate Specification
English1

CSW FGDC Application Profile

Table of Contents
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

1.

SCOPE.................................................................................................................................................. 92.

CONFORMANCE............................................................................................................................... 9

3.

NORMATIVE REFERENCES .......................................................................................................... 9

4.

TERMS AND DEFINITIONS .......................................................................................................... 115.

SYMBOLS AND ABBREVIATIONS.............................................................................................. 13

6

SYSTEM CONTEXT ........................................................................................................................ 14
6.1
APPLICATION DOMAIN ................................................................................................................. 15
6.2
ESSENTIAL USE CASES.................................................................................................................. 15
6.2.1 Publish metadata .................................................................................................................... 16
6.2.2 Discover metadata.................................................................................................................. 17
6.2.3 Harvest metadata.................................................................................................................... 17

7

INFORMATION MODELS ............................................................................................................. 19
7.1
CAPABILITY CLASSES................................................................................................................... 19
7.1.1 CSW extensions....................................................................................................................... 19
7.1.1.1

7.1.2

Unique Identifier ........................................................................................................................... 19

Mappings to the common XML Record format....................................................................... 20

7.1.2.1
7.1.2.2
7.1.2.3

OGC Core Queryable Properties................................................................................................... 20
OGC Core Returnable Properties .................................................................................................. 22
Compound Properties.................................................................................................................... 25

7.1.3 Additional Properties ............................................................................................................. 26
7.2
RESULT SETS ................................................................................................................................ 26
7.2.1
7.2.2
7.2.3

8

BRIEF Result Set............................................................................................................................... 28
SUMMARY Result Set...................................................................................................................... 28
FULL Result Set ................................................................................................................................ 28

EXTERNAL INTERFACES ............................................................................................................ 28
8.1
IMPORTED PROTOCOL BINDING (RELATIONSHIP TO THE COMMON MODEL) .................................. 28
8.2
INTERFACE SPECIFICATIONS......................................................................................................... 29
8.2.1 OGC_Service Interface........................................................................................................... 30
8.2.1.1

8.2.2

8.2.2.1
8.2.2.2
8.2.2.3
8.2.2.4

8.2.3

GetCapabilities Operation ............................................................................................................. 30

CSW Discovery Interface........................................................................................................ 31
GetRecords Operation................................................................................................................... 31
GetRecordById Operation............................................................................................................. 34
DescribeRecord Operation ............................................................................................................ 36
GetDomain Operation ................................................................................................................... 38

CSWT Manager Interface ....................................................................................................... 40

8.2.3.1
8.2.3.2

Harvest Operation ......................................................................................................................... 40
Transaction Operation................................................................................................................... 42

8.2.4 Record locking........................................................................................................................ 48
8.2.5 Error handling........................................................................................................................ 48
8.3
QUERY FACILITIES ....................................................................................................................... 48
8.4
SECURITY CONSIDERATIONS ........................................................................................................ 49
APPENDIX A -- ABSTRACT TEST SUITEAPPENDIX B – DESIGN RATIONALE
APPENDIX C -- FEMA MAPMOD CATALOG IMPLEMENTATION NOTESAPPENDIX D -- SCHEMAS AND SAMPLE XML FILES

2CSW FGDC Application Profile
1

Figures2

Figure 1: OGC Catalogue Service 2.0 .............................................................................. 14

3

Figure 2: Overall system use cases ................................................................................... 15

4

Figure 3: Publish metadata................................................................................................ 16

5

Figure 4: Discover metadata ............................................................................................. 17

6

Figure 5: Harvest metadata ............................................................................................... 177
8

Tables9

Table 1 - Operations provided by CSW capability classes............................................... 19

10

Table 2 - OGC Core Queryable Properties ....................................................................... 20

11

Table 3 – FGDC Queryable Properties............................................................................. 21

12

Table 4 – OGC Core Returnable Properties ..................................................................... 23

13

Table 5 - FGDC Returnable Properties............................................................................. 23

14

Table 6 – Mapping of Compound Properties.................................................................... 25

15

Table 7 - Additional Queryable/Returnable Properties .................................................... 26

16

Table 8 – Result Sets Supported by Schemas................................................................... 27

17

Table 9 - Result Set Properties.......................................................................................... 27

18

Table 10 - Mapping CSW operations to CSW(T) FGDC operations ............................... 28

19

Table 11 - Operation request encoding............................................................................. 29

20

Table 12 - Parameters in GetCapabilities operation request............................................. 30

21

Table 13 - Parameters in GetRecords operation request................................................... 32

22

Table 14 - Parameters in GetRecordById operation request ............................................ 35

23

Table 15 - Parameters in DescribeRecord operation request............................................ 37

24

Table 16 - Parameters in GetDomain operation request................................................... 38

25

Table 17 - Parameters in Harvest operation request ......................................................... 41

26

Table 18 - Parameters in Transaction operation request................................................... 43

27

Table 19 - Parameters of Insert Operation........................................................................ 43

28

Table 20 - Parameters of Update Operation ..................................................................... 44

29

Table 21 - Parameters of Delete Operation....................................................................... 45

30

Table 22 – OWS Common Exceptions............................................................................. 48

31
3

CSW FGDC Application Profile
1

Listings

2

Listing 1 – GetCapabilities Request in XML ................................................................... 30

3

Listing 2 - GetCapabilities Response................................................................................ 31

4

Listing 3 – GetRecords Request in XML ......................................................................... 33

5

Listing 4 – GetRecords Response in XML ....................................................................... 34

6

Listing 5 – GetRecordById Request in XML ................................................................... 35

7

Listing 6 – GetRecordById Response............................................................................... 35

8

Listing 7 – DescribeRecord Request in XML................................................................... 37

9

Listing 8 – DescribeRecord Response .............................................................................. 37

10

Listing 9 - GetDomain Request in XML .......................................................................... 39

11

Listing 10 – GetDomain Response ................................................................................... 39

12

Listing 11 - Harvest Request............................................................................................. 41

13

Listing 12 – Harvest Response ......................................................................................... 42

14

Listing 13 - Transaction Request ...................................................................................... 46

15

Listing 14 – Transaction Response ................................................................................... 47

164

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1i. Preface

2
3
4
5

This document explains how Catalogue Services based on the FGDC Content Standard
for Digital Geospatial Metadata (CSDGM) Application Profile for the OpenGIS®
Catalogue Service Implementation Specification v2.0.1 are organised and implemented
for the discovery, retrieval and management of data metadata

6
7
8

Suggested additions, changes, and comments on this draft report are welcome andencouraged. Such suggestions may be submitted by OGC portal message, email message,or by making suggested changes in an edited copy of this document.

9
10
11

Development of this draft specification was supported by the U.S. Federal Emergency
Management Agency (FEMA) under its Map Modernization (MapMod) program(http://hazards.fema.gov ).

12ii. Submitting Organizations

13
14
15
16
17
18
19
20

The following organizations submitted this document to the Open Geospatial
Consortium, Inc.
1. Image Matters LLC
2. Michael Baker Corporation
3. Federal Emergency Management Agency (US)
4. GeoConnections Canada
5. Environmental Systems Research Institute, Inc.
6. Intergraph Corporation

21

iii. Document contributor contact points

22

All questions regarding this document should be directed to the editor or the contributors:
Contact
CompanyJohn
Image Matters,
Davidson
LLC.
Patrick Neal Image Matters,
LLC.
Bruce
IntergraphWestcottCorporation

Emailjohnd@imagem.cc
patrickn@imagem.cc
Bwestcot@ingr.com

5OGC 06-129r1
1

CSW 2.0 FGDC CSDGM Application Profile

iv. Revision history
Date

Internal
version

EditorPrimary
clausesmodified
N/A

Initial version

N/A
6.3.1.1

Updated

07Sep2004

0.0.5

27Sep2005
06Dec2005
May2006

0.0.6
0.0.7
0.0.8

July2006

0.0.9

Neal,
Davidson
Neal
Neal
Neal,
WestcottWestcottAugust 2006

0.0.10Westcott

September
2006

0.0.11

Westcott

Description

Format and editorial changes
overall
Verification of OGC template
structure; Incorporation ofcontributors’ comments
Globally standardized “catalogue”
spelling and name of OGC
specification, as per OGC website.
Incorporated various comments &suggestions of reviewers
Final edits, prior to initial OGC
review

2
3

v. Changes to the OpenGIS® Catalogue Service Implementation
Specification

4
5
6

According to the application profile the OpenGIS® Abstract Specification requires nofurther changes that go beyond the required changes stated in OpenGIS® Catalogue
Service Implementation Specification v2.0.1.

7vi. Future work

8
9
10
11

Future work may include the extension of the profile to interoperate with UDDI service
registry instances. In addition, this profile specification will be adapted to conform to the
ISO 19139 technical specification and XML schema (ISO/TS 19139:2006 Geographic
information - Metadata - XML schema implementation

12

6

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

Foreword

2
3
4

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 Inc. shall not be held
responsible for identifying any or all such patent rights.

56This document, through its implementation profile, references several external standards
and specifications as dependencies:781) Unified Modeling Language (UML) Version 1.3, The Object Management Group(OMG): http://www.omg.org/cgi-bin/doc?formal/00-03-01

9102) The Extensible Markup Language (XML), World Wide Web Consortium,
http://www.w3.org/TR/1998/REC-xml-19980210

11
12
13

Appendix A, the Abstract Conformance Test Suite and Appendix D, Schemas andSample XML Files, are normative to this specification and shall be implemented when acomputing environment requires catalogue services.

14
15
16

Appendix B, Design rationale and Appendix C, FEMA MapMod Catalog Implementation
Notes are informative and provide background information, such as terminology andalternative implementation approaches.

17
18
19
20
21

This document contains references to the Z39.50 Application Profile for Geospatial
Metadata (a.k.a. the “GEO profile). Z39.50 is an internet transport protocol, and the“GEO profile” an implementation designed for use with that protocol, that were central tothe deprecated versions 1.x of the OGC Catalogue Specification. These references are
merely informative, intended to provide context with legacy Catalogue implementations.

7OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

Introduction

2
3
4
5
6
7
8
9

With the abundance of geospatial resources available today, technologies such as
catalogue services, are necessary to facilitate data discovery, retrieval, and maintenance.
Because of standardized interface specifications, clients of different origins and withpotentially different focuses can access this technology and the geospatial metadata towhich it provides potential access. Since these interfaces are standardized, a major rolein the development of catalogue 1 services is left to developers, defining information
models which can be utilized by these interfaces and yet remain independent of theunderlying metadata.

10
11

Several different organizations have provided insight into these kinds of information
models. They have produced such work as:

12
13

•

the Geodata Infrastructure North-Rhine Westphalia (GDI NRW) -- which is the basis
for the current Catalogue 2.0.1 Implementation Specification), and14•

several profiles of CSW 2.0.1 for ISO19115/ISO19119 and ebRIM

15
16
17
18
19
20
21

This profile defines an application profile for valid FGDC Content Standard for Digital
Geospatial Metadata (CSDGM) metadata documents as per the FGDC specification 2.
This profile, called FGDC CSDGM Catalogue or CSDGM Catalogue, is based on therequirements of the CSW 2.0.1 specification, and provides extensions to this base in
several areas. As stated in CSW 2.0.1 (with Corrigendum), a base profile that provides abasic set of information objects must be supported by each catalogue instance; in
addition, application profiles for different information communities should be specified.

22

1

The spelling variants “catalog” and “catalogue” have each been used by OGC and other standards
organizations. Because the current OGC specification document uses the “catalogue” variant, it has been
adopted for use in this document. Exceptions are made when referencing specific documents, websites, etc.
that use “catalog.”
2

Federal Geographic Data Committee. FGDC-STD-001-1998. Content standard for digital geospatial
metadata (revised June 1998) -- http://www.fgdc.gov/standards/projects/FGDC-standardsprojects/metadata/base-metadata/index_html

8OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

OpenGIS® Catalogue Services – FGDC CSDGM Application Profile for2

CSW 2.0

3

1.

4
5
6
7
8

This application profile document specifies the interfaces, bindings, and encodings
required to publish and access digital catalogs of metadata for geospatial data that comply
with the given profile. Metadata acts as generalized properties which can be queried andreturned through catalogue services for resource evaluation, and in many cases invocation
or retrieval of the referenced resource.

9
10
11
12
13
14

This document applies only to implementations of CSW supporting the FGDC Content
Standard for Digital Geospatial Metadata (CSDGM) information model and schema.
Implementations of CSW per this application profile are intended for purposes ofpublishing, inventory, discovery, and access of dataset and dataset collection resources.
Implementations conforming to this profile are not intended for similar purposes relative
to geospatial services and applications.

15

2.

16
17

Abstract conformance to the mandatory catalogue service interfaces is described inAppendix A. Test data and queries are not included in this profile.

18

3.

19
20
21
22
23

The following normative documents contain provisions that, through reference in thistext, constitute provisions of this part of OGC 04-021r3. 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.
IETF RFC 2141 (May 1997), URN Syntax, R. Moats http://www.ietf.org/rfc/rfc2141.txt

24
25

IETF RFC 2396 (August 1998), Uniform Resource Identifiers (URI): Generic Syntax,
Berners-Lee, T., Fielding, N., and Masinter, L., eds., http://www.ietf.org/rfc/rfc2396.txt

26
27
28

IETF RFC 2616 (June 1999), Hypertext Transfer Protocol – HTTP/1.1, Gettys, J.,
Mogul, J., Frystyk, H., Masinter, L., Leach, P., and Berners-Lee, T., eds.,
http://www.ietf.org/rfc/rfc2616.txt

29
30

IANA, Internet Assigned Numbers Authority, MIME Media Types, available at
http://www.iana.org/assignments/media-types/

31
32
33
34
35

ISO/IEC TR 10000-1:1998. Information Technology – Framework and taxonomy ofInternational Standardised Profiles – Part 1: General principles and documentation
framework. Technical Report, JTC 1. Fourth edition. Available [online]:
http://www.iso.ch/iso/en/ittf/ PubliclyAvailableStandards/c030726_ISO_IEC_TR_100001_1998(E).zip.

Scope

Conformance

Normative references

9OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3
4
5

ISO/IEC 10746-2:1996. Information Technology – Open Distributed Processing –Reference Model: Foundations. Common text with ITU-T Recommendation X.902.
Available [online]:
http://www.iso.ch/iso/en/ittf/PubliclyAvailableStandards/s018836_ISO_IEC_107462_
1996(E).zip.

6

ISO 19106:2003, Geographic Information – Profiles

7

ISO 19115:2003, Geographic Information – Metadata8

ISO 19139, Geographic information - Metadata - Implementation specification

9

OGC 99-113, OGC Abstract Specification Topic 13: Catalog Services

10

OGC 02-006, OGC Abstract Specification Topic 12: OpenGIS Service Architecture11

OGC 02-059, Filter Encoding Implementation Specification

12

OGC 04-016r2, OWS Common Implementation Specification, January 2004

13
14

OGC 04-038r4, ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP
ISO19115/19)

15
16

OGC 05-057r4, OpenGIS® Catalogue Services - Best Practices for Earth Observation
Products (0.3) BP

17

OGC 05-025r3, OGC™ Catalogue Services — ebRIM (ISO/TS 15000-3) profile of CSW

18
19

OMG UML, Unified Modeling Language, Version 1.3, The Object Management Group(OMG): http://www.omg.org/cgi-bin/doc?formal/00-03-01

20
21

W3C Recommendation January 1999, Namespaces In XML,
http://www.w3.org/TR/2000/REC-xml-names

22
23

W3C Recommendation 6 October 2000, Extensible Markup Language (XML) 1.0 (Second
Edition), http://www.w3.org/TR/REC-xml

24
25

W3C Recommendation 2 May 2001: XML Schema Part 0: Primer,
http://www.w3.org/TR/2001/REC-xmlschema-0-20010502/

26
27

W3C Recommendation 2 May 2001: XML Schema Part 1: Structures,
http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/

28
29

W3C Recommendation 2 May 2001: XML Schema Part 2: Datatypes,
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/

30
31

WSDL, Web Services Description Language (WSDL) 1.1. Available [online]:
http://www.w3.org/TR/wsdl

32

Z39.50 Maintenance Agency, http://www.loc.gov/z3950/agency/

33
34

Z39.50 Application Profile for Geospatial Metadata or "GEO",
http://www.blueangeltech.com/Standards/GeoProfile/geo22.htm

35
36

In addition to this document, this specification includes several normative XML Schema
files. These are posted online at the URL http://schemas.opengis.net/. These XML
10

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3

Schema files are also bundled with this document. In the event of a discrepancy between
the bundled and online versions of the XML Schema files, the online files shall beconsidered authoritative.

4

4.

5
6
7
8
9
10

For the purposes of this document, the following terms and definitions apply:
4.1
application profile
Set of one or more base standards and - where applicable - the identification of chosenclauses, classes, subsets, options and parameters of those base standards that arenecessary for accomplishing a particular function [ISO 19101, ISO 19106]

11
12
13

4.2
clientSoftware component that can invoke an operation from a server

14
15
16
17

4.3
data level
Stratum within a set of layered levels in which data is recorded that conforms todefinitions of types found at the application model level [ISO 19101]

18
19
20
21

4.4
dataset series
Collection of datasets sharing the same product specification [ISO 19113, ISO 19114,
ISO 19115]

22
23
24

4.5
geographic dataset
Dataset with a spatial aspect [ISO 19115]

25
26
27
28

4.6
geographic information
Information concerning phenomena implicitly or explicitly associated with a location
relative to the Earth [ISO 19128:2005]

29
30
31
32

4.7
georesource
Geographic information of a specific type (e.g. geographic dataset, geographic
application, geographic service)

33
34
35
36

4.8
identifier
Character string that may be composed of numbers and characters that is exchanged
between the client and the server with respect to a specific identity of a resource

37
38
39

4.9
interface
Named set of operations that characterize the behavior of an entity [ISO 19119]

Terms and definitions

11

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3

4.10
metadata dataset (metadata set)
Metadata describing a specific dataset [ISO 19101]

4
5
6
7

4.11
metadata entity
Group of metadata elements and other metadata entities describing the same aspect of
data

8
9
10

4.12
metadata schema
Conceptual schema describing metadata

11

NOTE

12
13
14
15

4.13
metadata section
Subset of metadata that defines a collection of related metadata entities and elements[ISO 19115]

16
17
18
19

4.14
operation
Specification of a transformation or query that an object may be called to execute [ISO19119]

20
21
22

4.15
parameter
Variable whose name and value are included in an operation request or response

23
24
25

4.16
qualified nameName that is prefixed with its naming context

26
27
28

4.17
requestInvocation of an operation by a client

29
30
31

4.18
response
Result of an operation, returned from a server to a client

32
33
34

4.19
schemaFormal description of a model [ISO 19101, ISO 19103, ISO 19109, ISO 19118]

35
36
37
38

4.20
serverservice instance
A particular instance of a service [ISO 19119 edited]

ISO 19115 describes a standard for a metadata schema. [ISO 19101]

12OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3
4

4.21
service
Distinct part of the functionality that is provided by an entity through interfaces [ISO19119]

5
6
7
8

4.22
service interface
Shared boundary between an automated system or human being and another automatedsystem or human being [ISO 19101]

9
10
11
12

4.23
service metadata
Metadata describing the operations and geographic information available at a server[ISO 19128:2005]

13
14
15

4.24
state
Condition that persists for a period

16
17
18

4.25
transfer protocol
Common set of rules for defining interactions between distributed systems [ISO 19118]

19
20
21
22

4.26
versionVersion of an Implementation Specification (document) and XML Schemas to which therequested operation conforms

23
24

5.
Symbols and abbreviations
Some frequently used abbreviated terms:

25

API

26

COTS Commercial Off The Shelf

27

CQL

Common Query Language

28

CRS

Coordinate Reference System

29

CSW Catalogue Service for the Web

30

DCE

Distributed Computing Environment

31

DC

Dublin Core

32

DCMI Dublin Core Metadata Initiative

33

DCP

34

FGDC Federal Geographic Data Committee

35

GML Geospatial Markup Language

Application Program Interface

Distributed Computing Platform

13

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

HTTP HyperText Transport Protocol

2

ISO

3

OGC OpenGIS Consortium

4

SQL

Structured Query Language

5

UID

Unique Identifier

6

UUID Universal Unique Identifier

7

UML Unified Modeling Language

8

URI

Uniform Resource Identifier

9

URL

Uniform Resource Locator

10

URN Uniform Resource Name

11

UTF-8 Unicode Transformation Format-8

12

WSDL Web Service Definition Language

13

W3C World Wide Web Consortium

14

XML eXtensible Markup Language

15

6

16
17
18

This section focuses on the purpose, scope and policies of catalogue services that comply
with the given profile. It documents special requirements and describes the context ofuse.

International Organization for Standardization

System context

19
20
21
22
23
24
25
26
27
28

Figure 1: OGC Catalogue Service 2.0

14OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Application domain 3

1

6.1

2
3
4
5
6

This profile defines a catalogue implementation which allows for the discovery, retrieval,and modification of geospatial metadata. It is not intended to be all-encompassing or
general purpose in scope. The catalogue information model used by this profile is basedon FGDC CSDGM specification, and is specifically designed to operate with FGDCbased geospatial metadata.

7
8
9
10

This application profile has no specific disciplinary focus. All communities working withthese sorts of geospatial information are addressed. Typical communities are surveying,environment, geology, landscaping, water management, power industry,
telecommunications etc.

11
12
13
14

The intention is to implement a generally understood information model based onstandard metadata with only a few relationships among the catalogue items. Usage should
be as simple as possible, implementing a set of use cases typical in the geospatial
community.

15
16
17

The requirements of the information model, search properties, details of the results sets
and interfaces were defined in close cooperation with users in various communities aswell as software vendors.

18

6.2

19
20
21
22

This section describes essential use cases for the purpose of demonstrating typicalinteractions between users, as well as a catalogue service that supports the specified
application profile. Figure 2 shows the overall system that contains major interactions
between the actors.

Essential use cases

Publ isher

PublishHarvestBrokerRequestor

23
24

Discover

CatalogueService

Figure 2: Overall system use cases
3

The discussion in this section is largely drawn from OGC 04-038r4, ISO19115/ISO19119 Application
Profile for CSW 2.0; contributors to the FGDC CSDGM profile offer their thanks to the developers of that
document.

15

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2

An actor is a person, organisation, or external system that plays a role in one or moreinteractions with the system. Four actors are identified:3
4
5

Publisher: A publisher publishes metadata descriptions to a catalogue. By doing so, heenables the discovery of that description record by a requestor entity. This actor is also
the owner of the geo-resource that he describes.

6
7

Broker: This actor is a specialised publisher that publishes and maintains metadata
records on behalf of the owner of georesources.

8
9Requestor: This actor searches for metadata records in a catalogue service, either bybrowsing or through more complicated queries.

10
11
12

Catalogue Service: This is a system that handles the discovery and publishing of
metadata entries. Furthermore, this actor has the ability to harvest metadata records fromother catalogue services.

13

The following sections describe the use cases in more detail.

14
15

6.2.1

Publish metadata

Descri be geo-resource

Publisher

CatalogueService

Publ ishBroker16
17

Figure 3: Publish metadata

18
19
20
21
22

Description: A publisher describes geo-resources by applying ISO19139 [ISO19139] as
specified by this document. A geo-resource might be a service, a geodataset (single orcollection) or an application. The publisher owns the georesource. As an alternative, thepublisher might be a broker that does not own the geo-resource, but describes andpublishes metadata descriptions to a catalogue service on behalf of a publisher.

23
24

Pre-conditions: The publisher knows the URL of the catalogue service has knowledge
about the transaction interface and has the right to access the catalogue service.
16

OGC 06-129r1
1
2

CSW 2.0 FGDC CSDGM Application Profile

Post-conditions: The metadata record is either successfully published to the catalogue
service or publishing fails due to a non-valid metadata description.

3
4

6.2.2

Discover metadata

Discover

Requestor

5
6

CatalogueService

Figure 4: Discover metadata

7
8
9
10

Description: A requestor discovers metadata entries in a catalogue service either bybrowsing the content of the catalogue or by placing certain query terms. If a service isdiscovered that fits his search terms, he can bind to this service in accordance with theinformation in the result sets of the catalogue service.

11

Pre-conditions: The requestor knows the location of the catalogue service.

12
13

Post-Condition: The requestor receives a valid catalogue response (due to a valid
request) with a result set that contains all the information that fits the requestor’s query.

14
15

6.2.3

Harvest metadata

CatalogueService

HarvestXML resource

16
17

Figure 5: Harvest metadata

18
19
20
21
22

Description: A catalogue service may harvest metadata records from a given XML
resource, i.e. a metadata description that complies with XML schemas provided by thisspecification. This could be a metadata description of services or geodata or, additionallyin case of services, a capabilities document of an OGC service that complies with OGC
Common Implementation Specification.

23
24

Pre-conditions: The resource is a valid XML document that complies with the schemas
given by this profile 4. The XML resource must be accessible over a network.

4

or is a capabilities document which must a priori be translated into the schema given by this profile.

17

OGC 06-129r1
1
2

CSW 2.0 FGDC CSDGM Application Profile

Post-Condition: The XML resource is inserted into the catalogue storage and is available
immediately in case of an adequate query.

3
4

18

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

7

Information models

234This profile is based on the FGDC CSDGM metadata specification and extends this byadding several additional properties which relate the FGDC CSDGM metadata to the
CSW Core requirements information model.

5

7.1

6
7
8

This section defines the capability classes of the catalogue service. The application
profile distinguishes several capability classes based on the general catalogue information
model.

910
11
12

Since both the OGC_Service and the Discovery functions must be provided by all
conforming implementations, they are a mandatory part of the capability class (CSWCatalog). A 'read-only' catalogue service has to provide operations labeled 'CSW'. In
addition, a transactional catalogue service has to provide operations labeled 'CSWT'.

13
14
15

The additional Manager functions, which provide a standardized interface for the active
management (push-model) or the passive harvesting (pull-model) of metadata, are an
optional part of the profile (CSWT Catalog).

Capability classes

Table 1 - Operations provided by CSW capability classes
Capability class label
CSW

Operations provided
OGC_Service.GetCapabilities
CSW_Discovery.DescribeRecord
CSW_Discovery.GetRecords
CSW_Discovery.GetDomain
CSW_Discovery.GetRecordById

CSWT

As above, plus:
CSW_Manager.Transaction
CSW_Manager.Harvest

16
17

7.1.1

CSW extensions

18
19

This profile requires extensions to the referenced OGC and FGDC specifications. These
extensions and recommendations are described in the following paragraphs.

20

7.1.1.1 Unique Identifier

21
22

UIDs are required to reference metadata records in the repository. Because the FGDCCSDGM metadata schema defines no unique identifier for a given instance, a separate

19

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3
4
5
6

field is needed to represent the UID of each instance record. For this implementation, theinformation model uses fgdc:recordID as the unique identifier for a given metadata
entity. This property must be associated with the database primary key field external to
the XML metadata. UUIDs are recommended to ensure the uniqueness of each identifier.
This profile, however, is satisfied with the use of UIDs to identify metadata records, as
the probability of a non-unique identifier is extremely remote.

7

7.1.1.1.1 GOS2

8
9
10
11
12

In conformance with the GOS2 specifications(http://www.geodata.gov/gos/metadata/CreatePublishMetadata.pdf ), this profile supports
the optional catid attribute assigned to full metadata records returned from CSW. This
attribute is assigned to the Title element of the xml-encoded metadata using the unique
identifier referenced above.

13

7.1.2

14

7.1.2.1 OGC Core Queryable Properties

15
16
17
18

CSDGM Catalogue uses queryable properties to formulate constraint expressions which
can be used to refine searches for metadata information. The core queryables as definedin the OGC catalogue specification and their mappings to this profile are defined in thefollowing table.

19
20
21

The queryable properties listed in Tables 2 and 3 should be encoded as simple
unqualified string literals. When found in a valid CSW request no procedure -- other thansimple string comparison -- is necessary for processing these queryable property names.

22

Table 2 - OGC Core Queryable Properties

Mappings to the common XML Record format

Property

Definition

Data type

Mapping to FGDC Information Model

Subject2

The topic of the content of
the resource.

Character String

Keywords, see Table 6

Title

A name given to theresource

Character String

Title:
metadata.idinfo.citation.citinfo.title

Abstract

A summary of the content
of the resource

Character String

Abstract:
metadata.idinfo.descript.abstract

Format

The physical or digitalmanifestation of theresource

Code List
One of MIME
types

Format:metadata.distinfo.stdorder.digform.digtfo
rm.formname

Identifier

An unambiguous reference
to the resource within agiven context

Identifier

No Direct Mapping

Modified

Date on which the resource
was last changed

Date as Character
String in format:
YYYYMMDD4

Metadata_Date:
metadata.metainfo.metd

Type

The nature or genre of thecontent of the resource.
Type can include generalcategories, genres oraggregation levels of

Code List

Citation: Geospatial Data PresentationForm:/metadata/idinfo/citation/citinfo/geoform

20

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Property

Definition
content.

Data type

Mapping to FGDC Information Model

Envelope

A bounding box for
identifying a geographic
area of interest

Numeric

Envelope, see Table 6

CRS2

Coordinate Reference
System (Authority and ID)
for the Envelope

Character String

Spatial_Reference_Information,
see Table 6

Association

Complete statement of a
one-to-one relationship

AnyText

This represents thecatalogue entry as a whole.

1
2

3
4

Not supported by the profile.
Character String

Any available XML element andattribute content conforming to the
FGDC content standard

Because of the nature of the mapping between the Core queryables and the FDGC metadata,
properties which have sub-properties cannot be used in the constraint portion of queries. Use themost appropriate sub-property instead. Note that this does not apply to spatial queries since theseare special cases and can only be performed on the Envelope property.
See discussion of FGDC recurrence, which follows Table 3.
See discussion of FGDC Dates, which follows Table 3.

1
2
3
4

FGDC CSDGM provides no mapping for a unique identifier of a resource or a metadata
record. As such, this profile assumes nothing about the unique identifier of a resource,
and assumes the use of a unique key, labeled fgdc:recordID, which is associatedwith the metadata record.

5
6
7
8
9
10

The OGC Core Queryable property “Modified” is mapped to the FGDC content element“metainfo.metd,” reflecting a recommended best practice. That is, since the FGDCCSDGM does not include in its information model a “Date on which the resource waslast changed,” this profile assumes that the same date will be recorded in metadata
records in the value for “metainfo.metd”. FGDC defines this content element as “the datethat the metadata were created or last updated.”

11
12

Table 3 – FGDC Queryable Properties
Property

Definition

Data type

Mapping to FGDC Information Model

Title

See Table 2 (above)

Originator

Creator of the resource

Character String

Originator:
metadata.idinfo.citation.citeinfo.origin

Publisher

Publisher of the resource

Character String

Publisher:
metadata.idinfo.citation.citeinfo.publinfo.pu
blish.

Abstract

See Table 2 (above)

PurposeA description of the purpose Character Stringof the resource

Purpose:metadata.idinfo.descript.purpose

21

OGC 06-129r1
Property

CSW 2.0 FGDC CSDGM Application Profile

Definition

Data type

Mapping to FGDC Information Model

GeospatialPr The type of geospatial data
esentationFo in the resourcerm

Code List

Geospatial_Presentation_Form:
metadata.idinfo.citation.citeinfo.geoform

PublicationD Date on which the resourceate
was published

Date as Character
String in format:
1
YYYYMMDD

Publication_Date:
metadata.idinfo.citation.citeinfo.pubdate

ThemeKeyw The topic of the content ofords
the resource.

Character String

Theme_Keywords:
Metadata.idinfo.keywords.theme.themekey

Progress

A description of the status of Code List
the resource

Progress:
metadata.idinfo.status.progress

BeginDate

Beginning date for the
resource

Date as Character
String in format:
YYYYMMDD1

Beginning_Date:
metadata.idinfo.timeperd.timeinfo.rngdates.b
egdateEndDateEnding date for the resource Date as Character
String in format:
YYYYMMDD1Ending_Date:
metadata.idinfo.timeperd.timeinfo.rngdates.e
nddate OR
metadata.idinfo.timeperd.timeinfo.sngdate.ca
ldate OR
metadata.idinfo.timeperd.timeinfo.mdattim.s
ngdate.caldate

Envelope

See Table 2 (above)

AnyText

See Table 2 (above)1

See discussion of FGDC Dates, which follows Table 3.

1
2
3
4
5

The OGC Core Queryable property “format” maps to the FGDC content element“formname” (see Table 2), which may occur multiple times in a single metadata record.
Implementations of this profile will be assumed to apply the query against all occurrencesof this content element in a record.

6
7
8
9
10
11

The specified domain for numerous “date” elements in the FGDC CSDGM include“YYYMMDD,” “YYYYMM,” “YYYY,” “Unknown,” "Not complete," and other values
which are not numeric 5. This profile assumes that the presence of content that does notconform to a specified numeric date convention may cause a query against a property thatspecifies such an element to fail. However such non-numeric values may be treateddifferently, depending upon the implementation.

12

7.1.2.2 OGC Core Returnable Properties

13
14

The following table lists the mapping between core returnable properties and theassociated properties defined by this profile.

5

http://www.fgdc.gov/metadata/csdgm/organization.html describes the liberties taken with the domains ofsome elements as follows: “The domain also may note that the domain is free from restrictions, and any
values that can be represented by the "type" of the data element can be assigned. These unrestricteddomains are represented by the use of the word "free" followed by the type of the data element (that is, freetext, free date, free real, free time, free integer).”

22

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile
Table 4 – OGC Core Returnable Properties

Dublin Core
metadata
element nameTerm used inapplication
profiledc:creator

Originator,
fgdc:origin

Character String

Originatormetadata.idinfo.citation.citeinfo.origin

dc:publisher

Publisher,
fgdc:publish

Character String

Publisher:
metadata.idinfo.citation.citeinfo.pubinfo.publish

dc:contributor

Contributor,
fgdc:datacred

Character String

Data_Set_Credit:
metadata.idinfo.datacreddc:language

Language

Character String

No Mapping, unused by this profile1

dc:rights

Rightsfgdc:constraints

Character String

Constraints, See Table 6

dc:title

Title,
fgdc:title

Character String

Title:
metadata.idinfo.citation.citinfo.title

dc:subject

Subject
fgdc:keywords

Code List
At least one of Topic Keywords, See Table 6
Category [ISO19115]

dct:abstract

Abstract,
fgdc:abstract

Character String

Abstract:
metadata.idinfo.descript.abstract

dc:modified

Modified,
fgdc:metd

Date as Character
String in Format:
YYYYMMDD

Metadata_Date
metadata.metainfo.metd

dc:typeType,
fgdc:direct

Code List

Direct_Spatial_Reference:
metadata.idinfo.spdoinfo.direct

dc:format

Format,fgdc:formname

Code List
One of MIME types

Format:metadata.distinfo.stdorder.digform.digtinfo.formna
medc:identifier

Identifier
fgdc:recordID

Identifier

No Mapping, See Table 2

dc:source

Source,fgdc:source

Character String

Source_Citation:
metadata.lineage.srcinfo.srccite.citeinfo.title

dc:relation

Relation,
fgdc:onlink

URI

Online_Linkage:
metadata.idinfo.citation.citeinfo.onlink

dct:spatial

Envelope
fgdc:bounding

Numeric

Bounding Coordinates, See Table 6

Data type

Property Mapping to FGDC Information Model

1
FGDC provides no content element(s) characterizing the language of the data resource or the metadata
record. The CSDGM was defined with an unstated default language of “English,” but is implemented in otherlanguages in many countries. Nothing in this profile is intended to prevent successful execution of all operations
in Catalogue instances that contain metadata records in languages other than English.

1
Table 5 - FGDC Returnable Properties

23

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

FGDC-definedelement nameTerm used inapplication
profilefgdc:title

Title

fgdc:pubdate

Publication Date Date as Character
String in Format:
YYYYMMDD

fgdc:begdate

Beginning Date

Date as Character
String in Format:
YYYYMMDD

Beginning_Date:
metadata.idinfo.timeperd.timeinfo.rngdates.begdate

fgdc:enddate

Ending Date

Date as Character
String in Format:
YYYYMMDD

Ending_Date:
metadata.idinfo.timeperd.timeinfo.rngdates.enddate

fgdc:bounding

Envelope

CompoundBounding_Coordinates, See Table 6

fgdc:onlink

Relation

URL

Onlink_Linkage:
metadata.idinfo.citation.citeinfo.onlink

fgdc:extent

ExtentNumberExtent:Not in FGDC Model1

fgdc:enttypl

Entity TypeLabel

Character String

Entity_Type_Label:
metadata.eainfo.detailed.enttyp.enttypl

fgdc:attrlabl

Attribute LabelCharacter String

Attribute_Label:
metadata.eainfo.detailed.attr.attrlabl

fgdc:browse

Browse Graphic Compound

Browse_Graphic, See Table 4

fgdc:dsgpoly

Data Set GPolygon

Data_Set_G_Polygon, See Table 4

1

Data type
Character String

CompoundProperty Mapping to FGDC Information Model
Title:
metadata.idinfo.citation.citeinfo.title
Publication_Date:
metadata.idinfo.citation.citeinfo.pubdate. Defined by GEO Profile as: (NorthBC-SouthBC)*(EastBC-WestBC)

1
2

24

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

12

7.1.2.3 Compound Properties

3
4
5

Certain properties of the Dublin Core element set cannot be mapped to the FGDC
information model of this profile in a one-to-one relationship. Table 6 lists thesecompound properties and their mappings.
Table 6 – Mapping of Compound Properties
Compoundelement nameDublin Core
sub-element
name

Envelope2
WestLimit
SouthLimit
EastLimit
NorthLimit
Subject

Terms used in application
profileBounding,
fgdc:bounding,
dct:spatial
WestBoundingCoordinate,fgdc:westbc,
dcmi:westlimit
SouthBoundingCoordinate,fgdc:southbc,
dcmi:southlimit
EastBoundingCoordinate,fgdc:eastbc,
dcmi:eastlimit
NorthBoundingCoordinate,fgdc:northbc,
dcmi:northlimit
Keywords,
fgdc:keywords,
dc:subject

CRS

CRS,
fgdc:spref,
csw:crs

RightsRights,fgdc:constraints,
dc:rights
AccessConstraints,
fgdc:accconst,
dct:accessRights
UseConstraints,
fgdc:useconst,
dct:license
Graphic,
fgdc:browse,
fgdc:graphic

AccessUse
BrowseGraphic

Mapping properties to FGDC Information
Model
Bounding_Coordinates
metadata.idinfo.spdom.bounding
West_Bounding_Coordinate:
metadata.idinfo.spdom.bounding.westbc
South_Bounding_Coordinate:
metadata.idinfo.spdom.bounding.southbc
East_Bounding-Coordinate:
metadata.idinfo.spdom.bounding.eastbc
North_Bounding_Coordinate:
metadata.idinfo.spdom.bounding.northbc
Keywords:
metadata.idinfo.*.keywords
metadata.idinfo.keywords.theme.themekey
metadata.idinfo.keywords.place.placekey
Metadata.idinfo.keywords.stratum.stratkey
metadata.idinfo.keywords.temporal.tempkey
Spatial_Reference_Information4:
metadata.spref
No direct mapping3
Access_Constraints:
metadata/idinfo/accconst
Use_Constraints:
metadata/idinfo/useconst
Browse_Graphic4:
metadata.idinfo.browse

25

OGC 06-129r1
Data Set
G-Polygon

CSW 2.0 FGDC CSDGM Application Profile
Data_Set_G_Polygon4:
metadata.idinfo.spdom.dsgpoly

Polygon,fgdc:dsgpoly
fgdc:polygon

1
No suitable mapping to DC elements. Non-FGDC queries should use the provided element name.
2
dc:Envelope contains the element dcmi:Box which contains the four coordinate elements. The
Envelope element is mapped to fgdc:Bounding and the Box element is automatically handled by the Server.
3
Although there is no direct mapping to a specific FGDC element, using this element in as a returnable
will result in the use of the sub-elements which may or may not map directly to the Dublin Core element set.
4
This element or its children/grandchildren are repeating elements and are only necessary for returnablesupport. Because of this, this element is stored and returned as an xml fragment containing all occurrences ofitself and its descendant nodes. Request for the values of these elements must be qualified in the “csw”
namespace, i.e. “fgdc:browse” would be “csw:browse”.

1
2

7.1.3

Additional Properties3
4
5

In addition to the core properties, this profile defines additional supported properties inTable 7. These are queryable and returnable and follow the same rules of use as the coreelements.
Table 7 - Additional Queryable/Returnable Properties
Name

Definition

Term used inapplication
profileData type

Property Mapping to Information
Model

Content
Begin Date

Begin daterelevant todata
referenced

BeginningDate
fgdc:begdate
csw:begindate

Date
Format:YYYYMMDD

metadata.idinfo.timeperd.timeinfo.rngdat
es.begdate

Content End
Date

End date
relevant todata
referenced

EndingDate
fgdc:enddate
csw:enddate

Date
Format:YYYYMMDD

metadata.idinfo.timeperd.timeinfo.rngdat
es.enddate

Progress

Status ofthe data
referenced

Progress
fgdc:progress
csw:progress

Character String

metadata.idinfo.status.progress

CalendarDate

Daterelevant to
the data
referenced

CalendarDate
fgdc:caldate
csw:calendardate

Date
Format:YYYYMMDD

metadata.idinfo.timeperd.timeinfo.sngdat
e.caldate

6
7

7.2

Result sets

8
9
10
11
12

This section defines XML Schema presentations for valid result sets of the application
profile. A representation of catalogue entries in a result set may substitute for the element
csw:AbstractRecord defined in the Catalogue Service Implementation Specifications
2.0.1 record schema, ‘record.xsd’ or the element csw:AbstractElement defined by therecord schema of this profile, ‘record-fgdc.xsd’. For this profile and all implementations,26

OGC 06-129r1
1
2

CSW 2.0 FGDC CSDGM Application Profile

the OGC Core schema result set (“OGCCORE”) is assumed to be synonymous with the“csw:Record” schema result set.
Table 8 – Result Sets Supported by Schemas
SchemaBRIEF

SUMMARYFULL

OGC Core/CSW

+

+

+

FGDC

+

+

+

GEO

+

+

+

3
4
5
6
7
8
9

Table 9 describes which properties of the information model of this profile are contained
within the supported result sets. An important note to point out is that the “full” result set
includes all elements of the metadata record, even those beyond the elements listed in thequeryable and returnable tables, since the valid response to such a request is to return theentire metadata record. It is important to note that a “full” result set response will always
contain the full FGDC CSDGM metadata record, regardless of the schema requested.

10
Table 9 - Result Set Properties
Property Name

FGDC
BRIEF

CSW
BRIEF

Abstract

GEO
BRIEF

FGDC
SUMM.

CSW
SUMM.

+

+

GEO
SUMM.

Attribute Label+

Browse Graphic+

Contributor+

Data Set G-Polygon+

Entity Type Label+

Envelope++

Extent+Format++++Modified++

Originator+

Identifier

+

+

+

Progress+

Publication Date+

Publisher+

PurposeRelation

+
+

+

+

27

OGC 06-129r1
Property Name

CSW 2.0 FGDC CSDGM Application Profile
FGDC
BRIEF

CSW
BRIEF

GEO
BRIEF

FGDC
SUMM.

CSW
SUMM.

GEO
SUMM.

Rights+

Source+Subject

+

+

+

+

+

+

+

+

Title

+

Type

+
+

1
2

7.2.1

BRIEF Result Set

3
4
5
6

A response to a valid catalogue service request with ElementSetName=BRIEF. This set
corresponds to the smallest amount of information which represents the metadata recordin the database. See Appendix D sections 2 and 3 for brief result set definitions andexamples.

7

7.2.2

8
9
10
11

A response to a valid catalogue service request with ElementSetName=SUMMARY. This set
corresponds to the average amount of information which represents the metadata recordin the database. See Appendix D sections 2 and 3 for summary result set definitions andexamples.

12

7.2.3

13
14
15

A response to a valid catalogue service request with ElementSetName=FULL. Such a
response includes the metadata record in its stored format in its entirety. See Appendix D
sections 2 and 3 for full result set definitions and examples.

16

8

17
18
19
20
21
22

This view describes the externally visible behavior of the system, including the interfaces
provided by its components and the supported protocol bindings. It defines the request
and response message structures as part of the operation signatures, primarily thedifferences to that of the OGC CS 2.0 base specification. It also documents supported
query facilities and some implementations guidance as well as a few security
considerations.

23

8.1

24
25
26

This profile imports the HTTP protocol binding from the CSW 2.0 specification. Table
10 shows the mapping of the operations specified by the CSW 2.0 specification to theoperations of this profile, CSW(T)-FGDC.

SUMMARY Result Set

FULL Result Set

External interfaces

Imported protocol binding (Relationship to the common model)

Table 10 - Mapping CSW operations to CSW(T) FGDC operations
CSW operation

CSW(T)-FGDC operation

28

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

CSW operation

1
2
3
4
5
6

CSW(T)-FGDC operation

OGC_Service.GetCapabilities

OGC_Service.GetCapabilities

CSW-Discovery.GetRecords

CSW Discovery.GetRecords

CSW-Discovery.DescribeRecord

CSW Discovery.DescribeRecord

CSW-Discovery.GetDomain

CSW Discovery.GetDomain

CSW-Discovery.GetRecordById

CSW Discovery.GetRecordById

CSW-Publication.Transaction

CSWT Manager.Transaction

CSW-Publication.Harvest

CSWT Manager.Harvest

All non-transactional CSW operations support keyword-value pairs (KVP) encoding ofrequests within a request URI. All operations support XML encoding of requests. Also,
all responses generated by the server are XML-encoded. KVP-encoding of requests is
supported through HTTP-GET binding while XML-encoded requests are supported
through HTTP-POST. Table 11 summarizes the CSW(T)-FGDC operations and theirencoding methods that are applied in this profile.
Table 11 - Operation request encoding
CSW(T)-FGDC Operation

Request encoding

GetCapabilities

XML (POST) and KVP (GET)

DescribeRecord

XML (POST) and KVP (GET)

GetDomain

XML (POST) and KVP (GET)

GetRecords

XML (POST) and KVP (GET)

GetRecordById

XML (POST) and KVP (GET)

Transaction

XML (POST)

HarvestXML (POST) and KVP (GET)

7
8

8.2

Interface specifications

9
10

This section describes the syntax and semantics of the interface operations of this profile
in comparison to those defined by the CSW 2.0 specification.

29

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

8.2.1

OGC_Service Interface2

8.2.1.1 GetCapabilities Operation

3
4
5
6

The GetCapabilities operation allows clients to retrieve service metadata from the server.
The response to a GetCapabilities request should be an XML-encoded document
containing service metadata about the server. HTTP-GET using KVP and HTTP-POST
using XML encoding are available as protocol bindings.

7
8
9

Examples of a GetCapabilities request and response are shown in Listing 1 and Listing 3,
respectively. Namespace declarations and some response information were omitted forspace and readability.
Table 12 - Parameters in GetCapabilities operation requestName
SERVICEREQUESTACCEPT
VERSIONSSECTIONSUPDATESEQUENCE

ACCEPT
FORMATS

Definition
Service typeidentifier
Operation namePrioritized sequenceof one or more
specification
versions accepted byclient, with preferredversions listed first
Unordered list of
zero or more namesof requested sections
in complete service
metadata document
Service metadata
document version,value is “increased”
whenever any change
is made in complete
service metadata
document
Prioritized sequenceof zero or more
response formats
desired by client,with preferred
formats listed first

Data Type and value

Multiplicity
and use

FGDC App.Profile

Character String type, not empty
Fixed value of “CSW”
Character String type, not empty
Fixed value of “GetCapabilities”
Sequence of Character String
type, not empty
Value is “2.0.1”
When omitted, return latest
supported version

Mandatory

Mandatory

Mandatory

Mandatory

Zero or one(Optional)

Zero or one(Optional)

Sequence of Character String
type, not empty
Value is list of section names
Allowed section names are
specified by each
Implementation Specification

Zero or one(Optional)

Character String type, not empty
Values are selected by eachserver, and are always opaque toclients

Zero or one(Optional)

Zero or one(Optional)
When omitted or
not supported byserver, return
complete service
metadata document
Zero or one(Optional)

Sequence of Character String
type, not empty
Value is list of format identifiers
Identifiers are MIME types offormats useful for service
metadata documents.
Supports “text/xml” and“text/html”

Zero or one(Optional)
Default
value is“text/xml”

Zero or one(Optional)
Default value is“text/xml”

10
Listing 1 – GetCapabilities Request in XML
11<csw:GetCapabilities service="CSW" version="2.0.1">30

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12

CSW 2.0 FGDC CSDGM Application Profile<csw:AcceptVersion><csw:Version>2.0.1</csw:Version></csw:AcceptVersion><csw:Sections><csw:Section>ServiceIdentification</csw:Section><csw:Section>OperationsMetadata</csw:Section><csw:Section>Contents</csw:Section></csw:Sections><csw:AcceptFormat><csw:OutputFormat>text/xml</csw:OutputFormat></csw:AcceptFormat></csw:GetCapabilities>

Listing 2 - GetCapabilities Response
13
14
15
16
17
18
19
20
21
22
23

<csw:Capabilities version="2.0.1" updateSequence="0"><ows:ServiceIdentification>...omitted for space...
</ows:ServiceIdentification><ows:OperationsMetadata>...omitted for space...
</ows:OperationsMetadata><csw:Contents>...omitted for space...
</csw:Contents></csw:Capabilities>

24
25

8.2.2

CSW Discovery Interface

26

8.2.2.1 GetRecords Operation

27
28
29

The GetRecords operation is equivalent to the combination of the two general model
operations Search and Present. HTTP-GET using KVP and HTTP-POST using XML
encoding are available as protocol bindings for this operation.

30

8.2.2.1.1 Request

31
32
33
34

The parameters of the GetRecords operation request are specified in Table 13. The
FGDC App.-Profile column lists any restrictions or variations in comparison to those of
the base specification. The encoding in the table is directly suitable for the HTTP-GET
binding.

35
36
37
38

An example of a GetRecords request in XML is shown in Listing 3. In this example, thebrief element set containing FGDC elements is requested for all records using an empty
constraint. The associated GetRecords response for this request is shown in Listing 4.
Namespace declarations were omitted for space and readability.

39

31

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Table 13 - Parameters in GetRecords operation request
Keyword
REQUESTSERVICE
VERSIONNAMESPACERESULTTYPEOUTPUTFORMAT

Data Type & Value
Character String.
Fixed value of “GetRecords”. The
value is case insensitive.
Character String.
Fixed value of “CSW”
Character String.
Fixed value of “2.0.1”
List of Character String,comma separated.
Used to specify namespace.
Format must be <prefix>:<url>.

CodeList.
One of “HITS”, “RESULTS” or“VALIDATE”.
If this value is ”HITS” or“VALIDATE”, ElementSetName
and ElementName are ignored.
Character String
Value is Mime type
Supports “text/ xml” and “text/html”

Optionality

FGDC App.-Profile

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Zero or one (Optional)
Include value for eachnamespace
If not included, allqualified names are indefault namespace
Optional
Default value is“RESULTS”.

Mandatory

Optional;
Default value is“text/xml”

Optional;
Default value is“text/xml”

Optional
Default value is“RESULTS”.

OUTPUTSCHEMA

Defined in a profile.
Must support “OGCCORE”.
Also supports “fgdc:metadata”,“csw:Record”, and “OGCCORE“.

Optional

Zero or one(Optional)
Default value is“fgdc:metadata”.

STARTPOSITION

Positive Integer

Optional
Default value is 1.

Optional
Default value is 1.

MAXRECORDS

Positive Integer

Optional
Default value is 10.

Optional
Default value is 10.

TYPENAMES

Mandatory

Mandatory

Optional

Optional

ELEMENTSETNA
ME

List of Character String, comma
separated
Unordered List of object types
implicated in the query
List of Character String
Valid values include the names andXPath expressions of FGDC metadata
model elements or their equivalent DC
names.
Character String
One of: “brief”, “summary”, or “full”.

Optional
Default value is“summary”.

Optional
Default value is“summary”.

CONSTRAINTLAN
GUAGE

Code List“FILTER”

Mandatory

This profile does notsupport“CQL_TEXT”

CONSTRAINT

Character String
The predicate expression specified in
the language indicated by the
CONSTRAINTLANGUAGE
parameter.

Optional
Default action is to
execute an
unconstrained query.

Optional
Default action is to
execute an
unconstrained query.

ELEMENTNAME

32

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Keyword

Data Type & Value
List of Character String, comma
SORTBYseparated
Ordered list of names of metadata
elements to use for sorting the response
KVP Format: element_name[:A|D]‘A’ for ascending sort, ‘D’ fordescending sort
DISTRIBUTEDSEA Boolean
RCH
Integer
May be specified only if
DISTRIBUTEDSEARCH is specified.
If not specified, the default value is 2.
RESPONSEHANDL URLERHOPCOUNT

Optionality
Optional
Default action is topresent the records inthe order in which they
are retrieved.

Optional
Default value is
FALSE.
Optional
Default value is 2

FGDC App.-Profile
Optional
Default action is topresent the records inthe order in which
they are retrieved.
Optional

Optional

Zero or one Optional
Not supported by thisIf not included, process profile.
request synchronously

1
Listing 3 – GetRecords Request in XML
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

<csw:GetRecords service="CSW" version="2.0.1" outputFormat="text/xml"
outputSchema="fgdc:metadata" startPosition="1" maxRecords="10"><csw:Query typeNames="Any"><csw:ElementSetName>brief</csw:ElementSetName><csw:Constraint><ogc:Filter><ogc:OR><ogc:AND><ogc:BBOX><ogc:PropertyName>Envelope</ogc:PropertyName><gml:Box><gml:coordinates>-179.899,-155.637 175.231,82.428</gml:coordinates></gml:Box></ogc:BBOX><ogc:PropertyIsBetween><ogc:PropertyName>Modified</ogc:PropertyName><ogc:LowerBoundary><ogc:Literal>19000000</ogc:Literal></ogc:LowerBoundary><ogc:UpperBoundary><ogc:Literal>20000000</ogc:Literal></ogc:UpperBoundary></ogc:PropertyIsBetween></ogc:AND><ogc:PropertyIsLike wildCard="*" singleChar="?" escapeChar="!"><ogc:PropertyName>fgdc:themekey</ogc:PropertyName><ogc:Literal>F*MA</ogc:Literal></ogc:PropertyIsLike></ogc:OR></ogc:Filter></csw:Constraint></csw:Query></csw:GetRecords>

33

OGC 06-129r1
1

CSW 2.0 FGDC CSDGM Application Profile

8.2.2.1.2 Response
Listing 4 – GetRecords Response in XML

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

<csw:GetRecordsResponse version="2.0.1"><csw:RequestId>db3331:10061cc6373:-7fff</csw:RequestId><csw:SearchStatus status="complete" /><csw:SearchResults resultSetId="1" elementSet="brief"
recordSchema="fgdc:metadata" numberOfRecordsMatched="419"
numberOfRecordsReturned="10" nextRecord="11"><fgdc:BriefRecord><fgdc:publish>Publisher 1</fgdc:publish><fgdc:metd>20021122</fgdc:metd><fgdc:title>Title 1</fgdc:title><fgdc:recordID>14da8f4:fee9daddfa:-7ffe</fgdc:recordID></fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord><fgdc:BriefRecord>...record contents omitted for space...
</fgdc:BriefRecord></csw:SearchResults></csw:GetRecordsResponse>

43
44

8.2.2.2 GetRecordById Operation

45
46
47
48

The GetRecordById request retrieves the default information model representation of
catalogue records using their identifier as the constraint. This operation presumes that aprevious query has been performed in order to obtain the identifiers that may be usedwith this operation.

49

8.2.2.2.1 Request

50
51

The parameters of the GetRecordById operation request are specified in Table 14. The
FGDC App.-Profile column lists any restrictions or variations in comparison to those of34

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

12the base specifications. The encoding in the table is directly suitable for the HTTP-GET
binding.

3
4
5
6

An example of a GetRecordById request in XML is shown in Listing 5. In this example,
a summary element set of FGDC elements is requested for a specific record matching thespecified ID. The associated GetRecordById response to the request is shown in Listing
6. Namespace declarations were omitted for space and readability.

7
Table 14 - Parameters in GetRecordById operation request
Keyword
REQUESTSERVICE

Data Type & Value
Character String.
Fixed values of “GetRecordById”. The value
is case insensitive.
Character String.

Optionality

ISO App.-Profile

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Optional
Default value is“text/xml”

Optional
Default value is“text/xml”

Optional.

Zero or one (Optional)
Default value is“fgdc:metadata”.

Zero or one(Optional)
Default value is“summary”.

Zero or one (Optional)
Default value is“summary”

One
MandatoryOne
Mandatory

Fixed value of “CSW”
VERSION

Character String.
Fixed value of “2.0.1”
OUTPUTFORM Character String
Value is Mime type
AT
Supports “text/ xml” and “text/html”
OUTPUTSCHEMAELEMENTSETNAMEDefined in a profile.
Must support “OGCCORE”.
Supports “fgdc:metadata”, “csw:record”,“OGCCORE“, and “fgdc:metadata”.
CodeList
One of: “brief”, “summary” or “full”

ID

KVP – Comma separated list of anyURI XML– Separately-tagged <Id> elements or commaseparated list inside single <Id> element.

8
Listing 5 – GetRecordById Request in XML
9
10
11
12
13
14

<csw:GetRecordById service="CSW" version="2.0.1" outputFormat="text/xml"
outputSchema="fgdc:metadata"><csw:Id>1f26605:fe7d93fd50:-7fea</csw:Id><csw:ElementSetName>summary</csw:ElementSetName></csw:GetRecordById>

15

8.2.2.2.2 Response
Listing 6 – GetRecordById Response35

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

CSW 2.0 FGDC CSDGM Application Profile<?xml version="1.0" encoding="UTF-8"?><fgdc:GetRecordByIdResponse version="2.0.1"><fgdc:SummaryRecord><fgdc:direct>DataSet</fgdc:direct><fgdc:keywords><fgdc:themekey>Inventory</fgdc:themekey><fgdc:themekey>Faults</fgdc:themekey><fgdc:themekey>FEMA</fgdc:themekey><fgdc:placekey>Mississippi</fgdc:placekey><fgdc:placekey>Maryland</fgdc:placekey><fgdc:placekey>Kentucky</fgdc:placekey><fgdc:stratkey>Sedimentary Rocks</fgdc:stratkey><fgdc:tempkey/></fgdc:keywords><fgdc:bounding><fgdc:westbc>-167.391</fgdc:westbc><fgdc:eastbc>71.435</fgdc:eastbc><fgdc:northbc>128.512</fgdc:northbc><fgdc:southbc>81.315</fgdc:southbc></fgdc:bounding><fgdc:abstract>Some abstract information.</fgdc:abstract><fgdc:source>FEMA</fgdc:source><fgdc:pubdate>19940014</fgdc:pubdate><fgdc:title>Essential Conterminous United States Faults</fgdc:title><fgdc:recordID>1f26605:fe8c0aac98:-7ed4</fgdc:recordID><fgdc:origin>Geospatial Impact Structures</fgdc:origin><fgdc:accconst>None</fgdc:accconst><fgdc:useconst>None</fgdc:useconst><fgdc:publish>FEMA</fgdc:publish><fgdc:onlink>
http://www.fema.gov/sample-documents/001.html</fgdc:onlink><fgdc:datacred>Third Party Associates, Inc.</fgdc:datacred><fgdc:formname>text/xml</fgdc:formname></fgdc:SummaryRecord></fgdc:GetRecordByIdResponse>37
38

8.2.2.3 DescribeRecord Operation

39
40

The DescribeRecord operation allows a client to discover elements of the information
model supported by the target catalogue service.

41

8.2.2.3.1 Request

42
43
44
45

Table 15 specifies the parameters for the DescribeRecord operation request. The FGDC
App.-Profile column lists any restrictions or variations in comparison to that of the basespecification. The encoding in the table is directly suitable for the HTTP-GET binding.
An example of a DescribeRecord request is shown in

46
47
48
49

Listing 7. In this example, the schema which defines the information model of thisprofile, defined by fgdc:metadata, is requested. The associated DescribeRecord
response is shown in Listing 8. The actual schema definition is omitted from the listingfor space. Namespace declarations were omitted for space and readability.

36

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Table 15 - Parameters in DescribeRecord operation request
Keyword

Data Type & Value

Optionality

FGDC App.Profile

REQUEST

Character String.
Mandatory
Fixed value of “DescribeRecord”. The
value is case insensitive.

MandatorySERVICE

Character String.
Fixed values of “CSW”

Mandatory

Mandatory

VERSION

Character String.
Fixed value of “2.0.1”

Mandatory

MandatoryNAMESPACE

List of Character String, comma
separated.
Used to specify a namespace and its
prefix. Format must be[<prefix>:]<url>. If the prefix is not
specified then this is the default
namespace.

Zero or one
Optional
Include value for eachnamespace
If not included, allqualified names are indefault namespace

Optional

TYPENAME

List of Character String, comma
separated
One or more qualified type names to be
described
Character String
Value is Mime type
Supports “text/ xml” and “text/html”

Zero or one (Optional)
Default action is todescribe all types known
to server
Optional
Default value is“text/xml”

Optional.

Character String

Zero or one (Optional)
Default value is
XMLSCHEMA

Only“XMLSCHEMA”
is supported

OUTPUTFORMATSCHEMALANGUAGE

Optional
Default value is“text/xml”

1
Listing 7 – DescribeRecord Request in XML
2
3
4
5
6
7

<?xml version="1.0" encoding="ISO-8859-1"?><csw:DescribeRecord version="2.0.1" service="CSW" outputFormat="text/xml"
schemaLanguage="XMLSCHEMA"><csw:typeName>fgdc:metadata</csw:typeName><csw:typeName>csw:record</csw:typeName></csw:DescribeRecord>

898.2.2.3.2 Response
Listing 8 – DescribeRecord Response

10
11
12
13
14
15
16

<csw:DescribeRecordResponse><csw:SchemaComponent targetNamespace=" http://www.opengis.net/cat/csw/csdgm"
parentSchema="metadataEntity.xsd" schemaLanguage="XMLSCHEMA"><xs:schema elementFormDefault="qualified">...omitted for space...
</xs:schema>

37

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10

CSW 2.0 FGDC CSDGM Application Profile</csw:SchemaComponent><csw:SchemaComponent targetNamespace="fgdc:http://www.fgdc.gov/csdgm/fgdc"
parentSchema="metadataEntity.xsd" schemaLanguage="XMLSCHEMA">...omitted for space...
</csw:SchemaComponent><csw:SchemaComponent targetNamespace="http://www.opengis.net/cat/csw"
parentSchema="metadataEntity.xsd" schemaLanguage="XMLSCHEMA">...omitted for space...
</csw:SchemaComponent></csw:DescribeRecordResponse>

11
12

8.2.2.4 GetDomain Operation

13
14
15
16

The GetDomain operation is used to obtain runtime information about the metadata
record elements and request parameters. This type of runtime information is useful for
generating user interfaces with meaningful pick lists or for generating query predicatesthat have a higher chance of identifying a result set.

17

8.2.2.4.1 Request

18
19
20

Table 16 specifies the parameters for the GetDomain operation request. The FGDC
App.-Profile column lists any restrictions or variations in comparison to those of the basespecification. The encoding in the table is directly suitable for the HTTP-GET binding.

21
22
23
24
25

An example of a GetDomain request in XML is shown in Listing 9. In this example, thelist of possible values for the parameter name GetRecords.ElementSetName and theschema which defines the property name fgdc:title are requested. The associatedresponse is shown in Listing 10. Namespace declarations were omitted for space andreadability.
Table 16 - Parameters in GetDomain operation request
Keyword
REQUESTSERVICE

Data Type & Value
Character String.
Fixed value of “GetDomain”. The value is caseinsensitive.

Optionality

ISO App.Profile

Mandatory

Mandatory

Mandatory

Mandatory

Character String.
Fixed value of “2.0.1”
Character String
Value is Mime type
Supports “text/ xml” and “text/html”

Mandatory

Mandatory

Optional
Default value is“text/xml”

Optional
Default value is“text/xml”

List of Character String, comma separated

Optional

Character String.
Fixed values of “CSW”

VERSIONOUTPUTFORMATPARAMETERNAME

Optional

Unordered list of names of an interface
parameter, of the form
OperationName.ParameterName

38

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

KeywordPROPERTYNAME

Data Type & Value
List of Character String, comma separated

ISO App.Profile

Optionality
Optional

Optional

Unordered list of names of requested properties,
from the information model that the catalogue isusing.

1
Listing 9 - GetDomain Request in XML
2
3
4
5
6
7
8
9
10

<csw:GetDomain service="CSW" version="2.0.1"><csw:ParameterName>GetRecords.ResultType</csw:ParameterName><csw:ParameterName>GetRecords.OutputFormat</csw:ParameterName><csw:ParameterName>GetRecords.ElementSetName</csw:ParameterName><csw:ParameterName>GetRecordById.OutputSchema</csw:ParameterName><csw:ParameterName>DescribeRecord.SchemaLanguage</csw:ParameterName><csw:ParameterName>Harvest.ResourceFormat</csw:ParameterName><csw:PropertyName>fgdc:title</csw:PropertyName></csw:GetDomain>

11
12

8.2.2.4.2 Response

13
14
15
16

The domain response is composed of one or more DomainValues elements, whichcontain a list of enumerated values (ListOfValues) or a reference to some authoritative
vocabulary (ConceptualSchema). An example of an authoritative vocabulary might be astandard list of animal and plant species names.

17
18
19

If the only child element of the DomainValue element is the PropertyName or
ParameterName element, this means that the server was unable to determine any
information about the specified property or parameter.

20
21

The XML encoding of a valid response is specified in the HTTP binding of CSW 2.0
specification. Please refer to this section to determine the appropriate XML schema.
Listing 10 – GetDomain Response

22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

<csw:GetDomainResponse version="2.0.1"><csw:DomainValues type="PropertyName" uom=""><csw:PropertyName>fgdc:title</csw:PropertyName><csw:ConceptualScheme><csw:Name>...omitted for space...</csw:Name><csw:Document>...omitted for space...</csw:Document><csw:Authority>...omitted for space...</csw:Authority></csw:ConceptualScheme></csw:DomainValues><csw:DomainValues type="ParameterName" uom=""><csw:ParameterName>GetRecords.ResultType</csw:ParameterName><csw:ListOfValues><csw:Value>hits</csw:Value><csw:Value>results</csw:Value><csw:Value>validate</csw:Value></csw:ListOfValues></csw:DomainValues>

39

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

CSW 2.0 FGDC CSDGM Application Profile<csw:DomainValues type="ParameterName" uom=""><csw:ParameterName>GetRecords.OutputFormat</csw:ParameterName><csw:ListOfValues><csw:Value>text/xml</csw:Value><csw:Value>text/html</csw:Value></csw:ListOfValues></csw:DomainValues><csw:DomainValues type="ParameterName" uom=""><csw:ParameterName>GetRecords.ElementSetName</csw:ParameterName><csw:ListOfValues><csw:Value>brief</csw:Value><csw:Value>summary</csw:Value><csw:Value>full</csw:Value></csw:ListOfValues></csw:DomainValues><csw:DomainValues type="ParameterName" uom=""><csw:ParameterName>GetRecordById.OutputSchema</csw:ParameterName><csw:ListOfValues><csw:Value>fgdc:metadata</csw:Value><csw:Value>csw:record</csw:Value><csw:Value>fgdc:metadata</csw:Value></csw:ListOfValues></csw:DomainValues><csw:DomainValues type="ParameterName" uom=""><csw:ParameterName>DescribeRecord.SchemaLanguage</csw:ParameterName><csw:ListOfValues><csw:Value>xmlschema</csw:Value></csw:ListOfValues></csw:DomainValues><csw:DomainValues type="ParameterName" uom=""><csw:ParameterName>Harvest.ResourceFormat</csw:ParameterName><csw:ListOfValues><csw:Value>text/xml</csw:Value></csw:ListOfValues></csw:DomainValues></csw:GetDomainResponse>

37
38

8.2.3

CSWT Manager Interface

39
40
41
42
43

The CSW-Transaction Manager Interface defines operations for creating, modifying anddeleting catalogue records. These operations can all performed using a Transaction
operation. The Manager Interface also defines the Harvest operation, which allows forbulk transmission of one catalogue to another for purposes of populating a datarepository.

44

8.2.3.1 Harvest Operation

45
46
47
48
49
50
51

The “harvestResource” operation, on the other hand, directs the catalogue to retrieve anaccessible metadata record and processes it for inclusion in the catalog, perhaps
periodically re-fetching the metadata records to refresh the information in the catalog.
The client does not need to be aware of the information model of the catalogue whenusing the “harvestResource” operation, since the catalogue itself is doing the workrequired to process the information. The client is simply pointing to where the metadata
resource to be harvested is.

40

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

8.2.3.1.1 Request

2

In the following tables, the parameters for harvest operation requests are specified.

3
4

The FGDC App.-Profile column lists any restrictions or variations in comparison to
those of the base specification. The base parameters are specified in Table 18.

56

An example of a harvest request is shown in Listing 15. The associated response isshown in Listing 16. Namespace declarations were omitted for space and readability.
Table 17 - Parameters in Harvest operation request
Keyword
REQUESTSERVICE

Data Type & Value
Character String.
Fixed value of “harvestResource”. The value iscase insensitive.
Character String.

Optionality

FGDC App.Profile

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Fixed value of “CSW”
VERSION

Character String.
Fixed value of “2.0.1”

OUTPUTFORMAT Character String
A MIME type indicating the format that the output
document should have
Supports “text/ xml” and “text/html”

Optional
Optional
Default value is Default value is“text/xml”“text/xml”

SOURCE

URI
Reference to the type of resource being harvested.

Mandatory

MandatoryRESOURCE
FORMAT

Character String
MIME type indicating format of the resource being
harvested

Zero or One(Optional)
Default value is“text/xml”

Zero or One(Optional)“text/xml” is only
format supported bythis profile.

RESOURCETYPEThe ResourceType parameter is a reference to aschema document that defines the structure of theresource being harvested.

Zero or One(Optional)

Zero or One(Optional)“fgdc:metadata” isonly type supportedby this profile.

HARVEST
INTERVAL

PeriodMust conform to ISO8601 Period syntax.

Zero or One(Optional)

Not supported bythis profile.

7
Listing 11 - Harvest Request
8
9
10
11
12
13
14

<csw:Harvest service="CSW" version="2.0.1" requestId="hOp1"
xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:ows="http://www.opengis.net/ows"
xmlns:ogc="http://www.opengis.net/ogc"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm"><csw:Source>http://localhost:8080/cswwar/csw.jsp</csw:Source><csw:ResourceType>fgdc:metadata</csw:ResourceType>41

OGC 06-129r1
1
2

CSW 2.0 FGDC CSDGM Application Profile<csw:ResourceFormat>text/xml</csw:ResourceFormat></csw:Harvest>

3
4

8.2.3.1.2 Response

5
6
7

The Harvest response reports a summary of the harvesting operation by indicating thenumber of records harvested from the old data repository(s) and inserted into the newrepository by the request.

8
9
10
11
12
13

Unlike the OpenGIS™ Catalogue Service Implementation Specification (2.0.1), thisprofile does not recommend using the InsertResults element to detail each record
harvested. The purpose of the Harvest operation is to perform a mass transit of data fromone catalogue to another, and a detail of each record in the list of potentially thousands ofharvested records would greatly affect performance of the CSW server as well as therequesting CSW client and the data repository interfaced by the server.
Listing 12 – Harvest Response

14
15
16
17
18
19
20

<csw:HarvestResponse version="2.0.1"><csw:HarvestResults requested="14da8f4:feaff59c37:-7fba"><csw:TransactionSummary><csw:totalInserted>10000</csw:totalInserted></csw:TransactionSummary></csw:HarvestResults></csw:HarvestResponse>

21
22

8.2.3.2 Transaction Operation

23
24
25
26
27

The “transaction” operation allows a client to formulate a transaction, and send it to thecatalogue to be processed. The transaction may contain metadata records and elements of
the information model that the catalogue understands. To use the transaction operation,
the client must know something about the information model that the catalogue
implements.

28

8.2.3.2.1 Request

29
30
31
32
33

In the following tables, the parameters for transaction operation requests are specified.
There is no KVP encoding for transaction operation request, because there is noconvenient way of encoding the transaction payloads using keyword-value pairs.
Although only XML is supported, the parameters are presented in tabular form to give a
better overview.

34
35
36
37

The FGDC App.-Profile column lists any restrictions or variations in comparison to
those of the base specification. The base parameters are specified in Table 18. The
Transaction element defines an atomic unit of work and is a container for one or more
insert, update and/or delete actions which are defined in the following tables.

38
39
40

An example of a transaction request using an Insert, Update, and Delete is shown in
Listing 13. The associated Transaction Response is shown in Listing 14. Namespacedeclarations were omitted for space and readability.

42

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Table 18 - Parameters in Transaction operation request
Keyword
REQUESTSERVICE

Data Type & Value
Character String.
Fixed value of “Transaction”. The value is caseinsensitive.
Character String.

Optionality

FGDC App.Profile

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Optional.
Default value is“text/xml”.

Supports“text/ xml”
and“text/html”

One or more

One or more

Fixed value of “CSW”
VERSION

Character String.
Fixed value of “2.0.1”

OUTPUTFORMAT Character String
A MIME type indicating the format that the output
document should have
TRANSACTION

Defines an atomic unit of work and is a container for
one or more insert, update and/or delete actions.

1
2
3
4
5
6
7
8
9

Valid parameters for an insert operation are listed in Table 19. The Insert element is acontainer for one or more records that are to be inserted into the catalog. These record(s)must conform to the schema of the information model described by the DescribeRecord
operation. Additionally, the schema by which the data repository is bound must be
defined as the namespace schema for each record to be inserted, using thexsi:noNamespaceSchemaLocation attribute of the fgdc:metadata element as specified
by the XML 1.0 specifications. An example of this can be found in the Appendix sectionof this document.

10
11
12
13
14

The verbal response attribute can be used to obtain a more detailed result set of
information from the newly inserted record. If the value of the attribute is “true”, theserver will return a “summary” result set from the record along with the standardtransactional summary information. If the value if “false”, then a “brief” result set isreturned.
Table 19 - Parameters of Insert Operation
KeywordTransactionType
REQUESTID

Data Type & Value
Code List
Value of “Insert”
May be used by a client application to associate auser-defined identifier with the operation.

Optionality

ISO App.-Profile

Mandatory

Mandatory

Zero or one

Zero or one

43

OGC 06-129r1
Keyword
VERBOSERESPONSE

RECORDHANDLECSW 2.0 FGDC CSDGM Application Profile
Data Type & Value
May be used by a client to indicate to a server theamount of detail to generate in the response. A
value of FALSE means that a CSW should
generate a terse or brief transaction response. A
value of TRUE, or the absence of the attribute,means that the normal detailed transaction
response should be generated.
Record(s) that conform to the schema of theinformation model described using the
DescribeRecord operation. Should be bound to
the CSW namespace.
Used to associate a mnemonic name for the
purpose of error handling.

Optionality

ISO App.-Profile

Boolean,default“FALSE”

Boolean, default“FALSE”
See description ofrequest.

Mandatory,
one or more

Mandatory, one or
more

Zero or one

Zero or one

1
2
3
4
5
6
7
8

Valid parameters for an update operation are specified in Table 20. An Update operation
may contain either a Record or a RecordProperty element to specify how to update therecord(s) delineated by the constraint. If a complete record instance is provided in therequest, the entire record in the catalogue will be replaced by the metadata record
contained within the Record element. If individual record property values are specified
using the RecordProperty element, then only those individual property values of thecatalogue record will be updated.

9
10
11
12
13

The RecordProperty element contains a Name element, specifying the name of the record
property to be updated, and a Value element, specifying the value to replace the existingvalue of the record property to be updated. The value of the Name element may be the
FGDC or equivalent element name or the XPath expression which identifies the FGDC
element, or the generic profile name for the element (See Table 2).
Table 20 - Parameters of Update Operation
KeywordTransactionType
REQUESTID

RECORD

Data Type & Value
CodeList
Value of “Update”
May be used by a client application toassociate a user-defined identifier with theoperation.
Complete record instance as Character String

Optionality

FGDC App.-Profile

Mandatory

Mandatory

Zero or one

Zero or one

Conditional

Conditional
Should be included
when“RecordProperty” is
not used.

44

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Keyword
VERBOSERESPONSE

Data Type & Value
May be used by a client to indicate to a server
the amount of detail to generate in the
response. A value of FALSE means that a
CSW should generate a terse or brieftransaction response. A value of TRUE, or theabsence of the attribute, means that the normal
detailed transaction response should be
generated.

Optionality

FGDC App.-Profile

Boolean,default“FALSE”

Boolean, default“FALSE”
Not used forTransactional
operations other thanInsert.

RECORDPROPERTY

A list of one or more property names with their Conditional
replacement values

Conditional
Should be included
when “Record” is not
used.

TYPENAMES

Character String

Zero or one

Zero or one of:Service, Dataset;
Dataset Collection,
Application

CONSTRAINTLANG
UAGECodeList“FILTER”

Must bespecifiedaccordingXML
encoding rules
for CSW 2.0

Must be specified
according XML
encoding rules for
CSW 2.0

CONSTRAINTLANGUAGEVERSION

StringMay be used to specify a version number
indicating which version of a specification theconstraint conforms to.

Mandatory

Not supported by thisprofile.

CONSTRAINT

Character String
The predicate expression specified in thelanguage indicated by the
CONSTRAINTLANGUAGE parameter.

Mandatory

Mandatory
Must be specified
according OGC
Filter 1.0.0 encoding
rules.

Zero or one

Zero or one

HANDLE

Used to associate a mnemonic name for the
purpose of error handling.

1
2
3

Table 21 specifies the parameters which are valid for a delete operation. All record
instances specified by the constraint will be affected by this operation.
Table 21 - Parameters of Delete Operation
KeywordTransactionType
REQUESTID

Data Type & Value
CodeList
Value of “Update”
May be used by a client application toassociate a user-defined identifier with theoperation.

Optionality

FGDC App.Profile

Mandatory

Mandatory

Zero or one

Zero or one

45

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

KeywordTYPENAMES

VERBOSERESPONSE

Data Type & Value
Character String

Optionality
Zero or one

Boolean, default
May be used by a client to indicate to a server“FALSE”
the amount of detail to generate in the
response. A value of FALSE means that a
CSW should generate a terse or brieftransaction response. A value of TRUE, or theabsence of the attribute, means that thenormal detailed transaction response shouldbe generated.

CONSTRAINTLANGU CodeList
AGE“FILTER”

Must bespecifiedaccording XML
encoding rules
for CSW 2.0

FGDC App.Profile
Zero or one of:Service, Dataset;
Dataset Collection,
Application
Boolean, default“FALSE”
Not used forTransactional
operations otherthan Insert.
Must be specified
according XML
encoding rules for
CSW 2.0

CONSTRAINTLANGU String
Mandatory
AGEVERSION
May be used to specify a version number
indicating which version of a specification theconstraint conforms to. For example, if“FILTER” is being used, this parameter could
be set to “1.0.0” indicating that the filter
conforms to version 1.0.0 of the Filter
Encoding Implementation Specification[OGC 02-059].

Not supported in
the profile.

CONSTRAINT

Mandatory.

Mandatory
Must be specified
according OGC
Filter 1.0.0
encoding rules.

Zero or one

Zero or one

HANDLE

String
The predicate expression specified in thelanguage indicated by the
CONSTRAINTLANGUAGE parameter.
Used to associate a mnemonic name for the
purpose of error handling.

1
Listing 13 - Transaction Request
2
3
4
5
6
7
8
9
10
11
12
13
14
15

<csw:Transaction service="CSW" version="2.0.1"
requestId="tOpi1" verboseResponse="false"><csw:Insert handle="insertop1"><csw:Record><metadata>...</metadata></csw:Record></csw:Insert><csw:Update handle="update1" typeNames="Any"><csw:RecordProperty><csw:Name>fgdc:pubdate</csw:Name><csw:Value>20040100</csw:Value></csw:RecordProperty><csw:Constraint><ogc:Filter>

46

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

CSW 2.0 FGDC CSDGM Application Profile<ogc:PropertyIsEqualTo><ogc:PropertyName>fgdc:recordID</ogc:PropertyName><ogc:Literal>10655dd:fe59c5225c:-7ffe</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></csw:Constraint></csw:Update><csw:Delete handle="delete1" typeNames="Any"><csw:Constraint><ogc:Filter><ogc:PropertyIsEqualTo><ogc:PropertyName>fgdc:recordID</ogc:PropertyName><ogc:Literal>10655dd:fe59c5225c:-7ffe</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></csw:Constraint></csw:Delete></csw:Transaction>

19
20

8.2.3.2.2 Response

21
22
23

The Transaction response reports a summary of the transaction by indicating the numberof records created, updated or deleted by the request and details the results of each Insert
operation in the InsertResult element of the response.

24
25
26

The InsertResult element only occurs if Insert operations were present in the request. If a
new record is inserted into the repository, this element will contain the newly created
identifier for the record.

27
28

The element <csw:AbstractRecord> of <TransactionResultType> must be substitutedby the brief result set specified in section 7.2.1.

29
Listing 14 – Transaction Response
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

<csw:TransactionResponse version="2.0.1"><csw:TransactionSummary requestId="14da8f4:feaff59c37:-7fff"><csw:totalInserted>1</csw:totalInserted><csw:totalUpdated>1</csw:totalUpdated><csw:totalDeleted>1</csw:totalDeleted></csw:TransactionSummary><csw:InsertResults handleRef="insertop1"><fgdc:BriefRecord><fgdc:publish>USGS</fgdc:publish><fgdc:pubdate>19630119</fgdc:pubdate><fgdc:title>USGS Inventory </fgdc:title><fgdc:recordID>14da8f4:feaff59c37:-7ffe</fgdc:recordID></fgdc:BriefRecord></csw:InsertResults></csw:TransactionResponse>

46
47

The handle attribute of an Insert request may be used to correlate the specific Insert
request instance with the related InsertResult element in the Transaction response.

47

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

8.2.4

Record locking

23This profile does not define a locking interface for the underlying data repository.
Instead, the repository is assumed to mediate concurrent access to catalogue records.

4

8.2.5

5
6
7
8
9
10
11
12
13

During a request which fails, due to improper formatting or run-time exceptions,
exception reports are generated and returned to the client. These reports comply with the
OGC Common specification definition of exception reports. In addition to thespecification, this profile defines an additional attribute for each exception generated. A
unique identifier is generated, according to UID standards, which is associated with thecurrent exception. This UID allows for easy referencing between requests and exceptions
as well as between the logged information for each exception in the different log files
maintained by this profile’s application. Table 22 lists valid exception codes supportedby this profile and their descriptions.

Error handling

Table 22 – OWS Common Exceptions
Exception CodeDescription of code“locator” value

OperationNotSupported

Request is for an operation that is not supported bythis server

Name of operation
not supported

MissingParameterValue

Operation request does not include a parameter value, Name of missing
and this server did not declare a default value for that parameterparameter

InvalidParameterValue

Operation request contains an invalid parametervalue aVersionNegotiationFailed

List of versions in “AcceptVersions” parameter value None, omit
in GetCapabilities operation request did not include“locator”
any version supported by this server
parameter

InvalidUpdateSequence

Value of (optional) updateSequence parameter in
GetCapabilities operation request is greater thancurrent value of service metadata updateSequencenumber

NoApplicableCode

No other exceptionCode specified by this service and None, omit
server applies to this exception“locator”
parameter

Name of parameterwith invalid value

None, omit
“locator”
parametera When an invalid parameter value is received, it seems desirable to place the invalid value(s) in
ExceptionText string(s) associated with the InvalidParameterValue value.

14
15

8.3

Query facilities

16
17
18
19
20
21

According to the CSW 2.0.1 specification, every catalogue service should support thecommon query language (CQL). The XML-encoded version of CQL, based on the OGC
Filter 1.0.0 specification, is supported by this profile. The plain-text encoding of thislanguage, referred to as CQL Text, is not supported because the OGC Filter specification
provides the same level of interoperability support in a formal, organized manner.
The following are supported by this profile:48

OGC 06-129r1
•
•
•

1
2
3
4
5
6
7
8
9

•

CSW 2.0 FGDC CSDGM Application Profile

All comparison operators
All logical operators
Expressions:o Property nameo Literal
Spatial operators:
o Intersect
o Disjoint
o BBOX

10

8.4

Security considerations

11
12
13
14

This profile does not discuss security issues with respect to data-sensitive operations,such as those in the CSWT interface. However, it is recommended that some level ofauthentication, such as HTTP Basic Authentication, be used to prevent unwanted accessto the CSWT interface.

49

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Appendix A[BW1](normative)

1
2
3
4

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

Abstract test suite

A.1

Read-only CSW
A.1.1 Basic CSW Client
A.1.1.1

Basic service elementsa) Test purpose: Verify that a CSW client satisfies therequirements for request parameter rules.
b) Test method: Generate an adequate sample of requests from theclient and verify that each is a valid request.
c) Reference: 8.1d) Test type: Basic

A.1.1.2

GetCapabilities Requesta) Test purpose: Verify that a CSW client satisfies all requirements
for a GetCapabilities request.
b) Test method: Generate an adequate sample of GetCapabilities
requests from the client and verify that each is a valid request.
c) Reference: 8.2.1.1d) Test type: Basic

A.1.1.3

GetRecords Requesta) Test purpose: Verify that a CSW client satisfies all requirements
for a GetRecords request.
b) Test method: Generate an adequate sample of GetRecords
requests from the client and verify that each is a valid request.
c) Reference: 8.2.2.1.1d) Test type: Basic

A.1.1.4

GetRecordById Requesta) Test purpose: Verify that a CSW client satisfies all requirements
for a GetRecordById request.
b) Test method: Generate an adequate sample of GetRecordById
requests from the client and verify that each is a valid request.
c) Reference: 8.2.2.2.1d) Test type: Basic

A.1.1.5

DescribeRecord Requesta) Test purpose: Verify that a CSW client satisfies all requirements
for a DescribeRecord request.
b) Test method: Generate an adequate sample of DescribeRecord
requests from the client and verify that each is a valid request.
50

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

CSW 2.0 FGDC CSDGM Application Profilec) Reference: 8.2.2.3.1d) Test type: Basic

A.1.1.6

GetDomain Requesta) Test purpose: Verify that a basic CSW client satisfies all
requirements for a GetDomain request.
b) Test method: Generate an adequate sample of GetDomain
requests from the client and verify that each is a valid request.
c) Reference: 8.2.2.4.1d) Test type: Basic

A.1.2 CSW Server
A.1.2.1

Version negotiationa) Test Purpose: Verify that a CSW server interface satisfies therequirements for version negotiation.
b) Test Method: Submit requests containing version number both
lower than and higher than the version supported by the server.
Verify that the server responses are in accord with the rules forversion negotiation.
c) Reference: 8.2.1.1d) Test Type: Basic

A.1.2.2

Request parameter rulesa) Test Purpose: Verify that a CSW server interface satisfies therequirements for request parameter rules.
b) Test Method: Generate a sample of requests from a client.
Include both invalid requests and valid request that vary within thelimits allowed by the rules. Verify that the server provides anappropriate response in each case.
c) Reference: 8.2.1d) Test Type: Basic

A.1.2.3

GetCapabilities responsea) Test Purpose: Verify that a basic CSW server interface satisfies
all requirements of the GetCapabilities operation.
b) Test Method: Make several GetCapabilities requests using avariety of input parameters. Verify that an appropriate response isreturned in each case.
c) Reference: 8.2.1.1d) Test Type: Basic

A.1.2.4

GetRecords responsea) Test Purpose: Verify that a basic CSW server interface satisfies
all requirements of the GetRecords operation.
b) Test Method: Make several GetRecords requests using a variety
of input parameters. Verify that an appropriate response is returnedin each case.

51

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

CSW 2.0 FGDC CSDGM Application Profilec) Reference: 8.2.2.1.2d) Test Type: Basic

A.2

A.1.2.5

GetRecordById responsea) Test Purpose: Verify that a basic CSW server satisfies all
requirements of the GetRecordsById operation.
b) Test Method: Make several GetRecordsById requests using avariety of input parameters. Verify that an appropriate response isreturned in each case.
c) Reference: 8.2.2.2.2d) Test Type: Basic

A.1.2.6

DescribeRecord responsea) Test Purpose: Verify that a basic CSW server interface satisfies
all requirements of the DescribeRecord operation.
b) Test Method: Make several DescribeRecord requests using avariety of input parameters. Verify that an appropriate response isreturned in each case.
c) Reference: 0d) Test Type: Basic

A.1.2.7

GetDomain responsea) Test Purpose: Verify that a basic CSW server interface satisfies
all requirements of the GetDomain operation.
b) Test Method: Make several GetDomain requests using a variety
of input parameters. Verify that an appropriate response is returnedin each case.
c) Reference: 8.2.2.4.2d) Test Type: BasicTransactional CSW
A.2.1 Client
A.2.1.1

Transaction requesta) Test Purpose: Verify that a CSW client satisfies all requirements
for a Transaction request.
b) Test Method: Generate an adequate sample of Transaction
requests from the client and verify that each is a valid request.
c) Reference: 8.2.3.1.1d) Test Type: Basic

A.2.1.2

Harvest requesta) Test Purpose: Verify that a CSW client satisfies all requirements
for a Harvest request.
b) Test Method: Generate an adequate sample of Harvest requests
from the client and verify that each is a valid request.
c) Reference:

52

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

CSW 2.0 FGDC CSDGM Application Profiled) Test Type: Basic

A.2.2 CSW Server
A.2.2.1

Transaction responsea) Test Purpose: Verify that a CSW server interface satisfies all
requirements for a Transaction operation.
b) Test Method: Make several Transaction requests using a variety
of input parameters. Verify that an appropriate response is returnedin each case.
c) Reference: 0d) Test Type: Basic

A.2.2.2

Harvest responsea) Test Purpose: Verify that a CSW server interface satisfies all
requirements for a Harvest operation.
b) Test Method: Make several Harvest requests using a variety of
input parameters. Verify that an appropriate response is returned ineach case.
c) Reference:d) Test Type: Basic

53

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Appendix B(informative)

1
2
3
4

Design rationale

5
6This section of the profile discusses decisions made during the design of a CSW 2.0.1compliant catalogue server, referred to as “CSW4FGDC”.

7

1. Information Model

89This section details the decisions made regarding support for an information model basedon FGDC metadata content.

10
11
12
13
14
15

1.1 The OpenGIS® Catalogue Implementation Service Specification (2.0.1) states that all
web services must support a common set of operations and operation parameters. It does
not, however, detail a mandatory set of metadata elements that must be supported.
Several implementations of the specifications have been based around the Dublin Core
(DC) set of elements, but this profile is designed to cover a catalogue service based on
FGDC elements.

16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

Despite the design for FGDC, this profile recommends any implementation of this design
support the inherent FGDC metadata elements as well as the equivalent DC elements asthey pertain to the supported FGDC elements. To overcome problems in mapping theelements of the two models to each other in a manner suitable for a catalogue service, thisprofile assumes that certain profile-specific elements may be created which serve as anintermediate mapping between FGDC and DC elements that do not directly map to eachother. For instance, DC defines a single-value element named “source” while FGDC
defines a set of compound elements named “source”. The proper mapping might be
dc:source to the “title” element defined within the fgdc:source element. However, this isconfusing with the fgdc:title element defined in the identification section of the record.
Therefore a new element designated “fgdc:source” is created to map dc:source to the title
element within fgdc:source. All requests for this element should be made using the“fgdc” qualification to ensure the proper values are extracted. Similar tactics should be
used with further information model discrepancies to ensure data integrity and metadata
content support.

31

2. Harvest Records

3233This section describes the decisions reached during the design of the harvest records
feature of CSW4FGDC.

34
35
36
37
38
39
40

2.1 The OpenGIS® Catalogue Implementation Service Specification (2.0.1) details theoptional usage of the verboseResponse attribute of the HarvestRecords operation to allow
for a “brief” or “summary” result set description of each record harvested as a result of
the harvest request. Because a harvest request can potentially affect several thousand
records, this profile omits the usage of a result set description for harvested records. The
normal description detailing the total number of harvested records is still required, but theuse of individual record descriptions is not recommended.

54

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

Appendix C(informative)

1
2
3
4

FEMA MapMod Catalog Implementation Notes

5
6
7
8
9

This appendix describes implementation decisions that were made in the design of the US
FEMA NFIP metadata catalog (accessible at
http://hazards.fema.gov/metadata/catalog/csw ) and the US NDEP and NDOP Tracking
System metadata catalog (accessible at http://hazards.fema.gov/metadata/ier/csw ). This
Appendix is intended to be informative to others who are implementing this profile.

10

C.1 Information Model

11
12

The following section describes issues that are a result of the inherent information modeland its mapping to the OGC Core sets of queryable and returnable elements.

13

C.1.1 Record Schemas

14
15
16
17
18
19

MapMod Catalog Server supports the OGC Core sets of queryable and returnable
elements as required by the OpenGIS® Catalogue Service Implementation Specification(2.0.1) (http://www.opengeospatial.org/standards/cat) and defined by the Specifications
record format schema, ‘record.xsd’. For FGDC metadata support, MapMod Catalog also
supports another version of this schema, ‘fgdc-record.xsd’, which defines alternative setsof returnable elements.

20

C.1.1.1 CSW:Record

21
22
23

OGC defines three result sets which must be supported by all Catalogue implementations.
The metadata elements contained in these result sets belong to the Dublin Core set of
metadata terms (http://dublincore.org/documents/dcmi-terms/).

24

C.1.1.2 FGDC:Record

25
26
27
28

MapMod Catalog Server defines alternative result sets to the three mandatory core sets.
The metadata elements contained therein belong to the FGDC metadata standard(http://www.fgdc.gov/metadata/csdgm/) and a set defined by the FGDC Application
Profile for CSW 2.0.

29

C.1.2 Unique Identifiers

30
31
32
33
34
35
36
37

The Dublin Core metadata term dc:identifier can potentially be used as the unique
identifier for records stored in the repository. However, there is no suitable mapping of
this DC term to an appropriate FGDC metadata term, so the unique identifier used by the
CSW Server is the primary key column in the repository's data table. This key isgenerated by the server during insert operations and is guaranteed to be unique with asuitable margin of error. See the section below for more details. Because of the need fora primary key, this implementation of the CSW Server assumes that all repository tables
will contain one primary key column and one XML metadata column.

55

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3
4
5

The ids generated by the system upon the insertion of records into the repository are
created using the Java™ UID class. This class generates unique keys by combining avirtual machine (VM) identifier, a long representation of the time during generation,
and a random number (to distinguish same-VM, same-time UIDs) to ensure that the key
is unique. See the Java™ 1.4.2 API Specification for more information on the UID class.

6

C.1.3 Bounding Coordinates

7
8
9
10

The FGDC element fgdc:bounding contains four sub-elements which represent
bounding coordinates. Unlike with the sub-elements of fgdc:keywords, these four subelements appear only once each in the XML metadata record. They must still be handled
differently than the rest of the metadata elements of the information model, though.

11
12
13

•

If the four coordinates are requested individually, each utilizes their associatedXPath expressions to extract the requested information in the same fashion as therest of the elements in the information model.

14
15
16
17
18

•

If the coordinates are requested through a single fgdc:bounding element request,
the XPath expression associated with this single element is used which contains
the XPath predicate symbol ‘*’ which identifies all sub-elements of the current
element at the next lowest level of the XML Document Object Model (DOM)
tree.

19
20

•

The resulting data returned from the query execution must be transformed tomatch the record schemas supported by this profile.

21

C.2 Compliance Issues

22
23
24

The following section describes any deviation by this profile from the OpenGIS®
Catalog Service Implementaiton Specification (2.0.1)(http://www.opengeospatial.org/standards/cat ).

25

C.2.1 Filter Support

26
27

The following sections describe the compliance of the MapMod Catalog Server
constraint language support.

28

C.2.1.1 CQL Text

29
30
31

OGC Filter, the XML-encoded version of CQL Text, provides a formal, organizedrepresentation of query constraints and should be used when constructing requests. CQL
Text is considered optional by this profile.

32

C.2.1.2 Function Operation

33
34

OGC Filter-based function operations are not supported by this profile as the FGDC
metadata elements assumed by this profile do not allow for function-based queries.

35

C.2.2 XPath Support

36
37

MapMod Catalog Server supports XPath expressions as references of queryable elements
in request files as per the OGC Filter Specifications 1.0.0 with a few exceptions:

38
39

•

Partial expressions (e.g., abbreviated relative location paths as per the OGC Filter
1.0.0 Specifications Document) are not supported by this profile. Relative
56

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

CSW 2.0 FGDC CSDGM Application Profile

location paths (RLPs) support requires the loading and maintenance of elementsof the FGDC information model which are not used by the discovery process(e.g., non-members of the core queryable/returnable sets). This leads toinefficient information model processing and therefore longer request processing
times. Because of this issue and the limited number of elements supported by thequeryable and returnable result sets of MapMod Catalog, this profile does notsupport the abbreviated relative location path requirement of the OGC Filter 1.0.0
Specification.
•

This profile assumes the use of namespaces for distinguishing elements of theinformation model (as in fgdc:title or the equivalent dc:title) but does
not assume the use of namespaces when processing XPath expressions (as in/metadata/idinfo/citeinfo/pubdate). The reason for this is because
the names of the elements can be similar across the FGDC and DC metadata
models (as in the case of the title element), but the XPath expression can only
map to the FGDC metadata element, and no two separate elements in the FGDC
metadata model share the same full XPath expression. Also, the records stored in
the repository are assumed to conform to the FGDC metadata schema, ‘fgdc-std001-1998-csw.xsd’, and that only FGDC metadata elements will be encounteredin the XML documents stored in the repository. If a mixed schema or
identification through DC XPath expressions were to be supported by the
MapMod Catalog Server, namespaces would be needed.

57

OGC 06-129r1
1
2
3
4

CSW 2.0 FGDC CSDGM Application Profile

Appendix D(normative)
Schemas and Sample XML Files

5

D.1 FGDC CSDGM Metadata

6

D.1.1 Schema for FGDC CSDGM

7
8

Refer to the full annotated XML schema defining FGDC metadata elements available at
http://www.csc.noaa.gov/metadata/xml/fgdc-std-001-1998-ann.zip.

9

D.1.2 Sample FGDC CSDGM metadata document

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

The following is an example of a valid FGDC CSDGM metadata record that validates tothe schema referenced above.
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><idinfo><citation><citeinfo><origin>Floodplain Mapping Program</origin><pubdate>20040901</pubdate><title>River Basin; 50 ft Hydrologically Corrected Digital
Elevation Model, September 2004</title><geoform>Framework-Elevation-Regular Grid</geoform><onlink>String</onlink><lworkcit><citeinfo><origin>String</origin><pubdate>2004</pubdate><title>2004-0001</title></citeinfo></lworkcit></citeinfo></citation><descript><abstract>50 ft Hydrologically Corrected Digital Elevation Model(DEM) in ASCII raster format. DEMs were developed from Light Detection andRanging (LIDAR) data acquired February through April 2003, with partial reflights for gap data in December 2003. Cell values in the Digital Elevation
Model were derived from a Triangulated Irregular Network (TIN) produced fromthe bare earth mass points and breaklines. Individual cell values are based on
an average of 25 points inside each 50 ft DEM cell. The data are organized in
10,000 ft x 10,000 ft tiles. Specific information about individual data tiles
is included in the data delivery index.
</abstract><purpose>THIS IS A SAMPLE METADATA RECORD THAT IN NO WAY
DESCRIBES ACTUAL GEOSPATIAL DATA</purpose></descript><timeperd><timeinfo><sngdate><caldate>2006</caldate></sngdate></timeinfo><current>String</current>58

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

CSW 2.0 FGDC CSDGM Application Profile</timeperd><status><progress>Complete</progress><update>String</update></status><spdom><bounding><westbc>-88.23211</westbc><eastbc>-87.89283</eastbc><northbc>41.13321</northbc><southbc>40.00134</southbc></bounding></spdom><keywords><theme><themekt>String</themekt><themekey>DEM</themekey><themekey>Elevation</themekey></theme><place><placekt>String</placekt><placekey>Lincoln County</placekey><placekey>String</placekey></place></keywords><accconst>Restricted</accconst><useconst>String</useconst><ptcontac><cntinfo><cntperp><cntper>String</cntper><cntorg>String</cntorg></cntperp><cntaddr><addrtype>String</addrtype><city>String</city><state>String</state><postal>String</postal><country>String</country></cntaddr><cntvoice>String</cntvoice><cntemail>String</cntemail></cntinfo></ptcontac><native>String</native></idinfo><dataqual><logic>String</logic><complete>String</complete><lineage><srcinfo><srccite><citeinfo><origin>String</origin><pubdate>2006</pubdate><title>String</title></citeinfo></srccite><typesrc>String</typesrc><srctime><timeinfo><sngdate><caldate>2006</caldate>59

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

CSW 2.0 FGDC CSDGM Application Profile</sngdate></timeinfo><srccurr>String</srccurr></srctime><srccitea>token1</srccitea><srccontr>String</srccontr></srcinfo><procstep><procdesc>String</procdesc><procdate>2006</procdate></procstep></lineage></dataqual><spdoinfo><direct>Point</direct><ptvctinf><sdtsterm><sdtstype>Point</sdtstype></sdtsterm><sdtsterm><sdtstype>Point</sdtstype></sdtsterm></ptvctinf></spdoinfo><spref><horizsys><planar><mapproj><mapprojn>Lambert Conformal Conic</mapprojn><lambertc><stdparll>0.0</stdparll><longcm>0.0</longcm><latprjo>0.0</latprjo><feast>0.0</feast><fnorth>0.0</fnorth></lambertc></mapproj><planci><plance>coordinate pair</plance><coordrep><absres>1.0</absres><ordres>1.0</ordres></coordrep><plandu>feet</plandu></planci></planar><planar><gridsys><gridsysn>State Plane Coordinate System 1983</gridsysn><spcs><spcszone>1000</spcszone><lambertc><stdparll>1</stdparll><longcm>1</longcm><latprjo>1</latprjo><feast>1</feast><fnorth>1</fnorth></lambertc></spcs></gridsys><planci><plance>coordinate pair</plance><coordrep>60

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

CSW 2.0 FGDC CSDGM Application Profile<absres>1.0</absres><ordres>1.0</ordres></coordrep><plandu>feet</plandu></planci></planar><geodetic><horizdn>String</horizdn><ellips>String</ellips><semiaxis>3.14159265358979</semiaxis><denflat>3.14159265358979</denflat></geodetic></horizsys><vertdef><altsys><altdatum>String</altdatum><altres>3.14159265358979</altres><altunits>String</altunits><altenc>Explicit elevation coordinate included with horizontal
coordinates</altenc></altsys></vertdef></spref><eainfo><detailed><enttyp><enttypl>Bare Earth Surface</enttypl><enttypd>String</enttypd><enttypds>String</enttypds></enttyp></detailed><overview><eaover>String</eaover><eadetcit>String</eadetcit></overview></eainfo><distinfo><distrib><cntinfo><cntperp><cntper>String</cntper><cntorg>String</cntorg></cntperp><cntaddr><addrtype>String</addrtype><address>String</address><city>String</city><state>String</state><postal>String</postal><country>String</country></cntaddr><cntvoice>String</cntvoice><cntemail>String</cntemail></cntinfo></distrib><distliab>String</distliab><stdorder><nondig>String</nondig><fees>String</fees></stdorder><stdorder><nondig>String</nondig><fees>String</fees>61

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

CSW 2.0 FGDC CSDGM Application Profile</stdorder></distinfo><distinfo><distrib><cntinfo><cntperp><cntper>String</cntper><cntorg>String</cntorg></cntperp><cntaddr><addrtype>String</addrtype><address>String</address><city>String</city><state>String</state><postal>String</postal><country>String</country></cntaddr><cntvoice>String</cntvoice><cntemail>String</cntemail></cntinfo></distrib><distliab>String</distliab><stdorder><nondig>String</nondig><fees>String</fees></stdorder></distinfo><metainfo><metd>20060101</metd><metc><cntinfo><cntperp><cntper>String</cntper><cntorg>String</cntorg></cntperp><cntaddr><addrtype>String</addrtype><address>String</address><city>String</city><state>String</state><postal>String</postal><country>String</country></cntaddr><cntvoice>String</cntvoice><cntemail>String</cntemail></cntinfo></metc><metstdn>String</metstdn><metstdv>String</metstdv><metextns><onlink>String</onlink><metprof>String</metprof></metextns><metextns><onlink>String</onlink><metprof>String</metprof></metextns></metainfo></metadata>

60
61

D.2 FGDC Application Profile Result Set Schemas
62

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1

This section describes the result sets defined by this profile.

2

D.2.1 Schemas

3
4

In the following sections, the schema fragments which define the various result sets forthis profile are listed.

5
6
7
8
9
10
11
12
13
14
15
16
17

D.2.1.1 Brief<xsd:complexType name="BriefRecordType" final="#all"><xsd:complexContent><xsd:extension base="csw:AbstractRecordType"><xsd:sequence><xsd:element ref="fgdc:recordID"/><xsd:element ref="fgdc:title"/><xsd:element ref="fgdc:metd"/><xsd:element ref="fgdc:publish"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>

18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

D.2.1.2 Summary<xsd:complexType name="SummaryRecordType" final="#all"><xsd:complexContent><xsd:extension base="csw:BriefRecordType"><xsd:sequence><xsd:element ref="fgdc:origin"/><xsd:element ref="fgdc:keywords"/><xsd:element ref="fgdc:abstract"/><xsd:element ref="fgdc:datacred"/><xsd:element ref="fgdc:direct"/><xsd:element ref="fgdc:formname"/><xsd:element ref="fgdc:source"/><xsd:element ref="fgdc:onlink"/><xsd:element ref="fgdc:bounding"/><xsd:element ref="csw:rights"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>

38
39
40
41
42
43
44
45
46
47
48

D.2.1.3 Full
<xsd:complexType name="FullRecordType" final="#all"><xsd:complexContent><xsd:extension base="fgdc:FGDCRecordType"><xsd:sequence><xsd:element ref="fgdc:recordID"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>49
50

D.2.2 Sample FGDC Result Sets

63

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

12This section provides sample records in the result set record format specified by thisprofile.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

D.2.2.1 Brief<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fed</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fee"
outputFormat="text/xml" outputSchema="fgdc:metadata" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="brief"><fgdc:BriefRecord><fgdc:title>River Basin; 50 ft Hydrologically Corrected Digital Elevation
Model, September 2004</fgdc:title><fgdc:publish /><fgdc:metd>20060101</fgdc:metd><fgdc:recordID>6cb4678f10807965a2bn8000</fgdc:recordID></fgdc:BriefRecord></csw:SearchResults></csw:GetRecordsResponse>

21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

D.2.2.2 Summary<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7ff1</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7ff2"
outputFormat="text/xml" outputSchema="fgdc:metadata" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="summary"><fgdc:SummaryRecord><fgdc:direct>Point</fgdc:direct><fgdc:abstract>50 ft Hydrologically Corrected Digital Elevation Model(DEM) in ASCII raster format. DEMs were developed from Light Detection andRanging (LIDAR) data acquired February through April 2003, with partial reflights for gap data in December 2003. Cell values in the Digital Elevation
Model were derived from a Triangulated Irregular Network (TIN) produced fromthe bare earth mass points and breaklines. Individual cell values are based on
an average of 25 points inside each 50 ft DEM cell. The data are organized in
10,000 ft x 10,000 ft tiles. Specific information about individual data tiles
is included in the data delivery index.</fgdc:abstract><fgdc:title>River Basin; 50 ft Hydrologically Corrected Digital Elevation
Model, September 2004</fgdc:title><fgdc:useconst>String</fgdc:useconst><fgdc:datacred /><csw:source>String</csw:source><csw:source>String</csw:source><fgdc:accconst>Restricted</fgdc:accconst><fgdc:keywords><fgdc:themekey>DEM</fgdc:themekey><fgdc:themekey>Elevation</fgdc:themekey><fgdc:placekey>Lincoln County</fgdc:placekey><fgdc:stratkey /><fgdc:tempkey /></fgdc:keywords><fgdc:publish /><fgdc:metd>20060101</fgdc:metd><fgdc:cntvoice1>String</fgdc:cntvoice1>

64

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13

CSW 2.0 FGDC CSDGM Application Profile<fgdc:bounding><fgdc:westbc>-88.2321</fgdc:westbc><fgdc:eastbc>-87.8928</fgdc:eastbc><fgdc:northbc>41.1332</fgdc:northbc><fgdc:southbc>40.0013</fgdc:southbc></fgdc:bounding><fgdc:origin>Floodplain Mapping Program</fgdc:origin><fgdc:onlink>String</fgdc:onlink><fgdc:recordID>6cb4678f10807965a2bn8000</fgdc:recordID><fgdc:formname /></fgdc:SummaryRecord></csw:SearchResults></csw:GetRecordsResponse>

14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

D.2.2.3 Full<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fef</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7ff0"
outputFormat="text/xml" outputSchema="fgdc:metadata" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="full"><fgdc:FullRecord><fgdc:recordID>6cb4678f10807965a2bn8000</fgdc:recordID><fgdc:FGDCRecord>
For space considerations full response not shown. Insert valid FGDC CSDGM
metadata content here (see clause D.1.2 above).
</fgdc:FGDCRecord></fgdc:FullRecord></csw:SearchResults></csw:GetRecordsResponse>

33
34

D.3 CSW Record Result Sets

35

This section describes the CSW “OGC Core” record format.

36

D.3.1 Schemas

37
38

In the following sections, the schema fragments which define the various result sets for
the OGC Core profile are listed.

39
40
41
42
43
44
45
46
47
48
49
50

D.3.1.1 Brief<xsd:complexType name="BriefRecordType"><xsd:complexContent><xsd:extension base="csw:AbstractRecordType"><xsd:sequence><xsd:element ref="dc:identifier" /><xsd:element ref="dc:type" /></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>65

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

D.3.1.2 Summary<xsd:element name="SummaryRecord" type="csw:SummaryRecordType"substitutionGroup="csw:AbstractRecord" /><xsd:complexType name="SummaryRecordType"><xsd:complexContent><xsd:extension base="csw:AbstractRecordType"><xsd:sequence><xsd:choice minOccurs="1" maxOccurs="unbounded"><xsd:element ref="dc:identifier" /><xsd:element ref="dc:type" /><xsd:element ref="dc:title" /><xsd:element ref="dc:subject" /><xsd:element ref="dc:format" /><xsd:element ref="dc:relation" /><xsd:element ref="dct:modified" /><xsd:element ref="dct:abstract" /><xsd:element ref="dct:spatial" /></xsd:choice></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>

24
25

D.3.1.1 Full

26
27
28

Full result sets are always returned in FGDC format. Refer to section D.2.1.3 for thisschema.

29

D.3.2 Sample CSW Record Result Sets

30

This section provides sample records in CSW result set record format.

31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

D.3.2.1 Brief<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7feb</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fec"
outputFormat="text/xml" outputSchema="csw:record" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="brief"><csw:BriefRecord><dc:type>Point</dc:type><dc:identifier>6cb4678f10807965a2bn8000</dc:identifier></csw:BriefRecord></csw:SearchResults></csw:GetRecordsResponse>

47
48
49

D.3.2.2 Summary<?xml version="1.0" encoding="UTF-8"?>

66

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

CSW 2.0 FGDC CSDGM Application Profile<csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fe9</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fea"
outputFormat="text/xml" outputSchema="csw:record" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="summary"><csw:SummaryRecord><dc:type>Point</dc:type><dct:abstract>50 ft Hydrologically Corrected Digital Elevation Model(DEM) in ASCII raster format. DEMs were developed from Light Detection andRanging (LIDAR) data acquired February through April 2003, with partial reflights for gap data in December 2003. Cell values in the Digital Elevation
Model were derived from a Triangulated Irregular Network (TIN) produced fromthe bare earth mass points and breaklines. Individual cell values are based on
an average of 25 points inside each 50 ft DEM cell. The data are organized in
10,000 ft x 10,000 ft tiles. Specific information about individual data tiles
is included in the data delivery index.</dct:abstract><dc:date>20040901</dc:date><dc:title>River Basin; 50 ft Hydrologically Corrected Digital Elevation
Model, September 2004</dc:title><dc:contributor /><dc:source>String</dc:source><dc:subject><fgdc:themekey>DEM</fgdc:themekey><fgdc:themekey>Elevation</fgdc:themekey><fgdc:placekey>Lincoln County</fgdc:placekey><fgdc:stratkey /><fgdc:tempkey /></dc:subject><dc:publisher /><dc:rights><fgdc:accconst>Restricted</fgdc:accconst><fgdc:useconst>String</fgdc:useconst></dc:rights><dc:modified>20060101</dc:modified><dct:spatial><fgdc:westbc>-88.2321</fgdc:westbc><fgdc:eastbc>-87.8928</fgdc:eastbc><fgdc:northbc>41.1332</fgdc:northbc><fgdc:southbc>40.0013</fgdc:southbc></dct:spatial><dc:creator>Floodplain Mapping Program</dc:creator><dc:relation>String</dc:relation><dc:identifier>6cb4678f10807965a2bn8000</dc:identifier><dc:format /></csw:SummaryRecord></csw:SearchResults></csw:GetRecordsResponse>

52
53
54
55
56
57
58

D.3.2.3 Full<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fe1</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus>

67

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12

CSW 2.0 FGDC CSDGM Application Profile<csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fe2"
outputFormat="text/xml" outputSchema="csw:record" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="full"><csw:FullRecord><csw:recordid>6cb4678f10807965a2bn8000</csw:recordid><fgdc:FGDCRecord>
For space considerations full response not shown. Insert valid FGDC CSDGM
metadata content here (see clause D.1.2 above).
</fgdc:FGDCRecord></csw:FullRecord></csw:SearchResults></csw:GetRecordsResponse>

13
14

D.4 GEO Result Sets

15
16

This section describes the record format specified by the GEO profile -http://www.blueangeltech.com/Standards/GeoProfile/geo22.htm .

17

D.4.1 Schemas

18
19

In the following sections, the schema fragments which define the various result sets for
the GEO profile are listed.

20
21
22
23
24
25
26
27
28
29
30

D.4.1.1 Brief<xsd:complexType name="BriefRecordType"><xsd:complexContent><xsd:extension base="csw:AbstractRecordType"><xsd:sequence><xsd:element ref="fgdc:title" /></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>

31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

D.4.1.2 Summary<xsd:complexType name="BriefRecordType"><xsd:complexContent><xsd:extension base="csw:AbstractRecordType"><xsd:sequence><xsd:element ref="csw:browse" /><xsd:element ref="fgdc:attrlabl" /><xsd:element ref="fgdc:geoform" /><xsd:element ref="csw:dsgpoly" maxOccurs="unbounded" /><xsd:element ref="fgdc:begdate" /><xsd:element ref="fgdc:enttypl" /><xsd:element ref="fgdc:keywords" /><xsd:element ref="fgdc:bounding" /><xsd:element ref="fgdc:pubdate" /><xsd:element ref="fgdc:purpose" /><xsd:element ref="fgdc:enddate" /><xsd:element ref="fgdc:extent" /><xsd:element ref="fgdc:onlink" /></xsd:sequence></xsd:extension>

68

OGC 06-129r1

CSW 2.0 FGDC CSDGM Application Profile

12</xsd:complexContent></xsd:complexType>3

D.4.1.3 Full

45

Full result sets are always returned in FGDC format. Refer to section D.2.1.3 for thisschema.

6
7

D.4.2 Sample GEO Result Sets

8This section provides sample records in GEO result set record format.

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

D.4.2.1 Brief<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm"
xmlns:geo="http://www.opengis.net/cat/csw/csdgm/geo" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fe5</csw:RequestId<csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fe6"
outputFormat="text/xml" outputSchema="geo:metadata" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="brief"><geo:BriefRecord><fgdc:title>River Basin; 50 ft Hydrologically Corrected Digital Elevation
Model, September 2004</fgdc:title></geo:BriefRecord></csw:SearchResults></csw:GetRecordsResponse>

25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

D.4.2.2 Summary<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm"
xmlns:geo="http://www.opengis.net/cat/csw/csdgm/geo" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fe7</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fe8"
outputFormat="text/xml" outputSchema="geo:metadata" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="summary"><geo:SummaryRecord><fgdc:pubdate>20040901</fgdc:pubdate><fgdc:enttypl>Bare Earth Surface</fgdc:enttypl><fgdc:enttypl>String</fgdc:enttypl><fgdc:enddate /><geo:extent>000000.3841</geo:extent><fgdc:dsgpoly><fgdc:dsgpolyo><fgdc:grngpoino><fgdc:gringlato /><fgdc:gringlongo /></fgdc:grngpoino></fgdc:dsgpolyo><fgdc:dsgpolyx><fgdc:grngpoinx><fgdc:gringlatx /><fgdc:gringlongx /></fgdc:grngpoinx>

69

OGC 06-129r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

CSW 2.0 FGDC CSDGM Application Profile</fgdc:dsgpolyx></fgdc:dsgpoly><fgdc:browse><fgdc:browsen /><fgdc:browsed /><fgdc:browset /></fgdc:browse><fgdc:geoform>Framework-Elevation-Regular Grid</fgdc:geoform><fgdc:purpose>THIS IS A SAMPLE METADATA RECORD THAT IN NO WAY DESCRIBESACTUAL GEOSPATIAL DATA</fgdc:purpose><fgdc:keywords><fgdc:themekey>DEM</fgdc:themekey><fgdc:themekey>Elevation</fgdc:themekey><fgdc:placekey>Lincoln County</fgdc:placekey><fgdc:stratkey /><fgdc:tempkey /></fgdc:keywords><fgdc:attrlabl /><fgdc:begdate /><fgdc:bounding><fgdc:westbc>-88.2321</fgdc:westbc><fgdc:eastbc>-87.8928</fgdc:eastbc><fgdc:northbc>41.1332</fgdc:northbc><fgdc:southbc>40.0013</fgdc:southbc></fgdc:bounding><fgdc:onlink>String</fgdc:onlink></geo:SummaryRecord></csw:SearchResults></csw:GetRecordsResponse>

30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

D.4.2.3 Full<?xml version="1.0" encoding="UTF-8"?><csw:GetRecordsResponse xmlns:csw="http://www.opengis.net/cat/csw"
xmlns:fgdc="http://www.opengis.net/cat/csw/csdgm"
xmlns:geo="http://www.opengis.net/cat/csw/csdgm/geo" version="2.0.0"><csw:RequestId>3df7c6fe:10e5c4d9348:-7fe3</csw:RequestId><csw:SearchStatus>complete</csw:SearchStatus><csw:SearchResults resultSetId="3df7c6fe:10e5c4d9348:-7fe4"
outputFormat="text/xml" outputSchema="geo:metadata" numberOfRecordsMatched="6"
numberOfRecordsReturned="1" nextRecord="2" ElementSetName="full"><geo:FullRecord><csw:recordid>6cb4678f10807965a2bn8000</csw:recordid><fgdc:FGDCRecord>
For space considerations full response not shown. Insert valid FGDC CSDGM
metadata content here (see clause D.1.2 above).
</fgdc:FGDCRecord></geo:FullRecord></csw:SearchResults></csw:GetRecordsResponse>70