DOCSLIB.ORG

Spectrum Technology Platform Version 2018.2.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Spectrum Technology Platform Version 2018.2.0 Spectrum Technology Platform Version 2018.2.0 Web Services Guide Table of Contents 1 - Getting Started REST 4 SOAP 26 2 - Web Services Enabling CORS 46 REST 47 SOAP 463 Chapter : Appendix Appendix A: Buffering 871 Appendix B: Country Codes 874 Appendix C: Validate Address Confidence Algorithm 899 1 - Getting Started In this section REST 4 SOAP 26 Getting Started REST The REST Interface Spectrum™ Technology Platform provides a REST interface to web services. User-defined web services, which are those created in Enterprise Designer, support GET and POST methods. Default services installed as part of a module only support GET. If you want to access one of these services using POST you must create a user-defined service in Enterprise Designer. To view the REST web services available on your Spectrum™ Technology Platform server, go to: http://server:port/rest Note: We recommend that you limit parameters to 2,048 characters due to URL length limits. Service Endpoints The endpoint for an XML response is: http://server:port/rest/service_name/results.xml The endpoint for a JSON response is: http://server:port/rest/service_name/results.json Endpoints for user-defined web services can be modified in Enterprise Designer to use a different URL. Note: By default Spectrum™ Technology Platform uses port 8080 for HTTP communication. Your administrator may have configured a different port. WADL URL The WADL for a Spectrum™ Technology Platform web service is: http://server:port/rest/service_name?_wadl For example: http://myserver:8080/rest/ValidateAddress?_wadl User Fields You can pass extra fields through the web service even if the web service does not use the fields. These fields are returned, unmodified, in the user_fields section of the response. For GET Spectrum Technology Platform 2018.2.0 Web Services Guide 4 Getting Started requests, user fields are passed in as a parameter in the URL like any other field. For POST requests, user fields are passed in as part of the user_fields element in the XML or JSON request. Note: User field names may not contain characters that are invalid in XML or JSON element names. For example, spaces are not valid. Sample REST Request Using GET with XML Response The following example illustrates how to make a REST request to the ValidateAddress service using the GET method requesting a response in XML. http://myserver:8080/rest/ValidateAddress/results.xml?Option.OutputCasing=U& Data.AddressLine1=1825+Kramer+Lane&Data.PostalCode=78759 The sample request would result in this response since an XML response was requested: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <xml.ValidateAddressResponse xmlns="http://www.pb.com/spectrum/services/ValidateAddress"> <output_port> <Address> <Confidence>82</Confidence> <RecordType>Normal</RecordType> <CountryLevel>A</CountryLevel> <ProcessedBy>USA</ProcessedBy> <MatchScore>0</MatchScore> <AddressLine1>1825 KRAMER LN</AddressLine1> <City>AUSTIN</City> <StateProvince>TX</StateProvince> <PostalCode>78758-4260</PostalCode> <PostalCode.Base>78758</PostalCode.Base> <PostalCode.AddOn>4260</PostalCode.AddOn> <Country>UNITED STATES OF AMERICA</Country> <user_fields/> </Address> </output_port> </xml.ValidateAddressResponse> Sample REST Request Using GET with JSON Response The following example illustrates how to make a REST request to the ValidateAddress service using the GET method requesting a response in JSON. http://myserver:8080/rest/ValidateAddress/results.json?Option.OutputCasing=U& Data.AddressLine1=1825+Kramer+Lane&Data.PostalCode=78759 The sample request wold result in this response since a JSON response was requested: { "ns1.json.ValidateAddressResponse" : Spectrum Technology Platform 2018.2.0 Web Services Guide 5 Getting Started { "ns1.output_port" : { "ns1.Confidence" : 82, "ns1.RecordType" : "Normal", "ns1.CountryLevel" : "A", "ns1.ProcessedBy" : "USA", "ns1.MatchScore" : 0, "ns1.AddressLine1" : "1825 KRAMER LN", "ns1.City" : "AUSTIN", "ns1.StateProvince" : "TX", "ns1.PostalCode" : "78758-4260", "ns1.PostalCode.Base" : 78758, "ns1.PostalCode.AddOn" : 4260, "ns1.Country" : "UNITED STATES OF AMERICA" } } } JSON POST Request User-defined web services can be exposed as a REST web service and configured to have a POST method that accepts JSON input. Specify Content-Type:application/json and use the following format for JSON POST requests. Flat Data Use this format in the body request to send flat data to a web service using POST. { "InputStageName": { "InputDataType": [ { "FieldName1": "FieldValue1", "FieldName2": "FieldValue2" } ] } } Where: InputStageName The name of the input stage as shown on the canvas in Enterprise Designer. The default name of the stage is Input. InputDataType The name given to the record-level entity. This value is specified in the dataflow's Input stage, in the Data type name field on the Input Fields tab. The default name of the record-level entity is Row. Spectrum Technology Platform 2018.2.0 Web Services Guide 6 Getting Started FieldName1 and FieldName2 The names of the input fields defined in the service's Input stage. FieldValue1 and FieldValue2 Input data that you want to send to the web service in the corresponding field. List Data List data consists of hierarchical groupings of fields grouped under a parent field. Note: In order to use list data as input, the service must be exposed as a REST web service without any GET resources. If the service has a GET resource you will get an error in Enterprise Designer when exposing the service because hierarchical fields are not supported for GET. Use the following format to send list data to a web service using POST. { "InputStageName": { "InputDataType": [ { "ListField1":[ {"SubfieldName1": "SubfieldValue1"}, {"SubfieldName2": "SubfieldValue2"} ] } ] } } Where: InputStageName The name of the input stage as shown on the canvas in Enterprise Designer. The default name of the stage is Input. InputDataType The name given to the record-level entity. This value is specified in the dataflow's Input stage, in the Data type name field on the Input Fields tab. The default name of the record-level entity is Row. ListField1 The name of the hierarchical field defined in the service's Input stage. SubfieldName1 and SubfieldName2 The names of child fields that comprise the list field. SubfieldValue1 and SubfieldValue2 Input data that you want to send to the web service. Spectrum Technology Platform 2018.2.0 Web Services Guide 7 Getting Started User Fields You can pass extra fields through the web service even if the web service does not use them. These fields are returned, unmodified, in the user_fields section of the response. The user fields you supply in the request do not need to be defined in the service dataflow's Input stage. { "InputStageName": { "InputDataType": [ { "user_fields": [ { "name": "FieldName1", "value": "FieldValue1" }, { "name": "FieldName2", "value": "FieldValue2" }] } ] } } Where: InputStageName The name of the input stage as shown on the canvas in Enterprise Designer. The default name of the stage is Input. InputDataType The name given to the record-level entity. This value is specified in the dataflow's Input stage, in the Data type name field on the Input Fields tab. The default name of the record-level entity is Row. FieldName1 and FieldName2 The name of the pass-through field. FieldValue1 and FieldValue2 The data you want to include in the passthrough field. Options You can specify options in the request, overriding the default options specified in the service dataflow. For user-defined web services, you can only specify options in the request if the dataflow has been configured to accept options. To configure a service to accept options in the request, open the service in Enterprise Designer and select Edit > Dataflow Options. Spectrum Technology Platform 2018.2.0 Web Services Guide 8 Getting Started To specify processing options in a request, use this format: "options" : { "OptionName1" : "Value1" }, Where: OptionName1 The name of the option. For a list of valid options for the service see the service's WADL or open the service in Enterprise Designer and select Edit > Dataflow Options. OptionValue1 A legal value for the option. For a list of legal values, open the service in Enterprise Designer and select Edit > Dataflow Options. Example JSON Request using POST The following example demonstrates how to include options, flat fields, a list field, and user-defined fields in a JSON request to a web service using POST. { "options" : { "OutputCasing" : "U" }, "Input": { "Address": [ { "AddressLine1": "1825 Kramer Ln", "City": "Austin", "StateProvince": "TX", "Accounts": [ { "AccountNumber": "120993", "ExpirationDate": "10-3-2017" }, { "AccountNumber": "898732", "ExpirationDate": "8-13-2016" } ], "user_fields": [ { "name": "Note1", "value": "Prefers decaffeinated coffee" }, { "name": "Note2", "value": "Requests east facing window" Spectrum Technology Platform 2018.2.0 Web Services Guide 9 Getting Started }] } ] } } In this example, • OutputCasing is an option exposed by the web service that controls whether the output is returned in upper case or lower case. In this request, it is set to U for upper case. • Input is the label of the Input stage in the dataflow as displayed on the canvas in Enterprise Designer. • Address is the name of the record-level entity as specified in the dataflow's Input stage, in the Data type name field on the Input Fields tab. • AddressLine1, City, and StateProvince are flat fields. • Accounts is a hierarchical ("list") field containing subfields
Load more

Recommended publications
  • Technical Reference Manual for the Standardization of Geographical Names United Nations Group of Experts on Geographical Names
    ST/ESA/STAT/SER.M/87 Department of Economic and Social Affairs Statistics Division Technical reference manual for the standardization of geographical names United Nations Group of Experts on Geographical Names United Nations New York, 2007 The Department of Economic and Social Affairs of the United Nations Secretariat is a vital interface between global policies in the economic, social and environmental spheres and national action. The Department works in three main interlinked areas: (i) it compiles, generates and analyses a wide range of economic, social and environmental data and information on which Member States of the United Nations draw to review common problems and to take stock of policy options; (ii) it facilitates the negotiations of Member States in many intergovernmental bodies on joint courses of action to address ongoing or emerging global challenges; and (iii) it advises interested Governments on the ways and means of translating policy frameworks developed in United Nations conferences and summits into programmes at the country level and, through technical assistance, helps build national capacities. NOTE The designations employed and the presentation of material in the present publication do not imply the expression of any opinion whatsoever on the part of the Secretariat of the United Nations concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontiers or boundaries. The term “country” as used in the text of this publication also refers, as appropriate, to territories or areas. Symbols of United Nations documents are composed of capital letters combined with figures. ST/ESA/STAT/SER.M/87 UNITED NATIONS PUBLICATION Sales No.
    [Show full text]
  • RDAP Transformation of Contact Information Draft-Lozano-Regext-Rdap-Transf-Contact-Inf-00
    Internet Engineering Task Force G. Lozano Internet-Draft ICANN Intended status: Standards Track Jun 24, 2016 Expires: December 26, 2016 RDAP Transformation of Contact Information draft-lozano-regext-rdap-transf-contact-inf-00 Abstract This document adds support for RDAP Transformation (i.e. translation and transliteration) of Contact Information. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 26, 2016. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
    [Show full text]
  • Sc22/Wg20 N860
    Final Draft for CEN CWA: European Culturally Specific ICT Requirements 1 2000-10-31 SC22/WG20 N860 Draft CWA/ESR:2000 Cover page to be supplied. Final Draft for CEN CWA: European Culturally Specific ICT Requirements 2 2000-10-31 Table of Contents DRAFT CWA/ESR:2000 1 TABLE OF CONTENTS 2 FOREWORD 3 INTRODUCTION 4 1 SCOPE 5 2 REFERENCES 6 3 DEFINITIONS AND ABBREVIATIONS 6 4 GENERAL 7 5 ELEMENTS FOR THE CHECKLIST 8 5.1 Sub-areas 8 5.2 Characters 8 5.3 Use of special characters 10 5.4 Numbers, monetary amounts, letter written figures 11 5.5 Date and time 12 5.6 Telephone numbers and addresses, bank account numbers and personal identification 13 5.7 Units of measures 14 5.8 Mathematical symbols 14 5.9 Icons and symbols, meaning of colours 15 5.10 Man-machine interface and Culture related political and legal requirements 15 ANNEX A (NORMATIVE) 16 Final Draft for CEN CWA: European Culturally Specific ICT Requirements 3 2000-10-31 FOREWORD The production of this document which describes European culturally specific requirements on information and communications technologies was agreed by the CEN/ISSS Workshop European Culturally Specific ICT Requirements (WS-ESR) in the Workshop’s Kick-Off meeting on 1998-11-23. The document has been developed through the collaboration of a number of contributing partners in WS-ESR. WS- ESR representation gathers a wide mix of interests, coming from academia, public administrations, IT-suppliers, and other interested experts. The present CWA (CEN Workshop Agreement) has received the support of representatives of each of these sectors.
    [Show full text]
  • 2. Common HOPE Metadata Structure
    HOPE Heritage of the People’s Europe Grant agreement No. 250549 Deliverable D2.2 The Common HOPE Metadata Structure, including the Harmonisation Specifications Deliverable number D2.2 Version 1.1 Authors Bert Lemmens – Amsab-ISG Joris Janssens – Amsab-ISG Ruth Van Dyck – Amsab-ISG Alessia Bardi – CNR-ISTI Paolo Manghi – CNR-ISTI Eric Beving – UPIP Kathryn Máthé – KEE-OSA Katalin Dobó – KEE-OSA Armin Straube – FES-A Delivery Date 31/05/2011 Dissemination Level Public HOPE is co-funded by the European Union through the ICT Policy Support Programme D2.2 Common HOPE Metadata Structure & Harmonisation Requirements V1.1 – 31/05/2011 Page 2 of 266 HOPE is co-funded by the European Union through the ICT Policy Support Programme D2.2 Common HOPE Metadata Structure & Harmonisation Requirements V1.1 – 31/05/2011 Page 3 of 266 Table of Contents Table of Contents 3 1. Introduction 8 1.1 Task Description 8 1.2 Approach 10 1.2.1 Task breakdown 10 1.2.2. Dublin Core Application Profile Guidelines 14 1.2.3. Used Terminology 15 1.2.4. Structure of the Document 17 1.3 Glossary 18 1.3.1 Hope glossary 18 1.3.2 Technical Glossary 18 2. Common HOPE Metadata Structure 24 2.1 Functional requirements 24 2.1.1 General 24 2.1.1.1 What does HOPE want to accomplish with the HOPE Aggregator? 24 2.1.1.2 What the HOPE Aggregator will not attempt to do? 26 2.1.2. Aggregation 26 2.1.2.1 What are the key characteristics of the HOPE metadata? 27 2.1.2.2 How do the characteristics of the HOPE metadata affect the design of the Common HOPE Metadata Structure? 28 2.1.3.
    [Show full text]
  • Standards and Standardisation a Practical Guide for Researchers
    Standards and Standardisation A practical guide for researchers Research and Innovation Europe Direct is a service to help you find answers to your questions about the European Union. Freephone number (*): 00 800 6 7 8 9 10 11 (*) Certain mobile telephone operators do not allow access to 00 800 numbers or these calls may be billed. More information on the European Union is available on the Internet (http://europa.eu). Cataloguing data can be found at the end of this publication. Luxembourg: Publications Office of the European Union, 2013 ISBN 978-92-79-25971-5 doi: 10.2777/10323 © European Union, 2013 Reproduction is authorised provided the source is acknowledged. Cover image: © Andrea Danti, #12386685, 2012. Source: Fotolia.com Printed in Luxembourg EUROPEAN COMMISSION DIRECTORATE-GENERAL FOR RESEARCH & INNOVATION Directorate G - Industrial technologies Standards A practical and Standardisation guide for researchers Author Dr. Peter Hatto LEGAL NOTICE Neither the European Commission nor any person acting on behalf of the Commission is responsible for the use which might be made of the following information. The views expressed in this publication are the sole responsibility of the author and do not necessarily reflect the views of the European Commission. More information on the European Union is available on the Internet (http://europa.eu). EUROPEAN COMMISSION Directorate-General for Research & Innovation Directorate G – Industrial Technologies Unit G1 – Horizontal Aspects E-mail: [email protected] Contact: Romain Bouttier
    [Show full text]
  • Centc304 N932
    CEN/TC304 N932 Source: Secretariat Date: 15 Dec 1999 Title: European Fallback Rules, ballot Mailed: 15 Dec 1999 Status: TC-enquiry: DEADLINE 1st March 2000 Action required: Respond before 1 March 2000 * Notes: This is a TC-enquiry, to establish the suitability of N932 to be sent for Formal vote as prENV. National member body officers, responsible for CEN/TC304 issues are asked to fill in this form and send it to the TC-secretariat before 1 March 2000. Comments in any form will be forwarded to the CEN/TC 304 Project Team of European Fallback Rules. The PT will before the next plenary of TC304 in April 2000 produce a disposition of comments and a revised draft. The PT will produce a disposition of comments and plans to ask the TC304 plenary in November to approve a revised draft to be sent for Formal Vote. Comments from affiliated members of CEN and liaisons are welcome and will be considered. Country:______________________________ Approves without comments ___ Approves with comments ___ Disapproves with comments ___ Date:_______________ Signature_____________________________________(National Member Body officer) Name:__________________________________ EUROPEAN PRESTANDARD DRAFT PRÉNORME EUROPÉENNE prENV_____ EUROPÄISCHE VORNORM ICS: 35.040 Descriptors: Data processing, information interchange, text processing, text communication, graphic characters, character sets, representation of characters, coded character sets, conversion, fallback English version Information Technology European fallback rules Technologies de l'information- Informations technologies Character repertoire and coding transformations: Character repertoire and coding transformations: European fallback rules - Nº 1 European fallback rules - Nº 1 This draft ENV is submitted to CEN members for Formal Vote. It has been drawn up by the Technical Committee CEN/TC 304.
    [Show full text]
  • Definition of Object-Oriented FRBR
    FRBR object-oriented definition and mapping from FRBRER, FRAD and FRSAD Document Type: Current Editorial Status: In Progress since [5/4/2017] Version 3.0 September 2017 International Working Group on FRBR and CIDOC CRM Harmonisation Supported by Delos NoE Editors: Chryssoula Bekiari Martin Doerr Patrick Le Bœuf Pat Riva Contributors: Trond Aalberg, Jérôme Barthélémy, Chryssoula Bekiari, Guillaume Boutard, Martin Doerr, Günther Görz, Dolores Iorizzo, Max Jacob, Carlos Lamsfus, Patrick Le Bœuf, Mika Nyman, João Oliveira, Christian Emil Ore, Allen H. Renear, Pat Riva, Richard Smiraglia, Stephen Stead, Maja Žumer, and others November 2015 Index INDEX ............................................................................................................................................... 2 FOREWORD ................................................................................................................................. 109 1. INTRODUCTION ..................................................................................................................... 1110 1.1. Purposes .................................................................................................................................................... 1110 1.1.1. A Common View of Cultural Heritage Information .......................................................................... 1211 1.1.2. A Verification of FRBR’s Internal Consistency ................................................................................ 1211 1.1.3. An Enablement of Information
    [Show full text]
  • Inventory of Romanization Tools
    Inventory of Romanization Tools Standards Intellectual Management Office Library and Archives Canad Ottawa 2006 Inventory of Romanization Tools page 1 Language Script Romanization system for an English Romanization system for a French Alternate Romanization system catalogue catalogue Amharic Ethiopic ALA-LC 1997 BGN/PCGN 1967 UNGEGN 1967 (I/17). http://www.eki.ee/wgrs/rom1_am.pdf Arabic Arabic ALA-LC 1997 ISO 233:1984.Transliteration of Arabic BGN/PCGN 1956 characters into Latin characters NLC COPIES: BS 4280:1968. Transliteration of Arabic characters NL Stacks - TA368 I58 fol. no. 00233 1984 E DMG 1936 NL Stacks - TA368 I58 fol. no. DIN-31635, 1982 00233 1984 E - Copy 2 I.G.N. System 1973 (also called Variant B of the Amended Beirut System) ISO 233-2:1993. Transliteration of Arabic characters into Latin characters -- Part 2: Lebanon national system 1963 Arabic language -- Simplified transliteration Morocco national system 1932 Royal Jordanian Geographic Centre (RJGC) System Survey of Egypt System (SES) UNGEGN 1972 (II/8). http://www.eki.ee/wgrs/rom1_ar.pdf Update, April 2004: http://www.eki.ee/wgrs/ung22str.pdf Armenian Armenian ALA-LC 1997 ISO 9985:1996. Transliteration of BGN/PCGN 1981 Armenian characters into Latin characters Hübschmann-Meillet. Assamese Bengali ALA-LC 1997 ISO 15919:2001. Transliteration of Hunterian System Devanagari and related Indic scripts into Latin characters UNGEGN 1977 (III/12). http://www.eki.ee/wgrs/rom1_as.pdf 14/08/2006 Inventory of Romanization Tools page 2 Language Script Romanization system for an English Romanization system for a French Alternate Romanization system catalogue catalogue Azerbaijani Arabic, Cyrillic ALA-LC 1997 ISO 233:1984.Transliteration of Arabic characters into Latin characters.
    [Show full text]
  • State of the Standards, January 31, 2012
    O O S C E ing f R D O SERU (SHAREd E-Res OURCE UndERS arTTanding)Icle St St O EXCERPted FRom: ISO/TR 14873 ISO/TR ES CORE (C CORE RI A 25964-1 R O B I IS ISO/ TR 11219 ISO/ n L I RFID Z39.7 DATa DicTIONARy STAN DicTIONARy DATa Z39.7 ISO 5127 ISO 8 INFORMATION STANDARDS QuARTERLY WINTER 2012 | VOL 24 | ISSUE 1 | ISSN 1041-0031 SPECIAL EDITION: YEAR IN REVIEW AND STATE OF THE STANDARDS ISO/TR 17068 ISO 13008 ISO 17316 ISO 3166 ISO 17316 11219 2789 O TR / IS O KBART PHASe 2 IS Open DisCOVERy INITIATIVE TE TE I ISO 13008 ISO Su NISO and TC46 G A ISO 2709 ISO T 2011 Year In REVIEW t GrOUP E S G cle I RT From ISO 2788 to ISO 25964: A al Intere The EVOLUTIon oF I on exCHAN I THESAURUS STANDARDS 17316 27729 O O IS IS S: Journal AT J DEVELopment oF RESOURCE NFORMAT -book SpeC I E SYNCHRONIZATIon STANDARD ISO 9:1995 STATE OF THE ORMAt ORMAt For F STANDARDS 16175-2 2709:2008, 2709:2008, O O IS IS SS 31 [SPECIAL EDITION] STATE OF THE 31,2012 ANUARY STANDARDS J This comprehensive report on NISO’s standards and initiatives appears in the first issue of the year of ISQ to keep readers informed of the scope and status of NISO’s program on an annual basis. If you have questions about any of the standards or development programs, contact the NISO office by phone (301-654-2512), via e-mail ([email protected]), or visit the Standards section of the NISO website (www.niso.org/standards).
    [Show full text]
  • Bsdploy Documentation Release 2.4.0.Dev0
    bsdploy Documentation Release 2.4.0.dev0 Tom Lazar Dec 22, 2017 Contents 1 Main Features 3 2 How it works 5 3 Example Session 7 4 Best of both worlds 9 5 Under the hood 11 6 Full documentation 13 7 Dive in 15 7.1 Client requirements........................................... 15 7.2 Server requirements........................................... 15 7.3 Client Installation............................................ 16 7.4 Quickstart................................................ 17 8 Tutorial 23 8.1 Tutorial.................................................. 23 8.2 Webserver................................................ 24 8.3 Transmission............................................... 27 8.4 Staging.................................................. 29 9 Setup 31 9.1 Overview................................................. 31 9.2 Bootstrapping.............................................. 38 9.3 Configuring a jailhost.......................................... 42 10 General usage 45 10.1 Managing jails.............................................. 45 10.2 Ansible integration............................................ 46 10.3 Fabric integration............................................. 48 10.4 Combining Ansible and Fabric...................................... 49 11 Special use cases 51 11.1 Staging.................................................. 51 11.2 Updating................................................. 53 i 11.3 Customizing bootstrap.......................................... 53 12 Contribute 55 13 License 57 14 TODO 59 ii bsdploy
    [Show full text]
  • ISO Types 1-6: Construction Code Descriptions
    ISO Types 1-6: Construction Code Descriptions ISO 1 – Frame (combustible walls and/or roof) Typically RMS Class 1 Wood frame walls, floors, and roof deck Brick Veneer, wood/hardiplank siding, stucco cladding Wood frame roof with wood decking and typical roof covers below: *Shingles *Clay/concrete tiles *BUR (built up roof with gravel or modified bitumen) *Single-ply membrane *Less Likely metal sheathing covering *May be gable, hip, flat or combination of geometries Roof anchorage *Toe nailed *Clips *Single Wraps *Double Wraps Examples: Primarily Habitational, max 3-4 stories ISO 2 – Joisted Masonry (JM) (noncombustible masonry walls with wood frame roof) Typically RMS Class 2 Concrete block, masonry, or reinforced masonry load bearing exterior walls *if reported as CB walls only, verify if wood frame (ISO 2) or steel/noncombustible frame roof (ISO 4) *verify if wood frame walls (Frame ISO 1) or wood framing in roof only (JM ISO 2) Stucco, brick veneer, painted CB, or EIFS exterior cladding Floors in multi-story buildings are wood framed/wood deck or can be concrete on wood or steel deck. Wood frame roof with wood decking and typical roof covers below: *Shingles *Clay/concrete tiles *BUR (built up roof with gravel or modified bitumen) *Single-ply membrane *Less Likely metal sheathing covering *May be gable, hip, flat or combination of geometries Roof anchorage *Toe nailed *Clips *Single Wraps *Double Wraps Examples: Primarily Habitational, small office/retail, max 3-4 stories If “tunnel form” construction meaning there is a concrete deck above the top floor ceiling with wood frame roof over the top concrete deck, this will react to wind forces much the same way as typical JM construction.
    [Show full text]
  • Graph Databases
    Graph databases Iztok Savnik, Famnit, UP Joint project with: Kiyoshi Nitta, Yahoo Japan Research Maj, 2016. 1 Outline 1) Graph data model (RDF) 2) Popular graph databases on Web 3) Big3store Graph data model (RDF + RDFS) Graph data model ● Graph database – Database that uses graphs for the representation of data and queries ● Vertexes – Represent things, persons, concepts, classes, ... ● Arcs – Represent properties, relationships, associations, ... – Arcs have labels ! RDF ● Resource Description Framework – Tim Berners Lee, 1998-2009 – This is movement ! ● What is behind ? – Graphs – Triples (3) – Semantic data models – Human associative memory (psychology) – Associative neural networks – Hopfield Network RDF RDF syntax ● N3, TVS ● Turtle ● TriG ● N-Triples ● RDF/XML ● RDF/JSON 7 Name spaces ● Using short names for URL-s – Long names are tedious ● Simple but strong concept ● Defining name space: prefix rdf:, namespace URI: http://www.w3.org/1999/02/22-rdf-syntax-ns# prefix rdfs:, namespace URI: http://www.w3.org/2000/01/rdf-schema# prefix dc:, namespace URI: http://purl.org/dc/elements/1.1/ prefix owl:, namespace URI: http://www.w3.org/2002/07/owl# prefix ex:, namespace URI: http://www.example.org/ (or http://www.example.com/) prefix xsd:, namespace URI: http://www.w3.org/2001/XMLSchema# 8 N-Triples <http://example.org/bob#me> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Person> . <http://example.org/bob#me> <http://xmlns.com/foaf/0.1/knows> <http://example.org/alice#me> . <http://example.org/bob#me> <http://schema.org/birthDate> "1990-07-04"^^<http://www.w3.org/2001/XMLSchema#date> .
    [Show full text]