Incorporation of an ISO Feature Catalogue in CSW ebRIM Dr Kristin Stock Social Change Online, UK and Centre for Geospatial Science University of Nottingham

Introduction Work completed under the EU funded MOTIIVE project. Added an ISO Feature Type Catalogue to an ebRIM Registry. Used the ebRIM Application Profile for CSW (WRS). Created an extension package.

What is Motiive? Marine Overlays on Topography for Annex II Valuation and Exploitation. Examined cost-benefit of using non- proprietary standards for data harmonisation. Marine domain. FTC Registry one part of the larger Motiive project.

Main Partners (FTC) Social Change Online: registry architecture, mapping, information model (Kristin Stock, Rob Atkinson). EDINA: implementation of registry (Chris Higgins, Mark Small). Science and Technology Facilities Council: content, web services (Andrew Woolf). HR Wallingford: web services, project management (Keiran Millard).

What is an ISO Feature Type Catalogue? A model for storing Feature Types and their: Attributes; Operations; Associations. Provides semantic content for data. Includes inheritance between FTs. Links attributes and operations.

Mapping to ebRIM (1) Classes from ISO mapped to specialisations of: ExtrinsicObject; Association; RegistryPackage. Attributes from ISO mapped to: ebRIM attributes where possible or ebRIM Classification Schemes or ebRIM Slots. Relationships from ISO mapped to: ebRIM Associations with specified AssociationType; Some required additional attributes.

Mapping to ebRIM (2) Used ebRIM data types. The application profile (extension package) document contains full details of the mapping from each ISO element. Draft: acts/staffPages/kristinstock/documents/07- xxx_FTC_Extension_Package_for_ebRIM_ ISOTS_ _Profile_of_CSW_2.0.2_v0.1.doc acts/staffPages/kristinstock/documents/07- xxx_FTC_Extension_Package_for_ebRIM_ ISOTS_ _Profile_of_CSW_2.0.2_v0.1.doc

Creating the Information Model (1) New classes: Extend the canoncial ObjectType Classification Scheme; New nodes under ExtrinsicObject; Handles inheritance. Instances of existing classes: Specialisations of non-ExtrinsicObject classes; For example, ebFC_Catalogue. Instances of associations.

Creating the Information Model (2) Attributes that are classifications: New classification schemes; Slots: Used ebRIM slots where possible; Used WRS slots where possible; New slots in the Slots ClassificationScheme; New Association Types: New types in the AssociationType ClassificationScheme.

Association Types Used mainly existing ebRIM association types (RelatedTo, EquivalentTo, AffiliatedWith, Implements) to represent semantic relationships; Added some new associations: between attributes and operations (TriggeredBy, Affects, Observes); PropertyOf, SubTypeOf… Recommend the creation of an AssociationType hierarchy for spatial relationships.

Stored Queries Predefined queries for the extension package; Added as Adhoc Queries (ebRIM); Some need to be called recursively (e.g inheriting and implementing).

Inheritance Project sought to demonstrate how FTs could inherit from each other. Inherit: Attributes Operations Associations. Types of inheritance: is a = SubTypeOf; behaves like = Implements (multiple inheritance, for common characteristics).

Abstract Test Suite (1) Test cases for each class. Combined test modules for subsets of classes.

Abstract Test Suite (2)

Extension Package Insert Created a WRS Transaction Insert statement to add the definitions to the registry: RegistryPackage; Classification Nodes for new classes; Classification Nodes for new association types; Classification Nodes for new slots; Stored queries.

Example Data Extension Package includes some example feature types.

Issues/Recommendations (1) Model for associations in ISO very rich and expressive, but complicated and difficult to understand and implement.

Issues/Recommendations (2) ISO makes relationships and operations dependent on a FT – but sometimes it may be desirable to model them separately.

Issues/Recommendations (3) ebRIM + WRS does not allow slots to be constrained to define which slots are allowed for a particular class.

Issues/Recommendations (4) Need for hierarchy of spatial association types.

Questions or Comments?