COBWEB: Towards an Optimised Interoperability Framework for Citizen Science

®

Sponsored by Hosted by

Towards an Optimised Towards an Optimised Interoperability Framework Interoperability Framework

for Citizen Sciencefor Citizen Science99th OGC Technical Committee

Dublin, IrelandIngo Simonis, Rob Atkinson (OGC-Europe)

21 June 2016

Copyright © 2016 Open Geospatial ConsortiumCopyright © 2016 Open Geospatial Consortium

OGC®

AgendaAgenda

• Context• Concepts• Collaboration and Resources

Copyright © 2016 Open Geospatial Consortium

OGC®

Stakeholders Stakeholders

Copyright © 2016 Open Geospatial Consortium

SurveyDesigner

SoftwareDeveloper

SoftwareDeployer

Data Collectors

Web Service

standards

SoftwareCataloguer

Funders System Architect

Users

System of systems

OGC®

ProblemProblem

• “Citizen Science Observations” – interoperability thereof• What does interoperability actually mean?

– And is it the same for all stakeholders?

• Current best practices:– Specialise a schema (WaterML2.0) – Write a profile document for a generic standard (NetCDF-CF, Hydro

profile of SOS, INSPIRE metadata profile)– These are all high burden for all stakeholders – and the machine-

readable parts are not very expressive– OGC Modular Specification – more expressive but document centric

• We cannot expect Citizen Scientists – or their communities of practice – to manage this – not scalable

Copyright © 2016 Open Geospatial Consortium

OGC®

Problem (mechanics)Problem (mechanics)

• Complex schema – whittle down to round peg, square peg.• Extensions

Copyright © 2016 Open Geospatial Consortium

OGC®

We have a patternWe have a pattern

• “Modular specification”• == class/interface hierarchies• Software tools handle these seamlessly.• Can we make this easily accessible to stakeholders in the

interoperability chain?

Copyright © 2016 Open Geospatial Consortium

OGC®

• What are the key things we need to express better?– Nature of things

• OWL, RDFS– Content – domain, range, granularity and subsetting

• SKOS,RDF-QB– Aggregation of data into sets, and binding of interfaces to these

• VoiD– Derivation (procedure parameters?)

• PROV

Copyright © 2016 Open Geospatial Consortium

OGC®

Typical Information ArchitectureTypical Information Architecture

<<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

Softwareinstances

Comply with and reference

Validation, configuration

uses

importsspecialises

Use and/or create

Customconfiguration

OGC®

Typical Information ArchitectureTypical Information Architecture

<<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

Softwareinstances

Comply with and reference

Validation, configuration

uses

importsspecialises

Use and/or create

Customconfiguration

XML (or other platform)

UML

OGC®

COBWEB SWE4CS: Citizen Science COBWEB SWE4CS: Citizen Science ProfileProfile

<<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

Softwareinstances

Comply with and reference

Validation, configuration

uses

importsspecialises

Use and/or create

Customconfiguration

O&M

GFM

ISO19103, 7, 15, 23

ISO19103, 7, 15, 23

O&M XML

COBWEB SoftwareinstancesCustom

configuration

OGC®

COBWEB SWE4CS: Citizen Science COBWEB SWE4CS: Citizen Science ProfileProfile

<<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

Softwareinstances

Comply with and reference

Validation, configuration

uses

importsspecialises

Use and/or create

Customconfiguration

WeedSurvey1

O&M4CS

ISO19103, 7, 15, 23, 56

ISO19103, 7, 15, 23,56

weedsurvey

COBWEB SoftwareinstancesCustom

configuration

OGC®

Typical Information Architecture - IssuesTypical Information Architecture - Issues

<<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

Softwareinstances

Comply with and reference

Validation, configuration

uses

importsspecialises

Use and/or create

Customconfiguration

general schemas: lots of config /

highly specialized schemas

no relationship between diff. schemas

schema only: no means to define content rules

OGC®

Architecture+ (+content) Architecture+ (+content) <<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

instances

Comply with and reference

uses

Use and/or create

Customconfiguration

Implementation profile

Contentdescription

Terminologyreferences

uses

Validation rules

Software

OGC®

Architecture+ (+content) Architecture+ (+content) <<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

instances

Comply with and reference

uses

Use and/or create

Customconfiguration

Implementation profile

Contentdescription

Terminologyreferences

uses

Validation rules

Software

OGC®

Architecture++ (reusable profiles) Architecture++ (reusable profiles)

INSPIRE-WQ

WMO-ChyWQ

INSPIRE-WFS

WMO-ChySOS

Hydro-Profile ofSOS

WMO-ChyWMS

WMO-ChyMetadata

INSPIRE-WFSWQ

INSPIREService

Irish WQ SOS

Irish SDI

Irish WQ WMS

INSPIRE-WMS

Final profile typically binds

custodian, Technical

Standards and target context.

Service.implements(INSPIRE-WMS) = True

Profile.getServices()

OGC®

OGC®

““Best Practice” ArchitectureBest Practice” Architecture<<ApplicationSchema>>

<<ApplicationSchema>>

XML-schema

ISO conceptual models

XML-schema

instances

Comply with and reference

uses

Use and/or create

Customconfiguration

Implementation profile

Contentdescription

Terminologyreferences

uses

Validation rules

Software

Terminology reusable

defines how to populate a schema

software works against small number of schema

patterns

data products: improved discovery, many impl.

options

OGC®

Rules(Reasoning)

RDF-IO

SKOS VOID DCATDataCube

DJANGO Admin UI DJANGO Custom UI (e.g. Wizards)

UML->OWL

Apps

Proof-of-concept ArchitectureProof-of-concept Architecture

Typical content management platform

W3C standards

ISO/OGC standards

LinkedDataAPI

Open source modules for W3C standards

OGC®

StatusStatus

• Initial capabilities deployed…– Open source

• Refining and populating with real data for COBWEB Use Cases

• Development of client software to demonstrate potential• Full Proof-of-concept at Orlanda• Best Practices documents in preparation:

– Multiple stakeholder view of interoperability value chain– Profile methodology– COBWEB/Citizen Science BP for O&M

Copyright © 2016 Open Geospatial Consortium

OGC®

Thank you very much!Thank you very much!

All research presented herein is supported by the European Commission through grant agreement 308513.

Dr. Ingo SimonisRob Atkinson

Open Geospatial Consortium (Europe)

isimonis@opengeospatial.org