DOCSLIB.ORG

IVOA Identifiers Version

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IVOA Identifiers Version International Virtual Observatory Alliance IVOA Identifiers Version 2.0 IVOA Recommendation 2016-05-23 Working group Resource Registry This version http://www.ivoa.net/documents/Identifiers/20160523 Latest version http://www.ivoa.net/documents/Identifiers Previous versions REC-1.12 PR-20050302 PR-20040621 WD-20040209.html WD-20031031 WD-20030930 PR-20030830.html Author(s) Markus Demleitner, Raymond Plante, Tony Linde, Roy Williams, Keith Noddle, and the IVOA Registry Working Group Editor(s) Markus Demleitner Version Control Revision 3158, 2015-11-20 09:04:09 +0100 (Fri, 20 Nov 2015) https://volute.g-vo.org/svn/trunk/projects/registry/Identifiers/Identifiers.tex arXiv:1605.07501v1 [astro-ph.IM] 24 May 2016 Abstract An IVOA Identifier is a globally unique name for a resource within the Vir- tual Observatory. This name can be used to retrieve a unique description of the resource from an IVOA-compliant registry or to identify an entity like a dataset or a protocol without dereferencing the identifier. This document describes the syntax for IVOA Identifiers as well as how they are created. The syntax has been defined to encourage global-uniqueness naturally and to maximize the freedom of resource providers to control the character content of an identifier. Status of This Document This document has been reviewed by IVOA Members and other interested parties, and has been endorsed by the IVOA Executive Committee as an IVOA Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. IVOA’s role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability inside the Astronomical Community. A list of current IVOA Recommendations and other technical documents can be found at http://www.ivoa.net/Documents/. Contents 1 Introduction3 1.1 Definitions . .4 1.2 Selected Requirements . .6 1.3 Rationale for Version 2 . .6 1.4 IVOA Identifiers within the VO Architecture . .7 2 Specification8 2.1 Overview (non-normative) . .8 2.2 Characters . .9 2.3 Syntax Components . .9 2.3.1 Scheme . .9 2.3.2 Authority . 10 2.3.3 Resource Key . 11 2.3.4 Query . 12 2.3.5 Fragment . 13 2.4 Usage . 13 2.5 Reference Resolution . 14 2.6 Normalization and Comparison . 14 3 Creating Identifiers 16 2 4 Special Identifier Types 16 4.1 Dataset Identifiers . 16 4.2 Standard Identifiers . 17 A Changes from Previous Versions 18 A.1 Changes from PR-2015-07-09 . 19 A.2 Changes from 1.12 . 19 A.3 Changes from v1.10 . 19 A.4 Changes from v1.0 . 20 A.5 Changes from v0.1 . 20 Acknowledgments This document builds on the concept of a Uniform Resource Identifier as de- scribed in RFC 3986 (Berners-Lee et al., 2005) and its predecessors. This document has been developed with support from the National Sci- ence Foundation’s Information Technology Research Program under Coopera- tive Agreement AST0122449 with The Johns Hopkins University, from theUK Particle Physics and Astronomy Research Council (PPARC), from the European Commission’s Sixth Framework Program via the Optical Infrared Coordination Network (OPTICON), and from the German Astrophyiscal Virtual Observatory GAVO, BMBF grant 05A14VHA. Conformance-related definitions The words “MUST”, “SHALL”, “SHOULD”, “MAY”, “RECOMMENDED”, and “OPTIONAL” (in upper or lower case) used in this document are to be inter- preted as described in RFC 2119 (Bradner, 1997). Usage of ABNF This specification uses ABNF (Crocker and Overell, 1997) to specify grammar rules. The rules from RFC 3986 are assumed throughout. Where both this specification and RFC 3986 define a nonterminal, the rule in this specification overrides the corresponding rule from RFC 3986. For explicitness, we write ABNF nonterminals in angle brackets (hlike thisi ) throughout. 1 Introduction Virtual Observatory applications frequently need to unambiguously refer to some resource or concept which is described elsewhere. It is therefore necessary 3 to define global, potentially dereferenceable identifiers. In the VO, these are called IVOA identifiers (IVOIDs). An unambiguous reference within the entire Virtual Observatory requires that the identifier is globally unique. Ensuring this uniqueness inevitably requires oversight by a moderating authority; however, a flexible framework can minimize the opportunity for duplicated identifiers. Many data providers in the VO were creating and using identifiers long be- fore this specification was developed. Their choices of identifiers were made presumably to best fit the needs of the data. In order to minimize the cost of adoption of the IVOA identifier framework the design specified here maxi- mizes the control providers have, thus allowing the reuse of the identifiers data providers already have in place as well as the creation of new idenfiers that are consistent with their overall organization. Identifiers are crucial to the operation of registries that aid users in dis- covering data and services (Benson et al., 2009). In general, a registry stores descriptions of data and services in a searchable form, and it distinguishes them by the unique identifier defined here. It thus serves as a primary key for the VO Registry, and thus allows dereferencing identifiers to metadata about a resource (the resource record). IVOA identifiers with query or fragment parts can furthermore reference essentially arbitrary entities like datasets or protocols, based on this primary mechanism of dereferencing. We recognize that resources do not always remain in the control of a single organization forever. This necessitates a form of referencing that is location- independent – or more precisely, organization-independent. Apart from enabling seamless transfers of data curation, an attractive use case for such identifiers is when several copies of a dataset exist at several locations around the VO and one could refer to all of them collectively, deferring the choice of a particular instance until it is actually needed. Such references thus serve as persistent pointers to data that can be flexibly resolved. This is very important to journal publishers that wish to refer to data in publications (whose useful life might be measured in decades) without worry that the references will become obsolete. This specification, in contrast, defines organization-dependent identifiers. Persistent, organization- and location-independent identifiers are not (directly) defined here. Referencing resources is addressed by the IETF standard for URIs, RFC 3986 (Berners-Lee et al., 2005). Thus, the framework proposed in this document builds directly on this standard. Essentially, this standard sets the parameters left open for application use by RFC 3986. 1.1 Definitions A Uniform Resource Identifier (URI) is defined by RFC 3986 as “a compact sequence of characters that identifies an abstract or physical resource” which complies with the syntax specification of that document (Berners-Lee et al., 4 2005). It can point to an actual retrievable resource, but there is no requirement for it to be dereferenceable at all, let alone by a stock web browser. An IVOA identifier, or IVOID, is a special sort of URI complying with all parts of this specification. Historically, these have also been known as IVOA Resource Names (IVORNs), in parallel to the Uniform Resource Names (URNs) that formulated extra requirements on persistency and location-independence. As plain IVOIDs do not fulfill those requirements and the term URN has been deprecated by RFC 3986, we now deprecate the term IVORN, too. A full IVOID can thus be split into a Registry part (schema, authority, and path) and a possibly empty local part consisting of query and fragment component, again using RFC 3986 nomenclature. An IVOID with an empty local part is also known as a Registry reference. In VO practice, the term resource is somewhat ambiguous. The IVOA Rec- ommendation on Resource Metadata (Hanisch et al., 2007), from here on re- ferred to as RM, defines it as “a VO element that can be described in terms of who curates or maintains it and which can be given a name and a unique identifier.” It then goes on to define the relevant pieces of metadata, which later provided the foundations of the data model behind the IVOA Registry. This might lead to the expectation that there is a 1:1 relationship between Registry records, “VO resources”, and IVOA identifiers, and version 1 of this document essentially implied as much. In this version, we only require Registry references to resolve in the Registry. IVOIDs having a nonempty local part do not dereference to Registry records. Since we want to maintain the notion that a resource is whatever a URI points to, “resource” as used here does not correspond to the usage of the term in VORe- source (Plante et al., 2008). To maintain the distinction, we call resources in the sense of VOResource Registry records. These form a subset of the resources (in the URI sense) that can be referenced by IVOIDs. We refer to organizations and providers in the sense that they are defined in RM: An organization is a specific type of resource that brings people together to pursue participation in VO applications. Organizations can be hierarchical and range greatly in size and scope. At a high level, it could be a university, observatory, or government agency. At a finer level, it could be a specific scientific project, space mission, or individual researcher. A provider is an organization that makes data and/or services available to users over the network. Definitions of other types of resources, including data collection and service, are also provided in RM, and are assumed by this document. 5 1.2 Selected Requirements This proposal is the result of various requirement studies for VO identifiers and registries in general (e.g. NVO ID requirements1). This section highlights a few of the important ones that guided the design of the ID framework.
Load more

Recommended publications
  • Armenian Alphabet Confusing Letters
    Armenian Alphabet: Help to Distinguish the “Look-Alike” (confusing) 12 of the 38 Letters of the Armenian Alphabet 6. B b z zebra 27. A a j jet (ch) church 17. ^ 6 dz (adze) (ts) cats 25. C c ch church 19. ch unaspirated ch/j (j) jet Q q • 14. ts unaspirated ts/dz (dz) adze ) 0 • 21. & 7 h hot initial y Maya medial y final in monosyllable except verbs silent final elsewhere 35. W w p piano 36. @ 2 k kid 34. U u v violin 31. t step unaspirated t/d (d) dance K k • 38. ~ ` f fantastic ARMENIAN ALPHABET First created in the 5th c. by Mesrop Mashtots. Eastern Armenian Dialect Transliteration. (Western Dialect, when different, follows in parentheses). 1. a father 14. ts unaspirated ts/dz (dz) adze G g ) 0 • 2. E e b boy (p) piano 15. k skip unaspirated k/g (g) go I i • 3. D d g go (k) kid 16. L l h hot 4. X x d dance (t) ten 17. ^ 6 dz (adze) (ts) cats 5. F f ye yet initial e pen medial 18. * 8 gh Parisian French Paris e pen initial ft, fh, fh2, fr you are 19. ch unaspirated ch/j (j) jet Q q • y yawn before vowel 20. T t m meet 6. B b z zebra 21. h hot initial 7. e pen & 7 + = y Maya medial 8. O o u focus y final in monosyllable except verbs silent final elsewhere 9. P p t ten 22. H h n nut 10.
    [Show full text]
  • Fonts for Latin Paleography 
    FONTS FOR LATIN PALEOGRAPHY Capitalis elegans, capitalis rustica, uncialis, semiuncialis, antiqua cursiva romana, merovingia, insularis majuscula, insularis minuscula, visigothica, beneventana, carolina minuscula, gothica rotunda, gothica textura prescissa, gothica textura quadrata, gothica cursiva, gothica bastarda, humanistica. User's manual 5th edition 2 January 2017 Juan-José Marcos [email protected] Professor of Classics. Plasencia. (Cáceres). Spain. Designer of fonts for ancient scripts and linguistics ALPHABETUM Unicode font http://guindo.pntic.mec.es/jmag0042/alphabet.html PALEOGRAPHIC fonts http://guindo.pntic.mec.es/jmag0042/palefont.html TABLE OF CONTENTS CHAPTER Page Table of contents 2 Introduction 3 Epigraphy and Paleography 3 The Roman majuscule book-hand 4 Square Capitals ( capitalis elegans ) 5 Rustic Capitals ( capitalis rustica ) 8 Uncial script ( uncialis ) 10 Old Roman cursive ( antiqua cursiva romana ) 13 New Roman cursive ( nova cursiva romana ) 16 Half-uncial or Semi-uncial (semiuncialis ) 19 Post-Roman scripts or national hands 22 Germanic script ( scriptura germanica ) 23 Merovingian minuscule ( merovingia , luxoviensis minuscula ) 24 Visigothic minuscule ( visigothica ) 27 Lombardic and Beneventan scripts ( beneventana ) 30 Insular scripts 33 Insular Half-uncial or Insular majuscule ( insularis majuscula ) 33 Insular minuscule or pointed hand ( insularis minuscula ) 38 Caroline minuscule ( carolingia minuscula ) 45 Gothic script ( gothica prescissa , quadrata , rotunda , cursiva , bastarda ) 51 Humanist writing ( humanistica antiqua ) 77 Epilogue 80 Bibliography and resources in the internet 81 Price of the paleographic set of fonts 82 Paleographic fonts for Latin script 2 Juan-José Marcos: [email protected] INTRODUCTION The following pages will give you short descriptions and visual examples of Latin lettering which can be imitated through my package of "Paleographic fonts", closely based on historical models, and specifically designed to reproduce digitally the main Latin handwritings used from the 3 rd to the 15 th century.
    [Show full text]
  • Ninidze, Mariam " a New Point of Vew on the Origin of the Georgian Alphabet"
    Maia Ninidze A New Point of View on the Origin of the Georgian Alphabet The history of the development of different scripts shows that writing may assume the organized systemic appearance that Georgian asomtavruli (capital alphabet) had in the 5th century only as a result of reform. No graphic system has received such refined appearance through its independent evolution. Take, for example, the development of the Greek alphabet down to 403 B.C. In reconstructing the original script of the Georgian alphabet I was guided by the point of view that "the first features and the later developed or introduced foreign elements should be demarked and in this way comparative chronology be defined" (10, p. 50) and that "knowledge of the historical development of the outline of letters will enable us to form an idea of how the change of the outline of letters occurred and ... perceive the type of the preceding change, no imprints on monuments of which have come down to us" (12. p. 202). When one alphabet evinces similarity with another in the outline of corresponding graphemes of similar sounds, this suggests their common provenance or one's derivation from the other. But closeness existing at the level of general systemic peculiarities is a sign of later, artificial assimilation. The systemic similarity of Georgian asomtavruli with Greek would seem to suggest that it was reformed on the basis of the Greek counterpart. The earliest Georgian inscriptions in the asomtavruli are characterized by similarity to Greek in: 1) equal height of letters, 2) geometric roundness of graphemes and linearity-angularity, 3) the direction of writing from left to right, 4) the order of the alphabet and the numerical value of graphemes, but not similarity in the form of individual graphemes.
    [Show full text]
  • Vocabularies in the VO Version 2.0
    International Virtual Observatory Alliance Vocabularies in the VO Version 2.0 IVOA Working Draft 2020-03-26 Working group Semantics This version http://www.ivoa.net/documents/Vocabularies/20200326 Latest version http://www.ivoa.net/documents/Vocabularies Previous versions WD-20190905 Author(s) Markus Demleitner Editor(s) Markus Demleitner Abstract In this document, we discuss practices related to the use of RDF-based vocabularies in the VO. This primarily concerns the creation, publication, and maintenance of vocabularies agreed upon within the IVOA. To cover the wide range of use cases envisoned, we define three flavours of such vo- cabularies: SKOS for informal knowledge organisation on the one hand, and strict hierarchies of classes and properties on the other. While the framework rests on the solid foundations of W3C RDF, provisions are made to facili- tate using IVOA vocabularies without specific RDF tooling. Non-normative appendices detail the current vocabulary-related tooling. Status of this document This is an IVOA Working Draft for review by IVOA members and other interested parties. It is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use IVOA Working Drafts as reference materials or to cite them as other than “work in progress”. A list of current IVOA Recommendations and other technical documents can be found at http://www.ivoa.net/documents/. Contents 1 Introduction4 1.1 Role within the VO Architecture................5 1.2 Relationship to Vocabularies in the VO Version 1.......6 1.3 Reading Guide..........................7 1.4 Terminology, Conventions, Typography.............7 2 Derivation of Requirements (Non-Normative)8 2.1 Use Cases.............................8 2.1.1 Controlled Vocabulary in VOResource.........8 2.1.2 Controlled Vocabularies in VOTable..........8 2.1.3 Datalink Link Selection.................8 2.1.4 VOEvent Filtering, Query Expansion..........9 2.1.5 Vocabulary Updates in VOResource..........9 2.1.6 Discovering Meanings.................
    [Show full text]
  • 2020 Global Payments Guide
    FS TREASURY SERVICES 2020 Global Payments Guide Your Guide To Making Cross-Currency Payments in over 160 Countries with Ease. 2020 Global Payments Guide Last Updated: November 13, 2020 For the most up-to-date version, please visit jpmorgan.com/visit/guide | 2 The J.P. Morgan Global Payments Guide is your desktop resource to help you make timely and accurate payments to beneficiaries around the world. Work with J.P. Morgan to get the global payment support that your business Setting up your payment Cross-Border Payment Requirement demands It is best practice to include the below standard information in Intermediary banks are often used when a payment is made in a With employees, suppliers and operations located around the payment instructions to avoid potential delays or returns: currency that is different from the local currency. When making a globe, ensuring prompt payments in multiple currencies is a payment through an intermediary bank, their SWIFT BIC must be Ordering Customer challenge. Your business requires a partner who takes the time to – included. understand your needs and helps ensure your payments are Account number processed smoothly. – Full name (no initials) Key Terms – Full address International Bank Account Number (IBANN As one of the top-ranked cash management and payments – Street address (avoid P.O. Box numbers) The International Bank Account Number, IBAN, is an internationally processors in the world, J.P. Morgan is able to offer the tools that – City agreed standard to identify an individual’s account at a financial help you manage your day-to-day global operations, along with – State Code institution.
    [Show full text]
  • Methods for the Reconstruction
    REF ID: A414644lc,..... -v' (3.) -Methods for the Reconstruction of \ Primary Alphabets - - t ~y K~ vrn to tne d 1~ uo '''.OT ~es r - - h n ~ longer need.~ ___ · NSA Techni·~al Libra~_!_·- 0 _ s--ot? I 'I/.. ~="'~ z_ ss ? · -- - Coi>Y No. f '??-- - - -- Publication No . DJ - / / ,I I I I ~ . RIVERBANK LABO RA TO RIES DEPARTMENT OF CIPHERS RIVERBANK - GENEVA, ILL. 1918 -~---- @'pproved for Release by NSA on 10-14-2014 pursuantto E_O_ 1352a - REF ID:A4146441 Methods for the Reconstruction of Primary Alphabets Publication No. 21 RIVERBANK LABORATORIES DEPARTMENT,OF CIPHERS RIVERBANK GENEVA, ILL. 1918 - --- ----- --- ~ ' .--- 1, -e?'. ' .? • ..- ' REF ID :A4·146441 Two Hundred copies of this publication were printed of which this is No. 151 ., . :· Copyright, 1918 GEORGE FABYAN REF ID:A4146441 . : I• INTRODUCTORY NOTE It is not our intention in this brochpre to describe any newly-discovered methods of I ' I cipher solution, or indeed, to make a detailed analysis of even any one system. vVe do not I 1-t:l' claim any remarkable achievement in putting· forth the few principles herein described. l They are meant rather as a stimulant to the more advanced student of deciphering. There­ ) fore no attempt has been made to make any exhaustive analysis of different systems, or of ' varying methods of using the same system'. The methods here given are1 issued primarily as an outline or suggestion to the cipher student who is more or less familiar with complicated systems, and who therefore will be quick to see the applicatjon of the present principles to any variations ()f known methods.
    [Show full text]
  • A Comparative Analysis of Information Hiding Techniques for Copyright Protection of Text Documents
    Hindawi Security and Communication Networks Volume 2018, Article ID 5325040, 22 pages https://doi.org/10.1155/2018/5325040 Review Article A Comparative Analysis of Information Hiding Techniques for Copyright Protection of Text Documents Milad Taleby Ahvanooey ,1 Qianmu Li ,1 Hiuk Jae Shim,2 and Yanyan Huang3 1 School of Computer Science and Engineering, Nanjing University of Science and Technology, Nanjing, China 2School of Computer and Sofware, Nanjing University of Information Science and Technology, Nanjing, China 3School of Automation, Nanjing University of Science and Technology, Nanjing, China Correspondence should be addressed to Milad Taleby Ahvanooey; [email protected] and Qianmu Li; [email protected] Received 6 October 2017; Revised 28 December 2017; Accepted 16 January 2018; Published 17 April 2018 Academic Editor: Pino Caballero-Gil Copyright © 2018 Milad Taleby Ahvanooey et al. Tis is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. With the ceaseless usage of web and other online services, it has turned out that copying, sharing, and transmitting digital media over the Internet are amazingly simple. Since the text is one of the main available data sources and most widely used digital media on the Internet, the signifcant part of websites, books, articles, daily papers, and so on is just the plain text. Terefore, copyrights protection of plain texts is still a remaining issue that must be improved in order to provide proof of ownership and obtain the desired accuracy. During the last decade, digital watermarking and steganography techniques have been used as alternatives to prevent tampering, distortion, and media forgery and also to protect both copyright and authentication.
    [Show full text]
  • Katakana Range: 30A0–30FF
    Katakana Range: 30A0–30FF This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 14.0 This file may be changed at any time without notice to reflect errata or other updates to the Unicode Standard. See https://www.unicode.org/errata/ for an up-to-date list of errata. See https://www.unicode.org/charts/ for access to a complete list of the latest character code charts. See https://www.unicode.org/charts/PDF/Unicode-14.0/ for charts showing only the characters added in Unicode 14.0. See https://www.unicode.org/Public/14.0.0/charts/ for a complete archived file of character code charts for Unicode 14.0. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 14.0 but do not provide all the information needed to fully support individual scripts using the Unicode Standard. For a complete understanding of the use of the characters contained in this file, please consult the appropriate sections of The Unicode Standard, Version 14.0, online at https://www.unicode.org/versions/Unicode14.0.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, #44, #45, and #50, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online. See https://www.unicode.org/ucd/ and https://www.unicode.org/reports/ A thorough understanding of the information contained in these additional sources is required for a successful implementation.
    [Show full text]
  • Phonetic Symbols, P
    36602. PHONOLOGY Prof. Yehuda N. Falk Phonetic Symbols, p. 1 The chart on this page is vowels; the one on p. 2 is consonants. For some sounds, more than one symbol is in use. In such a case, the symbol we will be using in class (which is generally the symbol commonly used by phonologists, and derives from the American transcriptional tradition) is listed above, and the other symbol (generally the official symbol of the International Phonetic Alphabet) is listed below. VOWELS In each box, the vowel symbol on the left is for an unrounded vowel and the symbol on the right is for a rounded vowel. Note that, since vowel articulations are points along a continuum, vowel transcriptions represent ranges of sounds. For this reason, the same symbol sometimes appears in more than one cell of the table. Front Central Back tense i ü ˙ ˙ u y High lax ¨ ˙ ˙ tense e ö o ø Mid lax ö o ø o or tense æ ¨ a or a or œ a Low lax æ ¨ or a or a or a Additional symbols: nasalized: ˜ (e.g. a˜) nonsyllabic (e.g. i ) long: (e.g. a ) main stress ´ (e.g. á) extra-short ˘ (e.g. a˘) secondary stress ` (e.g. à) Tones: extra high x˝/ high x´/middle x¯/low x`/extra low x/rising xˇ/falling xˆ CONSONANTS The symbol on the left is voiceless; the symbol on the right is voiced. Bilabial Labio- Dental Alveolar Palato-al- Retroflex Palatal Velar Uvular Pharyngeal Laryngeal p.2 Symbols, Phonetic PHONOLOGY 36602. dental veolar Stop p b t d t d t d c k q .
    [Show full text]
  • Proposal for an Armenian Script Root Zone LGR 1 General Information
    Proposal for an Armenian Script Root Zone LGR Version 3 Date: 2015-06-04 1 General information The purpose of this document is to give an overview of the proposed LGR and the rationale behind the design decisions taken. It includes a discussion of relevant features of the script, the communities or languages using it, the process and methodology used and information on the contributors. The formal specification of the LGR can be found in the accompanying XML document (Proposed-LGR-Armn- 20150604.xml). 1.1 Script for which the LGR is proposed Code: Armn N°: 230 English Name: Armenian Property Value Alias: Armenian Date: 2004-05-01 English name of the script: Hye Native name of the script: հայ The Armenian language is an Indo-European language spoken by the Armenians. It is the official language of the Republic of Armenia and the self-proclaimed Nagorno-Karabakh Republic. It has historically been spoken throughout the Armenian Highlands and today is widely spoken in the Armenian Diaspora. Armenian has its own unique script, the Armenian alphabet, invented in 405 AD by Mesrop Mashtots. Linguists classify Armenian as an independent branch of the Indo-European language family. There are two standardized modern literary forms, Eastern Armenian and Western Armenian, with which most contemporary dialects are mutually intelligible. 1 1.2 Principal languages using that script List Language code and name for each (from ISO 639-3) ISO 639-1 hy ISO 639-2 arm (B) hye (T) ISO 639-3 Variously: hye – Modern Armenian xcl – Classical Armenian axm – Middle Armenian Glottolog arme1241 Linguasphere 57-AAA-a 1.3 Geographic territories or countries with significant user communities for the script Official language in Armenia Nagorno-Karabakh Republic Big Diaspora using the Armenian language in Argentina Brazil Cyprus France Georgia (Samtskhe- Javakheti) Hungary Iraq Lebanon Poland Romania Syria Turkey Ukraine United States 2 Uruguay Total Armenian population in the world is about 10mln.
    [Show full text]
  • IPA Braille: an Updated Tactile Representation of the International Phonetic Alphabet
    IPA Braille: An Updated Tactile Representation of the International Phonetic Alphabet Print Edition Overview, Tables, and Sample Texts Edited by Robert Englebretson, Ph.D. Produced by CNIB For the International Council on English Braille 2008 List of ICEB Member Countries As Of April, 2008 Australia Canada New Zealand Nigeria South Africa United Kingdom United States ii Table of Contents ACKNOWLEDGEMENTS BY ROBERT ENGLEBRETSON.............................................. V FOREWORD by Fredric K. Schroeder .................................................................. VII ACCLAIM FOR IPA BRAILLE BY MARTHA PAMPERIN.............................................IX 1. INTRODUCTION ............................................................................................. 1 2. THE SYMBOLS OF THE IPA ............................................................................. 5 2.1. CONSONANTS (PULMONIC) .................................................................. 6 2.2. CONSONANTS (NON-PULMONIC) ....................................................... 11 2.3. OTHER SYMBOLS ................................................................................ 13 2.4. VOWELS ............................................................................................. 15 2.5. DIACRITICS ....................................................................................... 17 2.6. SUPRASEGMENTALS ........................................................................... 23 2.7. TONES & WORD ACCENTS..................................................................
    [Show full text]
  • Effects of Sensori-Motor Reinforcement on Alphabet Letter Discrimination Tasks
    Utah State University DigitalCommons@USU All Graduate Theses and Dissertations Graduate Studies 5-1970 Effects of Sensori-Motor Reinforcement on Alphabet Letter Discrimination Tasks Leona Magnus Peters Utah State University Follow this and additional works at: https://digitalcommons.usu.edu/etd Part of the Family, Life Course, and Society Commons Recommended Citation Peters, Leona Magnus, "Effects of Sensori-Motor Reinforcement on Alphabet Letter Discrimination Tasks" (1970). All Graduate Theses and Dissertations. 2264. https://digitalcommons.usu.edu/etd/2264 This Thesis is brought to you for free and open access by the Graduate Studies at DigitalCommons@USU. It has been accepted for inclusion in All Graduate Theses and Dissertations by an authorized administrator of DigitalCommons@USU. For more information, please contact [email protected]. ACKNOWL E DGMENT In appreciation of her contribution to this research, I would like to thank Dr. Carroll Lambert for her positive e ncouragement and critique in the planning, organization, and wr iting phases of this thesis. I would a lso like to express appreciation to the members of my committee, Dr. Don Car ter and Mrs. J oan Bowden, for their time a nd effort. Leona Magnus Peters TABLE OF CONTENTS Page INTRODUCTION 1 Statement of the Problem 4 Definition of Terms 4 REVIEW OF LITERATURE 6 Role of Sensory Input in Perceptual Learning of Alphabet Letters .... .. .......... 6 Characteristics of Difficulty Encountered in Perception of Alphabet Letters and Word Order .. ............. 10 The Role of the Sensori-Motor Reinforcement Program in the Learning Process . .. ... 13 Summary of Review of Literature 16 METHODS AND PROCEDURE 18 Se tting 18 Sample 19 Instruments 20 Pilot Study 22 Main Study .
    [Show full text]