DOCSLIB.ORG

Specific Agreement N. 5719.00 Page 1 of 119

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Specific Agreement N. 5719.00 Page 1 of 119 Customer: JRC - Ispra Specific Agreement N. 5719.00 Page 1 of 119 Authors: Matteo Villa, Fabio Status for the invocation of INSPIRE Spatial Data Last update: 20/04/2011 Cattaneo Services TXT e-Solutions S.p.A. Specific Contract 3263 under framework contract DIGIT 06760 STATUS FOR THE INVOCATION OF INSPIRE SPATIAL DATA SERVICES Joint Research Centre – Ispra Date Name Fabio Cattaneo (TXT) Issued by Matteo Villa (TXT) Michel Millot (JRC) 20/04/2011 Lars Bernard, Marek Brylski Distribution list (INSPIRE Network Drafting Team) SPECIFIC CONTRACT No.3263 UNDER F.C. No.DI/06760 Customer: JRC - Ispra Specific Agreement N. 5719.00 Page 2 of 119 Authors: Matteo Villa, Fabio Status for the invocation of INSPIRE Spatial Data Last update: 20/04/2011 Cattaneo Services Table of Contents 1. Executive Summary ........................................................................................................................ 7 2. Introduction ................................................................................................................................... 8 3. Purpose and Scope ......................................................................................................................... 9 4. References and applicable documentations ................................................................................ 10 5. Existing Standards ........................................................................................................................ 11 5.1. Web-services: Overview and concepts .................................................................................. 11 5.1.1. Web-service definition ................................................................................................. 11 5.1.2. Two main classes of web-services ............................................................................... 11 5.1.3. Styles of use ................................................................................................................. 12 5.1.4. Web-service standards and architecture ..................................................................... 13 5.1.5. Synchronous vs Asynchronous modes ......................................................................... 16 5.1.6. Pull and Push based web-service ................................................................................. 17 5.1.7. Business processes and workflows in Web-services ................................................... 19 5.2. Study of available technologies ............................................................................................. 21 5.2.1. SOAP based web-services ............................................................................................ 21 5.2.2. RESTful web-services ................................................................................................... 27 5.2.3. Web-service contracts ................................................................................................. 33 5.2.4. OGC web-service standards (OWS: WMS,WFS,WCS,WPS) .......................................... 41 5.2.5. BPEL workflow management ....................................................................................... 48 5.2.6. Wf-XML ........................................................................................................................ 59 5.2.7. OpenID ......................................................................................................................... 61 5.2.8. Summary ...................................................................................................................... 64 6. Existing Tools ................................................................................................................................ 67 6.1. COTS tools .............................................................................................................................. 67 6.1.1. ESRI ArcGIS Server ........................................................................................................ 67 6.1.2. ERDAS Apollo server .................................................................................................... 73 6.1.3. Intergraph GeoMedia SDI ............................................................................................ 75 6.1.4. CubeWerx Suite ............................................................................................................ 78 6.2. OTS tools ................................................................................................................................ 82 6.2.1. Geoserver ..................................................................................................................... 82 6.2.2. Mapserver .................................................................................................................... 84 6.2.3. ESA Service Support Environment (SSE) ...................................................................... 86 6.2.4. Deegree ........................................................................................................................ 88 6.2.5. 52North: 52n WPS ........................................................................................................ 90 6.2.6. Wald.Intevation: PyWPS .............................................................................................. 92 6.2.7. Zoo-project: Open WPS platform ................................................................................ 93 6.3. Summary ................................................................................................................................ 95 7. Service Level Agreement (SLA) .................................................................................................... 98 7.1. Definition of SLA and QoS in web-services ............................................................................ 98 7.2. SLA’s in Spatial Data Infrastructures (SDI) ........................................................................... 100 7.3. Requirements for the integration of SLAs in a SDI .............................................................. 101 7.4. Potential SLA elements for SDI services............................................................................... 102 SPECIFIC CONTRACT No.3263 UNDER F.C. No.DI/06760 Customer: JRC - Ispra Specific Agreement N. 5719.00 Page 3 of 119 Authors: Matteo Villa, Fabio Status for the invocation of INSPIRE Spatial Data Last update: 20/04/2011 Cattaneo Services 7.5. Requirements on the network / infrastructure ................................................................... 104 7.6. The Web Service Level Agreement (WSLA) standard .......................................................... 105 7.7. SLA aggregation .................................................................................................................... 110 8. Conclusions ................................................................................................................................ 115 9. Bibliography / Webography ....................................................................................................... 117 SPECIFIC CONTRACT No.3263 UNDER F.C. No.DI/06760 Customer: JRC - Ispra Specific Agreement N. 5719.00 Page 4 of 119 Authors: Matteo Villa, Fabio Status for the invocation of INSPIRE Spatial Data Last update: 20/04/2011 Cattaneo Services List of Figures Figure 1: Web service framework composition (source: IBM) .......................................................... 13 Figure 2: REST verbs and their CRUD equivalent ............................................................................... 27 Figure 3: Major elements of WSDL 1.1 .............................................................................................. 35 Figure 4: Major elements of WSDL 2.0 .............................................................................................. 36 Figure 5: WSDL 1.1 vs WSDL 2.0 (source: Wikipedia) ........................................................................ 36 Figure 6: WSDL 1.1 basic message exchange patterns (source: www.ajaxonomy.com) .................. 38 Figure 7: WSDL concrete and abstract portions (source: wwwajaxonomy.com).............................. 39 Figure 8: An example of a WADL description .................................................................................... 40 Figure 9: Feature comparison of OpenID, OAuth and SAML(source: Wikipedia) ............................. 61 Figure 10: Architecture for an OpenID enabled Geospatial workflow (source: G. Mason Uni) ........ 63 Figure 11: ArcGIS server architecture (source: ESRI) ......................................................................... 68 Figure 12: Map Service Capabilities(source: ESRI) ............................................................................. 70 Figure 13: Image Service Capabilities(source: ESRI) .......................................................................... 70 Figure 14: The ERDAS Apollo Suite (source: ERDAS website) ............................................................ 74 Figure 15: Map tiling (source: CubeWerx) ......................................................................................... 80 Figure 16: The Geoserver platform (source: Geoserver) ................................................................... 83 Figure 17: Basic architecture of MapServer applications (source: MapServer) ................................ 85 Figure 18: Top-level view of SSE Environment (source:
Load more

Recommended publications
  • What's in the Cloud?
    WHAT’S IN THE CLOUD? PRODUCT GUIDE / MARCH 9, 2019 DISCLAIMER Oracle Commerce Cloud is a fully featured, extensible SaaS commerce solution, delivered in the Oracle Cloud, supporting B2C and B2B models in a single platform. Commerce Cloud grants greater agility and cost savings, with the extensibility and control required in the ultra-competitive digital commerce market. SIMPLIFY your technology footprint. INNOVATE to stay ahead of consumer demands and competitors in a low-risk way. DELIVER to every customer, every time to increase loyalty and revenue. Commerce Cloud has frequent releases. Please ensure you have the latest documentation. This content was updated for the 19A release (released in February 2019) 2 FEATURE GUIDE / WHAT’S IN THE CLOUD? Product Features Unified Admin ................................................................................................. 5 Core Platform and APIs ................................................................................. 5 Modular, Headless Options ............................................................................ 6 Responsive Storefront .................................................................................... 6 Guided Search................................................................................................ 7 SEO ................................................................................................................ 8 Drag-and-Drop Experience Creation ............................................................. 9 Catalog Management ..................................................................................
    [Show full text]
  • Download.Php/10347/Wsbpel- Specification-Draft-120204.Htm, Last Accessed 2004-12-28
    Chapter 1: Security Security-relevance of semantic patterns in cross-organisational business processes using WS-BPEL K.P.Fischer1,2,3, U.Bleimann1, W.Fuhrmann1 and S.M.Furnell2,4 1 Aida Institute of Applied Informatics, University of Applied Sciences Darmstadt, Germany 2 Network Research Group, University of Plymouth, Plymouth, United Kingdom 3 Digamma Communications Consulting GmbH, Darmstadt, Germany 4School of Computer and Information Science, Edith Cowan University, Perth, Australia e-mail: [email protected] Abstract This paper gives an overview of the research project considering security aspects in the context of business process management. In particular, security issues arising when scripts written in the standardized scripting language WS-BPEL (formerly: BPEL4WS or BPEL for short) implementing cross-organisational business processes on top of Web services are deployed across security domain boundaries, are being investigated. It analyses the security- relevant semantics of this scripting language in order to facilitate checking for compliance with security policies effective at the domain of execution. Keywords Security Policy, Policy Enforcement, Cross-Organisational Business Process (CBP), Semantic Analysis, Web Services, Web Services Business Process Execution Language (WS-BPEL, BPEL) 1. Introduction Web services are currently considered a broadly adopted approach for the realization of a service oriented architecture (SOA) used in service oriented computing (SOC) (Curbera et al., 2003; Foster and Tuecke, 2005; Papazoglou and Georgakopoulos 2003). Web services, and the composition or orchestration of them, play a central role in current approaches to service oriented computing (Berardi et al., 2003). Service orientation is also expected to play an important role in grid computing, where the provisioning of computing resources within a conceptual huge network of collaborating computers and devices can also be fostered by services (so called grid services in this context) (Tuecke et al., 2003; ).
    [Show full text]
  • Voice.AI Gateway API Reference Guide Version
    Reference Guide AudioCodes Intuitive Human Communications for Chatbot Services Voice.AI Gateway API Version 2.2 Notice Voice.AI Gateway | API Reference Guide Notice Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document can be downloaded from https://www.audiocodes.com/library/technical-documents. This document is subject to change without notice. Date Published: November-04-2020 WEEE EU Directive Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product. Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our website at https://www.audiocodes.com/services-support/maintenance-and-support. Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our website at https://online.audiocodes.com/documentation-feedback. Stay in the Loop with AudioCodes - ii - Notice Voice.AI Gateway | API Reference Guide Notes and Warnings OPEN SOURCE SOFTWARE. Portions of the software may be open source software and may be governed by and distributed under open source licenses, such as the terms of the GNU General Public License (GPL), the terms of the Lesser General Public License (LGPL), BSD and LDAP, which terms are located at https://www.audiocodes.com/services-support/open-source/ and all are incorporated herein by reference.
    [Show full text]
  • Security and Privacy Issues in FHIR Subscription
    Security Working Group Security and Privacy Issues in FHIR Subscription Mohammad Jafari, Kathleen Connor, John M. Davis, Christopher Shawn Version 1.1 December 17 , 2019 (revised for publication on 1/20/2020) Security and Privacy Issues in FHIR Subscriptions December 17, 2019 Table of Contents 1 Introduction ................................................................................................................. 1 1.1 Related Technologies .................................................................................................... 2 2 Anatomy of a Subscription Service ............................................................................ 3 2.1 Subscription Topics ....................................................................................................... 3 2.2 Subscriptions Management ........................................................................................... 4 2.3 Event Monitor ................................................................................................................ 4 2.4 Notification Delivery ..................................................................................................... 4 2.5 Notification Processing ................................................................................................. 5 3 Security and Privacy Considerations ......................................................................... 6 3.1 Authorization for Subscription Management ................................................................ 6 3.2 Recipient’s Consent
    [Show full text]
  • Office365mon Subscription Management API
    Office365Mon Subscription Management API Office365Mon provides a set of APIs for managing subscriptions in our service. With it you can do things like create a subscription, change the details about the subscription, modify the list of administrators and notifications for a subscription, configure the resources being monitored for the subscription, and more. Using the subscription management API requires you to first create an application in your Azure Active Directory and add the Office365Mon applications to it. You’ll then reference your application information when requesting an access token that you can use to work with the subscription management API. This process is explained and illustrated in great detail in our API documentation for accessing report data, which you can download from https://www.office365mon.com/Office365Mon_AccessToken_And_API.pdf. It’s highly recommended to download that document first to ensure your environment is set up correctly before using this subscription management API. For resellers there are some special APIs just for you. You need to be registered with Office365Mon.Com to use the reseller APIs, which you can do by contacting us at [email protected]. Once you’re registered then you use the Reseller* APIs described at the end of this document to create new subscriptions and add and remove plans for those subscriptions. Once a subscription is actually created though, you can use the same Subscription Management APIs as everyone else to manage it – change the list of Admins, add or remove notification
    [Show full text]
  • Making Phone Calls from Blazor Webassembly with Twilio Voice
    © Niels Swimberghe https://swimburger.net - @RealSwimburger 1 About me • Niels Swimberghe aka Swimburger • Grew up in Belgium, working in USA • .NET Developer / Tech Content Creator • Blog at swimbuger.net • Twitter: @RealSwimburger • Company: 2 Programmatic communication using HTTP Webhooks Example TwiML Sample: https://demo.twilio.com/welcome/voice/ Based on in-depth guide on Twilio Blog Check out guide at Twilio Blog Application • Out of the box Blazor WebAssembly application • Phone dialer • Initiate phone calls from browser • Receive phone calls in browser Recommended architecture Demo architecture Demo architecture Auth flow 1. Ajax HTTP Request JWT token 2. Server generates JWT token and sends token in HTTP response 3. Twilio JavaScript SDK establishes bidirectional connection with Twilio over WebSocket Incoming call flow 1. Phone calls Twilio Phone Number 2. Twilio sends HTTP request to your webhook asking for instructions 3. Webhook responds with TwiML instructions Incoming call flow Webhook responds with TwiML instructions Incoming call flow 4. Twilio dials client 5. Client accepts incoming connection => VoIP established Outgoing call flow 1. Client connects to Twilio with To parameter 2. Twilio sends HTTP request to your webhook asking for instructions 3. Webhook responds with TwiML instructions Outgoing call flow Webhook responds with TwiML instructions Outgoing call flow 4. Twilio dials phone number 5. Phone accepts incoming connection => VoIP established Let’s see how its built Step 1: Create Twilio resources • You need to
    [Show full text]
  • What's in CX Commerce Cloud?
    What’s in CX Commerce Cloud? 20A release detail May 2020 | Version 1.00 Copyright © 2020, Oracle and/or its affiliates PURPOSE STATEMENT Oracle CX Commerce is a cloud-native, fully featured, extensible SaaS commerce solution, delivered in the Oracle Cloud, supporting B2C and B2B models in a single platform. CX Commerce grants greater agility and cost savings, with the extensibility and control required in the ultra-competitive digital commerce market. SIMPLIFY your technology footprint. INNOVATE to stay ahead of demands and competitors in a low-risk way. DELIVER to every customer, every time to increase loyalty and revenue. DISCLAIMER CX Commerce has frequent releases. Please ensure you have the latest documentation This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.
    [Show full text]
  • Alibaba Cloud
    AAlliibbaabbaa CClloouudd Alibaba Cloud AlAiblibaabbaa CClloouud dS eSrveicrev iMces hMesh DaDtaa Ptlaan Pelane Document Version: 20210809 Document Version: 20210809 Alibaba Cloud Service Mesh Dat a Plane·Legal disclaimer Legal disclaimer Alibaba Cloud reminds you t o carefully read and fully underst and t he t erms and condit ions of t his legal disclaimer before you read or use t his document . If you have read or used t his document , it shall be deemed as your t ot al accept ance of t his legal disclaimer. 1. You shall download and obt ain t his document from t he Alibaba Cloud websit e or ot her Alibaba Cloud- aut horized channels, and use t his document for your own legal business act ivit ies only. The cont ent of t his document is considered confident ial informat ion of Alibaba Cloud. You shall st rict ly abide by t he confident ialit y obligat ions. No part of t his document shall be disclosed or provided t o any t hird part y for use wit hout t he prior writ t en consent of Alibaba Cloud. 2. No part of t his document shall be excerpt ed, t ranslat ed, reproduced, t ransmit t ed, or disseminat ed by any organizat ion, company or individual in any form or by any means wit hout t he prior writ t en consent of Alibaba Cloud. 3. The cont ent of t his document may be changed because of product version upgrade, adjust ment , or ot her reasons. Alibaba Cloud reserves t he right t o modify t he cont ent of t his document wit hout not ice and an updat ed version of t his document will be released t hrough Alibaba Cloud-aut horized channels from t ime t o t ime.
    [Show full text]
  • Developer Guide Amazon Chime Developer Guide
    Amazon Chime Developer Guide Amazon Chime Developer Guide Amazon Chime: Developer Guide Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Chime Developer Guide Table of Contents What is Amazon Chime? ..................................................................................................................... 1 Pricing ...................................................................................................................................... 1 Resources .................................................................................................................................. 1 Extending the Amazon Chime desktop client ......................................................................................... 2 User management ...................................................................................................................... 2 Invite multiple users ........................................................................................................... 2 Download user list ............................................................................................................
    [Show full text]
  • Micro Focus Fortify Software Security Center User Guide
    Micro Focus Fortify Software Security Center Software Version: 20.2.0 User Guide Document Release Date: Revision 2 - January 5, 2021 Software Release Date: November 2020 User Guide Legal Notices Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK https://www.microfocus.com Warranty The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Except as specifically indicated otherwise, a valid license from Micro Focus is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notice © Copyright 2008 - 2021 Micro Focus or one of its affiliates Trademark Notices All trademarks, service marks, product names, and logos included in this document are the property of their respective owners. Documentation Updates The title page of this document contains the following identifying information: l Software Version number l Document Release Date, which changes each time the document is
    [Show full text]
  • Using Azure Services from Webassembly Modules
    Using Azure services from WebAssembly modules Radu Matei May 11, 2021 This article originally appeared on the Microsoft DeisLabs blog1 WAGI, the WebAssembly Gateway Interface2, is a simple way of writing and executing HTTP response handlers as WebAssembly modules. We recently added new features to WAGI3, such as pulling modules from OCI registries and outbound HTTP connections from guest modules, which opened the possibility of using Azure services from Wasm modules, and in this article we explore building and running such modules. WAGI provides a very simple application model for building server-side HTTP response handlers using WebAssembly. Theoretically, any language that compiles to WASI, WebAssembly System Interface4, can be used build a WAGI handler, since WAGI is modeled after the CGI specification5 – read the request body from the process’ standard input and environment variables and write the response to standard output. Since the request bodies can be read as byte arrays, modules can perform any computation on them, with the advantage of running the modules in the WASI isolation sandbox, together with an experimental HTTP library6 that allows modules to send outbound HTTP connections. But besides raw HTTP connections, most real-world scenarios will also regularly need to use external services such blob storage, databases, or message-passing systems, which is why we are experimenting with using a subset of the Azure SDK for Rust from WebAssembly modules – specifically, Azure Blob Storage (reading and writing blobs), Cosmos DB (reading
    [Show full text]
  • Download.Php/10347/Wsbpel-Specification-Draft-120204.Htm, Last Accessed 2004-12-28
    A Security Infrastructure for Cross-Domain Deployment of Script-Based Business Processes in SOC Environments K.P.Fischer1,3, U. Bleimann1, W. Fuhrmann1, S.M Furnell2,4 1 Aida Institute of Applied Informatics, University of Applied Sciences Darmstadt, Germany 2 Network Research Group, University of Plymouth, Plymouth, United Kingdom 3 Digamma Communications Consulting GmbH, Darmstadt, Germany 4School of Computer and Information Science, Edith Cowan University, Perth, Australia e-mail: [email protected] Abstract This paper addresses security aspects arising in service oriented computing (SOC) when scripts written in a standardized scripting language such as WS-BPEL (formerly: BPEL4WS or BPEL for short), BPML, XPDL, WSCI in order to implement business processes on top of Web services are deployed across security domain boundaries. It proposes an infrastructure and methods for checking the scripts deployed, prior to execution, for compliance with security policies effective at the domain in which a remotely developed script-based business process is to be executed. Keywords Security Policy, Policy Enforcement, Service Oriented Computing (SOC), Service Oriented Architecture (SOA), Business Process Management, Web Services, Web Services Business Process Execution Language (WS-BPEL) 1. Introduction Service oriented computing (SOC) is currently considered one of the most promising new paradigms for distributed computing (Papazoglou and Georgakopoulos, 2003). Though com- paratively new, a significant amount of research has already been dedicated to this area (e.g. Deubler et al. 2004). Web services, and the composition or orchestration of them, play a central role in current approaches to service oriented computing (Berardi et al. 2003). Service orientation is also expected to have an important influence in the area of grid computing, where the provisioning of computing resources within a conceptual huge network of collaborating computers and devices can also be fostered by services (so called grid services in this context) provided by different nodes (Tuecke et al.
    [Show full text]