1 / 30

Presentation Overview

Web Pricing & Ordering Service (WPOS) XML Configuration & Pricing Format (XCPF) Dr. Roland M. Wagner Joint EuroSDR / eurogeographics e-Delivery Workshop BKG, Frankfurt 2005-02-23. Presentation Overview. 1. History and Background. 6. Next steps. 5. Projects. 2. Encoding XCPF.

callum
Download Presentation

Presentation Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Pricing & Ordering Service (WPOS)XML Configuration & Pricing Format (XCPF)Dr. Roland M. WagnerJoint EuroSDR / eurogeographicse-Delivery WorkshopBKG, Frankfurt2005-02-23 Name

  2. Presentation Overview 1. History and Background 6. Next steps 5. Projects 2. Encoding XCPF 4. Service Chaining 3. Functions WPOS

  3. Company A Company B 1.1. Need: SDI is Infrastructure or “Bridge Building” eBusiness Service: WPOS Environment A Environment B Security Service: “WAAS” Data Access Service: WMS,WFS,.. Encoding: jpg,GML,...

  4. 1.2. Geo-eBusiness Workflow and Standards State-of-the-art Interoperability 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...) ATTENTIONINTER-OPERABILITY TRAP!

  5. Company A Company B 1.3. Need WMSClient • No Interference withdata stream protocol • Cascading Support • Support different Data-Protocols (WMS, WFS,..) • Implementation independent (No Vendor Specific Parameter) Interface WAAS ? WPOS ? Interface WMSService Interface Interface WPOS ? WAAS ? Interface Interface WMSService WMS Service

  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-39r1L.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

  7. 1.5. Motivation: Geo-eBusiness Diversity with WPOS/XCPF

  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

  9. Presentation Overview 1. History and Background 2. Encoding XCPF

  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? 

  11. 2.2. Pricing in the Geo Domain Geo-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

  12. Position: 2 DHM 5 km² Position: 1 Top 50 10 km² Scaled areaPrice Minimum Price, Taxes =>1992 € =>5982 € =>4340 € Position: 3 Top 50 7 km² =>6341 € 2.3. Example • “Shopping cart”: Pos. 1: f1((area(polygon), areaPrice(area), updatefactor dataformat, useCategory, userCategory, workstations, licensingTime, Taxes))= 1234 € Pos. 3: f1(..............) = 987 € Pos. 2: f2(...) = 4340 € Sum 6561 € => 5982 € Scale Pricing: areaPrice = 17 km² * 0.9 €/km²or areaPrice= 15 km² * 1 €/km² + 2 km² * 0.9 €

  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

  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

  15. 2.6. XCPF: Calculation Object • parameter groups • multiple (intermediate) formulae • externalXCPF Web Service Calls • formula encoding with W3C MathML

  16. Presentation Overview 1. History and Background 2. Encoding XCPF 3. Functions WPOS

  17. XCPFcatalogue 3.1. „Filling the receipt“ Concept XCPFproduct instance WPOS Operation • GetCapabilities • GetPriceModel • GetPrice • OrderProduct • GetOrderList • GetProduct productID XCPF XCPFproduct + price calc. configParams, ServiceRequest XCPF configParams, ServiceRequest,customerID XCPFproduct +customer ID XCPF customerID XCPFproduct +status XCPF

  18. Presentation Overview 1. History and Background 2. Encoding XCPF 4. Service Chaining 3. Functions WPOS

  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

  20. 1a 1b 2a 2c 3a 3e 2b 2f 2d 2d WMServiceFacade WPOClient WPOService WMCFacade 3j 3f Interface Interface Interface Interface 2e 3b 3d 3c WPOSFacade WAA-C WAA-S WPOCFacade 3i 3g Interface Interface Interface Interface 3h 4.2. Embedding: Talking WMS, WPOS,… WMClient WMService Interface Interface Client Service WM : OGC Web Mapping WPOS : Web Pricing & Ordering WAA : Security

  21. WM Client WMS Service getMap getMap „image file“ 4.3. WPOS: Standard Sequence with WMS WPO Client WPOS Service getPriceModel XCPF Price Model Configuration getPrice Price Okay / not orderProduct TAN Store TAN getProduct „data file“

  22. Presentation Overview 1. History and Background 5. Projects 2. Encoding XCPF 4. Service Chaining 3. Functions WPOS

  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 ?

  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

  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)

  26. 5.4. New Project • State Schleswig-Holstein and Hamburg (Start January 2005) • Two states, an integrated Project • Multiple Sub Portals on Municipality level

  27. Presentation Overview 1. History and Background 6. Next steps 5. Projects 2. Encoding XCPF 4. Service Chaining 3. Functions WPOS

  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

  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

  30. How do you do Geo-E-Business ? Dr. Roland M. Wagnerroland.wagner@uni-muenster.de

More Related