COBWEB: Towards an Optimised Interoperability Framework for Citizen Science

®
Sponsored by Hosted by
Towards an OptimisedTowards an Optimised
Interoperability FrameworkInteroperability Framework
for Citizen Sciencefor Citizen Science
99th OGC Technical Committee
Dublin, Ireland
Ingo 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
®
StakeholdersStakeholders
Survey
Designer
Software
Developer
Software
Deployer
Data Collectors
Web Service
standards
Software
Cataloguer
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

OGC
®
Problem (mechanics)Problem (mechanics)
• Complex schema – whittle down to round peg, square peg.
• Extensions

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?

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

OGC
®
Typical Information ArchitectureTypical Information Architecture
<<ApplicationSchema>><<ApplicationSchema>>
XML-schemaXML-schema
ISO conceptual models
XML-schema
Softwareinstancesinstances
Comply with and reference
Validation, configuration
uses
imports
specialises
Use and/
or create
Custom
configuration

OGC
®
Typical Information ArchitectureTypical Information Architecture
XML-schema
uses
imports
specialises
Use and/
or create
Custom
configuration
XML (or other
platform)
UML

OGC
®
COBWEB SWE4CS: Citizen ScienceCOBWEB SWE4CS: Citizen Science
ProfileProfile
XML-schema
uses
imports
specialises
Use and/
or create
Custom
configuration
O&M
GFM
ISO
19103, 7, 15, 23
ISO
19103, 7, 15, 23
O&M XML
COBWEB Softwareinstancesinstances
Custom
configuration

OGC
®
COBWEB SWE4CS: Citizen ScienceCOBWEB SWE4CS: Citizen Science
ProfileProfile
XML-schema
uses
imports
specialises
Use and/
or create
Custom
configuration
WeedSurvey1
O&M4CS
ISO
19103, 7, 15, 23, 56
ISO
19103, 7, 15, 23,56
weedsurvey
COBWEB Softwareinstancesinstances
Custom
configuration

OGC
®
Typical Information Architecture - IssuesTypical Information Architecture - Issues
XML-schema
uses
imports
specialises
Use and/
or create
Custom
configuration
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)
XML-schema
instancesinstances
uses
Use and/
or create
Custom
configuration
Implementation profile
Content
description
Terminology
references
uses
Validation rules
Software

OGC
®
Architecture++ (reusable profiles)Architecture++ (reusable profiles)
INSPIRE-WQ
WMO-Chy
WQ
INSPIRE-WFS
WMO-Chy
SOS
Hydro-Profile of
SOS
WMO-Chy
WMS
WMO-Chy
Metadata
INSPIRE-WFS
WQ
INSPIRE
Service
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
®
““Best Practice” ArchitectureBest Practice” Architecture
XML-schema
instancesinstances
uses
Use and/
or create
Custom
configuration
Implementation profile
Content
description
Terminology
references
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 DCAT
DataCub
e
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

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 Simonis
Rob Atkinson
Open Geospatial Consortium
(Europe)
isimonis@opengeospatial.org

COBWEB: Towards an Optimised Interoperability Framework for Citizen Science

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (10)

Similar to COBWEB: Towards an Optimised Interoperability Framework for Citizen Science

Similar to COBWEB: Towards an Optimised Interoperability Framework for Citizen Science (20)

More from COBWEB Project

More from COBWEB Project (20)

Recently uploaded

Recently uploaded (20)

COBWEB: Towards an Optimised Interoperability Framework for Citizen Science