Functional Requirements Specification

From DigiRepWiki

Scope

The document offers a functional requirements specification for the Geospatial Application Profile. An analysis of the community served by the profile and an indication of the methodologies used are also included.

From the JISC specification for the work:

• Metadata:
  • In scope: DC elements plus any additional elements necessary
  • Out of scope: other metadata standards

• Identifiers:
  • In scope: Examine how identifiers could be used with geospatial data

• Domain for DC coverage (spatial and temporal) :
  • In scope: Preference for spatial reference system domain, geometry and temporal domain to be used to define the scope of data

• Controlled vocabularies (subject classification, name authority, etc):
  • In scope: Ensuring the application profile is hospitable to the use of a variety of subject access solutions e.g. classification schemes, controlled vocabularies, name authority lists
  • Out of scope: decisions on terminology solutions

• Additional search entry points e.g. Repository of origin
  • In scope: inclusion of properties required to fulfil other search requirements such as institution of origin, research funder, national and regional views. These requirements need to be mapped with the Intute Repository Search.

• XML Schema – In scope: how would an XML Schema work with the metadata provided with the geospatial data??

• Archival Requirements.

Methods

A 'strawman' document will be developed that will attempt to harmonise DC and broader community (Open Geospatial Consortium (OGC)) worldviews. This strawman will be reviewed by the working group and by a broader community of interest in order that the developed profile is sufficiently future proofed and consistent with both the traditional repository community and the geo-specific community.

Community

The 'community' consists of both the narrower 'geo' specific community of interest (in practice those consumers of existing geospatial resources and services e.g. Digimap, SIDS, AHDS,UKBORDERS)as well as the broader digital library repository community (typified by those with interests in pre and post print journal articles). The geo community tends to be more focused on data hence the Application Profile is geared more towards geospatial data (as popularly) defined by that community, rather than the broader application of the term. That is to say, in the first instance GAP is concerned more with geospatial artifacts/datasets per se rather than on geospatially-enabling all resource descriptions.