DOCSLIB.ORG

Achieving Interoperability Using Open Standards and Specifications David Danko, Esri Marten Hogeweg, Esri Abstracting Geographic Knowledge

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Federal GIS Conference February 9–10, 2015 | Washington, DC Achieving Interoperability Using Open Standards and Specifications David Danko, Esri Marten Hogeweg, Esri Abstracting geographic knowledge Visualization, Encapsulating Analytics, real world Decision support. knowledge Models Maps Geodata Metadata GIS interoperability – exchanging and using geographic knowledge Interoperability: the ability of two or more systems or components to exchange information and to use the information that has been exchanged * Technical interoperability Semantic interoperability * IEE Abstracting unlimited variety of features/phenomena GIS - merging diverse information Diverse: information types formats location reference systems perspectives Distributed Integrated by location Interoperability enablers Infrastructure Supportive networks, Interfaces, hardware • Practical, widely used • Providing technical and semantic interoperability • Fit for purpose • Geographic structures Knowledgeable users Interoperability Standards • Data formats • Well trained • Content description • Understand the need for • Quality quality • Data management • Metadata to understand • Visualization and use data and services properly • Geoweb services Laws • Metadata Intellectual property protection, Authorization to share ESRI learns about and supports standards through active participation: Implementations –IT/industry standards Organizations – GIS standards – ISO TC 211 – OGC – ANSI/INCITS –L1 – CEN – Global Map – GSDI – DGIWG – IHO – GWG Standards Development – International Standards Projects/Testbeds – Regional Standards – OGC Web Services testbeds – National Standards – GEOSS – Information Community Standards – INSPIRE – NATO Core GIS Standards • An agreement between a provider and a consumer a reference document enabling interoperability • Standards Development Organizations (SDOs) ISO TC211 Abstract Models, Software XML/XSD, HTML, Content, Vocabulary. Interfaces: XSLT, URI. Instantiations based on ISO and W3C standards Domain Infrastructure Technical interoperability standards ISO 19139 Metadata XML Schema WMS GML Organizations in which ESRI participates to establish Technical Interoperability example: ISO 19128, 19139 example: WMS, WFS, GML example: XML, URI, HTML5 Semantic Interoperability Standards INSPIRE Data specification on Geology ISO 19115 Metadata Title = name by which the resource is known FGDC Framework data models GML Organizations in which ESRI participates to establish Semantic Interoperability example: ISO 19157 Data quality, 19110 Feature Catalogue Methodology example: Point Symbology for Emergency Management, NAP example: INSPIRE Metadata Implementing Rules and Data example: FGDC Framework Themes, Specifications Content Standard for Digital Geospatial Metadata GIS Standardization – functional areas 1. Basic Geographic Structures (semantic interoperability) - ISO Spatial Schema, Coverages, Coordinate Ref Systems standards 2. Content description (semantic interoperability) - FACC, SDSFIE, Standardized Data Models - Feature Catalogs, Metadata 3. Data Management (semantic and technical) - OGC Simple Features 4. Data Formats (technical interoperability) - VPF, OGC GML 5. Visualization (semantic and technical) - SLD, MIL-STD 2525 6. GeoWeb Services (technical interoperability) - OGC Catalog, Web Services, HTTP Putting it all together Using standard’s functional areas to provide geographic knowledge Basic Geographic Structure Content Description Data Management Data Format Examples: Visualization ISO 19107 Spatial Schemas Examples: Web services ISO 19111 Spatial referencing by coordinates ISO 19109 Rules for Application Schemas ISO 19123 Schema for coverage geometry ISO 19110 Feature Catalog Examples: and functions ISO 19115 Metadata GML, WMS, WCS ISO 19144 Classification Systems WFS, MIL-STD 2525 ISO TC 211Participation • ESRI provides leadership role in ISO TC 211 Standards Development: • Project lead on many ISO Standards • Provide technical experts on many Work Item project teams • Provide support for ISO TC 211 standards outreach • Meeting sponsorship ISO TC 211 Standards examples ISO 19107 Spatial schema ISO 19111 Spatial referencing by ISO 19115 Metadata Conceptual schemata for coordinates Schema for describing geographic describing, representing and Defines the conceptual schema for information and services manipulating the spatial spatial reference systems. The data required characteristics of geographic features to define 1, 2, and 3-dimensional systems ESRI serves many roles within OGC Board of Directors Architecture Board Planning Committee Technical Committee Lead several Standards and Domain Working Groups Joint Advisory Group to ISO TC211 OGC Forums Testbeds & Plugfests Testing & Compliancy Outreach Program Financial Support 160+ Compliant past and present products http://www.opengeospatial.org/resource/products/compliant#ESRI OGC Web Services examples I-295 Web Feature Service Web Map Service Geospatial feature publishing/streaming service Geospatial “picture” publishing/viewing service Web Map Tile Service static base maps where the bounding box and scales have been constrained to discrete tiles Global Map http://ww Abstract: vector data NOAA Weather htt Abstract: point featur Landsat http://www.N Abstract: 30m satelli Web Processing Service Interface for publishing geospatial algorithms, calculations or models Web Coverage Service Imagery and gridded data publishing/processing service Catalog Service-Web Metadata publishing/search service ISO TC 211 Standards 6709:2008 - Standard representation of latitude, longitude and altitude for 19130:2010 -Sensor and data models for imagery and gridded data geographic point locations 19101:2002 - Reference model Part 1: Fundamentals 19130-2 - SAR, InSAR, Lidar and Sonar 19101-2:2008 - Reference model - Part 2: Imagery 19131:2007 - Data product specifications 19103:2005 - Conceptual schema language 19132:2007 - Location based services - Reference model 19104:2008 - Terminology 19133:2005 - Location based services - Tracking and navigation 19105:2000 - Conformance and testing 19134:2007 - Multimodal location based services for routing and navigation 19106:2004 - Profiles 19135:2005 - Procedures for registration of geographical information items 19107:2003 - Spatial schema 19135-2 - XML Schema Implementation 19108:2002 - Temporal schema 19136:2007 - Geography Markup Language 19109:2005 - Rules for applicaiton schema 19137:2007 - Core profile of the spatial schema 19110:2005 - Methodology for feature cataloguing 19138:2006 - Data quality measures 19111:2007 - Spatial referencing by coordinates 19139:2007 - Metadata - XML schema implementation 19111-2:2009 - Extension for parametric value 19141:2008 - Schema for moving features 19112:2003 - Spatial referencing by geographic identifiers 19142:2010 - Web Feature Service 19113:2002 - Quality principles 19143:2010 - Filter encoding 19114:2003 - Quality evaluation procedures 19144-1:2009 - Classification Systems – Part 1: Classification system structure 19115:2003 - Metadata 19144-2 - Land Cover Meta Language (LCML) 19115-2:2009 - Extension for imagery and gridded data 19145 - Registry of representations of geographic point location 19116:2004 - Positioning services 19146:2010 - Cross-domain vocabulary 19117:2005 - Portrayal 19147 - Transfer nodes 19118:2005 - Encoding 19148 - Linear referencing 19119:2005 - Services 19149 - Rights expression language for geographic information 19120:2001 - Functional standards 19150-1 - Ontology - Part 1: Framework 19121:2000 - Imagery and gridded data 19150-2 - Ontology - Part 2: Rules for developing OWL 19122:2004 - Qualifications and Certification of personnel 19148 - Linear referencing 19123:2005 - Schema for coverage geometry and functions 19152 - Land Administration Domain Model (LADM) 19124 - Imagery and gridded data components 19153 - Geospatial Digital Rights Management Reference Model 19125-1:2004 - Simple feature access - Part 1: Common architecture 19154 - Ubiquitous public access - Reference model 19125-2:2004 - SQL option 19155 - Place Identifier (PI) Architecture 19126:2009 - Profile - FACC Data Dictionary 19156 - Observations and measurements 19127:2005 - Geodetic codes and parameters 19157 - Data quality 19128:2005 - Web Map server interface 19158 - Quality assurance of data supply 19129:2009 - Imagery, gridded and coverage data framework 19159 - Calibration and validation of remote sensing imagery sensors and data 19160 - Addressing OGC Standards 22. PUCK 1. Cat: ebRIM App Profile: Earth Observation Products 23. SWE Common Data Model 2. Catalogue Service 24. SWE Service Model 3. CityGML 25. Sensor Model Language 4. Coordinate Transformation 26. Sensor Observation Service 5. Filter Encoding 27. Sensor Planning Service 6. GML in JPEG 2000 28. Simple Features 7. GeoAPI 29. Simple Features CORBA 8. Geopackage 30. Simple Features OLE/COM 9. GeoSparql 31. Simple Features SQL 10. Geography Markup Language 32. Styled Layer Descriptor 11. Geospatial eXtensible Access Control Markup Language (GeoXACML) 33. Symbology Encoding 12. IndoorGML 34. Table Joining Service 13. KML 35. WaterML 14. Location Services (OpenLS) 36. Web Coverage Processing Service 15. NetCDF 37. Web Coverage Service 16. Observations and Measurements 38. Web Feature Service 17. Open GeoSMS 39. Web Map Context 18. OpenMI 40. Web Map Service 19. OpenSearch Geo 41. Web Map Tile Service 20. Ordering Services Framework for Earth Observation Products 42. Web Processing Service 21. OWS Context 43. Web Service Common W3C Standards Accessibility
Recommended publications
  • Show Guideguide Web Searching for GIS Services and Web Mapping Have Been Either Published Or an Introduction Adopted by OGC

    Show Guideguide Web Searching for GIS Services and Web Mapping Have Been Either Published Or an Introduction Adopted by OGC

    showshow guideguide Web searching for GIS services and Web Mapping have been either published or An Introduction adopted by OGC. Who are OGC’s members? to OpenGIS There are three main levels of OGC membership: Principal, Technical and By Adam Gawne-Cain and Chris Holcroft Associate. The higher membership levels confer more voting rights. There are now OpenGIS is the activity pursued by the Open GIS over 300 members featuring 20 Principal members and 25 Technical members from Consortium (OGC). OpenGIS seeks to achieve around the globe. transparent access to disparate geo-data and geo- The membership of OGC is impressively processing resources in a networked environment by broad. Most major GIS companies are members, along with database companies, providing a rich suite of open interface specifications. operating system companies, national mapping agencies, large government These interface specifications will enable GIS developers departments, universities and research to create inter-operable components that provide this institutes. The membership is international, but mainly focused in North transparency. America and Europe. The difference between OpenGIS and A second advantage of OGC’s interface- How does OGC make Interface previous attempts to standardise GIS is based approach is that users can be sure Specifications? that OGC agrees interfaces, and not that they are looking at genuine, live data, Every two months, the OGC Technical neutral file formats. The problem with and not at a static file generated some time Committee (TC) and Management neutral file formats (e.g. SDTS or NTF) in the past. Committee (MC) meet for a week. was that specifications grew so complex The meetings are held in different that each GIS could only support a sub-set A third, practical advantage of interfaces locations around the world, hosted by one of the format.
  • Implementing OGC Web Map Service Client Applications Using JSP, JSTL and XMLC

    Implementing OGC Web Map Service Client Applications Using JSP, JSTL and XMLC

    Implementing OGC Web Map Service Client Applications Using JSP, JSTL and XMLC Hao Ding , Richard Pascoe & Neville Churcher Department of Computer Science University of Canterbury. Christchurch, New Zealand Phone: +64 3 364-2362 Fax: +64 3 364-2569 Email: [email protected] , {richard, neville}@cosc.canterbury.ac.nz Presented at SIRC 2002 – The 14th Annual Colloquium of the Spatial Information Research Centre University of Otago, Dunedin, New Zealand th December 3-5 2002 ABSTRACT Java technologies are widely used in web application development. In this paper are described three approaches to developing Java-based web applications and our experiences with applying each to the development of client that interact with servers implementing the OGC (Open GIS Consortium) Web Map Service (WMS) specification. Also described is the installation and configuration of open source software that implements the WMS specification. The paper is concluded with some preliminary insights into when one of the three approaches to WMS client implementation is more suited to another. Keywords and phrases: WMS, JSP, JSTL, XMLC, map layer, web map server 1.0 INTRODUCTION Of the many technologies, such as Common Gateway Interface (CGI), Active Server Pages (ASP), JavaServer Pages (JSP), that are used to develop web applications, three are of particular interest to the research presented here. These three technologies or approaches to developing clients that utilise web services are JavaServer Pages (JSP), JSP with the use of tags from the JSP Standard Tag Library (JSTL), and the eXtensible Markup Language Compiler (XMLC). JSP is a more convenient way to write Java servlets, and allows the insertion of Java code directly into static HTML (Hypertext Markup Language) pages.
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • Spectrum Spatial Getting Started Guide

    Spectrum Spatial Getting Started Guide

    Spectrum™ Technology Platform Version 12.0 SP1 Spectrum Spatial Getting Started Guide Table of Contents 1 - What Is Location Intelligence? 6 - Services Mapping Service 32 2 - What is Spectrum Spatial? Feature Service 33 Geometry Service 40 Map Tiling Service 43 Spectrum Spatial Concepts 6 Web Feature Service (WFS) 43 Web Map Service (WMS) 44 3 - Modules and Stages Web Map Tile Service (WMTS) 44 Named Resource Service 45 Location Intelligence Module 9 Enterprise Routing Services 45 Enterprise Routing Module 16 Enterprise Geocoding Module 16 GeoConfidence Module 17 4 - Named Resources Named Maps 20 Named Tables 20 Named Layers 20 Named Tiles 21 Named Styles 21 Named Connections 21 Named WMTS Layers 21 Named Label Sources 22 5 - Tools Spatial Manager 24 Management Console 24 Enterprise Designer 24 MapInfo Pro 28 Map Uploader 30 MapInfo Workspace (MWS) Import 30 1 - What Is Location Intelligence? Location intelligence is: • An awareness of relationships between location information and business analysis and operations • The ability to use the understanding of geographic relationships to predict how it impacts a business or organization • The capability to react to how location influences an organization by changing business processes in order to minimize risk and maximize opportunities Location Intelligence enables a business to measure, compare and analyze its data from business operations, in conjunction with external data such as transportation networks, regulatory jurisdictions, market characteristics or its own customers. In this section 2 - What is Spectrum Spatial? Spectrum Spatial is an enterprise location intelligence platform designed to provide organizations with a suite of broadly applicable location capabilities, including spatial analysis, mapping, routing, geocoding, and geoprocessing.
  • Opengis Web Feature Services for Editing Cadastral Data

    Opengis Web Feature Services for Editing Cadastral Data

    OpenGIS Web Feature Services for editing cadastral data Analysis and practical experiences Master of Science thesis T.J. Brentjens Section GIS Technology Geodetic Engineering Faculty of Civil Engineering and Geosciences Delft University of Technology OpenGIS Web Feature Services for editing cadastral data Analysis and practical experiences Master of Science thesis Thijs Brentjens Professor: prof. dr. ir. P.J.M. van Oosterom (Delft University of Technology) Supervisors: drs. M.E. de Vries (Delft University of Technology) drs. C.W. Quak (Delft University of Technology) drs. C. Vijlbrief (Kadaster) Delft, April 2004 Section GIS Technology Geodetic Engineering Faculty of Civil Engineering and Geosciences Delft University of Technology The Netherlands Het Kadaster Apeldoorn The Netherlands i ii Preface Preface This thesis is the result of the efforts I have put in my graduation research project between March 2003 and April 2004. I have performed this research part-time at the section GIS Technology of TU Delft in cooperation with the Kadaster (the Dutch Cadastre), in order to get the Master of Science degree in Geodetic Engineering. Typing the last words for this thesis, I have been realizing more than ever that this thesis marks the end of my time as a student at the TU Delft. However, I also realize that I have been working to this point with joy. Many people are “responsible” for this, but I’d like to mention the people who have contributed most. First of all, there are of course people who were directly involved in the research project. Peter van Oosterom had many critical notes and - maybe even more important - the ideas born out of his enthusiasm improved the entire research.
  • Cityjson: a Compact and Easy-To-Use Encoding of the Citygml Data Model

    Cityjson: a Compact and Easy-To-Use Encoding of the Citygml Data Model

    CityJSON: A compact and easy-to-use encoding of the CityGML data model Hugo Ledoux Ken Arroyo Ohori Kavisha Kumar Balazs´ Dukai Anna Labetski Stelios Vitalis This is the author’s version of the work. It is posted here only for personal use, not for redistribution and not for commercial use. The definitive version will be published in the journal Open Geospatial Data, Software and Standards soon. H. Ledoux, K. Arroyo Ohori, K. Kumar, B. Dukai, A. Labetski, and S. Vitalis (2018). CityJ- SON: A compact and easy-to-use encoding of the CityGML data model. Open Geospatial Data, Software and Standards, In Press. DOI: http://dx.doi.org/10.1186/s40965-019-0064-0 Full details of the project: https://cityjson.org The international standard CityGML is both a data model and an exchange for- mat to store digital 3D models of cities. While the data model is used by several cities, companies, and governments, in this paper we argue that its XML-based ex- change format has several drawbacks. These drawbacks mean that it is difficult for developers to implement parsers for CityGML, and that practitioners have, as a con- sequence, to convert their data to other formats if they want to exchange them with others. We present CityJSON, a new JSON-based exchange format for the CityGML data model (version 2.0.0). CityJSON was designed with programmers in mind, so that software and APIs supporting it can be quickly built. It was also designed to be compact (a compression factor of around six with real-world datasets), and to be friendly for web and mobile development.
  • Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction

    Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction

    Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction - Introduction to Simple Features - What is the GeoPackage? - Esri Support - Looking ahead… Geographic Things 3 Why add spatial data to a database? • The premise: - People want to manage spatial data in association with their standard business data. - Spatial data is simply another “property” of a business object. • The approach: - Utilize the existing SQL data access model. - Define a simple geometry object. - Define well known representations for passing structured data between systems. - Define a simple metadata schema so applications can find the spatial data. - Integrate support for spatial data types with commercial RDBMS software. Simple Feature Model 10 area1 yellow Feature Table 11 area2 green 12 area3 Blue Feature 13 area4 red Geometry Feature Attribute • Feature Tables contain rows (features) sharing common properties (Feature Attributes). • Geometry is a Feature Attribute. Database Simple Feature access Query Connection model based on SQL Cursor Value Geometry Type 1 Type 2 Spatial Geometry (e.g. string) (e.g. number) Reference Data Access Point Line Area Simple Feature Geometry Geometry SpatialRefSys Point Curve Surface GeomCollection LineString Polygon MultiSurface MultiPoint MultiCurve Non-Instantiable Instantiable MultiPolygon MultiLineString Some of the Major Standards Involved • ISO 19125, Geographic Information - Simple feature access - Part 1: common architecture - Part 2: SQL Option • ISO 13249-3, Information technology — Database
  • A Pilot for Testing the OGC Web Services Integration of Water-Related Information and Models

    A Pilot for Testing the OGC Web Services Integration of Water-Related Information and Models

    RiBaSE: A Pilot for Testing the OGC Web Services Integration of Water-related Information and Models Lluís Pesquer Mayos, Simon Jirka, Grumets Research Group CREAF 52°North Initiative for Geospatial Open Source Software Edicifi C, Universitat Autònoma de Barcelona GmbH 08193 Bellaterra, Spain 48155 Münster, Germany [email protected] [email protected] Christoph Stasch, Joan Masó Pau, Grumets Research Group CREAF 52°North Initiative for Geospatial Open Source Software Edicifi C, Universitat Autònoma de Barcelona GmbH Bellaterra, Spain 48155 Münster, Germany [email protected] [email protected] David Arctur, Center for Research in Water Resources, University of Texas at Austin 10100 Burnet Rd Bldg 119, Austin, TX USA [email protected] Abstract—The design of an interoperability experiment to The OGC is an international industry consortium of demonstrate how current ICT-based tools and water data can companies, government agencies and universities participating work in combination with geospatial web services is presented. in a consensus process to develop publicly available interface This solution is being tested in three transboundary river basins: standards. Some successful examples of OGC standards for Scheldt, Maritsa and Severn. The purpose of this experiment is to general spatial purposes are, for example, the Web Map assess the effectiveness of OGC standards for describing status Service (WMS) for providing interoperable pictorial maps and dynamics of surface water in river basins, to demonstrate over the web and the Keyhole Markup Language (KML) as a their applicability and finally to increase awareness of emerging data format for virtual globes. On the other hand, hydrological standards as WaterML 2.0.
  • Metadata and Data Standards. Sharing Data in Hydrology: Best Prac�Ces

    Metadata and Data Standards. Sharing Data in Hydrology: Best PracCes

    Metadata and Data Standards. Sharing Data in Hydrology: Best Prac8ces Ilya Zaslavsky San Diego Supercomputer Center LMI Workshop, Hanoi, August 18-22 / With several slides from last week’s HDWG workshop, presented By HDWG memBers Irina Dornblut, Paul Sheahan, and others/ Outline • Why use standards? • Open Geospaal ConsorFum, and spaal data standards • Standards for water data, and the OGC/WMO Hydrology Domain Working Group – history, acFviFes, WMO connecFon, workshop last week – Suite of water data standards • WaterML 2.0 in detail (opFonal) • Assessing compliance, and the CINERGI project (opFonal) Why sharing data in LMI? • Several countries rely on the Mekong But data sharing is complicated Challenges: Habitat alteraon PolluFon Extreme weather events Over-exploitaon of resources Diseases and invasive species Poverty and social instability . Water - our most valuable asset But ... • In many places we can’t assess – How much we have – Where it is – Who owns it – What it is fit for – How much we will have – Where it will Be • We certainly can’t yet share informaon in a useful Fmeframe – In parFcular given the complexity of water cycle Why is it important to coordinate? • The orBiter was taken within 57 km of the surface where it likely disintegrated Why? • The flight system so[ware used metric units (Newtons); so[ware on the ground used the Imperial system (pound-force, or lbf) A common situaon in hydrology… Hydro Jack Need flow data! Don Hmm mayBe Don can help… *RING RING* To: Jack Hmm, I’ve got one site. I’ll 01/02/09, 3.2, 3, 1 Hi Don, I need some send it through… 01/02/09, 3.1, 3, 1 *RING RING* upper Derwent flow 10 minutes… readings for my 10 minutes… Ok.
  • XML Pipeline Performance

    XML Pipeline Performance

    XML Pipeline Performance Nigel Whitaker DeltaXML Ltd <[email protected]> Tristan Mitchell DeltaXML Ltd <[email protected]> Abstract This paper considers XML pipeline performance of a case study constructed from real code and data. It extends our original small study into 'Filter Pipeline Performance' on the saxon-help email list. The system used in this case study is a comparison tool for OASIS OpenDocument Text or '.odt' files. We will not describe the code in detail, but rather concentrate on the mechanisms used to interlink the various pipeline components used. These components include XML parsers, XSLT filter stages, XML comparison, Java filters based on the SAX XMLFilter interface and serialization. In the previous study we compared two pipelining techniques; this paper will extend this to consider three mechanisms which can be used to construct pipelines; these are: • The Java API for XML Processing (JAXP) included in Java Standard Edition 1.4 and subsequent releases • The s9api package provided by the Saxon XSLT processor 9.0 and sub- sequent releases • The Calabash implementation of the XProc XML pipeline language Our primary focus is performance and we will look at run times and memory sizes using these technologies. The overall runtime of the complete system will be described, but we will then concentrate on the performance of running a chain of filters (XSLT and Java based) as this is likely to be of moregeneral interest. We will also discuss some optimization techniques we have implemen- ted during the development process and further ideas for future performance improvement work. 1. Introduction In this section we will introduce the system being studied, briefly describe the data and also some aspects of the experimental approach.
  • OWS-4 Geodds Mass Market (Formerly Georss) Interoperability Program Report

    OWS-4 Geodds Mass Market (Formerly Georss) Interoperability Program Report

    OGC 07-004 Open Geospatial Consortium Inc. Date: 2007-05-02 Reference number of this OGC® document: OGC 07-004 Version: 0.0.1 Category: OpenGIS® Discussion Paper Editor: Panagiotis (Peter) A. Vretanos OWS-4 GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report Copyright notice Copyright © 2007 Open Geospatial Consortium. All Rights Reserved To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ Warning This document is not an OGC Standard. This document is an OGC Discussion Paper and is therefore not an official position of the OGC membership. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Further, an OGC Discussion Paper should not be referenced as required or mandatory technology in procurements. Document type: OpenGIS® Discussion Paper Document subtype: Engineering Specification Document stage: Draft Document language: English File name: 07-004.doc OGC 07-004 Contents 1 SCOPE..........................................................................................................................................................1 2 CONFORMANCE........................................................................................................................................1 3 NORMATIVE REFERENCES....................................................................................................................1 4 TERMS AND DEFINITIONS.....................................................................................................................3
  • Access Control Models for XML

    Access Control Models for XML

    Access Control Models for XML Abdessamad Imine Lorraine University & INRIA-LORIA Grand-Est Nancy, France [email protected] Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 2 Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 3 What is XML? • eXtensible Markup Language [W3C 1998] <files> "<record>! ""<name>Robert</name>! ""<diagnosis>Pneumonia</diagnosis>! "</record>! "<record>! ""<name>Franck</name>! ""<diagnosis>Ulcer</diagnosis>! "</record>! </files>" 4 What is XML? • eXtensible Markup Language [W3C 1998] <files>! <record>! /files" <name>Robert</name>! <diagnosis>! /record" /record" Pneumonia! </diagnosis> ! </record>! /name" /diagnosis" <record …>! …! </record>! Robert" Pneumonia" </files>! 5 XML for Documents • SGML • HTML - hypertext markup language • TEI - Text markup, language technology • DocBook - documents -> html, pdf, ... • SMIL - Multimedia • SVG - Vector graphics • MathML - Mathematical formulas 6 XML for Semi-Structered Data • MusicXML • NewsML • iTunes • DBLP http://dblp.uni-trier.de • CIA World Factbook • IMDB http://www.imdb.com/ • XBEL - bookmark files (in your browser) • KML - geographical annotation (Google Maps) • XACML - XML Access Control Markup Language 7 XML as Description Language • Java servlet config (web.xml) • Apache Tomcat, Google App Engine, ... • Web Services - WSDL, SOAP, XML-RPC • XUL - XML User Interface Language (Mozilla/Firefox) • BPEL - Business process execution language