DOCSLIB.ORG

User's Manual for Spatial Data Product Specification Description

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
User's Manual for Spatial Data Product Specification Description Technical Report of the Geographical Survey Institute A1-No.264 User's Manual for Spatial Data Product Specification Description May 2002 Preface to English Edition In Japan, the Geographical Survey Institute and private companies have jointly created and updated the Japanese Standards for Geographic Information (JSGI) in accordance with several standards in the draft stage to arrange implementation tests and utilization manuals since before the international standard based on ISO/TC211 si issued. User's Manual for Spatial Data Product Specification Description is created to spread the standards based on ISO/TC211 in Japan. This manual assumes that national organizations, local public organizations, and private companies use the ISO standards, and has the purpose that is different from that of ISO19131 Data Product Specifications. However, in order to help consider creating the standard for data product specifications or use the ISO standards in countries, this English version is created. The original of this manual is created from JSGI that is created in Japanese based on the draft standard created in English. Therefore, this English version is created through the processes of translation from English to Japanese, and from Japanese to English. Because of the time limit, the retranslated English technical terms are not examined carefully, and note that some terms are not correct. XML tag names are described alphabetically, but many of them are based on the Japanese alphabet (Roman character) notation instead of English because it is assumed that they are used in Japan. These tag names are not forcibly translated into English but "Note(E)" is appended to them. Japanese own terms are also supplemented with "Note(E)," but some of unimportant terms may remain in Japanese or have no supplementary explanation. Appendix B gives an overview of Japan Metadata Profile, UML and XML, and is included in Contents, but is omitted. Because JSGI is not based on the latest ISO/TC211 draft standard and Japanese-own revisions are made in JSGI, care is needed to use JSGI. For example, JSGI-Metadata remains based on the ISO19115 First Draft because the Japan Metadata Profile (JMP) in which Japanese own revisions are made based on the First Draft has already been used for clearinghouses in Japan. Other JSGI standards are about half a year to one year later than the latest ISO draft standard. In future, JSGI and utilization manuals will also be updated as standardization by ISO makes progress. The English version of some reports on and materials related to the results of implementation tests will also be created and released. The Secretariat of Joint Research Project Geographical Survey Institute May 2002 ii Table of Contents Chapter 1 Overview ........................................................................................................................ 1 1. Product Specification Description..................................................................................... 3 1.1 Requirement Specification and Procureme nt Specification ........................................................ 3 1.2 Product Specification and Production Specification ............................................................... 3 1.3 Product Specification description .......................................................................................... 5 3. Purpose of This Manual.................................................................................................... 6 4. Scope of This Manual ....................................................................................................... 8 5. Using This Manual ........................................................................................................... 8 Chapter 2 Geographic Information Standard..................................................................................... 9 1. Purpose of Geographic Information Standard.................................................................. 9 2. Overview of Geographic Information Standard.............................................................. 11 2.1 Data Structure ............................................................................................................... 12 2.2 Quality......................................................................................................................... 12 2.3 Metadata ...................................................................................................................... 13 2.4 Encoding...................................................................................................................... 13 2.5 Spatial Reference System................................................................................................ 14 2.6 Feature Catalogue .......................................................................................................... 15 Chapter 3 Contents of Product specification description.................................................................... 16 1. Overview of Spatial Data................................................................................................ 16 1.1 Purpose of Spatial Data................................................................................................... 16 1.2 Geographic Scope of Data ............................................................................................... 17 1.3 Temporal Scope............................................................................................................. 17 1.4 References (Spatial Reference System, Coordinate System, Temporal Reference, Weights and Measures) ............................................................................................................................ 17 1.5 Temporal Reference Sys tem............................................................................................ 18 2. Contents of Data to be Acquired ..................................................................................... 18 2.1 Feature Definition.......................................................................................................... 19 2.1.1 Overview of feature definition ................................................................................... 20 2.1.2 Feature definition technique ...................................................................................... 20 2.1.2.1 Feature definition ............................................................................................... 20 2.1.2.2 Spatial attribute .................................................................................................. 21 2.1.2.3 Temporal attribute .............................................................................................. 21 2.1.2.4 Thematic attribute and thematic diagram................................................................ 22 2.1.2.5 Feature relationship ............................................................................................ 22 2.2 Data Structure and Application Schema............................................................................. 24 i 2.2.1 Data structure.......................................................................................................... 24 2.2.2 Application schema ................................................................................................. 25 2.2.3 UML class diagram................................................................................................. 28 2.3 Quality......................................................................................................................... 29 2.3.1 Quality (concept and necessity).................................................................................. 29 2.3.1.1 Concept............................................................................................................ 29 2.3.1.2 Necessity.......................................................................................................... 30 2.3.2 Quality contents ...................................................................................................... 30 2.3.2.1 Completeness .................................................................................................... 32 2.3.2.2 Logic consistency............................................................................................... 33 2.3.2.3 Positional accuracy............................................................................................. 33 2.3.2.4 Temporal accuracy............................................................................................. 34 2.3.2.5 Thematic accuracy............................................................................................. 35 2.4 Requirement Definition Table .......................................................................................... 35 2.4.1 Example of requirement definition ............................................................................. 35 2.4.2 Contents of requirement definition.............................................................................. 36 2.5 Example of Describing Application Schema for Feature....................................................... 38 2.6 Required Quality ........................................................................................................... 39 2.6.1 Describing quality requirement definition .................................................................... 39 2.6.2 Analyzing required quality.......................................................................................
Load more

Recommended publications
  • Albuquerque Citizen, 07-30-1909 Hughes & Mccreight
    University of New Mexico UNM Digital Repository Albuquerque Citizen, 1891-1906 New Mexico Historical Newspapers 7-30-1909 Albuquerque Citizen, 07-30-1909 Hughes & McCreight Follow this and additional works at: https://digitalrepository.unm.edu/abq_citizen_news Recommended Citation Hughes & McCreight. "Albuquerque Citizen, 07-30-1909." (1909). https://digitalrepository.unm.edu/abq_citizen_news/3141 This Newspaper is brought to you for free and open access by the New Mexico Historical Newspapers at UNM Digital Repository. It has been accepted for inclusion in Albuquerque Citizen, 1891-1906 by an authorized administrator of UNM Digital Repository. For more information, please contact [email protected]. TRAIN ARRIVALS WEATHER FORECAST No. 1- -7-4. Mo 4- - V No. 7- - io.5S" LB1 Denver, Colo., July 30. Parllf ctositi No. S 6.40 & v. uqueeque A i:o Iccil showers tonigt.l Satartfiy. ir No. 1 1. 4 5 p ''. Citizen 9 ' VvE. GET THE NEWS FIRST VOLUME LU. ALBUQUERQUE. NEW MEXICO. FIU DAY. JULY :30. 1909. NUMBEK 1G9 NECESSITIES ARE REDUCED They Insisted on Forcing Consuclo and EVEI YN MAY M SUE! PROMINENT PRELATESTO Revision Downward Duke to Make Up QUICKLY ENDED FOR SEPARATION BE AT SANTA FE LUXURIES TAXED HIGHER BY TROOPS FROMJjARRY IN AUGUSI evee-i. V Reported Complete Tariff Bill Mob at Barcelona Hemmed His Wife Shocked at Revela- Cardinal Gibbons and Atgr. Conferees , e s i In bv Cavalry "".. and ' tions Made During the Falconlo Will Take Part to Congress Today After Working I i 1 XT' Surrendered A- Present Insanity In Unusual Cere- fter a Hard Over the Various Schedules for the Tflal.
    [Show full text]
  • Uwsgi Documentation Release 2.0
    uWSGI Documentation Release 2.0 uWSGI Jun 17, 2020 Contents 1 Included components (updated to latest stable release)3 2 Quickstarts 5 3 Table of Contents 33 4 Tutorials 303 5 Articles 343 6 uWSGI Subsystems 375 7 Scaling with uWSGI 457 8 Securing uWSGI 485 9 Keeping an eye on your apps 503 10 Async and loop engines 511 11 Web Server support 525 12 Language support 541 13 Other plugins 629 14 Broken/deprecated features 633 15 Release Notes 643 16 Contact 741 17 Commercial support 743 18 Donate 745 19 Sponsors 747 20 Indices and tables 749 i Python Module Index 751 Index 753 ii uWSGI Documentation, Release 2.0 The uWSGI project aims at developing a full stack for building hosting services. Application servers (for various programming languages and protocols), proxies, process managers and monitors are all implemented using a common api and a common configuration style. Thanks to its pluggable architecture it can be extended to support more platforms and languages. Currently, you can write plugins in C, C++ and Objective-C. The “WSGI” part in the name is a tribute to the namesake Python standard, as it has been the first developed plugin for the project. Versatility, performance, low-resource usage and reliability are the strengths of the project (and the only rules fol- lowed). Contents 1 uWSGI Documentation, Release 2.0 2 Contents CHAPTER 1 Included components (updated to latest stable release) The Core (implements configuration, processes management, sockets creation, monitoring, logging, shared memory areas, ipc, cluster membership and the uWSGI Subscription Server) Request plugins (implement application server interfaces for various languages and platforms: WSGI, PSGI, Rack, Lua WSAPI, CGI, PHP, Go .
    [Show full text]
  • Gynecology & Obstetrics
    ISSN 0100-7203 RBGO eISSN 1806-9339 Gynecology & Obstetrics Revista Brasileira de Ginecologia e Obstetrícia Number 6 • Volume 43 • Pages 425–501 • June 2021 ISSN 0100-7203 RBGO Gynecology and Obstetrics Revista Brasileira de Ginecologia e Obstetrícia Editor in Chief Marcos Felipe Silva de Sá Universidade de São Paulo, Ribeirão Preto, SP, Brazil Former Editors Jean Claude Nahoum Sérgio Pereira da Cunha Rio de Janeiro, RJ (1979–1989) Ribeirão Preto, SP (1994–1997) Clarice do Amaral Ferreira Jurandyr Moreira de Andrade Rio de Janeiro, RJ (1989–1994) Ribeirão Preto, SP, Brazil (1997–2015) Associated Editors Agnaldo Lopes da Silva Filho Fabrício da Silva Costa Instituto Fernandes Figueira, Universidade Federal de Minas Gerais, Monash University, Melbourne, Rio de Janeiro, RJ, Brazil Belo Horizonte, MG, Brazil Victoria, Australia Maria Celeste Osório Wender Alessandra Cristina Marcolin Fernanda Garanhani de Castro Surita Universidade Federal do Rio Grande do Sul, Universidade de São Paulo, Universidade Estadual de Campinas, Porto Alegre, RS, Brazil Ribeirão Preto, SP, Brazil Campinas, SP, Brazil Maria Laura Costa do Nascimento Ana Katherine da Silveira Gonçalves Fernando Marcos dos Reis Universidade Estadual de Campinas, Universidade Federal do Rio Grande do Universidade Federal de Minas Gerais, Campinas, SP, Brazil Norte, Natal, RN, Brazil Belo Horizonte, MG, Brazil Melânia Maria Ramos de Amorim Andréa da Rocha Tristão Gabriel Costa Osanan Universidade Federal de Campina Grande, Campina Grande, PB, Brazil Universidade Estadual Paulista Universidade
    [Show full text]
  • Julien Danjou
    The Hacker’s Guide to Scaling Python Julien Danjou Julien Danjou <[email protected]> Copyright © 2016-2017 Julien Danjou Revision History Revision 1.0 May 2017 JD First Edition. About this Book Version 1.0 released in 2017. When I released The Hacker’s Guide to Python in 2014, I had no idea that I would be writing a new book so soon. Having worked on OpenStack for a few more years, I saw how it is easy to struggle with other aspects of Python, even after being on board for a while. Nowadays, even if computers are super-fast, no server is fast enough to handle millions of request per second, which is a typical workload we want to use them for. Back in the day, when your application was slow, you just had to optimize it or upgrade your hardware – whichever was cheaper. However, in a world where you may already have done both, you need to be able to scale your application horizontally, i.e., you have to make it run on multiple computers in parallel. That is usually the start of a long journey, filled with concurrency problems and disaster scenarios. Developers often dismiss Python when they want to write performance enhancing, and distributed applications. They tend to consider the language to be slow and not suited to that task. Sure, Python is not Erlang, but there’s also no need to ditch it for Go because of everyone saying it is faster. I would like to make you aware, dear reader, that a language is never slow.
    [Show full text]
  • A Thin Web Application Framework Based on Server-Side Javascript
    Diploma Thesis A Thin Web Application Framework based on Server-side JavaScript Jan Varwig July 20th, 2009 Supervisor: Prof. Dr. Clemens Cap Lehrstuhl fur¨ Informations- und Kommunikationsdienste Fakult¨at fur¨ Informatik und Elektrotechnik Universit¨at Rostock 2nd Examiner: Prof. Dr. Dietmar Jannach Lehrstuhl fur¨ Dienstleistungsinformatik Fakult¨at fur¨ Informatik Technische Universit¨at Dortmund Contents 1 Motivation 1 1.1 A Short History of the Web . 1 1.2 Current Problems in Web Development . 3 1.2.1 Heterogenous Languages . 4 1.2.2 Redundancy in Code . 5 1.2.3 Glue Code . 5 1.2.4 Object-Relational Mapping . 6 1.3 Use Cases . 7 1.3.1 Model Validation . 7 1.3.2 Data Transformation . 8 1.3.3 Exposure of Objects Through APIs . 9 1.3.4 Dynamic Object Properties . 9 1.3.5 Storage and Retrieval of Compound Objects . 10 1.4 Goals . 11 1.4.1 A Single Language . 11 1.4.2 Code Reuse between Server and Client . 11 1.4.3 Elimination of Glue Code . 11 1.4.4 Tight Integration of a JSON Database . 12 1.5 Existing Single-Language Frameworks . 12 1.6 Key Ideas . 13 1.6.1 A Design Based on JavaScript . 13 1.6.2 Key Ideas Put to Work . 15 2 Background 19 2.1 Existing Approaches to Web Frameworks . 19 2.1.1 Request-/Action-Based MVC . 19 2.1.2 Component Based . 20 2.1.3 Free Form . 21 2.2 Web-Applications vs. Web-Services . 21 2.3 JavaScript............................ 22 2.4 Changes in Recent Years .
    [Show full text]
  • Polyglot Programming DC 2015 Brock Wilcox [email protected]
    HTTP Adapers Polyglot Programming DC 2015 Brock Wilcox [email protected] Web Applications Request → Response Let's go BACK.... to 1993 CGI Common Gateway Interface Request → Response ... Unix! Request → Response ENV + STDIN → STDOUT ENV == Headers (params) STDIN == POST STDOUT == Headers + Body #!/bin/sh # A lovely cgi application echo "Content-type: text/html" echo echo "Hello, world! Query:" echo $QUERY_STRING Parse the query string if you want cgi programs rise from ash then burn again upon each request Long running applications Kinda long-running mod_perl mod_php mod_python ... Kinda long-running FastCGI Just run your own HTTPD Also annoying Same webserver language, but unlink from webserver. Web App Frameworks func app(request) → response response = [ status, headers, body ] Common Lisp - Clack Clojure - Ring Elixir - Plug Haskell - Hack2 Java - Servlets? Javascript - JSGI Lua - WSAPI Perl - PSGI Perl6 - P6SGI Python - WSGI Ruby - Rack Scala - SSGI * - uWSGI # Python WSGI def application(environ, start_response): start_response('200 OK', [('Content-Type', 'text/plain')]) yield 'Hello, world!' # Ruby Rack app = lambda do |env| [200, {"Content-Type" => "text/plain"}, ["Hello, world!"]] end # Perl PSGI my $app = sub { my ($env) = @_; return [200, ['Content-Type' => 'text/plain'], ["Hello, world!"]]; } // Javascript JSGI require("jsgi-node").start(function(request){ return { status:200, headers:{}, body:["Hello, world!"] }; }); # Elixir Plug defmodule MyPlug do import Plug.Conn def init(options) do # initialize options options
    [Show full text]
  • Javascript Web Applications
    www.allitebooks.com www.allitebooks.com JavaScript Web Applications www.allitebooks.com www.allitebooks.com JavaScript Web Applications Alex MacCaw Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo www.allitebooks.com JavaScript Web Applications by Alex MacCaw Copyright © 2011 Alex MacCaw. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mary Treseler Indexer: Fred Brown Production Editor: Holly Bauer Cover Designer: Karen Montgomery Copyeditor: Marlowe Shaeffer Interior Designer: David Futato Proofreader: Stacie Arellano Illustrator: Robert Romano Printing History: August 2011: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. JavaScript Web Applications, the image of a Long-eared owl, and related trade dress are trademarks of O’Reilly Media, Inc. 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 O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein. ISBN: 978-1-449-30351-8 [LSI] 1313086859 www.allitebooks.com Table of Contents Preface .
    [Show full text]
  • Latest Stable Release)3
    uWSGI Documentation Release 2.0 uWSGI Jun 17, 2020 Contents 1 Included components (updated to latest stable release)3 2 Quickstarts 5 3 Table of Contents 33 4 Tutorials 303 5 Articles 343 6 uWSGI Subsystems 375 7 Scaling with uWSGI 457 8 Securing uWSGI 485 9 Keeping an eye on your apps 503 10 Async and loop engines 511 11 Web Server support 525 12 Language support 541 13 Other plugins 629 14 Broken/deprecated features 633 15 Release Notes 643 16 Contact 741 17 Commercial support 743 18 Donate 745 19 Sponsors 747 20 Indices and tables 749 i Python Module Index 751 Index 753 ii uWSGI Documentation, Release 2.0 The uWSGI project aims at developing a full stack for building hosting services. Application servers (for various programming languages and protocols), proxies, process managers and monitors are all implemented using a common api and a common configuration style. Thanks to its pluggable architecture it can be extended to support more platforms and languages. Currently, you can write plugins in C, C++ and Objective-C. The “WSGI” part in the name is a tribute to the namesake Python standard, as it has been the first developed plugin for the project. Versatility, performance, low-resource usage and reliability are the strengths of the project (and the only rules fol- lowed). Contents 1 uWSGI Documentation, Release 2.0 2 Contents CHAPTER 1 Included components (updated to latest stable release) The Core (implements configuration, processes management, sockets creation, monitoring, logging, shared memory areas, ipc, cluster membership and the uWSGI Subscription Server) Request plugins (implement application server interfaces for various languages and platforms: WSGI, PSGI, Rack, Lua WSAPI, CGI, PHP, Go .
    [Show full text]
  • Albuquerque Citizen, 09-22-1908 Hughes & Mccreight
    University of New Mexico UNM Digital Repository Albuquerque Citizen, 1891-1906 New Mexico Historical Newspapers 9-22-1908 Albuquerque Citizen, 09-22-1908 Hughes & McCreight Follow this and additional works at: https://digitalrepository.unm.edu/abq_citizen_news Recommended Citation Hughes & McCreight. "Albuquerque Citizen, 09-22-1908." (1908). https://digitalrepository.unm.edu/abq_citizen_news/2874 This Newspaper is brought to you for free and open access by the New Mexico Historical Newspapers at UNM Digital Repository. It has been accepted for inclusion in Albuquerque Citizen, 1891-1906 by an authorized administrator of UNM Digital Repository. For more information, please contact [email protected]. TRAIN ARRIVALS No. i P- - m. No 4 5. 50 p. m. No. p. m 710.55 22-- Citj Mover. Colo., !eot. F.i, nlDht No. 8 6 40 p. m. Albuquerque MJ7Walii. No. 9 1 1.45 p. m. "WE GET THE IXEWS FIRST" and Wednesday. VOLUME 23. ALBUQUERQUE. -- NEW MEXICO. TUESDAY, SEPTEMHEK 22. 108. 228 i . mendation was therein made that tacked snd killed Maloney. Mi'dte l cel'tion of duty die tatc to him. the j , cjti way T firm t- nifi nnminniT PROPERTY OWNERS WILL Central avenue be paved from the Follia was in his whin he tried I wllunu whole coneern Is for - fir. FNO t U I Fa street, and to escape and he crushed skull IIii I I ftK Santa tracks to Fifth her IlLInrrlL welfare of the ueuuju aiiu wno . ii i mi nuiiu i the inuiion as adopted by the city with the same bar. He ul.so ftruck proved ln a lifetime of diftlcu.t iiluiuliii council, contemplated that Central at Mi- - Robinson, breaking her aim useful public service his extraordlnuiya.
    [Show full text]
  • Javascript and Mootools Classes, and the Mootools Class Internals
    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® THE EXPERT’S VOICE® IN WEB DEVELOPMENT Companion eBook Available Written for Pro JavaScript with MooTools MooTools 1.3 Pro JavaScript with MooTools is unlike any other JavaScript book on the mar- Pro JavaScript JavaScript ket today. While similar books focus on either JavaScript as a language of the browser or how to use JavaScript frameworks, Pro JavaScript with MooTools fills the gap between these topics and moves beyond—exploring the advanced features of JavaScript and how the MooTools framework uses these features to further improve the language itself. The book itself takes a unique three-pronged approach. It first walks you Pro Mark Joseph Obcena through the advanced features of JavaScript and the MooTools framework, including native augmentation and type creation, a comprehensive discussion of JavaScript functions, object-oriented programming with native JavaScript and MooTools Classes, and the MooTools Class internals. You’ll then learn all about JavaScript in the DOM: the Elements Class and its internals, the MooTools Event system, Selector engines and MooTools Slick, Ajax and the Request Object, and Animation and the Fx classes. JavaScript The final section really sets the book apart from all others, as it discusses with JavaScript outside the browser. You’ll take an in-depth look at CommonJS and MooTools, using MooTools outside the browser using Meso, and creating CommonJS web applications via the MooTools Deck framework. MooTools with THE APRESS ROADMAP MooTools MooTools Pro JavaScript
    [Show full text]
  • Javascript Web Applications.Pdf
    JavaScript Web Applications JavaScript Web Applications Alex MacCaw Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo JavaScript Web Applications by Alex MacCaw Copyright © 2011 Alex MacCaw. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mary Treseler Indexer: Fred Brown Production Editor: Holly Bauer Cover Designer: Karen Montgomery Copyeditor: Marlowe Shaeffer Interior Designer: David Futato Proofreader: Stacie Arellano Illustrator: Robert Romano Printing History: August 2011: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. JavaScript Web Applications, the image of a Long-eared owl, and related trade dress are trademarks of O’Reilly Media, Inc. 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 O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors
    [Show full text]
  • Learning Node Shelley Powers
    www.allitebooks.com www.allitebooks.com Learning Node Shelley Powers Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo www.allitebooks.com Learning Node by Shelley Powers Copyright © 2012 Shelley Powers. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Editor: Simon St. Laurent Indexer: Aaron Hazelton, BIM Publishing Services Production Editor: Rachel Steely Cover Designer: Karen Montgomery Copyeditor: Rachel Monaghan Interior Designer: David Futato Proofreader: Kiel Van Horn Illustrators: Robert Romano and Rebecca Demarest September 2012: First Edition. Revision History for the First Edition: 2012-08-24 First release See http://oreilly.com/catalog/errata.csp?isbn=9781449323073 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Learning Node, the image of a hamster rat, and related trade dress are trademarks of O’Reilly Media, Inc. 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 O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein.
    [Show full text]