DOCSLIB.ORG

1 Proposed IMMA Revisions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1 Proposed IMMA Revisions Proposed IMMA Revisions Revised DRAFT, 19 August 2015 (v21) Scott Woodruff, Dave Berry, Philip Brohan, Eric Freeman, Zaihua Ji, Elizabeth Kent, Sandy Lubker, Shawn Smith, Steve Worley et al. Introduction Format changes—to yield IMMA version 1—are marked below in blue within Supplement C of the current IMMA (version 0) documentation. The abbreviated version of the documentation (http://icoads.noaa.gov/e-doc/imma/R2.5-imma_short.pdf) includes Supp. D, providing details on individual field configurations; whereas the complete documentation (http://icoads.noaa.gov/e-doc/imma/R2.5-imma.pdf) also provides additional background in its main text and in Supps. A-B, including more detailed comparisons between IMMA and international exchange (IMMT/IMMPC) formats. Detailed background/discussion notes for the Core and attachments (attms) appear following each table below. When significant changes or additions to attm content were needed (i.e. for Immt, Mod-qc, and Meta-vos) a revised attm was created with a new table number and new attachment ID (ATTI), but the old configuration was retained as a deprecated attm. The Nocn, Ecr, Rean-qc, Ivad, Error, and Uida attms are new, and the Auto, Nocq, Alt-qc, Track, and Hist attms are proposed (with many details of the proposed attms to be finalized; including any new field abbreviations, which need to be checked for uniqueness to avoid possible overlaps with already defined field abbreviations). The following items discuss aspects of the planned changes in greater detail: 1. Abbreviated structural element names in italics: A new IMMA documentation feature— to enhance communication—is that the Core and attms (e.g. Icoads) are all given abbreviated names in italics, but with only the first letter in uppercase, to distinguish them from the fully capitalized IMMA field abbreviations. 2. Switch to attm-internal field numbering: E.g. within the Icoads attm, the fields are now numbered 1-51 rather than 49-99. Otherwise documentation maintenance was becoming challenging, and in conjunction with the IVAD project this is viewed as a more flexible approach. However, the revised Fortran program to read/write IMMA1 ({rwimma1}1) still utilizes a linear field numbering approach for assigning array storage across the Core and all attms. 3. Operational and deprecated attms: Rather than change (i.e. add/subtract, or modify, fields) attms, a new attm version is created, with tables for the deprecated attms tentatively retained only in the last-version format documentation (and noting that by itself the item 2 field numbering switch is not considered such a change). The {rwimma1} program is able to read both the operational and deprecated attms, and the format remains fully backward compatible. Related also to item 2, the new Rean-qc, Ivad, and Error attms include fields for input component number (i.e. 0=Core or ATTI) (ICNR/ICNI/ICNE) and field number within the input component number (FNR/FNI/FNE). 1 In this document, {braces} are used to mark the names of Fortran software, with {rwimma1} referring specifically to http://icoads.noaa.gov/software/rwimma1. With limited modifications, this program can also write IMMA1. In terms of processing new attms, the current program will process the Nocn, Ecr, Rean-qc, Ivad, Error, and Uida attms, including processing of Subsidiary records. 1 4. Additional software maintenance considerations: To make translation software adapted from {rwimma} (e.g. existing adaptations of {rwimma1} used to translate data from other formats into IMMA) more robust over the longer term, usage of field abbreviations (e.g. FTRUE(SST)) rather than hard-coded storage array locations (e.g. FTRUE(35)) appears prudent with the advantage e.g. W2 is defined in both Tables C2 and C5. 5. Switch to multi-record “linked-report” approach: Rather than modifying the Icoads attm as originally proposed to include UID and associated release-tracking information etc., those fields are placed in a short new Uida attm (see Table C98), which appears both in the Main and (any optional) Subsidiary records, linking them all together, e.g.: Main IMMA record: Core + Icoads + Immt + Mod-qc + Meta-vos + Nocn + Uida + Suppl Subsidiary IMMA record: Uida + Rean-qc + Rean-qc + Rean-qc … + Rean-qc Subsidiary IMMA record: Uida + Ivad + Ivad + Ivad … + Ivad Subsidiary IMMA record: Uida + Error + Error + Error … + Error Each complete multi-record construct (i.e. Main plus Subsidiary records) is referred to below as a “linked-report.” Alternatively, information such as ship metadata (Meta-vos) attms, or the proposed alternative QC (Alt-qc) attms, might be conveyed separately back to ICOADS in a file containing only Subsidiary records, i.e. to be blended with (or possibly into fields in other attms, in the case of Alt-qc) the Main records before provision to users: Subsidiary IMMA record: Uida + Meta-vos Subsidiary IMMA record: Uida + Alt-qc + Alt-qc + Alt-qc … + Alt-qc Such Subsidiary-only records thus would not ordinarily be provided directly to users. The way this is being implemented is still anticipated to be fully backward compatible. The Core has not changed, but {rwimma1} checks the first few characters of each record to determine whether it is a Subsidiary record (i.e. starts with “9815”). 6. Software constraints on linked-reports and attm composition: Processing by {rwimma1} of Main+Subsidiary records (linked-reports), and of the Ivad and Error attms, presently is being implemented with these fairly loose constraints: (i) Both Main and Subsidiary records are allowed by {rwimma1} to contain multiples of any attachment in any order; except the Suppl attm, if present, must be the last Main attm. (ii) In the event of repeating (except Ivad and Error) attms, the last attm takes precedence and overwrites information from all previous (e.g. Subsidiary attms take precedence over any repeating Main attms). (iii) Subsidiary records must each begin with a Uida attm, followed by zero or more attms of any type except Suppl. (iv) The maximum number of Ivad and Error attms within a linked-report is set at 100 each. In addition, while by definition of UID two (or more) Main records should never appear with the same UID, no check is envisioned as feasible at the present time for UID uniqueness. 7. Status of new-field content: In the revised attms (Immt, Mod-qc, and Meta-vos) newly defined fields generally will not be populated (i.e. in the prototype Release 2.5 dataset), with the exception of field MDS in the Meta-vos attm (see also related discussion in Annex C). In the new Uida attm, UID is set as discussed below Table C98, and the Release number fields are set as RN1=2, RN2=5, RN3=1, i.e. this is considered R2.5.1, to distinguish it from the original R2.5. 2 Table 1 provides a summary of the development status of the IMMA components, and Table 2 outlines different record structures currently available with Release 2.5 (R2.5), the prototype Release 2.5.1 (R2.5.1), or under development for Release 3.0 (R3.0). These Annexes provide additional background information: • Annex A: Implementation/Unresolved Issues • Annex B: Development of the Unique Report ID (UID); and Intra-record Release No. (RN) Tracking • Annex C: Reprocessing Notes for Recovering Missing Field Configurations, Etc. • Annex D: QC Flag Discussion • Annex E: Edited Cloud Report (Ecr) attm • Annex F: Author Reference Code (ARC) Registration and Storage • Annex G: Discussion of ICOADS Future IMMA/IVAD Archival Structure NOTE: strikethrough in Suppl. C below indicates updates are still needed, or marks material that has been moved elsewhere. Table 1. Status of IMMA components and related information. Shaded components are deprecated. Component Abbrev. Status Reference Length information (char.) Core Core operational Table C0 108 ICOADS attm Icoads operational Table C1 65 IMMT-2/FM 13 attm (none) deprecated Table C2 (sep. doc.) 76 Model quality control attm (none) deprecated Table C3 (sep. doc.) 66 Ship metadata attm (none) deprecated Table C4 (sep. doc.) 67 IMMT-5/FM 13 attm Immt operational Table C5 94 Model quality control attm Mod-qc operational Table C6 68 Ship metadata attm Meta-vos operational Table C7 58 Near-surface oceano. attm Nocn operational Table C8 102 Edited cloud report attm Ecr operational Table C9 – Annex E 32 Reanalyses QC/feedback attm Rean-qc operational Table C95 61 IVAD attm Ivad operational Table C96 53 Error attm Error operational Table C97 variable Unique report ID attm Uida operational Table C98 15 Supplemental data attm Suppl operational Table C99 variable Automated instrument. attm Auto proposed Table CP1 41 Near-surface oceano. QC attm Nocq proposed Table CP2 28 Alternative QC attm Alt-qc proposed Table CP3 TBD Platform tracking attm Track proposed Table CP4 TBD Historical attm Hist proposed Table CP5 TBD Buoy metadata attm Meta-buoy proposed TBD TBD Daily observational (Daily) attm Daily proposed TBD TBD 3 Table 2. IMMA record structures currently operational for R2.5, R2.5.1, and the “linked-report” Main + Subsidiary (optional) record structure being implemented for R3.0. Inclusion of the attm count (ATTC) field in the Core, and of the attm ID (ATTI) and attm data length (ATTL) fields at the beginning of each attm, enables computer parsing of the records. Thus additional variations on these basic record types are implemented by inclusion or omission of attms, and new attms can be defined in the future as needed for new data or metadata requirements.1 Release Record structure Len. (char.)2 R2.5 Core + Icoads + Immt2 + Mod-qc3 + Meta-vos3 [+ Suppl] 372 R2.5.1 Core + Icoads + Immt + Mod-qc + Meta-vos + Uida [+ Suppl] 408 R3.0: Main Core + Icoads + Immt + Mod-qc + Meta-vos + Nocn + Ecr + Uida [+ Suppl] 544 Subsid.
Load more

Recommended publications
  • Seamless Interoperability and Data Portability in the Social Web for Facilitating an Open and Heterogeneous Online Social Network Federation
    Seamless Interoperability and Data Portability in the Social Web for Facilitating an Open and Heterogeneous Online Social Network Federation vorgelegt von Dipl.-Inform. Sebastian Jürg Göndör geb. in Duisburg von der Fakultät IV – Elektrotechnik und Informatik der Technischen Universität Berlin zur Erlangung des akademischen Grades Doktor der Ingenieurwissenschaften - Dr.-Ing. - genehmigte Dissertation Promotionsausschuss: Vorsitzender: Prof. Dr. Thomas Magedanz Gutachter: Prof. Dr. Axel Küpper Gutachter: Prof. Dr. Ulrik Schroeder Gutachter: Prof. Dr. Maurizio Marchese Tag der wissenschaftlichen Aussprache: 6. Juni 2018 Berlin 2018 iii A Bill of Rights for Users of the Social Web Authored by Joseph Smarr, Marc Canter, Robert Scoble, and Michael Arrington1 September 4, 2007 Preamble: There are already many who support the ideas laid out in this Bill of Rights, but we are actively seeking to grow the roster of those publicly backing the principles and approaches it outlines. That said, this Bill of Rights is not a document “carved in stone” (or written on paper). It is a blog post, and it is intended to spur conversation and debate, which will naturally lead to tweaks of the language. So, let’s get the dialogue going and get as many of the major stakeholders on board as we can! A Bill of Rights for Users of the Social Web We publicly assert that all users of the social web are entitled to certain fundamental rights, specifically: Ownership of their own personal information, including: • their own profile data • the list of people they are connected to • the activity stream of content they create; • Control of whether and how such personal information is shared with others; and • Freedom to grant persistent access to their personal information to trusted external sites.
    [Show full text]
  • The International Maritime Meteorological Archive
    ARCHIVAL OF DATA OTHER THAN IN IMMT FORMAT: The International Maritime Meteorological Archive (IMMA) Format Rapporteur: Scott Woodruff NOAA Earth System Research Laboratory (ESRL), Boulder, CO, USA Updated Report (14 March 2007) Update of JCOMM-SGMC-VIII/Doc.17 submitted to: Joint WMO-IOC Technical Commission for Oceanography and Marine Meteorology (JCOMM) Working Group on MMS, Subgroup on Marine Climatology (SGMC) Eighth Session, Asheville, NC, USA (10-14 April 2000) ————— Update of ETMC-I/Doc. 4.1, Appendix submitted to: JCOMM Expert Team on Marine Climatology (ETMC) First Session, Gdynia, Poland (7-10 July 2004) ————— Appendix of ETMC-II/Doc. 4.1 submitted to: JCOMM Expert Team on Marine Climatology (ETMC) Second Session, Geneva, Switzerland (26-27 March 2007) Contents Introduction Background Format Content and Structure Format Implementation References Supplements: A. Existing Formats and Codes B. Comparison of WMO IMM and ICOADS LMR Formats C. Record Types D. Field Configurations Document Revision Information Introduction 1. With increasing recognition of the importance of upgrading and maximizing the data available for analyses of the climate record (Barnett et al. 1999), efforts have intensified to digitize additional historical ship data (and metadata) that exist in many national logbook collections (Diaz and Woodruff 1999, Woodruff et al. 2004). Current efforts are focused on data during major gaps in the existing record, such as the two world wars, and adding 19th century and earlier data (e.g., Elms et al. 1993, Manabe 1999, García- Herrera et al. 2005, Woodruff et al. 2005). 2. At present, however, there is no effective, internationally agreed format for exchange of keyed historical data.
    [Show full text]
  • Download Pdf Encoded Base64 Download Pdf Encoded Base64
    download pdf encoded base64 Download pdf encoded base64. Completing the CAPTCHA proves you are a human and gives you temporary access to the web property. What can I do to prevent this in the future? If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware. If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices. Another way to prevent getting this page in the future is to use Privacy Pass. You may need to download version 2.0 now from the Chrome Web Store. Cloudflare Ray ID: 67d29af1285415e8 • Your IP : 188.246.226.140 • Performance & security by Cloudflare. Downloading a base 64 PDF from an api request in Javascript. Possibly the longest and most specific title in a tech related Medium post I’ve written to date. I had this exact issue a while ago and couldn’t seem to find any good posts or articles covering it so I thought I’d create my own for future front end devs that might have the same problem. The problem. Saving a pdf as base 64 in the backend makes sense, but to the user it’s just a random combination of numbers and letters. Luckily html natively supports parsing base64 pdfs to normal ones and downloading them like so. Which works really well in modern browsers. However, in the scenario where there’s no base64 pdf code when the user first lands on the site and they need to click a button to fetch the code from a database, how would you get this code above.
    [Show full text]
  • AMIRA Supports a Wide Range of Recording Codecs, Resolutions and Project Settings to Fit Your Needs
    AMIRA Software Update Package 5.4 U S E R M A N U A L 16 August 2018 2 Imprint Imprint Copyright © 2018 Arnold & Richter Cine Technik GmbH & Co. Betriebs KG. All rights reserved. No portions of this document may be reproduced without prior written consent of Arnold & Richter Cine Technik GmbH & Co. Betriebs KG. Specifications are subject to change without notice. Errors, omissions, and modifications excepted. AMIRA, ALEXA, ALEXA XT, ALEXA SXT, ALEXA LF and ALEXA Mini are trademarks or registered trademarks of Arnold & Richter Cine Technik GmbH & Co. Betriebs KG. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. Original version. For further assistance Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Tuerkenstr. 89 D-80799 Munich, Germany E-mail: [email protected] www.arri.com/service Document revision history Document ID: 10000464 Version Release Date 1.0 K08608 12 Sep 2014 1.1 K08658 19 Dec 2014 2.0 K08781 31 Mar 2015 3.0 K08941 02 Nov 2015 4.0 K09036 23 May 2016 4.1 K09090 07 June 2016 5.0 K09396 21 June 2017 5.2 K09599 08 Dec 2017 5.3 K09696 30 May 2018 5.4 K09800 16 August 2018 Contents 3 Contents 1 For Your Safety / 为了您的安全............................................................. 9 1.1 Risk Levels and Alert Symbols / 危险级别和警示标志.......................... 9 1.2 Vital Precautions / 重要安全措施.........................................................10 1.3 General Precautions / 般安全措施.......................................................11 2 Sensor Related Information
    [Show full text]
  • Netwitness Hunting Guide Copyright © 1994-2019 Dell Inc
    NetWitness Hunting Guide Copyright © 1994-2019 Dell Inc. or its subsidiaries. All Rights Reserved. Trademarks RSA, the RSA Logo and EMC are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. All other trademarks used herein are the property of their respective owners. For a list of EMC trademarks, go to www.emc.com/legal/emc-corporation-trademarks.htm. License Agreement This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any other person. No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by EMC. Third-Party Licenses This product may include software developed by parties other than RSA. Note on Encryption Technologies This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when using, importing or exporting this product. Distribution Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC believes the information in this publication is accurate as of its publication date.
    [Show full text]
  • Ariba Buyer Configuration Guide Iii Table of Contents
    Ariba Buyer™ Configuration Guide Release 9r1 Document Version 21 August 2013 Copyright © 1996–2012 Ariba, Inc. All rights reserved. This documentation, as well as the Ariba software and/or services described in it, contain proprietary information. They are provided under a license or other agreement containing restrictions on use and disclosure and are also protected by copyright, patent and/or other intellectual property laws. Except as permitted by such agreement, no part of the document may be reproduced or transmitted in any form by any means, electronic, mechanical or otherwise, without the prior written permission of Ariba, Inc. Ariba, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the documentation. The information contained in the documentation is subject to change without notice. Ariba, the Ariba logo, AribaLIVE, SupplyWatch, Ariba.com, Ariba.com Network and Ariba Spend Management. Find it. Get it. Keep it. and PO-Flip are registered trademarks of Ariba, Inc. Ariba Procure-to-Pay, Ariba Buyer, Ariba eForms, Ariba PunchOut, Ariba Services Procurement, Ariba Travel and Expense, Ariba Procure-to-Order, Ariba Procurement Content, Ariba Sourcing, Ariba Savings and Pipeline Tracking, Ariba Category Management, Ariba Category Playbooks, Ariba StartSourcing, Ariba Spend Visibility, Ariba Analysis, Ariba Data Enrichment, Ariba Contract Management, Ariba Contract Compliance, Ariba Electronic Signatures, Ariba StartContracts, Ariba Invoice Management, Ariba Payment Management, Ariba Working Capital Management, Ariba Settlement, Ariba Supplier Information and Performance Management, Ariba Supplier Information Management, Ariba Discovery, Ariba Invoice Automation, Ariba PO Automation, Ariba Express Content, Ariba Ready, and Ariba LIVE are trademarks or service marks of Ariba, Inc.
    [Show full text]
  • Werkzeug Documentation (1.0.X) Release 1.0.1
    Werkzeug Documentation (1.0.x) Release 1.0.1 Pallets May 11, 2021 Contents 1 Getting Started 3 1.1 Installation................................................3 1.2 Werkzeug Tutorial............................................5 1.3 API Levels................................................ 13 1.4 Quickstart................................................ 14 2 Serving and Testing 21 2.1 Serving WSGI Applications....................................... 21 2.2 Test Utilities............................................... 26 2.3 Debugging Applications......................................... 32 3 Reference 37 3.1 Request / Response Objects....................................... 37 3.2 URL Routing............................................... 55 3.3 WSGI Helpers.............................................. 69 3.4 Filesystem Utilities............................................ 76 3.5 HTTP Utilities.............................................. 76 3.6 Data Structures.............................................. 85 3.7 Utilities.................................................. 101 3.8 URL Helpers............................................... 109 3.9 Context Locals.............................................. 116 3.10 Middleware................................................ 119 3.11 HTTP Exceptions............................................ 124 4 Deployment 131 4.1 Application Deployment......................................... 131 5 Additional Information 137 5.1 Important Terms............................................. 137 5.2 Unicode.................................................
    [Show full text]
  • Mom Documentation Release 0.1.3
    mom Documentation Release 0.1.3 Yesudeep Mangalapilly July 30, 2015 Contents 1 Getting the library 3 2 User Guides 5 2.1 Contributing...............................................5 3 API Documentation 7 3.1 mom ...................................................7 3.2 Codecs.................................................. 28 3.3 Cryptography primitives......................................... 46 3.4 Networking................................................ 51 3.5 Operating System helpers........................................ 52 4 Contribute 55 4.1 Contributing............................................... 55 5 Indices and tables 57 Python Module Index 59 i ii mom Documentation, Release 0.1.3 Mother of all our Python projects. Batteries for Python. Contents 1 mom Documentation, Release 0.1.3 2 Contents CHAPTER 1 Getting the library $ pip install mom or $ git clone git://github.com/gorakhargosh/mom.git or $ git clone http://code.google.com/p/python-mom/ $ cd mom $ python setup.py install 3 mom Documentation, Release 0.1.3 4 Chapter 1. Getting the library CHAPTER 2 User Guides 2.1 Contributing Welcome hackeratti! So you have got something you would like to see in mom? Whee. This document will help you get started. 2.1.1 Important URLs mom uses git to track code history and hosts its code repository at github. The issue tracker is where you can file bug reports and request features or enhancements to mom. 2.1.2 Before you start Ensure your system has the following programs and libraries installed before beginning to hack: 1. Python 2. git 3. ssh 2.1.3 Setting up the Work Environment mom makes extensive use of zc.buildout to set up its work environment. You should get familiar with it. Steps to setting up a clean environment: 1.
    [Show full text]
  • Testowanie Bezpieczeństwa Aplikacji Internetowych. Receptury
    Testowanie bezpieczeñstwa aplikacji internetowych. Receptury Autor: Paco Hope, Ben Walther T³umaczenie: Rados³aw Meryk ISBN: 978-83-246-2208-5 Tytu³ orygina³u: Web Security Testing Cookbook Format: 168x237, stron: 312 Poznaj i wykorzystaj mechanizmy testowania zabezpieczeñ, a nikt nie przeœlizgnie siê przez Twoj¹ witrynê! • Jak zainstalowaæ i skonfigurowaæ narzêdzia do testowania zabezpieczeñ? • Jak szybko i sprawnie znaleŸæ problemy w aplikacjach? • Jak wykorzystywaæ testy powtarzalne? Witryny internetowe oraz ich aplikacje stanowi¹ swoist¹ wirtualn¹ furtkê do wszystkich korporacji i instytucji. Jak zatem zadbaæ, aby nikt niepo¿¹dany nie przedosta³ siê do œrodka? Co sprawia, ¿e witryna jest naprawdê bezpieczna? I w jaki sposób testowaæ aplikacjê, aby nie by³ to proces ¿mudny i czasoch³onny, a raczej sprawny i skuteczny? Oto rozwi¹zanie — niniejsza ksi¹¿ka zawiera proste receptury, dziêki którym z ³atwoœci¹ znajdziesz luki w aplikacjach, zanim zrobi¹ to ró¿ni hakerzy. Ksi¹¿ka „Testowanie bezpieczeñstwa aplikacji internetowych. Receptury” to napisany zrozumia³ym jêzykiem podrêcznik, dziêki któremu szybko poznasz mechanizmy testowania zabezpieczeñ. Praktyczne przyk³ady zawarte w tym przewodniku sprawi¹, ¿e szybko nauczysz siê w³¹czaæ systemy zabezpieczeñ do standardowych procedur kontroli aplikacji. Bez problemu stworzysz testy dotycz¹ce funkcji AJAX, a tak¿e przeprowadzisz rozbudowane, wieloetapowe testy podatnoœci na klasyczne problemy: skrypty krzy¿owe oraz wstrzykiwanie kodu. • Bezpieczeñstwo oprogramowania • Instalacja darmowych narzêdzi
    [Show full text]
  • Werkzeug Documentation (0.15.X) Release 0.15.6
    Werkzeug Documentation (0.15.x) Release 0.15.6 Pallets Jan 26, 2020 Contents 1 Getting Started 3 1.1 Installation................................................3 1.2 Transition to Werkzeug 1.0........................................5 1.3 Werkzeug Tutorial............................................6 1.4 API Levels................................................ 14 1.5 Quickstart................................................ 15 2 Serving and Testing 21 2.1 Serving WSGI Applications....................................... 21 2.2 Test Utilities............................................... 26 2.3 Debugging Applications......................................... 32 3 Reference 37 3.1 Request / Response Objects....................................... 37 3.2 URL Routing............................................... 54 3.3 WSGI Helpers.............................................. 67 3.4 Filesystem Utilities............................................ 74 3.5 HTTP Utilities.............................................. 74 3.6 Data Structures.............................................. 83 3.7 Utilities.................................................. 99 3.8 URL Helpers............................................... 106 3.9 Context Locals.............................................. 112 3.10 Middleware................................................ 115 3.11 HTTP Exceptions............................................ 121 4 Deployment 127 4.1 Application Deployment......................................... 127 5 Contributed Modules 133 5.1 Contributed
    [Show full text]
  • Search Improvement Within the Geospatial Web in the Context of Spatial Data Infrastructures
    2012 22 Aneta Jadwiga Florczyk Search improvement within the geospatial web in the context of spatial data infrastructures Departamento Informática e Ingeniería de Sistemas Director/es Zarazaga Soria, Francisco Javier López Pellicer, Francisco Javier Tesis Doctoral Autor Director/es UNIVERSIDAD DE ZARAGOZA Repositorio de la Universidad de Zaragoza – Zaguan http://zaguan.unizar.es Departamento Director/es Tesis Doctoral SEARCH IMPROVEMENT WITHIN THE GEOSPATIAL WEB IN THE CONTEXT OF SPATIAL DATA INFRASTRUCTURES Autor Aneta Jadwiga Florczyk Director/es Zarazaga Soria, Francisco Javier López Pellicer, Francisco Javier UNIVERSIDAD DE ZARAGOZA Informática e Ingeniería de Sistemas 2012 Repositorio de la Universidad de Zaragoza – Zaguan http://zaguan.unizar.es Departamento Director/es Tesis Doctoral Autor Director/es UNIVERSIDAD DE ZARAGOZA Repositorio de la Universidad de Zaragoza – Zaguan http://zaguan.unizar.es SEARCH IMPROVEMENT WITHIN THE GEOSPATIAL WEB IN THE CONTEXT OF SPATIAL DATA INFRASTRUCTURES Aneta Jadwiga Florczyk PhD DISSERTATION RESEARCH ADVISORS Dr. Francisco Javier Zarazaga–Soria Dr. Francisco Javier López–Pellicer May 2012 Computer Science and Systems Engineering Department Universidad de Zaragoza © Copyright by author, copyrightyear All Rights Reserved iii Acknowledgments I would like to thank all members of the IAAA research group of the University of Zaragoza, to which I had pleasue belong during the thesis development, for their collaboration and support in any aspect, and especially, my research advisors, F.Javier Zarazaga–Soria and F.Javier López–Pellicer for their endless forbearance and patience. Also, I would like to express my gratitude to members of the IFGI of the University of Muenster, Germany, and every other person I have met there, who made effort to make my stay a wonderful ex- perience, which has contributed to my profesional and personal development.
    [Show full text]
  • DNS-Morph: UDP-Based Bootstrapping Protocol for Tor
    Rami Ailabouni*, Orr Dunkelman, and Sara Bitan DNS-Morph: UDP-Based Bootstrapping Protocol For Tor Abstract: Tor is one of the most popular systems for on the Internet. Organizations and governments engage anonymous communication and censorship circumven- in Internet censorship due to variety of reasons, among tion on the web, currently used by millions of users every them political, moral, or religious. Since Tor became day. This puts Tor as a target for attacks by organiza- public in 2002 [11] and started gaining popularity among tions and governmental bodies whose goal is to hinder users in the world as a system for anonymous commu- users’ ability to connect to it. These attacks include deep nication and censorship circumvention, many countries packet inspection (DPI) to classify Tor traffic as well tried to block their citizens’ connections to it. These as legitimate Tor client impersonation (active probing) attempts started with simple methods like blacklisting to expose Tor bridges. As a response to Tor-blocking Tor’s website [45] so users would not be able to reach it attempts, the Tor community has developed Pluggable and download the Tor client software [42], and got more Transports (PTs), tools that transform the appearance sophisticated with time to include actively downloading of Tor’s traffic flow. the Tor nodes (also called relays) list from the Tor Di- In this paper we introduce a new approach aiming to rectory Servers and blacklisting them, deploying DPI enhance the PT’s resistance against active probing at- to search for Tor communication characteristics (e.g., tacks, as well as white-listing censorship by partitioning Tor’s TLS handshake cipher suite [58]), as well as ac- the handshake of the PT from its encrypted communi- tive probing (impersonating a Tor client and connecting cation.
    [Show full text]