Geographic Information Geomatics Data Management Services Geographic Standards ISO TC211 Geographic Information Geomatics ISO/IEC JTC1 SC32 Data Management Services

Presentation Outline Statistical Office Viewpoint Interoperability Goals Standards Overview The Geo-thematic Bridge Summary

Pyramid of Standards-based Applications Finding Time, Place, Theme, Focus Assessing Relevance, Quality, Cost, Timeliness, Concepts, Methods, Sources, This next slide serves to broaden the discussion to encompass the viewpoint of information users. The “need to find” and the “need to assess” layers of Boyko’s Hierarchy of Information Needs are served by the provision of meta-information. The “need to use” is served by the provision of metadata. Note, however, that this implies that descriptions that define the human (meta-information) perspective must be tightly coupled to the descriptions that drive the technology. This coupling must be “by design and construction” rather than by supposition to enable the valid production of user-defined, on-demand information products and services. The “need to manage” is the supporting bedrock of Boyko’s Hierarchy. This requires the application of sound information life cycle management practices to the underlying information assets. Using Classifications, Questionnaires, Codebooks, Dictionaries, Database Schemas, Record Layouts Managing Harmonization, Integration, Creation, Preservation, Retention, Disposal

Interoperability Goals Increase data use and reuse. Reduce costs for data collection and integration. Reduce cost for data maintenance and management. General increases in efficiency.

Enabling Interoperability Client-server single database applications Stovepipes Data tran sfer and warehousing Connectivity Data sharing within broad subject areas Inter- Connectivity Enterprise-wide system and data integration Inter- Operability Implementation continuum Enterprise view Application

The Back-end Systems………. Collection and Production Clean Data RealTime Data “Refined” Source Data Meta Stuff Data Products Source Data

The Front-end Systems…. Management & Access Application & Access Tools Visualization Tools GIS Tools Web Browser “Refined” Source Data Meta Stuff Data Products RealTime Data Spatial Data Technology Open Interface Flexible Architecture Expandable Neutral Rapid Access Easy Interfaces & Protocols

Key Issue for building the “Interoperable Systems” Preserve the investment in the existing data - GIS databases, CAD drawings, imagery, raster data, etc…..

SIG GIS OGDI ICDG WWW CGDI DIGEST NSDI CORBA TCP/IP IIOP ISO/TC211 FGDC SIG OGDI CGDI TCP/IP SAIF ICDG XDR RPC ISO/TC211 DIGEST OGIS GIS RDA NSDI SDTS DXF HTML CORBA HTTP IIOP Standards Fatigue WWW

International Standards: Agreement on the present… A Strategy for the Future Physical Level: Database Schema ISO SQL3 & SQL/MM Common Language Common Data Model Common Spatial Functions Repository, Dictionary & ADT Support APIs (OGDI/CLI/ RDA) Application Level: User-defined View OGIS Simple Feature SQL JAVA & OLE/DB COM/CORBA Compliance Services Interfaces Conceptual Level: Subject Area Model Logical Information ISO TC211 Common Meta -Model Spatial Features & Operators Modelling Methods -Information Services Definition

ISO/TC 211 organization Framework and reference model Olaf Østensen Chairman WG 1 WG 4 WG 2 WG 3 WG 5 Christopher Morten Ken Bullock Les Rackham Kees Wevers Dabrowski Borrebæk Australia UK Netherlands USA Norway Framework and reference model Geospatial models and operators Geospatial data administration Geospatial services Profiles and functional standards 5

JTC 1 Organizational Chart ISO JTC 1 IEC JTC 1 Organizational Chart Technical Directions JTC 1 Subcommittees & Working Groups Rapporteur Groups Business Teams Imaging Electronic Commerce Conformity Assessment (ANSI) Global Information Infrastructure (NSAI) Registration Authorities (ANSI) Coded Character Sets SC 2 - Coded Character Sets (JISC) Data Capture and Identification Systems SC 17 - Identification Cards & Related Devices (BSI) SC 31 - Automatic Identification & Data Capture Techniques (ANSI) Data Management Service SC 32 - Data Management Services (ANSI) Distributed Application Services SC 33 - Distributed Application Services (ANSI) Document Description Languages JTC 1/WG 4 - Document Description Languages (ANSI) Information Interchange Media SC 11 Flexible Magnetic Media for Digital Data Interchange (ANSI) SC 23 - Optical Disk Cartridge for Information Interchange (JISC) IT Terminology SC 1 - Vocabulary (AFNOR) Multimedia and Representation SC 24 - Computer Graphics and Image Processing (BSI) SC 29 - Coding of Audio, Picture, Multimedia and Hypermedia Information (JISC) Networking & Interconnects SC 6 - Telecommunications and Information Exchange Between Systems (ANSI) SC 25 - Interconnection of Information Technology Equipment (DIN) SC 26 - Microprocessor Systems (JISC) Office Equipment SC 28 - Office Equipment (ABNT) Programming Languages & Software Interfaces SC 22 -Programming Languages, Their Environments and Systems Software Interfaces (ANSI) Security SC 27 - IT Security Techniques (DIN) Software Engineering SC 7 - Software Engineering (SCC) User Interfaces JTC 1/WG 5 - User Interfaces (BSI) As of 22 October 1997. This chart is subject to revision. 1

Level Pair schema database Type Level Pair Instance Defines and Controls schema database Concept #1, Level Pair, (Operational Context) The schema, together with the database, is referred to as a “level pair”. The schema acts as an active dictionary, controlling data manipulation operations on the contents of the database. A schema, or model, is created using the schema definition facilities of the database language SQL ( create table, create column, etc.). Component of the database schema are described in terms of types. A data type is a set of representable values. Instances of data in the database conform to the data type specification (e.g., Numeric, Decimal, Integer, Float, Real, etc.). These predefined types can be supplemented by user-defined, abstract data types. Now let’s look at Concept #2, Interlocking Level Pairs: 10 10 10 10

Interlocking Level Pairs database-1 schema-1 database-2* schema-2 Defines and Controls Level Pair Level Pair Concept #2, Interlocking Level Pairs (ties operational and design contexts together) Interlock occurs when application schema-1 in database-2 (source form) is exported to the operational context and activated (object form). In practice, this interlock is established when the results of design are moved to the operational context (original design or maintenance revision). Now, Concept #3, Recursive Interlocking Level Pairs *database-2 contains a representation of schema-1 11 11 11 11

Recursive Interlocking Level Pairs database-1 database-2 database-3 schema-1 schema-2 schema-3 Tying it all together, the “three step” The interlocking process can be repeated, recursively as shown above. The RMDM allows N levels of recursion. The IRDS framework fixes N at three, having four levels, 3 interlocking level pairs and two interlocks. Now, a more concrete example, 12 12 12 12

Extending the Level Pair: Data, Metadata and Meta-Information cross- references Metadata (database schema) Meta-Information (web document) illustrates and explains defines and controls The Extended Level Pair: Includes three components linked by three relationships: Components: Meta-Information, metadata, data. Relationships: Describes, Cross-references and Controls Meta-Information (sometimes called Business Metadata): Human-oriented, multi-media, multi-lingual structured static or dynamic electronic document. Supports interpretation of database content through the describes relationship. Metadata (sometimes called technical metadata): Machine-oriented database schema. Support database integrity through the controls relationship. Meta-Information (meaning and use) is tied to metadata (access and computation ) through the cross-reference relationship Now let’s assemble the building blocks Database 20 20 20 20

Building the Geo-Thematic Bridge: the Geographic Abutment Geographic Policy and Standards Context Geographic Design and Maintenance Geographic Operational Object Type Association Definition Schema Level Dictionary Application Record Field Value Field in Value in Admin Area Name Pop Count Prov Ont Que Admin Area Record Type 8888 9999 This slide is a cross-sectional view of the IRDS Staircase, showing content for a simple geographic example. 2/16/2019

Building the Geo-Thematic Bridge: the Thematic Abutment Thematic Policy and Standards Context Thematic Design and Maintenance Thematic Operational Object Type Association Definition Schema Level Dictionary Application Record Field Value Field in Value in Person Age Sex Marital Status Single Married Person Record Type M F Integer Male Female 32 28 This is the equivalent slide for the thematic abutment. 2/16/2019

Building the Geo-Thematic Bridge: The Policy and Standards Keystone This slide shows the geo-thematic bridge supported by the geographic and thematic abutments. Note that the geographic and thematic abutments are linked by common Information Management and Technology Management standards and policies. The Statistics Canada Common Databases and Metadata Working Group serves as the forum for IM/IT as well as geo-thematic bridging. 2/16/2019

Summary Client Oriented Applications Interoperability Standards Finding, Assessing, Using and Managing Interoperability Registers first (Geography/Business, etc.) Standards Content/Containers/Carriers The Geo-thematic Bridge Harmonize, then integrate

Geographic Information Geomatics SQL Multimedia Spatial Geographic Standards ISO TC211 Geographic Information Geomatics ISO IEC JTC1 SC32 SQL Multimedia Spatial