BEUTH Hochschule für Technik BERLIN(BHT Berlin) University of Applied Sciences

Reaching the Next Level: From Technical to Business Interoperability

Creative Commons like Licensing in Roaming Enabled SDIs (rSDI)

Global Spatial Data Infrastructure 11Rotterdam, 2009-06-17

Master Thesis:Ye FanghongIFGI WWU Münster

Supervisor:Prof. Dr.Roland M. WagnerBHT Berlin

BHT Berlin 2

Method of master thesis and this presentation

1. Introduction2. Problem Statement & Proposal:

1. A roaming enabled operation model2. Key adaption issues for SDI

1. License types2. Product types

3. Existing models as a research environment 1. Role model2. Process model3. Architecture model

4. Analysis focus currently on “find” in the publish-find-agree-bind1. Abstract roaming workflow and data2. Existing components (OGC, INSPIRE Catalogue and

Metadata specification, profiles and versions) and mapping5. Results

BHT Berlin 3

Method of master thesis and this presentation

1. Introduction2. Problem Statement & Proposal:

1. A roaming enabled operation model2. Key adaption issues for SDI

1. License types2. Product types

3. Existing models as a research environment 1. Role model2. Process model3. Architecture model

4. Analysis focus currently on “find” in the publish-find-agree-bind1. Abstract roaming workflow and data2. Existing components (OGC, INSPIRE Catalogue and

Metadata specification, profiles and versions) and mapping5. Results

SDI RoamingEC GI GIS 2006

Problem Statement: How to operate an SDI ?

„A VISA clearing house“

Supplier A

SupplierB

SupplierC

SupplierD

How to ensure user expected large coverage with limited capabilities, different legal environments and enough degree of freedoms for providers?

Adaption of the roaming operation model from other infrastructures (2006)

„A GSM clearing house“

Supplier A

SupplierB

SupplierC

SupplierD

Wagner: A Roaming-enabled SDI (rSDI): The Relationship between Technology and Market Presence, 12 th EC GI GIS Workshop, Innsbruck, Austria, 2006

Wagner: A Roaming-enabled SDI (rSDI): -Balancing interests, opportunities, investments and risks-, 9 th GSDI, Santiago, Chile, 2006

BHT Berlin 5

Supplier A

SupplierB

SupplierC

SupplierD

„THE Supplier“

„A clearing house“

Supplier A

SupplierB

SupplierC

SupplierD

Change the thinking!

Many GI players were used to operate a “monopoly” structure, this needed to be changed to enable cross-provider business interoperability

2.2. Key adaption issues for SDI

Product types

INSPIRE offers with the Annex I-III definitions (INSPIRE) SDI wide known product types and (hopefully) unique references.

License types

Creative Commons offers multiple license types and an unique reference by URI

Key preconditions for a roaming operation model (SDI) are network wide known product types and in the case of data with IPR common license types.

Since 2006….

BHT Berlin 7

Method of master thesis and this presentation

1. Introduction2. Problem Statement & Proposal:

1. A roaming enabled operation model2. Key adaption issues for SDI

1. License types2. Product types

3. Existing models as a research environment 1. Role model2. Process model3. Architecture model

4. Analysis focus currently on “find” in the publish-find-agree-bind1. Abstract roaming workflow and data2. Existing components (OGC, INSPIRE Catalogue and

Metadata specification, profiles and versions) and mapping5. Results

2.1. A roaming enabled operation model

BHT Berlin 8

Domain EndUser

AccountManager

Sales Delivery

SDI ServiceCustomer

SDI ServiceProvider

Advertiser

Domain SoftwareSupplier

DomainServiceProvider

SDICommittee

SDIAgency

SDI SoftwareSupplier

IPR Owner

Roles

Who ?

Home Provider

2.1. A roaming enabled operation model

BHT Berlin 9

SDI ServiceCustomer

SDI ServiceProvider

AdvertiserSales Delivery

AccountManager

Who ?

Roles

Legal Organizations

Home Provider

2.1. A roaming enabled operation model

BHT Berlin 10

SDI ServiceCustomer

SDI ServiceProvider

AdvertiserSales Delivery

AccountManager

VisitedProvider

SDI ServiceCustomer

SDI ServiceProvider

AdvertiserSales Delivery

AccountManager

unknownProvider

SDI ServiceCustomer

SDI ServiceProvider

AdvertiserSales Delivery

AccountManager

Roles

Legal Organizations

Multiple instances (home provider)Who ?

Home Provider

2.1. A roaming enabled operation model

BHT Berlin 11

SDI ServiceProvider

AdvertiserSales Delivery

AccountManager

VisitedProviderSDI Service

Provider

AdvertiserSales Delivery

AccountManager

SDI ServiceCustomer

Roles,

Legal Organizations

Multiple instances (home provider)

Which relationship (roaming, visited provider relationship)

Who ?

Home Provider

2.1. A roaming enabled operation model

BHT Berlin 12

SDI ServiceProvider

AdvertiserSales Delivery

AccountManager

VisitedProviderSDI Service

Provider

AdvertiserSales Delivery

AccountManager

SDI ServiceCustomer

Roles,

Legal Organizations

Multiple instances (home provider)

Which relationship (roaming, visited provider relationship)

Who ?

Define the roaming relationship more in detail together withexisting components:

Process Model

Architecture

How?

Overview of…

…existing Frameworks and Models

…the gap analysis

BHT Berlin 13

Tie

rs

Process Phases

AccountManager

Sales Delivery

SDI ServiceCustomer

SDI ServiceProvider

AdvertiserIPR Owner

Domain EndUser

SDI ServiceCustomer

SDI ServiceCustomer

Roles Model

Tie

rs

Process Phases

Da

taS

erv

ice

App

l.

Publish Find Agree Bind

AccountManager

Sales Delivery

SDI ServiceCustomer

SDI ServiceProvider

AdvertiserIPR Owner

Domain EndUser

SDI ServiceCustomer

SDI ServiceCustomer

Roles and Process Model

Tie

rs

Process Phases

Da

taS

erv

ice

App

l.

Publish Find Agree Bind

AccountManager

Sales Delivery

SDI ServiceCustomer

AdvertiserIPR Owner

Domain EndUser

SDI ServiceCustomer

SDI ServiceCustomer

Spatial Data Set

Applications and Geoportals

Register DataService Metadata

Data Set Metadata

GeoRMData

GeoRM Layers

Registers Discovery Service ViewService

InvokeSDService

DownloadService

Transf. Service

GeoRMService

SDI ServiceProvider

Roles, Process and Architecture Model

BHT Berlin 17

Method of master thesis and this presentation

1. Introduction2. Problem Statement & Proposal:

1. A roaming enabled operation model2. Key adaption issues for SDI

1. License types2. Product types

3. Existing models as a research environment 1. Role model2. Process model3. Architecture model

4. Analysis focus currently on “find” in the publish-find-agree-bind1. Abstract roaming workflow and data2. Existing components (OGC, INSPIRE Catalogue and

Metadata specification, profiles and versions) and mapping5. Results

Tie

rs

Process Phases

Da

taS

erv

ice

App

l.

Publish Find Agree Bind

SDI ServiceCustomer

Advertiser

SDI ServiceCustomer

Spatial Data Set

Applications and Geoportals

Register DataService Metadata

Data Set Metadata

GeoRMData

GeoRM Layers

Registers Discovery Service ViewService

InvokeSDService

DownloadService

Transf. Service

GeoRMService

SDI ServiceProvider

This thesis focus only on the find phase

Data Set Metadata

Tie

rs

Process Phases

Da

taS

erv

ice

App

l.

Find

SDI ServiceCustomer

Advertiser

SDI ServiceCustomer

Applications and Geoportals

Service Metadata

Data Set Metadata

Discovery ServiceSDI Service

Provider

http://creativecommons.org/licenses/by-nc-sa/3.0/

<GetRecord..<….

On interface, schema and codelist level

Operations:

BHT Berlin 20

ISO19119

ISO19139

…with multiple profiles

Currently the many different catalogue / discovery service specification are defined and partly in use.

Therefore a dimension in the analysis were different CS-W * specifications

For the meta data model the existing ISO 19915 / 19139 was used together with the INSPIRE IR.Some data field names needed to be adapted with a slightly different meaning (e.g. distributor vs. provider). Also the xlink arc role attributedwas used to assign the partnerships

ISO19119

ISO19139

ISO19119

ISO19139

Discovery ServiceINSPIRE Profile

OGC CS-W2.0.2

Free Filter Encoding(WFS like)

Tie

rs

Process Phases

Da

taS

erv

ice

App

l.

Find

SDI ServiceCustomer

Advertiser

SDI ServiceCustomer

Applications and Geoportals

Service Metadata

Data Set Metadata

RM Layers

Discovery ServiceSDI Service

Provider

This thesis focus only on the find phase

Roaming RM Client Layers

Client side needs to know which home provider he has.Therefore the client side gets a RM Layer. This layer can be compared to the function of a GSM SIMcard.

For the find phase only the homeprovider (ID) needs to be stored and added to the request.

Depending on the CSW profile also additional logic needs to be executed in this Client RM/roaming layer.

BHT Berlin 22

Method of master thesis and this presentation

1. Introduction2. Problem Statement & Proposal:

1. A roaming enabled operation model2. Key adaption issues for SDI

1. License types2. Product types

3. Existing models as a research environment 1. Role model2. Process model3. Architecture model

4. Analysis focus currently on “find” in the publish-find-agree-bind1. Abstract roaming workflow and data2. Existing components (OGC, INSPIRE Catalogue and

Metadata specification, profiles and versions) and mapping5. Results

Key results

BHT Berlin 23

Although the knowledge of the home provider needs to be added in all cases at the client side ( a la simcard ), the INSPIRE IR for Metadata and Discovery service can be used for the roaming model without any implementation modifications.

Detailed results: Ye Fanghong,2009: Adaptation of the Creative Commons Approach and the Roaming Concept to Spatial Data Infrastructures (SDI), Master Thesis, Institute for Geoinformatics, University of Münster. Supervisor Prof. Dr. Wagner

Another thesis focuses on the overall process model and in detail on the “agree” phase. Results expected in August 2009

Conclusion

Operation ModelsCentered Business Operation Model (a la e-commerce)Roaming Operation to introduce

seamless business and technical interoperability CompetitionBalancing of risks, investments and opportunities

Gap analysis with existing components in the “find” phasePositive, no specification/implementation change needed

Planed gap analysis for the “agree” and later “bind” phase

BHT Berlin 24