DOCSLIB.ORG

Kirja-Alan Onix

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Kirja-Alan Onix KIRJA-ALAN ONIX SUOMALAINEN SOVELLUS Versio 3.0.2. Marraskuu 2012 Päivitetty huhtikuu 2015 Helsinki 2012 ISBN 978-952-10-8321-1 (PDF) Työryhmä: Mirja Anttila, Kansalliskirjasto Peter Bagge, Kustannusosakeyhtiö Otava Juha Hakala, Kansalliskirjasto Jari Heikkinen, Kansalliskirjasto Susanna Honkanen, Suomalainen Kirjakauppa Oy Maarit Huttunen, Kansalliskirjasto Karin von Koskull, Stockmann Oyj Abp, Akateeminen Kirjakauppa Tuomo Suominen, Sanoma Pro Oy Olli Tuuteri, BTJ Finland Oy Aija Vahtola, Kansalliskirjasto Eila Vainikka, Kuntaliitto Susanna Vestman, Kirjavälitys Oy Laura Vuorensola, Stockmann Oyj Abp, Akateeminen kirjakauppa Suomalainen ONIX-sovellus perustuu seuraaviin dokumentteihin: ONIX for Books Product Information Format Specification Release 3.0 revision 1, January 2012 ONIX for Books: Code Lists Issues 18–27 Alkuperäiset dokumentit ovat saatavilla osoitteessa http://www.editeur.org/ Kommentit formaattiin ja mahdolliset lisäkysymykset Suomen ONIX-keskukselle. http://www.onix.fi/ 1 Sisällys Suomalaisen sovelluksen esipuhe ........................................................................................................... 4 ONIX-viesti .............................................................................................................................................. 5 Viestin rakenne ................................................................................................................................... 5 P.1 Tuotetietueen viite ja tyyppi (Record reference number, type and source) .............................. 19 P.2 Tuotteen yksilöivät tunnisteet (Product numbers) ..................................................................... 20 Osio 1: Tuotteen bibliografinen kuvaus (product description) ............................................................. 22 P.3 Tuotemuoto (Product form) ....................................................................................................... 22 P.4 Tuotteen osat (Product parts)..................................................................................................... 33 P.5 Sarja (Collection) [0–n]................................................................................................................ 41 P.6 Nimeke (Product title detail) ...................................................................................................... 47 P.7 Tekijä (Authorship) [0–n] ............................................................................................................ 53 P.8 Konferenssi (Conference)............................................................................................................ 61 P.9 Painos (Edition) ........................................................................................................................... 64 P.10 Kieli ja kirjoitusjärjestelmä (Language) ..................................................................................... 66 P.11 Laajuus ja muuta tietoa sisällöstä (Extents and other content) ............................................... 68 P.12 Aihe (Subject) ............................................................................................................................ 73 P.13 Kohderyhmä (Audience) ........................................................................................................... 78 Osio 2: Markkinointiaineisto (Marketing collateral detail) ................................................................... 82 P.14 Tuotetta kuvaavat tekstit (Descriptions and other supporting text) ........................................ 82 P.15 Mediaviittaukset (Cited content) .............................................................................................. 85 P.16 Linkit markkinointimateriaaliin (Links to supporting resources) .............................................. 87 P.17 Palkinnot (Prizes) ...................................................................................................................... 95 Osio 4: Julkaisutiedot ja myyntirajoitukset (Publishing detail) ............................................................. 97 P.19 Kustantaja (Publisher) ............................................................................................................... 97 P.19.15 Tuotteen yhteystiedon rooli (Product contact role) [1] .................................................... 102 P.19.16 Tuotteen yhteystietojen tunnisteen tyyppi (Product contact identifier type) [1] ............. 102 P.19.17 Tunnistejärjestelmän nimi (Identifier type name) [0-1] .................................................... 102 P.19.18 Tunniste (Identifier value) [1] ............................................................................................ 103 P.19.19 Yhteysorganisaation nimi (Product contact name) [0-1] ................................................... 103 P.19.20 Yhteyshenkilön nimi (Contact name) [0-1] ........................................................................ 103 P.19.21 Yhteyshenkilön sähköpostiosoite (Product contact e-mail address) [0-1] ........................ 103 P.20 Tuotteen tila ja julkaisuaika (Global publishing status and dates / copyright) ....................... 104 2 P.21 Myyntirajoitukset (Territorial rights and other sales restrictions) ......................................... 109 Osio 5: Tuotteeseen liittyvät aineistot (Block 5: related material) ..................................................... 113 P.23 Liitännäistuotteet (Related products) ..................................................................................... 113 Osio 6: Välitystiedot (Block 6: Product supply) ................................................................................... 117 P.25 Tuotteen tilan lisätiedot (Market publishing detail) ............................................................... 117 P.26 Välittäjä ja kaupalliset tiedot (Supply detail) [0-1] ................................................................. 118 3 Suomalaisen sovelluksen esipuhe Kirja-alan yhteinen tuotetietoformaatti: Suomalainen ONIX-sovellus 3.0 Uusi suomalainen ONIX-sovellus 3.0 on ilmestynyt kesällä 2012. Uuden sovelluksen pohjana ovat EDItEURin julkaisemat kansainväliset formaattiversiot: ONIX for Books 3.0 vuodelta 2009 ja Release 3.0 revision 2 (3.0.2) vuoden 2014 alusta, sekä lokakuussa 2011 ilmestynyt ONIX for Books Implementation and Best Practices Guide Release. Formaattiin sisältyviä koodilistoja päivitetään neljä kertaa vuodessa. Myös suomalaisen sovelluksen koodilistat pidetään ajan tasaisina – sellaiset uudet koodit (tai kokonaan uudet koodilistat), joita pidetään tarpeellisina myös suomalaisessa sovelluksessa, lisätään sovellukseen säännöllisinä päivityksinä. Päivityksistä ilmoitetaan Onix-keskuksen www-sivuilla ja sieltä on myös aina saatavissa päivitetty versio sovelluksesta. Suomalaisen ONIX-sovelluksen 3.0 käännöstyöhön on osallistunut ONIX-keskuksen lisäksi suomalaisen kirja-alan toimijoista koostuva tekninen ONIX-ryhmä. Kansainvälistä ONIX-yhteistyötä on ylläpidetty osallistumalla kansainvälisen EDItEUR -organisaation toimintaan. Toimijoiden toivotaan huomioivan, että formaattisovellus 3.0 ei ole yhteensopiva version 2.1 kanssa. Siirtymä 2.1:stä 3.0:aan on edennyt eri maissa ja eri organisaatioissa eri vauhtia. Jotkut organisaatiot tulevat jatkamaan 2.1:n käyttöä myös vuoden 2014 jälkeen. Noita organisaatioita suositellaan kuitenkin vahvasti siirtymään 3.0:aan niin pian kuin mahdollista. ONIX 2.1 ei lakkaa toimimasta, mutta osa EDItEUR:in tuesta 2.1:lle lopetetaan. Suomalainen ONIX-sovellus 3.0 on poimittavissa maksutta osoitteesta: www.onix.fi. Lisätietoa Kirja-alan ONIXin suomalaisesta sovelluksesta ja siihen liittyvistä palveluista on saatavissa ONIX-keskuksen kotisivuilla (www.onix.fi) ja ONIX-keskuksesta. ONIX-keskus ja tekninen ONIX-ryhmä 4 ONIX-viesti Viestin rakenne ONIX for Books on XML-pohjainen formaatti, jonka avulla voidaan välittää tietoja kirjoista ja kirjoihin liittyvistä tuotteista. ONIX-formaatin mukainen tuoteviesti koostuu neljästä osasta: viestin alusta, jonka muodon ja sisällön määrää XML-standardi, otsikko-ryhmästä, viestin sisältämistä tuotetietueista ja viestin lopusta. Otsikko-osassa ilmoitetaan mm. viestin lähettäjä ja lähetysaika. Otsikko-ryhmää on käsitelty tarkemmin seuraavassa luvussa. ONIX-viesti sisältää yhden tai useampia tuotetietueita. Kerralla voidaan periaatteessa lähettää kuinka monta tietuetta hyvänsä. ONIX-formaatissa tuotetietoa välitetään vapaamuotoisena tekstinä ja koodilistojen avulla. Koodilistoja käytetään, jotta tuotetiedot olisivat sekä lähettäjälle että vastaanottajalle mahdollisimman yksiselitteisessä muodossa. Koodilistoja päivitetään säännöllisesti ja uusia koodeja lisätään tarpeen mukaan. Koodin vanhentuessa sitä ei poisteta, mutta vanhentuneen koodin käyttöä ei suositella. ONIX-viestin tulee olla XML-standardin mukainen ja yhteensopiva EDItEURin ylläpitämässä skeemassa määritellyn rakenteen kanssa. Skeema on saatavana kolmessa formaatissa, joista RNG ja XSD -skeemojen avulla voidaan validoida viesti myös koodilistojen koodien osalta, DTD-skeema ei sisällä koodilistoja. Validointi DTD-formaattia käyttäen ei ole riittävä eikä sitä suositella, koska koodien arvoja ei voida tällä menetelmällä validoida. Toteuttajat voivat vapaasti valita, mitä skeemaa käyttävät ONIX-viestien validoinnissa, mutta jos DTD-skeema valitaan, toteuttajien täytyy jollain muulla tapaa tarkistaa, että kaikki koodien arvot ovat voimassa. Kukin skeema on lisäksi saatavana kahdessa muodossa, joista toisessa on käytetty XML-elementtien koko
Load more

Recommended publications
  • L2/20-246 Teeth and Bellies: a Proposed Model for Encoding Book Pahlavi
    L2/20-246 Teeth and bellies: a proposed model for encoding Book Pahlavi Roozbeh Pournader (WhatsApp) September 7, 2020 Background In Everson 2002, a proposal was made to encode a unified Avestan and Pahlavi script in the Unicode Standard. The proposal went through several iterations, eventually leading to a separate encoding of Avestan as proposed by Everson and Pournader 2007a, in which Pahlavi was considered non-unifiable with Avestan due to its cursive joining property. The non-cursive Inscriptional Pahlavi (Everson and Pournader 2007b) and the cursive Psalter Pahlavi (Everson and Pournader 2011) were later encoded too. But Book Pahlavi, despite several attempts (see the Book Pahlavi Topical Document list at https://unicode.org/L2/ topical/bookpahlavi/), remains unencoded. Everson 2002 is peculiar among earlier proposals by proposing six Pahlavi archigraphemes, including an ear, an elbow, and a belly. I remember from conversations with Michael Everson that he intended these to be used for cases when a scribe was just copying some text without understanding the underlying letters, considering the complexity of the script and the loss of some of its nuances to later scribes. They could also be used when modern scholars wanted to represent a manuscript as written, without needing to over-analyze potentially controversial readings. Meyers 2014 takes such a graphical model to an extreme, trying to encode pieces of the writing system, most of which have some correspondence to letters, but with occasional partial letters (e.g. PARTIAL SHIN and FINAL SADHE-PARTIAL PE). Unfortunately, their proposal rejects joining properties for Book Pahlavi and insists that “[t]he joining behaviour of the final stems of the characters in Book Pahlavi is more similar to cursive variants of Latin than to Arabic”.
    [Show full text]
  • Ancient Scripts
    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]
  • Iso/Iec Jtc1/Sc2/Wg2 N3241 L2/07-102
    ISO/IEC JTC1/SC2/WG2 N3241 L2/07-102 2007-04-12 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Proposal for encoding the Parthian, Inscriptional Pahlavi, and Psalter Pahlavi scripts in the BMP of the UCS Source: Michael Everson Status: Individual Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2007-04-12 The three scripts proposed here were used to write a number of Indo-European languages, chiefly Parthian, and Middle Persian. They are descended from the Imperial Aramaic script used in Iran during the during the Achaemenid period (549–330 BCE), the Seleucid period (330–210 BCE) and the early Parthian period (210 BCE–224 CE). By the second century CE the Parthian script had evolved, and was used as the official script during the first part of the Sassanian period (224–651 CE). The main sources of Parthian are the inscriptions from Nisa (near present Ashgabat, Turkmenistan) and from Hecatompolis, as well as from texts in Manichean script, and a number of Sasanian multilingual inscriptions. In Pars in what is now southern Iran however the Aramaic script evolved differently, into the Inscriptional Pahlavi script, which was used regularly as a momumental script until the fifth century CE. The Psalter Pahlavi script was used in Chinese Turkestan and is so named because of its used in a fragmentary manuscript of the Psalms of David. This script itself developed (or decayed) into the ambiguous Book Pahlavi script which was replaced by the Avestan reformed script.
    [Show full text]
  • ONIX for Books Codelists Issue 40
    ONIX for Books Codelists Issue 40 23 January 2018 DOI: 10.4400/akjh All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All ONIX users should note that this is the fourth issue of the ONIX codelists that does not include support for codelists used only with ONIX version 2.1. Of course, ONIX 2.1 remains fully usable, using Issue 36 of the codelists or earlier. Issue 36 continues to be available via the archive section of the EDItEUR website (http://www.editeur.org/15/Archived-Previous-Releases). These codelists are also available within a multilingual online browser at https://ns.editeur.org/onix. Codelists are revised quarterly. Go to latest Issue Layout of codelists This document contains ONIX for Books codelists Issue 40, intended primarily for use with ONIX 3.0. The codelists are arranged in a single table for reference and printing. They may also be used as controlled vocabularies, independent of ONIX. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists used only with earlier releases have been removed. For details of which code list to use with which data element in each version of ONIX, please consult the main Specification for the appropriate release. Occasionally, a handful of codes within a particular list are defined as either deprecated, or not valid for use in a particular version of ONIX or with a particular data element.
    [Show full text]
  • Preliminary Proposal to Encode the Book Pahlavi Script in the Unicode Standard
    UTC Document Register L2/13-141R Preliminary proposal to encode the Book Pahlavi script in the Unicode Standard Roozbeh Pournader, Google Inc. July 24, 2013 1. Background This is a proposal to encode the Book Pahlavi script in the Unicode Standard. Book Pahlavi was last proposed in the “Preliminary proposal to encode the Book Pahlavi script in the BMP of the UCS” (L2/07-234 = JTC1/SC2/WG2 N3294). Here is a short summary of the major differences in the character repertoire between that document and this proposal: • Characters only proposed here: an alternate form of d and a second alternate form of l (see section 7), one atomic symbol and two atomic ligatures (section 8), combining dot below (sections 3 and 6); • Characters proposed in L2/07-234 but not proposed here: ABBREVIATION TAA (representable as a character sequence, section 9), three archigraphemes (ambiguity, implementability, and multiple representation concerns, section 5), combining three dots below (no evidence of usage found), KASHIDA (unified with TATWEEL, sections 9 and 10), numbers (more information needed, section 10). 2. Introduction Book Pahlavi was the most important script used in writing the Middle Persian language.1 It probably started to be commonly used near the end of the Sassanian era (sixth century CE), evolving from the non-cursive Inscriptional Pahlavi. While the term “Book Pahlavi” refers to the script mostly surviving in books, Book Pahlavi has also been used in inscriptions, coins, pottery, and seals. Together with the alphabetic and phonetic Avestan script, the Book Pahlavi abjad is of religious importance to the Zoroastrian community, as most of their surviving religious texts have been written in one or both of the scripts.
    [Show full text]
  • Name Hierarchy Methods Enums and Flags
    Pango::Gravity(3pm) User Contributed Perl Documentation Pango::Gravity(3pm) NAME Pango::Gravity − represents the orientation of glyphs in a segment of text HIERARCHY Glib::Enum +−−−−Pango::Gravity METHODS gravity = Pango::Gravity::get_for_matrix ($matrix) • $matrix (Pango::Matrix) gravity = Pango::Gravity::get_for_script ($script, $base_gravity, $hint) • $script (Pango::Script) • $base_gravity (Pango::Gravity) • $hint (Pango::GravityHint) boolean = Pango::Gravity::is_vertical ($gravity) • $gravity (Pango::Gravity) double = Pango::Gravity::to_rotation ($gravity) • $gravity (Pango::Gravity) ENUMS AND FLAGS enum Pango::Gravity • ’south’ / ’PANGO_GRAVITY_SOUTH’ • ’east’ / ’PANGO_GRAVITY_EAST’ • ’north’ / ’PANGO_GRAVITY_NORTH’ • ’west’ / ’PANGO_GRAVITY_WEST’ • ’auto’ / ’PANGO_GRAVITY_AUTO’ enum Pango::GravityHint • ’natural’ / ’PANGO_GRAVITY_HINT_NATURAL’ • ’strong’ / ’PANGO_GRAVITY_HINT_STRONG’ • ’line’ / ’PANGO_GRAVITY_HINT_LINE’ enum Pango::Script • ’invalid−code’ / ’PANGO_SCRIPT_INVALID_CODE’ • ’common’ / ’PANGO_SCRIPT_COMMON’ • ’inherited’ / ’PANGO_SCRIPT_INHERITED’ • ’arabic’ / ’PANGO_SCRIPT_ARABIC’ • ’armenian’ / ’PANGO_SCRIPT_ARMENIAN’ • ’bengali’ / ’PANGO_SCRIPT_BENGALI’ • ’bopomofo’ / ’PANGO_SCRIPT_BOPOMOFO’ • ’cherokee’ / ’PANGO_SCRIPT_CHEROKEE’ • ’coptic’ / ’PANGO_SCRIPT_COPTIC’ • ’cyrillic’ / ’PANGO_SCRIPT_CYRILLIC’ • ’deseret’ / ’PANGO_SCRIPT_DESERET’ • ’devanagari’ / ’PANGO_SCRIPT_DEVANAGARI’ • ’ethiopic’ / ’PANGO_SCRIPT_ETHIOPIC’ • ’georgian’ / ’PANGO_SCRIPT_GEORGIAN’ perl v5.28.0 2018-10-29 1 Pango::Gravity(3pm) User Contributed
    [Show full text]
  • Book Pahlavi
    ISO/IEC JTC1/SC2/WG2 N3294 L2/07-234 2007-07-30 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Preliminary proposal to encode the Book Pahlavi script in the BMP of the UCS Source: Michael Everson, Roozbeh Pournader, and Desmond Durkin-Meisterernst Status: Individual Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Replaces: N2556 Date: 2007-07-30 1. Introduction. “Pahlavi” is a term used in two senses. As a term for language, it means Zoroastrian or Sasanian Middle Persian. As a term for writing systems. the word is used to describe the scripts used to write religious and secular Sasanian Middle Persian and closely similar material, such as epigraphic Parthian and Middle Persian. Three “Pahlavi” scripts are distinguished: Inscriptional Pahlavi, Psalter Pahlavi, and Book Pahlavi. All of these derive from Imperial Aramic. Book Pahlavi is an alphabetic script with an incomplete representation of vowels. The original Imperial Aramaic script’s development is marked by a progressive loss of differentiation of many letters. Thus the Imperial Aramaic letters Ö WAW, ç NUN, è AYIN, and ì RESH coalesced into one simple vertical stroke, in Book Pahlavi written Ñ. (In Inscriptional Pahlavi only Ö WAW, ç NUN, and ì RESH coalesce into •.) The Imperial Aramaic letters Ä ALEPH and á HET coalesced into Book Pahlavi Ä; the Imperial Aramaic letters Ç GIMEL, É DALETH, and â YODH coalesced into Book Pahlavi Ç; and (less importantly) the Imperial Aramaic letters å MEM and í QOPH coalesced into Book Pahlavi ä.
    [Show full text]
  • N3353-AI Action Items from M51 Page 1 of 8 2007-10-10 Hangzhou, China; 2007-09-17/21
    Action Items for review at Meeting M52 Section 16 of meeting M50 minutes document N3353 16 Action items All the action items recorded in the minutes of the previous meetings from M25 to M47, and M49, have been either completed or dropped. Status of outstanding action items from earlier meetings M48 and M50, and new action items from the last meeting M51 are listed in the tables that follow. Meeting 25, 1994-04-18/22, Antalya, Turkey (document N1033) Meeting 26, 1994-10-10/14,San Francisco, CA, USA (document N1117) Meeting 27, 1995-04-03/07, Geneva, Switzerland (document N1203) Meeting 28, 1995-06-22/26, Helsinki, Finland (document N1253) Meeting 29, 1995-11-06/10, Tokyo, Japan (document N1303) Meeting 30, 1996-04-22/26, Copenhagen, Denmark (document N1353) Meeting 31, 1996-08-12/16, Québec City, Canada (document N1453) Meeting 32, 1997-01-20/24, Singapore (document N1503) Meeting 33, 1997-06-30/07-04, Heraklion, Crete, Greece (document N1603) Meeting 34, 1998-03-16/20, Redmond, WA, USA (document N1703) Meeting 35, 1998-09-21/25, London, UK (document N1903) Meeting 36, 1999-03-09/15, Fukuoka, Japan (document N2003) Meeting 37, 1999-09-17/21, Copenhagen, Denmark (document N2103) Meeting 38, 2000-07-18/21, Beijing, China (document N2203) Meeting 39, 2000-10-08/11, Vouliagmeni, Athens, Greece (document N2253) Meeting 40, 2001-04-02/05, Mountain View, CA, USA (document N2353), and Meeting 41, 2001-10-15/18, Singapore (document 2403) Meeting 42, 2002-05-20/23, Dublin, Ireland (document N2453) Meeting 43, 2003-12-09/12, Tokyo, Japan (document
    [Show full text]
  • ONIX for Books Codelists Issue 36
    ONIX for Books Codelists Issue 36 20 January 2017 DOI: 10.4400/akjh Go to latest Issue All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All ONIX users should note that this is the fourth issue of the ONIX codelists following the end of ‘twilight’ support for codelists used only with ONIX version 2.1. From the beginning of 2015, ONIX 2.1 was no longer fully supported by EDItEUR and was termed a ‘legacy format’. All versions of ONIX earlier than 2.1 are termed ‘obsolete’. Three years prior notice of this sunsetting of support for version 2.1 was given by EDItEUR and the ONIX International Steering Committee, and for several years, all users have been strongly advised to migrate to ONIX 3.0, which will remain fully supported for the foreseeable future. This ‘sunset’ of support also applies to the matching Supply Update message. At sunset, documentation and various XML tools for version 2.1 were withdrawn. However, certain codelists that were unique to 2.1 (for example codelists 7, 10 and 78) were updated as normal throughout 2015. This ‘twilight’ support for 2.1 codelists ended in January 2016 (Issue 32), and thereafter, codelists that are not used with ONIX 3.0 – 7, 10, 78 etc – have not been updated. They have been included in their ‘frozen’ form in downloadable codelist files until this Issue 36. The ONIX International Steering Committee has agreed that these frozen codelists will be removed in early 2017.
    [Show full text]
  • ONIX for Books Codelists Issue 47
    ONIX for Books Codelists Issue 47 31 October 2019 DOI: 10.4400/akjh Go to latest Issue All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All ONIX users should note that this issue of the ONIX codelists does not include support for codelists used only with ONIX version 2.1. ONIX 2.1 remains fully usable, using Issue 36 of the codelists or earlier, and Issue 36 continues to be available via the archive section of the EDItEUR website (https://www.editeur.org/15/Archived-Previous-Releases). These codelists are also available within a multilingual online browser at https://ns.editeur.org/onix. Codelists are revised quarterly. Layout of codelists This document contains ONIX for Books codelists Issue 46, intended primarily for use with ONIX 3.0. The codelists are arranged in a single table for reference and printing. They may also be used as controlled vocabularies, independent of ONIX. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists used only with earlier releases have been removed. For details of which code list to use with which data element in each version of ONIX, please consult the main Specification for the appropriate release. Occasionally, a handful of codes within a particular list are defined as either deprecated, or not valid for use in a particular version of ONIX or with a particular data element.
    [Show full text]
  • DVD Frequently Asked Questions (And Answers)
    DVD Frequently Asked Questions (and Answers) This is the November 11, 2004 revision of the official Internet DVD FAQ for the rec.video.dvd Usenet newsgroups. (See below for what's new.) Send corrections, additions, and new questions to Jim Taylor <[email protected]>. This FAQ is updated at least once a month. If you are looking at a version more than a month old, it's an out-of-date copy. The most current version is at DVD Demystified. Contents • [0] Where can I get the DVD FAQ? • [0.1] Has the DVD FAQ been translated into other languages? • [0.2] This FAQ is too long and technical. Is there a simpler version? • [0.3] Is this FAQ any good? Who wrote it? How do I know it's accurate? • [0.4] How big is this thing? • [1] General DVD • [1.1] What is DVD? • [1.2] What are the features of DVD-Video? • [1.3] What's the quality of DVD-Video? • [1.4] What are the disadvantages of DVD? • [1.5] What DVD players and drives are available? • [1.5.1] Which player should I buy? • [1.6] What DVD titles are available? • [1.6.1] Where can I read reviews of DVDs? • [1.6.2] How do I find out when a movie or TV show will be available on DVD? • [1.6.3] Why isn't my favorite movie on DVD? • [1.6.4] How can I find DVDs with specific features or characteristics? • [1.6.5] Why do some rental stores and retailers not carry widescreen DVDs? • [1.7] How much do players and drives cost? • [1.8] How much do discs cost? • [1.9] How is DVD doing? Where can I get statistics? • [1.10] What are "regional codes," "country codes," or "zone locks"? • [1.11] What are the copy protection
    [Show full text]
  • Table of Contents Part I Introduction 4 Part II Find Answers in the Manual 5 Part III Getting Started 8 1 Getting Started
    Contents I Table of Contents Part I Introduction 4 Part II Find answers in the manual 5 Part III Getting started 8 1 Getting Started................................................................................................................................... - Your first 10 clicks 9 2 Getting Started................................................................................................................................... - Adding your first movie 11 3 Getting Started................................................................................................................................... - Quick guide 13 4 Getting Started................................................................................................................................... - Useful and powerful tips 15 Part IV Buying Movie Collector 18 Part V Support 21 Part VI Common Tasks 22 1 Adding Movies................................................................................................................................... Automatically 23 2 Editing movies................................................................................................................................... 25 3 Browsing................................................................................................................................... your collection 28 4 Finding a................................................................................................................................... movie in your collection 31 5 Printing ..................................................................................................................................
    [Show full text]