Name Writing for Swedish Authorities

Total Page:16

File Type:pdf, Size:1020Kb

Name Writing for Swedish Authorities ISO/IEC JTC 1/SC 35 N 0749 DATE: 2005-01-31 ISO/IEC JTC 1/SC 35 User Interfaces Secretariat: Association Française de Normalisation (AFNOR) TITLE: Name-writing in Swedish Authorities' data processing - Background information SOURCE: Karl Ivar Larsson, Swedish Expert STATUS: FYI DATE: 2005-01-31 DISTRIBUTION: P and O members of JTC1/SC35 MEDIUM: E NO. OF PAGES: 16 Secretariat ISO/IEC JTC 1/SC 35 – Nathalie Cappel-Souquet – 11 Avenue Francis de Pressensé 93571 St Denis La Plaine Cedex France Telephone: + 33 1 41 62 82 55; Facsimile: + 33 1 49 17 91 29 e-mail: [email protected] LWP Consulting R 04/2-1 Note: This document was handed out in the SC35 Stockholm meeting 2004-11-24. Contents 1 General background 3 2 Languages and writing systems 3 2.1 General aspects 3 2.2 Minority language issues 4 2.3 EU working languages 5 2.4 Writing systems 5 3 Character data processing 6 3.1 Fundamental requirements 6 3.2 Character representation 7 3.3 Standards for character representation 8 4 Computer keyboards 11 4.1 General characteristics 11 4.2 The "group" concept 11 4.3 Keyboard standards 12 4.4 Swedish keyboard situation 12 4.5 "Soft keyboards" 13 5 Proposed guidelines for representation of names 13 5.1 General principles 13 5.2 Character set: letters 13 5.3 Character set: non-alphabetic characters 14 5.4 Required character set 14 5.5 Character transliteration 14 References 16 2 © Copyright 2004 LWP Consulting 2004-09-30 LWP Consulting R 04/2-1 Name-writing in Swedish Authorities' data processing – Background information (Note: Since the contents of this document may be of interest in some Authorities' international contacts, it has been written in English.) 1 General background Electronic interchange of information between Public Authorities in Sweden is increas- ing in importance extremely rapidly, as is interchange between Authorities and citizens as well as companies. The Swedish Government has decided to promote the "24-hour Public Administration" concept, to provide continuous access to public information. Information interchange is however often made difficult by a lack of compatibility be- tween different Authorities' data processing and/or communication systems. A multi- tude of such systems exist in the marketplace, some conforming to formal standards, and others based on "proprietary" – i.e. company-specific – principles. The Govern- ment has therefore found it essential: "To decide on a minimum of binding rules and standards necessary for a well function- ing electronic communication within the public administration and with its customers and to provide a supporting set of basic functions as a common infrastructure for the communication and co-operation between the different public agencies." (Extract from speech by Gunnar Lund, Swedish Minister for International Economic Affairs and Financial Markets). The Ministry of Finance has appointed "Nämnden för elektronisk förvaltning" (The Swedish Board for electronic administration, e-nämnden) to initiate necessary work on guidelines, later to be turned into formal regulations. The Board started its work in January 2004, and has commissioned a number of specific tasks. One such task is to develop a set of guidelines to satisfy the needs in data processing for correctly representing names of individuals, companies and geographical places. With today's international situation – including the Swedish EU membership – this re- quires the handling of a set of letters vastly larger than was earlier needed. The Board has commissioned Statskontoret (The Swedish "Agency for Administrative Development" – to investigate the matter and propose guidelines to be referred for comments to Authorities and others concerned. Statskontoret, in turn, has commis- sioned part of this investigation to the company LWP Consulting. This document describes various factors of relevance in the matter, including: • An overview of languages and their writing systems • Factors relating to representation of letters and other characters in data processing • Proposed guidelines for the representation of names in Authorities' data processing 2 Languages and writing systems 2.1 General aspects A very large number of languages exist in the world, although the number is rapidly decreasing as languages spoken by small minorities become extinct. Considerably more than 3.000 languages could however probably still be identified, although some of them can be considered dialectal varieties of a common language. Many of these languages/dialects however lack an established writing system, and are therefore not candidates for commonplace data processing. The number of languages in the world 3 © Copyright 2004 LWP Consulting 2004-09-30 LWP Consulting R 04/2-1 used by a larger number of speakers and also possessing a writing system could be put at around 200. The number of characters needed to correctly write even this smaller number of lan- guages is extremely large. This is mainly because the writing systems of the three im- portant languages Chinese, Japanese and Korean use an "ideographic" system of writ- ing, with tens of thousands of characters. (The common term "ideographic" is used here loosely and not strictly correctly; also it should be noted that the indigenous Korean system Hangul is really syllabic, although used in a way necessitating data processing similar to the truly "ideographic" systems.) In comparison, the number of characters actually used in international exchanges of computerised information is small. Most such exchanges use the Latin, the Cyrillic or the Arabic script. Information originating from languages with other writing systems is then "transliterated" into one of these scripts (the term "transcription" is also used in the connection, but here only "transliteration" is used, without a strict definition). 2.2 Minority language issues 2.2.1 General factors One factor to be considered for the data processing of names is majority- vs. minority- language use. In most countries, public administrations permit writing of names only in the writing system of the "official" language, although this is often not clearly stated in national legislation. In Sweden, for instance, the law governing the taking of a new personal name (SFS 1982:1134) simply states that a surname cannot be accepted if its "composition, pronunciation or spelling" is "not suitable". This text is, naturally, not a very precise basis for interpretations in a specific case. The matter becomes even more complicated by the fact that some countries do not explicitly declare a "state" language. A survey of the matter in the case of Europe (see References) however concludes that: "Most European constitutions declare one or more languages as the state, national or official language. Generally these three terms are used with one and the same meaning, i.e. that the languages declared are those used by the authorities, particularly in legal connections." Out of the 47 states recognised by the Council of Europe (CoE) as European – i.e. being either CoE members or eligible for membership – 28 explicitly declare one or more state/national/official language(s) in their constitutions, and another two do it indirectly. However the remaining countries, amongst them all of the Scandinavian states, do not declare a state language. The matter of language minorities, and therefore also of their requirements on name- writing, is now becoming internationally recognised because of the CoE "European Charter for Regional or Minority languages" (CETS No. 148). This charter has at pres- ent (September 2004) been ratified by 17 CoE member states, including Sweden, and further signed – although not yet ratified – by another 13. 2.2.2 The Sami situation in Sweden Part of the Swedish ETS 148 ratification is an undertaking "to allow and/or encourage . the use or adoption, if necessary in conjunction with the name in the official language(s), of traditional and correct forms of place-names in regional or minority languages." and further "to allow the use or adoption of family names in the regional or minority languages, at the request of those concerned." 4 © Copyright 2004 LWP Consulting 2004-09-30 LWP Consulting R 04/2-1 These parts of the Swedish ratification apply to Sami, Finnish and Meänkieli (Tornedal Finnish), and are supported in legislations SFS 1999:1175 and 1176. While Finnish and Meänkieli are well-defined languages, "Sami" is somewhat unspecific, since several varieties exist, generally considered separate languages, with partly differing alphabets. In the absence of a clear specification, the Swedish legislation should be considered to apply to all Sami varieties. The data processing requirements of Sami have been specified in documents issued by the joint Finnish-Norwegian-Swedish Sami Parliamentary Council; see References. 2.3 EU working languages After the latest EU enlargement the number of official working languages in the union's institutions is 20. Irish Gaelic and the Luxembourg language Letzeburgesh – which is really a German dialect – were not requested as working languages; and Belgium, Austria and the EU-recognised part of Cyprus use the majority languages of other EU countries. At present two scripts are in use within EU, the Latin and the Greek. With the possible future entry of candidate country Bulgaria the Cyrillic script will also come into use. It should be noted however that the Swedish situation for personal names already makes handling of Cyrillic-script names necessary, on a very much larger scale than Greek-script ones. Also Turkish-origin names are important in Sweden. The EU working language situation therefore not really influences needed decisions on name-handling in Swedish Authorities. 2.4 Writing systems 2.4.1 Concept of characters and "glyphs" A problem emerging with the introduction of data processing was the need to differenti- ate between characters as "conceptual entities" and their corresponding rendering, i.e. their written, printed or screen-displayed representation. For such representation the term "glyph" is used.
Recommended publications
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [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]
  • DICOM PS3.5 2021C
    PS3.5​ DICOM PS3.5 2021d - Data Structures and Encoding​ Page 2​ PS3.5: DICOM PS3.5 2021d - Data Structures and Encoding​ Copyright © 2021 NEMA​ A DICOM® publication​ - Standard -​ DICOM PS3.5 2021d - Data Structures and Encoding​ Page 3​ Table of Contents​ Notice and Disclaimer ........................................................................................................................................... 13​ Foreword ............................................................................................................................................................ 15​ 1. Scope and Field of Application ............................................................................................................................. 17​ 2. Normative References ....................................................................................................................................... 19​ 3. Definitions ....................................................................................................................................................... 23​ 4. Symbols and Abbreviations ................................................................................................................................. 27​ 5. Conventions ..................................................................................................................................................... 29​ 6. Value Encoding ...............................................................................................................................................
    [Show full text]
  • Me-Api Documentation Release V0.1.0
    me-api Documentation Release v0.1.0 lord63 February 20, 2016 Contents 1 User’s Guide 1 1.1 Introduction...............................................1 1.2 Qucikstart................................................2 1.3 Integrate with your sites.........................................2 1.4 Gallery: live demos...........................................6 2 Developer’s Guide 7 2.1 Contribute to me-api...........................................7 2.2 Develop a new middleware........................................8 3 Additional Notes 11 3.1 Authors.................................................. 11 i ii CHAPTER 1 User’s Guide 1.1 Introduction Me-api is a personal API built on python and flask that allows for extensible integrations. It’s a python port of the original Node.js version me-api. It is called me-api, you can build a personal website with it. With me-api, you can fetch your photos on instagram, get your tweets from twitter, show you code activity on github, list your blog post from medium, and etc. 1.1.1 Data Representation There are two main json files: me.json and modules.json. me.json: { "name":"lord63", "join_github":"20 Aug 2013" } It’s all about you. Your name, your age, your hobbies, you can add anything about youself. You’ll see them on the root path “/” once you’ve configured me-api. modules.json: { "modules":{ "medium":{ "path":"/blog", "data":{ "me":"@username" } }, "github":{ "path":"/code", "data":{ "me":"username" } } } } 1 me-api Documentation, Release v0.1.0 Just as its name, it has many modules. Using custom middleware, you can attach the data pulled from various social media feeds to specific endpoints in your API. “path” is the endpoint which you want to host the middleware on, “data” contains some other info so that we can fetch data from the site(some may need authentication).
    [Show full text]
  • Section 18.1, Han
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]
  • BGN/PCGN Romanization Guide
    TABLE OF CONTENTS I. Introduction II. Approved Romanization Systems and Agreements Amharic Arabic Armenian Azeri Bulgarian Burmese Byelorussian Chinese Characters Georgian Greek Hebrew Japanese Kana Kazakh Cyrillic Khmer (Cambodian) Kirghiz Cyrillic Korean Lao Macedonian Maldivian Moldovan Mongolian Cyrillic Nepali Pashto Persian (Farsi and Dari) Russian Serbian Cyrillic Tajik Cyrillic Thai Turkmen Ukrainian Uzbek III. Roman-script Spelling Conventions Faroese German Icelandic North Lappish IV. Appendices A. Unicode Character Equivalents B. Optimizing Software and Operating Systems to Display BGN-approved geographic names Table . Provenance and Status of Romanization Systems Contained in this Publication Transliteration Date Class Originator System Approved BGN/PCGN Amharic System 967 967 System BGN/PCGN Arabic 96 System 96 System BGN/PCGN Armenian System 98 98 System Roman Alphabet Azeri 00 Azeri Government 99 Spelling Convention BGN/PCGN Bulgarian System 9 9 System BGN/PCGN Burmese Burmese Government Agreement 970 970 Agreement 907 System BGN/PCGN Byelorussian 979 System 979 System Xinhua Zidian Chinese Pinyin System Agreement 979 dictionary. Commercial Press, Beijing 98. Chinese Wade-Giles Agreement 979 System BGN/PCGN Faroese Roman Script Spelling 968 Spelling Convention Convention BGN/PCGN 98 System 98 Georgian System BGN/PCGN German Roman Script Spelling 986 Spelling Convention Convention Greek ELOT Greek Organization for Agreement 996 7 System Standardization BGN/PCGN Hebrew Hebrew Academy Agreement 96 96 System System Japanese
    [Show full text]
  • Line Break in Google Spreadsheets
    Line Break In Google Spreadsheets Danish and multistorey Chelton transmigrated: which Georg is manubrial enough? Old-rose Antoni enrolls: he big-note his Punchinello half and avoidably. How birchen is Paten when unremarkable and unwithholding Patty hook-ups some alabaster? An early in its mobile phone images and line in the linked to master google updates or multiple documents in manage users cannot edit the monitor the custom selection Google spreadsheets as you will appear on it back on is for line break the lines of a second row, and mexico cruises. Google spreadsheet in line breaks, tips to the raw characters to recognize the instructions for the super user has the name. And line break the spreadsheets be included in this reply back after you the first element. If google spreadsheet in line break up. Take you a matter which were performed in different icons located in between shopify store after this on power? We have in. Thank you for line break in the lines in the. The elaboration of its flow forecast expects a break in your json in excel functions available the magic behind the product is nothing to automatically converted to. New lines into a break the spreadsheets. Empowering google spreadsheets, a line breaks and financial reporting tool for this as the global tech podcaster: apple podcasts google data? My spreadsheet at google spreadsheets and line breaks and if selected section header. Please do this block to break line breaks in bulk sheets for the. Install google spreadsheet, a line breaks. Thanks winston that google spreadsheet cell that every line breaks, but others will be due to add a function.
    [Show full text]
  • Open Data Plan for 2020 to 2022
    Office of the Government Chief Information Officer (OGCIO) Open Data Plan for 2020 to 2022 A. Departmental datasets to be released in 2020 (In Target Release Date Order) # Type of Data/ Name of Dataset Target Release Frequency of Update Remarks Date (in mm/yyyy) 1. IT / 01/2020 As and when there are new ICT Event Calendar aims at collating ICT Event Calendar entries major ICT events in Hong Kong to facilitate promotion of Hong Kong as an ICT hub. The dataset includes information on event name, event type (e.g. exhibition), date, time, organiser, venue, event description, link to event website and organiser contact information (JSON) 2. IT/ 01/2020 As and when there are new Titles, current challenges, expected List of Service Needs of Government entries outcomes of service needs raised by Departments posted in Smart Government government departments, and their Innovation Lab corresponding entries in the website of Smart Government Innovation Lab (JSON) 3. IT/ 01/2020 As and when there are new Titles, descriptions and supplier List of Solutions from IT Suppliers collected entries names of IT solutions proposed by IT in Smart Government Innovation Lab suppliers, and their corresponding entries in the website of Smart Government Innovation Lab (JSON) 4. IT / 01/2020 As and when necessary List of programmes funded by the Programmes in Encouraging ICT Adoption OGCIO in encouraging ICT adoption among the Elderly by OGCIO among the elderly. The dataset includes project information under each programme such as project name, implementer’s name and contact, implementation period and link to programme details on OGCIO website (JSON) Note: To replace Table D #10 dataset “IT/Past Programmes in Encouraging ICT Adoption among the Elderly by OGCIO” 5.
    [Show full text]
  • Design for Inclusion White Paper
    Design for Inclusion: Creating a New Marketplace Industry White Paper National Council on Disability October 28, 2004 National Council on Disability 1331 F Street, NW, Suite 850 Washington, DC 20004 Design for Inclusion: Creating a New Marketplace—Industry White Paper This report is also available in alternative formats and on NCD’s award-winning Web site (www.ncd.gov). Publication date: October 28, 2004 202-272-2004 Voice 202-272-2074 TTY 202-272-2022 Fax Notes: The views contained in this report do not necessarily represent those of the Administration as this and all NCD documents are not subject to the A-19 Executive Branch review process. Please note that reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not constitute or imply its endorsement by the National Council on Disability. National Council on Disability Members and Staff Members Lex Frieden, Chairperson, Texas Patricia Pound, First Vice Chairperson, Texas Glenn Anderson, Ph.D., Second Vice Chairperson, Arkansas Milton Aponte, J.D., Florida Robert R. Davila, Ph.D., New York Barbara Gillcrist, New Mexico Graham Hill, Virginia Joel I. Kahn, Ph.D., Ohio Young Woo Kang, Ph.D., Indiana Kathleen Martinez, California Carol Novak, Florida Anne M. Rader, New York Marco Rodriguez, California David Wenzel, Pennsylvania Linda Wetters, Ohio Staff Ethel D. Briggs, Executive Director Jeffrey T. Rosen, General Counsel and Director of Policy Mark S. Quigley, Director of Communications Allan W. Holland, Chief Financial Officer Julie Carroll, Attorney Advisor Joan M. Durocher, Attorney Advisor Martin Gould, Ed.D., Senior Research Specialist Geraldine Drake Hawkins, Ph.D., Program Analyst Pamela O’Leary, Interpreter Brenda Bratton, Executive Assistant Stacey S.
    [Show full text]
  • Spectrum Technology Platform Version 12.0
    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.
    [Show full text]