datum name web pricing & ordering service (wpos) xml configuration & pricing format (xcpf)...
TRANSCRIPT
•
Datum Name
Web Pricing & Ordering Service (WPOS)XML Configuration & Pricing Format (XCPF)
Dr. Roland M. Wagner
Joint EuroSDR / eurogeographicse-Delivery Workshop
BKG, Frankfurt2005-02-23
Name: Dr. Wagner 2
Presentation Overview
3. Functions WPOS
1. History and Background
4. Service Chaining
2. Encoding XCPF5. Projects
6. Next steps
Name: Dr. Wagner 3
1.1. 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
Name: Dr. Wagner 4
1.2. Geo-eBusiness Workflow and Standards
1a.) Find with Meta-data (ISO, OGC)
1b.) Find with Mapping (WMS)
2.) Authentication & Authorization
3.) Pricing & Ordering
4.) Data Generation & Integration (WFS, WCS, WCTS...)
State-of-the-art Interoperability
ATTENTIONINTER-
OPERABILITYTRAP!
Name: Dr. Wagner 5
1.3. Need
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 ?
Name: Dr. Wagner 6
1.4. History• First presentation of the need and requirements at the OGC meeting in Liège, March 2001• WPOS in GDI NRW Testbed I in 2001• Presentation of approach and concepts at the OGC meeting in 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, O.S.,Hamburg,..) 2003-05• Study of other e-Business approaches June 2003• GDI.NRW released WPOS Spec May/June 2004• Founding of the OGC GeoDRM WG June 2004• Goal OGC geoDRM Demonstrator April 2005, Fracati
Name: Dr. Wagner 7
1.5. Motivation: Geo-eBusiness Diversity with WPOS/XCPF
Name: Dr. Wagner 8
1.6. Benefits There is a need to SELL geo-information to have
revenues for further developments of SDIs !!
XCPF: math. approach copes will a very wide range of pricing models & easy adjustments
Support different protocols (a XSL file per protocol) Support of existing networks Implementation independent Automation of value chains Rationalization
Name: Dr. Wagner 9
Presentation Overview
1. History and Background
2. Encoding XCPF
Name: Dr. Wagner 10
2.1. „How does it cost?“ A non-trivial question
• Geo-Information products are not off-the-shelf products !
• How to offer/price Geo-Services?
Name: Dr. Wagner 11
2.2. Pricing in the Geo DomainGeo-product pricing is complex due to
high value and very high prices wide range of configuration possibilities
No suitable mainstream solution available !
Generic structures needed! “The lowest common denominator for all pricing
Ideas is the mathematical formula” -Proofed- Product description in ISO 19115
Name: Dr. Wagner 12
2.3. Example Position: 1Top 5010 km²• “Shopping cart”:
Position: 3Top 507 km²
Pos. 2: f2(...) = 4340 €
Pos. 1: f1((area(polygon), areaPrice(area), updatefactor dataformat, useCategory, userCategory, workstations, licensingTime, Taxes))= 1234 €Pos. 3: f1(..............) = 987 €
Sum 6561 €
Position: 2DHM5 km²
=>5982 €
Minimum Price, Taxes
Scale Pricing: areaPrice = 17 km² * 0.9 €/km²or areaPrice= 15 km² * 1 €/km² + 2 km² * 0.9 €
=>1992 €
=>4340 €
Scaled areaPrice
=>6341 € => 5982 €
Name: Dr. Wagner 13
2.4. XML Configuration & Pricing Format (XCPF) Object Axis
XCPF hierarchy to group product items for complex group pricing integration of different catalogs optimizing with object inheritance product cascading
Name: Dr. Wagner 14
2.5. XCPF: Product Object
The smallest unit short description hosting the basic
pricing formula
hosting the product configuration(layer, style,pixel,...)
workflow status all contract aspects
Name: Dr. Wagner 15
2.6. XCPF: Calculation Object parameter groups multiple
(intermediate) formulae
externalXCPF Web Service Calls
formula encoding with W3C MathML
Name: Dr. Wagner 16
Presentation Overview
3. Functions WPOS
1. History and Background
2. Encoding XCPF
Name: Dr. Wagner 17
3.1. „Filling the receipt“ ConceptXCPF
catalogue
XCPFproductinstance
WPOS Operation GetCapabilities GetPriceModel GetPrice OrderProduct GetOrderList GetProduct
XCPFproduct
+ price calc.
XCPFproduct
+customer ID
XCPFproduct+status
productID
XCPF
configParams, ServiceRequest
XCPF
configParams, ServiceRequest,
customerID
XCPF
customerID
XCPF
Name: Dr. Wagner 18
Presentation Overview
3. Functions WPOS
1. History and Background
4. Service Chaining
2. Encoding XCPF
Name: Dr. Wagner 19
4.1. WPOS Concept: Requirement no geo-data protocol interference,
e.g. WMC WMS, WMS will never understand “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 Packages and Layering
Name: Dr. Wagner 20
4.2. Embedding: Talking WMS, WPOS,…
WMClient
Interface
WMService
Interface
1a
1b
Client Service
Interface
WPOClient
WMServiceFacade
WPOService
Interface
WMCFacade
Interface
Interface
2a
2b
2c
2d2f 2d
2e
WA
A-C
Interface
WPOSFacade
Interface
Interface
WA
A-S
WPOCFacade
Interface
3a
3b
3c
3d
3e
3j 3f
3i 3g
3h
WM : OGC Web MappingWPOS : Web Pricing & OrderingWAA : Security
Name: Dr. Wagner 21
4.3. WPOS: Standard Sequence with WMS
WPOClient
WPOSService
getPriceModel
XCPF Price ModelConfiguration
getPrice
PriceOkay / not
orderProduct
TANStore TAN
getProduct
„data file“
WMClient
WMSService
getMap
getMap
„image file“
Name: Dr. Wagner 22
Presentation Overview
3. Functions WPOS
1. History and Background
4. Service Chaining
2. Encoding XCPF5. Projects
Name: Dr. Wagner 23
5.1. Project: Pathfinder, O.S.
• Chaining of WFS / WPOS with WFS Façade• Partner
• IONIC
• EDINA• Businessmodel:
• Initial Order
• Update
• Subscription• Use Case e-procurement for a large distributor• Public presentation: Agile 2003
Price ?
Name: Dr. Wagner 24
5.2. Project: Geobroker Brandenburg
• LGB is the Mapping Agency of Brandenburg, a German State• Large number of product resources, may different services• Usage of OGC/ISO conform software component• Consortium:
• AED-Sicad (Geo-Server)
• Con Terra (Catalog)
• Fraunhofer ISST (Pricing&Ordering)• Reference solution for other projects (3 tenders)• Pricing: Complex Pricing, but for non on-the-fly production• Shop Application, WPOS interface not open to public• Public Presentation: CeBit 2004, http://geobroker.geobasis-bb.de
Name: Dr. Wagner 25
5.3. Project: LDS / LVermA Northrhine-Westfalia (NRW)
• LDS is ASP for Mapping Agency NRW
• NRW is another German state
• Large number of product resources, may different services
• Different pricing models
• WPOS interface will be open to public
• Partner:
• AED-Sicad
• Public Presentation: CeBit 2004
• Part of “GDI NRW Verbundprojekt” (see CeGI)
Name: Dr. Wagner 26
5.4. New Project
• State Schleswig-Holstein and Hamburg (Start January 2005)
• Two states, an integrated Project
• Multiple Sub Portals on Municipality level
Name: Dr. Wagner 27
Presentation Overview
3. Functions WPOS
1. History and Background
4. Service Chaining
2. Encoding XCPF5. Projects
6. Next steps
Name: Dr. Wagner 28
6.1. Review• After 4 solutions are carried out:
• No major problems appeared
• Therefore, only smart changes
• Usage of mathematic formulae a good decision
• Implementation- and protocol-independency is a key issue
• Other e-business approaches not helpful, e.g. UDDI, ECO, ebXML,XCBL
• We are confident enough to recommend the discussion paper to move
on in the OGC acceptance process
Name: Dr. Wagner 29
6.2. Preview
• Update OGC Discussion Paper 02-39r1
• New HTTP POST profile with Schema
• Adjustments to latest Web Service Developments/Styles
• Façade Examples for WMS and WFS
• XCPF as description language in a separate Document
• Invitation to all interested institutions to join !
• GeoDRM seems to be the right place within OGC