DOCSLIB.ORG

Spectrum Technology Platform Version 12.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Spectrum Technology Platform Version 12.0 Web Services Guide Table of Contents 1 - Getting Started REST 4 SOAP 27 2 - Web Services REST 51 SOAP 396 Chapter : Appendix Appendix A: Buffering 798 Appendix B: Country Codes 801 Appendix C: Validate Address Confidence Algorithm 833 1 - Getting Started In this section REST 4 SOAP 27 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 12.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 12.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. Use the following format for JSON POST requests. Flat Data Use this format 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. FieldName1 and FieldName2 Spectrum Technology Platform 12.0 Web Services Guide 6 Getting Started 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 12.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 12.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 12.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 name AccountNumber and ExpirationDate. There are two accounts included in this example. • user_fields contains
Recommended publications
  • Technical Reference Manual for the Standardization of Geographical Names United Nations Group of Experts on Geographical Names

    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.
  • Names of Countries, Their Capitals and Inhabitants

    Names of Countries, Their Capitals and Inhabitants

    United Nations Group of Experts on Geographical Names (UNGEGN) East Central and South-East Europe Division (ECSEED) ___________________________________________________________________________ The Nineteenth Session of the East Central and South-East Europe Division of the UNGEGN Zagreb, Croatia, 19 – 21 November 2008 Item 9 and 10 of the agenda Document Symbol: ECSEED/Session.19/2008/10 Names of countries, their capitals and inhabitants Submitted by Poland* ___________________________________________________________________________ * Prepared by Maciej Zych, Commission on Standardization of Geographical Names Outside the Republic of Poland, Poland. 19th Session of the East, Central and South-East Europe Division of the United Nations Group of Experts on Geographical Names Zagreb, 19 – 21 November 2008 Names of countries, their capitals and inhabitants Maciej Zych Commission on Standardization of Geographical Names Outside the Republic of Poland 1 Names of countries, their capitals and inhabitants In 1997 the Commission on Standardization of Geographical Names Outside the Republic of Poland published the first list of Names of countries, their capitals and inhabitants, comprising both independent countries as well as non-self-governing and autonomous territories. The second edition appeared in 2003. Numerous changes occurred in geographical names in the six years since the previous list was published. New countries and new non-self-governing and autonomous territories appeared, some countries changed their names, other their capital or its name, the Polish names for several countries and their capitals also changed as did the recommended principles for the Romanization of several languages using non-Roman systems of writing. The third edition of Names of countries, their capitals and inhabitants appeared in the end of 2007, the data it contained being updated for mid-July 2007.
  • Taxation Paradigms: JOHN WEBB SUBMISSION APRIL 2009

    Taxation Paradigms: JOHN WEBB SUBMISSION APRIL 2009

    Taxation Paradigms: What is the East Anglian Perception? JOHN WEBB A thesis submitted in partial fulfilment of the requirements of Bournemouth University for the degree of Doctor of Philosophy SUBMISSION APRIL 2009 BOURNEMOUTH UNIVERSITY What we calf t[ie beginningis oftenthe end And to makean endis to makea beginning ?fie endis wherewe start ++++++++++++++++++ Weshall not ceasefrom exploration And the of exploring end .. Wilt to arrivewhere we started +++++++++++++++++ 7.S f: Cwt(1974,208: 209) ? fie Four Quartets,Coffected Poems, 1909-1962 London: Faderand Fader 2 Acknowledgements The path of a part time PhD is long and at times painful and is only achievablewith the continued support of family, friends and colleagues. There is only one place to start and that is my immediate family; my wife, Libby, and daughter Amy, have shown incredible patienceover the last few years and deserve my earnest thanks and admiration for their fantastic support. It is far too easy to defer researchwhilst there is pressingand important targets to be met at work. My Dean of Faculty and Head of Department have shown consistent support and, in particular over the last year my workload has been managedto allow completion. Particularthanks are reservedfor the most patientand supportiveperson - my supervisor ProfessorPhilip Hardwick.I am sure I am one of many researcherswho would not have completed without Philip - thank you. ABSTRACT Ever since the Peasant'sRevolt in 1379, collection of our taxes has been unpopular. In particular when the taxes are viewed as unfair the population have reacted in significant and even violent ways. For example the Hearth Tax of 1662, Window Tax of 1747 and the Poll tax of the 1990's have experiencedpublic rejection of these levies.
  • RDAP Transformation of Contact Information Draft-Lozano-Regext-Rdap-Transf-Contact-Inf-00

    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.
  • A Chinese Mobile Phone Input Method Based on the Dynamic and Self-Study Language Model

    A Chinese Mobile Phone Input Method Based on the Dynamic and Self-Study Language Model

    A Chinese Mobile Phone Input Method Based on the Dynamic and Self-study Language Model Qiaoming Zhu, Peifeng Li, Gu Ping, and Qian Peide School of Computer Science & Technology of Soochow University, Suzhou, 215006 {qmzhu, pfli, pgu, pdqian}@suda.edu.cn Abstract. This paper birefly introduces a Chinese digital input method named as CKCDIM (CKC Digital Input Method) and then applies it to the Symbian OS as an example, and it also proposes a framework of input method which adopted the Client/Server architecture for the handheld computers. To improve the performance of CKCDIM, this paper puts forward a dynamic and self-study language model which based on a general language model and user language model, and proposes two indexes which are the average number of pressed-keys (ANPK) and the hit rate of first characters (HRFC) to measure the performance of the input method. Meanwhile, this paper brings forward a modified Church-Gale smoothing method to reduce the size of general language model to meet the need of mobile phone. At last, the experiments prove that the dynamic and self-study language model is a steady model and can improve the performance of CKCDIM. Keywords: Chinese Digital Input Method, Architecture of Input Method, Dynamic and Self-study Language Model, HRFC, ANPK. 1 Introduction With the developing of communication technology and the popularization of the mobile phone in China, the use of text message in mobile phone is growing rapidly. According to CCTV financial news report, the total number of Short Message Service use will grow from 300 billions in 2005 to 450 billions in 2006 in China.
  • Sc22/Wg20 N860

    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.
  • Panacea.Html>

    Panacea.Html>

    Panace@ Boletín de Medicina y Traducción Verbibunda panaceica L. Vol. VI, n.o 19. Marzo, 2005 <www.medtrad.org/panacea.html> Panace@ (<www.medtrad.org/panacea.html>) es la revista de MedTrad, foro internético independiente y plurinacional constituido por profesionales de la comunicación escrita en el ámbito de la lengua, la medicina y las ciencias biológicas. Panace@ publica textos originales sobre los diversos aspectos de la traducción y el lenguaje de la medicina y ciencias afines, sobre todo en español, pero la revista está abierta a colaboraciones en cualquier idioma. Panace@ es una publicación trimestral con cuatro números anuales: dos números sencillos, que aparecen en marzo y junio, y un número doble, que aparece en noviembre. Los originales para publicación deben enviarse en soporte electrónico a [email protected]. La propiedad intelectual de los originales corresponde a los autores, y los derechos de edición y publicación, a Panace@. Los artículos aparecidos en la revista podrán ser utilizados libremente con propósitos educativos y científicos, siempre y cuando se cite correctamente su autoría y procedencia. Panace@ espera de los autores y colaboradores el máximo respeto a las consideraciones de ética editorial incluidas en las normas de Vancouver, que pueden consultarse en el Escaparate de MedTrad (<www.medtrad.org/biblioteca/style_guides/Spanish_VANCOUVER.htm>). Las opiniones expresadas en esta publicación son responsabilidad exclusiva de los autores de los artículos. ISSN 1537 - 1964 Publicación incorporada a Redacción Director:
  • 2. Common HOPE Metadata Structure

    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.
  • Standards and Standardisation a Practical Guide for Researchers

    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
  • A Könyvtárüggyel Kapcsolatos Nemzetközi Szabványok

    A Könyvtárüggyel Kapcsolatos Nemzetközi Szabványok

    A könyvtárüggyel kapcsolatos nemzetközi szabványok 1. Állomány-nyilvántartás ISO 20775:2009 Information and documentation. Schema for holdings information 2. Bibliográfiai feldolgozás és adatcsere, transzliteráció ISO 10754:1996 Information and documentation. Extension of the Cyrillic alphabet coded character set for non-Slavic languages for bibliographic information interchange ISO 11940:1998 Information and documentation. Transliteration of Thai ISO 11940-2:2007 Information and documentation. Transliteration of Thai characters into Latin characters. Part 2: Simplified transcription of Thai language ISO 15919:2001 Information and documentation. Transliteration of Devanagari and related Indic scripts into Latin characters ISO 15924:2004 Information and documentation. Codes for the representation of names of scripts ISO 21127:2014 Information and documentation. A reference ontology for the interchange of cultural heritage information ISO 233:1984 Documentation. Transliteration of Arabic characters into Latin characters ISO 233-2:1993 Information and documentation. Transliteration of Arabic characters into Latin characters. Part 2: Arabic language. Simplified transliteration ISO 233-3:1999 Information and documentation. Transliteration of Arabic characters into Latin characters. Part 3: Persian language. Simplified transliteration ISO 25577:2013 Information and documentation. MarcXchange ISO 259:1984 Documentation. Transliteration of Hebrew characters into Latin characters ISO 259-2:1994 Information and documentation. Transliteration of Hebrew characters into Latin characters. Part 2. Simplified transliteration ISO 3602:1989 Documentation. Romanization of Japanese (kana script) ISO 5963:1985 Documentation. Methods for examining documents, determining their subjects, and selecting indexing terms ISO 639-2:1998 Codes for the representation of names of languages. Part 2. Alpha-3 code ISO 6630:1986 Documentation. Bibliographic control characters ISO 7098:1991 Information and documentation.
  • Database Globalization Support Guide

    Database Globalization Support Guide

    Oracle® Database Database Globalization Support Guide 19c E96349-05 May 2021 Oracle Database Database Globalization Support Guide, 19c E96349-05 Copyright © 2007, 2021, Oracle and/or its affiliates. Primary Author: Rajesh Bhatiya Contributors: Dan Chiba, Winson Chu, Claire Ho, Gary Hua, Simon Law, Geoff Lee, Peter Linsley, Qianrong Ma, Keni Matsuda, Meghna Mehta, Valarie Moore, Cathy Shea, Shige Takeda, Linus Tanaka, Makoto Tozawa, Barry Trute, Ying Wu, Peter Wallack, Chao Wang, Huaqing Wang, Sergiusz Wolicki, Simon Wong, Michael Yau, Jianping Yang, Qin Yu, Tim Yu, Weiran Zhang, Yan Zhu This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S.
  • Discover Your Phone

    Discover Your Phone

    Discover Your Phone accept, except as required by applicable law, liability for any error, omission or discrepancy between this user 262000 color guide and the product described. The device is meant to main screen be connected to GSM/GPRS networks. Back of the phone: Charger/USB camera lens connector Hard keys Stylus pen Also called Red key or On/Off key. Touch screen Hang up key • In menu or edit mode, short press to return to idle screen. Camera key • During an incoming call or call in progress, press to end the call Hang up, or reject the call. Cancel and On/Off key • When the phone is switched Answer key off, long press to switch on the Up key, phone. keypad lock • When the phone is switched Down key, Vibration on, long press to switch off the on/off key phone anytime. Also called Green key or Send key: Philips continuously strives to improve its products. Answer key • Answer a call or dial a phone Therefore, Philips reserves the rights to revise this user number guide or withdraw it at any time without prior notice. • In idle mode, press to view the Philips provides this user guide “as is” and does not dialed calls list. Up key • Browse the menu/list on the Side camera • In idle mode, short press to and same menu level. key enter the camera, long press to Down key • Browse SMS contents or other enter video camera. long text messages. • When in camera/video camera • Scroll to the previous or next preview mode, short press to picture when viewing pictures.