1. 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 11 Rotterdam, 2009-06-17 Master Thesis: Ye Fanghong IFGI WWU Münster Supervisor: Prof. Dr. Roland M. Wagner BHT Berlin

2. BHT Berlin 2 Method of master thesis and this presentation 1. Introduction 2. Problem Statement & Proposal: 1.A roaming enabled operation model 2.Key adaption issues for SDI 1.License types 2.Product types 3.Existing models as a research environment 1.Role model 2.Process model 3.Architecture model 4.Analysis focus currently on “find” in the publish-find-agree-bind 1.Abstract roaming workflow and data 2.Existing components (OGC, INSPIRE Catalogue and Metadata specification, profiles and versions) and mapping 5.Results

3. BHT Berlin 3 Method of master thesis and this presentation 1. Introduction 2. Problem Statement & Proposal: 1.A roaming enabled operation model 2.Key adaption issues for SDI 1.License types 2.Product types 3.Existing models as a research environment 1.Role model 2.Process model 3.Architecture model 4.Analysis focus currently on “find” in the publish-find-agree-bind 1.Abstract roaming workflow and data 2.Existing components (OGC, INSPIRE Catalogue and Metadata specification, profiles and versions) and mapping 5.Results

4. SDI Roaming EC GI GIS 2006 Problem Statement: How to operate an SDI ? „A VISA clearing house“ Supplier A Supplier B Supplier C Supplier D 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 Supplier B Supplier C Supplier D 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

5. BHT Berlin 5 Supplier A Supplier B Supplier C Supplier D „THE Supplier“ „A clearing house“ Supplier A Supplier B Supplier C Supplier D Change the thinking! Many GI players were used to operate a “monopoly” structure, this needed to be changed to enable cross-provider business interoperability

6. 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 BHT Berlin 6 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….

7. BHT Berlin 7 Method of master thesis and this presentation 1. Introduction 2. Problem Statement & Proposal: 1.A roaming enabled operation model 2.Key adaption issues for SDI 1.License types 2.Product types 3.Existing models as a research environment 1.Role model 2.Process model 3.Architecture model 4.Analysis focus currently on “find” in the publish-find-agree-bind 1.Abstract roaming workflow and data 2.Existing components (OGC, INSPIRE Catalogue and Metadata specification, profiles and versions) and mapping 5.Results

8. 2.1. A roaming enabled operation model BHT Berlin 8 Domain End User Account Manager SalesDelivery SDI Service Customer SDI Service Provider Advertiser Domain Software Supplier Domain Service Provider SDI Committee SDI Agency SDI Software Supplier IPR Owner Roles Who ?

9. SDI Committee SDI Agency SDI Software Supplier IPR Owner Home Provider 2.1. A roaming enabled operation model BHT Berlin 9 SDI Service Customer SDI Service Provider Advertiser SalesDelivery Account Manager Who ? Domain End User Domain Software Supplier Domain Service Provider Roles Legal Organizations

10. Home Provider 2.1. A roaming enabled operation model BHT Berlin 10 SDI Service Customer SDI Service Provider Advertiser SalesDelivery Account Manager Visited Provider SDI Service Customer SDI Service Provider Advertiser SalesDelivery Account Manager unknown Provider SDI Service Customer SDI Service Provider Advertiser SalesDelivery Account Manager Roles Legal Organizations Multiple instances (home provider) Who ?

11. Home Provider 2.1. A roaming enabled operation model BHT Berlin 11 SDI Service Provider Advertiser SalesDelivery Account Manager Visited Provider SDI Service Provider Advertiser SalesDelivery Account Manager SDI Service Customer Roles, Legal Organizations Multiple instances (home provider) Which relationship (roaming, visited provider relationship) Who ?

12. Home Provider 2.1. A roaming enabled operation model BHT Berlin 12 SDI Service Provider Advertiser SalesDelivery Account Manager Visited Provider SDI Service Provider Advertiser SalesDelivery Account Manager SDI Service Customer Roles, Legal Organizations Multiple instances (home provider) Which relationship (roaming, visited provider relationship) Who ? Define the roaming relationship more in detail together with existing components: Process Model Architecture How?

13. Overview of… …existing Frameworks and Models …the gap analysis BHT Berlin 13

14. Tiers Process Phases Account Manager SalesDelivery SDI Service Customer SDI Service Provider AdvertiserIPR Owner Domain End User SDI Service Customer SDI Service Customer Roles Model

15. Tiers Process Phases Data Service Appl. PublishFindAgreeBind Account Manager SalesDelivery SDI Service Customer SDI Service Provider AdvertiserIPR Owner Domain End User SDI Service Customer SDI Service Customer Roles and Process Model

16. Tiers Process Phases Data Service Appl. PublishFindAgreeBind Account Manager SalesDelivery SDI Service Customer AdvertiserIPR Owner Domain End User SDI Service Customer SDI Service Customer Spatial Data Set Applications and Geoportals Register Data Service Metadata Data Set Metadata GeoRM Data GeoRM Layers Registers Discovery Service View Service InvokeSD Service Download Service Transf. Service GeoRM Service SDI Service Provider Roles, Process and Architecture Model

17. BHT Berlin 17 Method of master thesis and this presentation 1. Introduction 2. Problem Statement & Proposal: 1.A roaming enabled operation model 2.Key adaption issues for SDI 1.License types 2.Product types 3.Existing models as a research environment 1.Role model 2.Process model 3.Architecture model 4.Analysis focus currently on “find” in the publish-find-agree-bind 1.Abstract roaming workflow and data 2.Existing components (OGC, INSPIRE Catalogue and Metadata specification, profiles and versions) and mapping 5.Results

18. Tiers Process Phases Data Service Appl. PublishFindAgreeBind Account Manager SalesDelivery SDI Service Customer AdvertiserIPR Owner Domain End User SDI Service Customer SDI Service Customer Spatial Data Set Applications and Geoportals Register Data Service Metadata Data Set Metadata GeoRM Data GeoRM Layers Registers Discovery Service View Service InvokeSD Service Download Service Transf. Service GeoRM Service SDI Service Provider This thesis focus only on the find phase

19. Data Set Metadata Tiers Process Phases Data Service Appl. Find SDI Service Customer Advertiser SDI Service Customer Applications and Geoportals Service Metadata Data Set Metadata Discovery Service SDI Service Provider http://creativecommons.org/licenses/by-nc-sa/3.0/ <GetRecord.. <…. On interface, schema and codelist level Operations:

20. BHT Berlin 20 ISO 19119 ISO 19139 …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 attributed was used to assign the partnerships ISO 19119 ISO 19139 ISO 19119 ISO 19139 Discovery Service INSPIRE Profile OGC CS-W 2.0.2 Free Filter Encoding (WFS like)

21. Tiers Process Phases Data Service Appl. Find SDI Service Customer Advertiser SDI Service Customer Applications and Geoportals Service Metadata Data Set Metadata RM Layers Discovery Service SDI 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.

22. BHT Berlin 22 Method of master thesis and this presentation 1. Introduction 2. Problem Statement & Proposal: 1.A roaming enabled operation model 2.Key adaption issues for SDI 1.License types 2.Product types 3.Existing models as a research environment 1.Role model 2.Process model 3.Architecture model 4.Analysis focus currently on “find” in the publish-find-agree-bind 1.Abstract roaming workflow and data 2.Existing components (OGC, INSPIRE Catalogue and Metadata specification, profiles and versions) and mapping 5.Results

23. 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

24. Conclusion Operation Models Centered Business Operation Model (a la e-commerce) Roaming Operation to introduce seamless business and technical interoperability Competition Balancing of risks, investments and opportunities Gap analysis with existing components in the “find” phase Positive, no specification/implementation change needed Planed gap analysis for the “agree” and later “bind” phase BHT Berlin 24