institut software- und systemtechnik fraunhofer isst chaining façades: higher efficiency in...

InstitutSoftware- undSystemtechnik

Fraunhofer

ISST

Chaining Façades: Higher Efficiency in evolution-enabled Spatial Data Infrastructures (SDI)

10th GI & GIS Workshop

Presentation

Dr. Roland M. WagnerFraunhofer-Institut für Software- und Systemtechnik Berlin/Dortmund

June 23rd, 2004


Fraunhofer

ISST

Dr. Roland Wagner, [email protected]

Presentation Overview

3. Chaining Approach

1. Chaining Concept vs. Functionalities

4. Generalization

2. Requirements5. Conclusion

6. Outlook: Applications


Fraunhofer

ISST


1.1. Chaining Concept vs. Application Functionality

Chaining (…is needed for these...)

• Usage of References rather than single Metadata Entries (example: pricing model in <fee> tag)

• Add onlineResource Class to Metadata (19115) or getcapabilitities (OGC, BSM)

• …

Functionalities

• Web Pricing & Ordering Service (WPOS)

• Web Authentication & Authorization Service (WAAS)

• Monitoring

• Optimization


Fraunhofer

ISST


1.2. History: Chaining Concept and Functionality

• First presentation of the need and requirements at the OGC meeting in Liège, March 2001• Presentation of approach and concepts at the OGC meeting in London, June 2002• Invited Expert for INSPIRE Meeting London, June 2002• Discussion Paper OGC Doc: 02-39r1 L.A., Dec 2002• WPOS HTTP POST profile 2003• Experience and Proof through multiple (paid) projects (LGB, LDS NRW, Ordnance Survey,..) 2003/04

• GDI.NRW released WPOS Spec May/June 2004• OGC Meeting State-of-the-art Southampton 2004


Fraunhofer

ISST


1.3. Need: SDI is Infrastructure or “Bridge Building”

Environm

ent BE

nvironment

A

Encoding: jpg,GML,...

Data Access Service: WMS,WFS,..

Company A Company B

Security Service: “WAAS”

eBusiness Service: WPOS


Fraunhofer

ISST


2.1. Geo-eBusiness Workflow and Standards

1a.) Find with Meta-data (ISO, OGC)

1b.) Find with Mapping (WMS)

2.) Authentication & Authorization (WAAS)

3.) Pricing & Ordering (WPOS)

4.) Data Generation & Integration (WFS, WCS, WCTS...)

State-of-the-art Interoperability

ATTENTIONINTER-

OPERABILITYTRAP!


Fraunhofer

ISST


2.2. Need for an interoperable Security (WAAS) and e-Business (WPOS) Solution ?!

WMSService

Interface

WMSService

Interface

WMSService

Interface

InterfaceInterface

Co

mp

an

y A

Co

mp

an

y B

WPOS ?

No Interference withdata stream protocol

Cascading Support Support different Data-

Protocols (WMS, WFS,..)

Implementation independent (No Vendor Specific Parameter)

Interface

WMSClient

WAAS ?

WPOS ?WAAS ?


Fraunhofer

ISST


2.3. Requirements for Pricing & Ordering within a SDI no geo-data protocol interference,

e.g. WMC WMS, WMS will never understand e.g. “getPrice”

implementation independentno data service enhancement necessary

but price calculation, ordering and accounting of

requested geo-data support of additional configuration parameter,

e.g. WMS request and configParam “licenseTime”

multi-protocol support, e.g. WMS,WFS,WCS,…

Protocol Handler and Layering


Fraunhofer

ISST


3.1. Protocol Handler: Chaining with Functionally Layer

WMClient

Interface

WMService

Interface

1a

1b

Client Service

3j 3f

3i 3g

3h

WM : OGC Web MappingWPO : Web Pricing & OrderingWAA : Security

2d2f 2d

2e

2a

2b

WPOClient

WPOService

Interface

2c

WM

SF

aça

de

WM

CF

aça

de

3a 3e

3b

3c

3d

WAAClient W

PO

CF

aça

deWAA

ServiceWP

OS

Fa

çad

e Interface


Fraunhofer

ISST


3.2. Protocol Handler: Sequence

WPOClient

WPOSService

getPriceModel

XCPF Price ModelConfiguration

getPrice

PriceOkay / not

orderProduct

TANStore TAN

getProduct

„data file“

WMClient

WMSService

getMap

getMap

„image file“

Fa

çad

e

Client Service

Fa

çad

e


Fraunhofer

ISST


3.3. Protocol Handler: Cascading Case

• Cascading fundamental integration and distribution method in an SDI

• WAAS and WM Façade in Figure neglected

Company D

WPO-Client

WPO-Client

WPO-Service

WM-Service

WM-Client

WM-ClientTransparency

WPO-Service

WM-Service

WPO-Service

WM-Service

Company B

User

Company C


Fraunhofer

ISST


3.4. Protocol Handler: Cascading Case – in Detail –

WPO-Client

WPO-Service

WM-Service

WM-Client

I II

Company DCompany C

Company AI.) Bypassing Protocol

Stream, e.g.WPOS.getPrice

II.) Interacting Protocol Stream, e.g. WPOS.getProduct;

WM-Client URL is pointing to WM Façade of WPOS


Fraunhofer

ISST


4.1. Number of Façades for Services Chaining

• “Zoo” of Protocols:• Function: WMS, WCS, WFS, WCTS,

WPOS, WAAS,…

• Version: 1.0.0, 1.1.0, 1.2.0, 2.0.0,…• SubProtocol: POST, GET, SOAP,…

• Assumption: • 6 Protocols * 2 Versions * 1.5 SubProtocols = 18 Variants

• Vendor1-ServiceA, Vendor2-ServiceB

* m = n (open)


Fraunhofer

ISST


4.2. Approach: Introduction of Façade Service

Publish

WPOS-Server

WMS Request

Pricing

WMS Response

2b

2c

2d

RegistryService

Façade Service

GetFaçadeService(OGC, WMS, v

1.1.0)

FaçadeServ. URL

translateRequest

Service

WMS-Service

1. WPOS: Unknown Protocol Request

2. Call Registry for Façade Service

3. Call Façade Service


Fraunhofer

ISST


5. Conclusion: Advantages of Façades

• High Concentration of Protocol-/Version-specific Logic in a Façade.

• Clear Separation between general and specific Logic

• High re-usability of components (Much lower implementation efforts)

• Support of proprietary Services (/protocols)

• Adding/Removing of sub protocols in running GDI possible (e.g. Security Cracks)

• Automated update of distributed SDI components on-request possible

WPO Client WPO Service

WM

SF

aça

de

WM

CF

aça

de


Fraunhofer

ISST


6. Application Outlook: Geo-eBusiness Diversity with WPOS/XCPF


Fraunhofer

ISST


Questions ?

Statements?

How do you do Geo-eBusiness

Dr. Roland M. Wagner

[email protected]

institut software- und systemtechnik fraunhofer isst chaining façades: higher efficiency in...

Documents

roland wagner

wm faade of wpos slide

data access service

waas ebusiness service

b client service 3j3f

company b wpos

wmc wms

mapping wms