datum 2005-03-30 name dr. roland m. wagner overview: geo digital rights management note: the...

•

Datum 2005-03-30 Name Dr. Roland M. Wagner

Overview: Geo Digital Rights Management

Note: The Presentation and the paper do not represent any official OGC opinion due to on going work

Name R. Wagner Overview: GeoDRM 2

Need

• Geoinformation (GI) characteristics• Large volumes

• Represents the real world => permanent need for updates

• High number of participating organizations• For data capturing and value adding

• Transport: Spatial Data Infrastructure (SDI)

Trading a valuable good


GeoDRM Stack for Trading GI

GeoDRM Framework

Copyright

Authentication

Authorization

Pricing & Ordering

Other, e.g. WaterMarking

GeoDRM FrameworkGeoDRM operations:

• basic operations vs. enhanced operations

• sub-set possible, depending on business model

• open number (enhanced)

• abstract and concrete interfaces


General Requirements

• Re-use of existing geoDRM solutions, • Security, Pricing & Ordering, Copyright, Licensing, water marking

• Support of multiple mainstream protocols• SAML, OSCI,…

• “Embedding without touching” Principle• Clear separation with (Framework-Interface) Drivers

• Support for multiple (OGC) protocols

• All Protocols are based on HTTP, working on-the-fly and state-less

• Short-term: Client-Service Architecture, • no third Object (e.g. Trust Center)


Approach: IT Mainstream example

WebBrowser

TCP/IP TCP/IP

PPP

Win

WebServer

PPP

Win

UMTSUMTS

WLANClient Service

WLAN


WC-Client

Deductive Approach: GeoDRM

geoDRMFramework

geoDRMFramework

future

E-GIF

future

E-GIF

OSCIOSCI

SAMLClient Service

SAML

WM-ClientWF-

Client

WCSWMS

WFS


GeoDRM Components

• Architecture• Separation between specialized and general

Protocols

• Description => Information Model• ISO 19115 Metadata and Basic Service Model

• Processing => Process Model• Negotiation Process between Client and Service for

concrete solutions


WFSGeoDRM: Architecture

WF-Client

Example:OGC Web Feature Service (WFS) and Client (WFClient)


WFSGeoDRM: Architecture

GeoDRM Framework Service


GeoDRM Framework Client


WF-Client



WFS




Framework-Interface Client

geoDRM: Architecture

Driver

GeoDRM1 A

Driver

Driver

GeoDRM1 B

Driver

Framework-Interface ServiceDriver

GeoDRM1 A

Driver

Driver

GeoDRM1 B

Driver

Driver

GeoDRM1 C

Driver

Framework-Interface Service

Driver

GeoDRM2 A

Driver

Driver

GeoDRM2 B

Driver

Framework-Interface Service

Driver

GeoDRM1 C

Driver


Driver

GeoDRM2 A

Driver

Driver

GeoDRM2 B

Driver



WF-Client


Concrete Sub-Solutions





geoDRM: Architecture

Driver

WSC1 A

Driver

Framework-Interface ServiceDriver

WSS1 A

Driver

Authentication-Interface Service

Driver

WPOS2 A

Driver

Pricing&Ordering-Interface Service

Authentication-Interface Client

Driver

WPOC2 A

Driver

Pricing&Ordering-Interface Client

WFS

WF-Client

Example:OGC Web Feature Service

Web Security Service

Web Pricing & Ordering Service


Process Chain



Driver

GeoDRM1 A

Driver


Driver

GeoDRM2 A

Driver

Framework-Interface Client • GeoDRM Framework general (abstract) Interface

• Transformation of information models by “Service Driver”

• Concrete (Third Party) solutions

• Transformation

• Framework


• Large Number of Driver required

• Re-use of existing Driver by introduction of Driver Registry Service (Driver DB)

Sub-solution for multiple Operations


Framework-Interface ClientDriver

DB

Driver

GeoDRM

1-2 A

GeoDRM


Driver



• Dynamic Process Model description for on-the-fly download of Driver

• Evolution-enabled GeoDRM

Sub-solution for single Operation



GeoDRM1 A


Driver

Driver

DriverDB


GeoDRM Framework ProcessgeoDRMClient geoDRMService

OWClient OWService

CatalogClient

Set(geoDRMServiceURL, OWSServiceURL)

setDriverAssign Port/URL

DriverService

getcapabilities(geoDRMServiceURL)

getDrivers

setURL(geoDRMClientURL)

request(geoDRMClientURL)

doServiceRequest(geoDRMServiceURL,OWServiceURL)

getDriversrequest(OWSURL)

responseresponse

response

• GeoDRM Preparation Processes required


Conclusion

• GeoDRM: umbrella for geo-(e)Business Services

• Framework required to embed various business requirements but assure SDI interoperability

• open number of geoDRM operations

• OGC founded GeoDRM WG in summer 2004

• First OGC GeoDRM demonstrator for April meeting (Frascati)

• Significantly work required / busy weekly telecons

• Invitation to interesting parties


Questions & Answers…

Contact:

Dr. Roland M. Wagner

Co-Chair: OGC geoDRM Working Group

Chair: GDI NRW geo-(e)Business Special Interest Group

Institute for geoinformatics (IFGI), University of Münster

(www.ifgi.de)

eMail: [email protected]

datum 2005-03-30 name dr. roland m. wagner overview: geo digital rights management note: the...

Documents