ZedAI Attribution

From zedwiki

Jump to: navigation, search


 1. The act of attributing or ascribing, as a quality,
 character, or function, to a thing or person, an effect to
 a cause. [1913 Webster]

In our case, a matter of getting a way to handle print (not metadata) attribution in for example book#frontmatter.

Note again - head/meta will address formal bibliographic attribution: this topic concerns the capturing of attributions as it appears printed in books, periodicals, etc.

Contents

What we have

The current attribution module was a quick placeholder hack, containing the elements

  • creator
  • contributor (to be extended with @role)
  • publisher
  • date
  • copyright

What we need

A module for attribution which allows

  • capturing print attributions re the work being republished (its title, its halftitle, etc)
  • capturing print attributions re people or agencies involved in the production of the work (author, editor, illustrator, etc)
  • a module that includes a small set of relevant base elements, that can be extended using @role and/or RDF/a. We want to avoid element-bloat while still having dedicated elements for the most common occurences.
  • a mechanism (for processors to) to handle overlaps and duplication (see below)

Problem: handling overlaps between metadata and title pages

There is a direct overlap between

  • head metadata, which contains "formal"/bibliographic attributions
  • cover and frontmatter attributions, which may sometimes be identical to head meta, but often is not because of halftitles etc

Proposed solution: Recognize that there are two goals in these two areas of markup:

  • For head metadata, the goal is to accurately and fully represent the bibliographical data for the underlying resource
  • For frontmatter, the goal is to accurately and fully represent the content of the underlying resource (e.g., the printed page)

Considered in this way, these two goals do not, in fact overlap, even though the "content" of the two may be similar. In designing frontmatter markup, we should focus on the kinds of structures that appear on title pages, etc. without concern about bibliography in the more formal sense.

Problem: duplication of data in frontmatter

If we stay with the aim to allow a full undiscriminating capture of cover and frontmatter for those that need it, we observe

  • That some items (such as title) are likely to be repeated in the resulting XML, even when excluding head meta - full title page, repeated full title page, halftitle page, etc
  • That many republishers will not be interested in this, and may (for reasons of economy and general sanity) choose to avoid duplications in the first place by simply not including them in the XML. But at the moment the grammar does not enforce that.

Proposed solution: Allow duplication to happen freely, but establish a way to provide sufficient data for processing agents to filter out redundant data. For example, a titlepage element could be repeatable, with the role attribute used to distinguish between "main" and "half" title pages, etc.

This allows processing agents to answer the question: if a certain output medium should only contain the title once in the actual content, which one should be used? (e.g., actually remove the halftitle page and the duplicated fulltitle page from frontmatter while converting a ZedAI document to, say, a grammar intended for inclusion in a DTB distribution fileset).

Attribution in DocBook5

Three elements, where one is anonymous+extension:

  • author
  • editor
  • othercredit, with a class enumeration of:
    • “copyeditor”
    • “graphicdesigner”
    • “productioneditor”
    • “technicaleditor”
    • “translator”
    • “other”

DocBook thus does not support markup of constructs such as publisher, etc., which makes it less useful to our needs here.

Attribution in TEI 1.3.0

TEI P5 includes attribution data in the header, similar to our metadata. It also includes markup for bibliographical references. While these may provide some elements that would prove useful, the most appropriate to our needs is the markup for the titlePage element. This element includes a type attribute that is used to distinguish between full, half, series, etc. titles. It can include:

  • docTitle (the title of a document, including all its constituents) This can be just text, or may contain one or more:
    • titlePart (a subsection or division of the title of a work)
      • @type defines the role of the part. Open-ended, with predefined values of "main", "sub", "alt", "short", "desc"
  • byline (the primary statement of responsibility given for a work) This can include:
    • docAuthor (the name of the author of the document) This can also be a direct descendant of titlePage
  • docEdition (an edition statement)
  • docImprint (the imprint statement: place and date of publication, publisher name) This can be just text, or may include:
    • publisher (the name of the organization responsible for the publication or distribution of a bibliographic item) There is also a generic <code>name element that can be used in this context.
    • pubPlace (the name of the place where a bibliographic item was published)
    • docDate (the date of a document) There is also a generic date element that can be used in this context.
  • argument (a formal list or prose description of the topics addressed by a subdivision of a text(
  • imprimatur (a formal statement authorizing the publication of a work)
  • epigraph (a quotation, anonymous or attributed, appearing at the start of a section or chapter, or on a title page)

The main thing missing here is a generic "contributor" element: TEI only has this within its bibliographical markup (the editor element), not title page markup.

Proposal #1

A subset of the TEI constructs should be sufficient for the book profile. At maximum, we might use:

titlepage 
Container for a title page of any kind. @role used to distinguish various flavors
doctitle 
Container for title text or multiple titlepart elements
titlepart 
A distinct piece of a title (e.g., main title, subtitle, series title, etc.) @role distinguishes types
byline 
Container for a prose attribution (e.g., "By the late, great Rufus T. Firefly").
creator 
An author. Can be contained inside a byline
contributor 
A contributor to the work, such as an editor, translator, etc. @role distinguishes types
edition 
The edition statement in whatever form it appears on the title page
imprint 
Container for publisher information (can include publisher, place, date)
publisher 
The name of the publisher
place 
Location of publisher
date 
Date of publication

Possible simplifications:

  1. Just use title instead of doctitle and titlepart. The different parts of the title could be marked up with span and @role.
  2. Skip byline and just markup using p, wrapping the names with creator, etc.
  3. Merge creator and contributor and rely entirely on @role to distinguish
  4. Use p/@role identify the edition statement (rather than a dedicated element)
  5. Skip imprint and just use the publisher, place, and date within a plain text container such as p
  6. Skip titlePage, and use section@role

Samples proposal #1

The following are some quick-hack samples made using real books of various types. These use the "maximum" element set outlined above. Namespaces and CURIE prefixes are omitted for reasons of simplicity and laziness.

Here are the half and full title pages from an O'Reilly book, showing how we could use a repeatable titlepage element with half/full titles (and possibly series titles, etc.) distinguished by @role values. 

    <titlepage role="halftitle">
        <doctitle>
            <titlepart role="main">JAVA IN A NUTSHELL</titlepart>
            <titlepart role="sub">A Desktop Quick Reference</titlepart>
        </doctitle>
    </titlepage>
    <titlepage role="fulltitle">
        <doctitle>
            <titlepart role="main">JAVA IN A NUTSHELL</titlepart>
            <titlepart role="sub">A Desktop Quick Reference</titlepart>
        </doctitle>
        <edition>Fourth Edition</edition>
        <creator>David Flanagan</creator>
        <imprint>
            <publisher>O'REILLY</publisher>
            <place>Beijing</place>
            <place>Cambridge</place>
            <place>Farnham</place>
            <place>Köln</place>
            <place>Paris</place>
            <place>Sebastopol</place>
            <place>Taipei</place>
            <place>Tokyo</place>
        </imprint>
    </titlepage>

In this sample, note the use of byline (to contain the text linking authors, etc.) and repeatable title, to cover series title. 

    <titlepage>
        <doctitle>Agile Software Development with Scrum</doctitle>
        <byline>
            <creator>Ken Schwaber</creator> and <creator>Mike Beedle</creator>
        </byline>
        <doctitle role="series">SERIES IN AGILE SOFTWARE DEVELOPMENT</doctitle>
        <byline><contributor role="editor">Robert C. Martin</contributor>, Series Editor</byline>
        <imprint>
            <publisher>Prentice Hall</publisher>
            <place>Upper Saddle River, New Jersey 07458</place>
        </imprint>
    </titlepage>

And here are just a bunch of other, similar samples: 

    <titlepage>
        <creator>William Shakespeare</creator>
        <doctitle>
            <titlepart role="main">The Tragedy of OTHELLO</titlepart>
            <titlepart role="sub">The Moor of Venice</titlepart>
        </doctitle>
        <byline>Edited by <contributor role="editor">Alvin Kernan</contributor></byline>
        <doctitle role="series">The Signet Classic Shakespeare</doctitle>
        <byline>GENERAL EDITOR:  <contributor role="editor">SYLVAN BARNET</contributor></byline>
        <imprint>
            PUBLISHED BY
            <publisher>THE NEW AMERICAN LIBRARY</publisher>,
            <place>NEW YORK</place> AND <place>TORONTO</place>
            <publisher>THE NEW ENGLISH LIBRARY LIMITED</publisher>,
            <place>LONDON</place>
        </imprint>
    </titlepage>

    <titlepage>
        <doctitle>
            <titlepart role="series">Prentice Hall World Explorer</titlepart>
            <titlepart role="main">THE ANCIENT WORLD</titlepart>
        </doctitle>            
        <imprint>
            <publisher>PRENTICE HALL</publisher>
            <place>Needham, Massachusetts</place>
            <place>Upper Saddle River, New Jersey</place>
        </imprint>
    </titlepage>

    <titlepage>
        <doctitle>
            <titlepart role="main">The Mythical Man-Month</titlepart>
            <titlepart role="sub">Essays on Software Engineering</titlepart>
        </doctitle>
        <edition>Anniversary Edition</edition>
        <byline>
            <creator>Frederick P. Brooks, Jr.</creator>
            <place>University of North Carolina at Chapel Hill</place>
        </byline>
        <imprint>
            <publisher>ADDISON-WESLEY</publisher>
            <place>Boston</place>
            <place>San Francisco</place>
            <place>New York</place>
            <place>Toronto</place>
            <place>Montreal</place>
            <place>London</place>
            <place>Munich</place>
            <place>Paris</place>
            <place>Madrid</place>
            <place>Capetown</place>
            <place>Sydney</place>
            <place>Tokyo</place>
            <place>Singapore</place>
            <place>Mexico City</place>
        </imprint>
    </titlepage>

    
    <titlepage>
        <doctitle>MC-GRAW HILL SCIENCE</doctitle>
        <edition>MACMILLAN/MCGRAW-HILL EDITION</edition>
        <creator>RICHARD MOYER</creator>
        <creator>LUCY DANIEL</creator>
        <creator>JAY HACKETT</creator>
        <creator>PRENTICE BAPTISTE</creator>
        <creator>PAMELA STRYKER</creator>
        <creator>JOANNE VASQUEZ</creator>
        <creator>NATIONAL GEOGRAPHIC SOCIETY</creator>
        <imprint>
            <publisher>McGraw-Hill School Division</publisher>
            <place>New York</place>
            <place>Farmington</place>
        </imprint>
    </titlepage>

Proposal #2

Target is to create a generic attribution module with members that can be used

  • in book profile frontmatter
  • in book profile cover
  • in compendium-style profiles or publications
  • in periodicals/newsfeeds profile
  • etc

Use the general outline of proposal 1, with the following modifications:

  • use section with @role for titlePage (possibly <section @role="titleInfo") and @role="imprint" (and@role="imprimatur"). The deferring of these constructs to section@role means that we
    • decouple the modules members from a specific context
    • ascertain that we dont interpret CMOS's description of an ideal state as a description of a required state. CMOS doesnt apply 100% empirically
  • accept d:doctitle, and maintain its text|titlePart* contentmodel. Note: we could use the already existing x:title here, but a separate elem could be favorable to disambiguate it from inline use of x:title (in tables, lists)...
  • add the element identifier for use to capture ISBN, ISSN etc codes, -- use RDF/a to capture scheme used? Or dedicated scheme attribute? (Remember: the formal capture of this information is in metadata anyway)
  • accept byline as in #1, also add dateline (as needed in periodicals)
  • accept edition as in #1, use <section role="prevEditions" or similar to wrap previous editions. Use RDF/a on edition to say if its the current or a previous edition?
  • accept publisher, place, creator, contributor as in #1. Make sure vocab contains all necessary CURIEs for contributor; -- use RDF/a or Role for contributor specialization?
  • add dedicated copyright element

Copyright page examples

Here are some sample copyright pages with ad hoc markup inspired by Proposal #2 

<section role="copyright">
    <doctitle>Java in a Nutshell, Fourth Edition</doctitle>
    <byline>by <creator>David Flanagan</creator></byline>
    <copyright>Copyright 
        <date>2002</date>, <date>1999</date>, <date>1997</date>, <date>1996</date> 
        <publisher>O'Reilly &amp; Associates, Inc.</publisher>
        All rights reserved.</copyright>
    <p>Printed in the United States of America</p>

    <p>
        Published by 
        <imprint>
            <publisher>O'Reilly &amp; Associates, Inc.</publisher>, 
            <place>1005 Gravenstein Highway North, Sebastopol, CA 95472.</place>
        </imprint>
    </p>

    <p>O'Reilly &amp; Associates books may be purchased for educational, business, or sales
        promotional use. Online editions are also available for most titles (<a
            href="safari.oreilly.com">safari.oreilly.com</a>). For more information contact our
        corporate/institutional sales department: (800) 998-9938 or corporate@oreilly.com.</p>

    <byline>Editors: <contributor>Paula Ferguson</contributor> and <contributor>Robert
        Eckstein</contributor></byline>
    <byline>Production Editor: <contributor>Matt Hutchinson</contributor></byline>
    <byline>Cover Designer: <contributor>Edie Freedman</contributor></byline>
    <p>Printing history:
        <date>February 1996</date>: <edition>First Edition</edition>.
        <date>May 1997</date>: <edition>Second Edition</edition>.
        <date>November 1999</date>: <edition>Third Edition</edition>.
        <date>March 2002</date>: <edition role="current">Fourth Edition</edition>.
    </p>
    <p>Nutshell Handbook, the Nutshell Handbook logo, ....</p>
    <p>Many of the designations used by manufacturers and sellers ...</p>
    <p>While every precaution has been taken ...</p>
    <p>ISBN:  <identifier>0-596-00283-1</identifier></p>
</section>

<section role="copyright">
    <p>
        Library of Congress Cataloging-inPublication Data
        <line>Agile Software Development with Scrum/Schwaber K., Beedle M. Adff  p. cm.</line>
        <line>Includes bibliographical references index.  ISBN  0-13-067634-9  1.Scrum,</line>
        <line>Software Development.  2.  Agile Software Methods.  I.  Title.</line>
        <line>512'-dc21 2001</line>
        <line>QA814.G27  00-055035  CIP</line>
    </p>
    
    <byline>VP and Editorial Driector, ECS:  <contributor>Marcia J. Horton</contributor></byline>
    <!-- several contributors omitted here -->
    
    <copyright>© <date>2002</date> by <publisher>Prentice Hall</publisher></copyright>
    <imprint>
        <publisher>Prentice-Hall, Inc.</publisher>
        <place>Upper Saddle River, NJ 07458</place>
    </imprint>
    <p>All rights reserved.  No part of this book ...</p>
    
    <p>The author and publisher of this book have used their best efforts ...</p>
    
    <p>Printed in the United States of America</p>
    
    <p>10 9 8 7 6 5</p>
    
    <p>ISBN <identifier>0-13-067634-9</identifier></p>
    
    <imprint><publisher>Pearson Education Ltd.</publisher>, <place>London</place></imprint>
    <imprint><publisher>Pearson Education Australia Pty. Ltd.</publisher>, <place>Sydney</place></imprint>
    <!-- etc., several imprints omitted here -->
 </section>

<section role="copyright">
    <p>Carefully selected, edited, and printed, Signet Classics provide a treasury of the world's
        great writings in handsomely designed volumes.</p>
    
    <copyright>Copyright © <date>1963</date> by <contributor>Alvin Kernan</contributor></copyright>
    <copyright>Copyright © <date>1963</date> by <contributor>Sylvan Barnet<contributor></copyright>
    <p>All rights reserved.</p>
    
    <p>Eighth printing</p>
    
    <p>Signet trademark reg. U.S. Pat. Off. and foreign countries ....</p>
    
    <p>SIGNET CLASSICS are published in the United States by 
        <imprint>
            <publisher>The New American Library, Inc.</publisher>,
            <place>1301 Avenue of the Americas, New York, New York 10019</place>
        </imprint>, in Canada by
        <imprint>
            <publisher>The New American Library of Canada Limited</publisher>,
            <place>295 King Street East, Toronto 2, Ontario</place>
        </imprint>, in the United Kingdom by
        <imprint>
            <publisher>The New English Library Limited</publisher>,
            <place>Barnard's Inn, Holborn, London, E.C. 1, England</place>
        </imprint>
    </p>
    
    <p>Printed in the United States of America</p>
</section>

Proposal #3

Creates a set of generic elements. This differentiates the elements from metadata (both head and rdf/a). The elements are usable in all inline contexts (not restricted to cover/frontmatter). The elements also have direct usability in for example braille and speech production, because of the specific rendering behaviors associated with them (contract/dont contract) etc.

elements

  • x:title
  • titlepart
  • date
  • name
  • place
  • identifier

roles

  • titlepage
  • halftitlepage
  • imprint
  • imprimatur
  • copyright (statement)
  • copyrightPage
  • publisher
  • roles primarily for different types of individual contributor roles : creator, editor, translator, illustrator, ??
  • roles primarily for <titlePart>: seriesTitle, mainTitle, subTitle, ??
  • byline
  • dateline
  • edition
  • prevEdition
  • roles primarily for identifiers: isbn, issn, ??

Examples for proposal 3

Here are the same title and copyright page examples done using proposal #3 markup. 

    <section role="halftitlepage">
        <title>
            <titlepart role="maintitle">JAVA IN A NUTSHELL</titlepart>
            <titlepart role="subtitle">A Desktop Quick Reference</titlepart>
        </title>
    </section>
    <section role="titlepage">
        <title>
            <titlepart role="maintitle">JAVA IN A NUTSHELL</titlepart>
            <titlepart role="subtitle">A Desktop Quick Reference</titlepart>
        </title>
        <p role="edition">Fourth Edition</p>
        <name role="creator">David Flanagan</name>
        <p role="imprint">
            <name role="publisher">O'REILLY</name>
            <place>Beijing</place>
            <place>Cambridge</place>
            <place>Farnham</place>
            <place>Köln</place>
            <place>Paris</place>
            <place>Sebastopol</place>
            <place>Taipei</place>
            <place>Tokyo</place>
        </p>
    </section>
    <section role="copyrightpage">
        <title>Java in a Nutshell, Fourth Edition</title>
        <p role="byline">by <name role="creator">David Flanagan</name></p>
        <p role="copyright">Copyright 
            <date>2002</date>, <date>1999</date>, <date>1997</date>, <date>1996</date> 
            <name role="publisher">O'Reilly & Associates, Inc.</name>
            All rights reserved.</p>
        <p>Printed in the United States of America</p>
        
        <p role="imprint">
            Published by 
            <name role="publisher">O'Reilly & Associates, Inc.</name>, 
            <place>1005 Gravenstein Highway North, Sebastopol, CA 95472.</place>
        </p>
        
        <p>O'Reilly & Associates books may be purchased for educational, business, or sales
            promotional use. Online editions are also available for most titles (<a
                href="safari.oreilly.com">safari.oreilly.com</a>). For more information contact our
            corporate/institutional sales department: (800) 998-9938 or corporate@oreilly.com.</p>
        
        <p role="byline">Editors: <name role="editor">Paula Ferguson</name> and <name role="editor">Robert
            Eckstein</name></p>
        <p role="byline">Production Editor: <name role="contributor">Matt Hutchinson</name></p>
        <p role="byline">Cover Designer: <name role="contributor">Edie Freedman</name></p>
        <p>Printing history:
            <date>February 1996</date>: <span role="edition">First Edition</span>.
            <date>May 1997</date>: <span role="edition">Second Edition</span>.
            <date>November 1999</date>: <span role="edition">Third Edition</span>.
            <date>March 2002</date>: <span role="currentedition">Fourth Edition</span>.
        </p>
        <p>Nutshell Handbook, the Nutshell Handbook logo, ....</p>
        <p>Many of the designations used by manufacturers and sellers ...</p>
        <p>While every precaution has been taken ...</p>
        <p>ISBN:  <identifier role="isbn">0-596-00283-1</identifier></p>
    </section>

    <section role="titlepage">
        <title>Agile Software Development with Scrum</title>
        <byline>
            <creator>Ken Schwaber</creator> and <creator>Mike Beedle</creator>
        </byline>
        <title role="seriestitle">SERIES IN AGILE SOFTWARE DEVELOPMENT</title>
        <byline><name role="editor">Robert C. Martin</name>, Series Editor</byline>
        <p role="imprint">
            <name role="publisher">Prentice Hall</name>
            <place>Upper Saddle River, New Jersey 07458</place>
        </p>
    </section>
    <section role="copyrightpage">
        <p>
            Library of Congress Cataloging-inPublication Data
            <l>Agile Software Development with Scrum/Schwaber K., Beedle M. Adff  p. cm.</l>
            <l>Includes bibliographical references index.  ISBN  0-13-067634-9  1.Scrum,</l>
            <l>Software Development.  2.  Agile Software Methods.  I.  Title.</l>
            <l>512'-dc21 2001</l>
            <l>QA814.G27  00-055035  CIP</l>
        </p>
        
        <p role="byline">VP and Editorial Driector, ECS:  <name role="contributor">Marcia J. Horton</name></p>
        <!-- several contributors omitted here -->
        
        <p role="copyright">© <date>2002</date> by <name role="publisher">Prentice Hall</name></p>
        <p role="imprint">
            <name role="publisher">Prentice-Hall, Inc.</name>
            <place>Upper Saddle River, NJ 07458</place>
        </p>
        <p>All rights reserved.  No part of this book ...</p>
        
        <p>The author and publisher of this book have used their best efforts ...</p>
        
        <p>Printed in the United States of America</p>
        
        <p>10 9 8 7 6 5</p>
        
        <p>ISBN <identifier role="isbn">0-13-067634-9</identifier></p>
        
        <p role="imprint"><name role="publisher">Pearson Education Ltd.</name>, <place>London</place></p>
        <p role="imprint"><name role="publisher">Pearson Education Australia Pty. Ltd.</name>,
            <place>Sydney</place></p>
        <!-- etc., several imprints omitted here -->
    </section>

    <section role="titlepage">
        <name role="creator">William Shakespeare</name>
        <title>
            <titlepart role="maintitle">The Tragedy of OTHELLO</titlepart>
            <titlepart role="subtitle">The Moor of Venice</titlepart>
        </title>
        <l role="byline">Edited by <name role="editor">Alvin Kernan</name></l>
        <title role="seriestitle">The Signet Classic Shakespeare</title>
        <l role="byline">GENERAL EDITOR:  <name role="editor">SYLVAN BARNET</name></l>
        <p role="imprint">
            PUBLISHED BY
            <name role="publisher">THE NEW AMERICAN LIBRARY</name>,
            <place>NEW YORK</place> AND <place>TORONTO</place>
            <name role="publisher">THE NEW ENGLISH LIBRARY LIMITED</name>,
            <place>LONDON</place>
        </p>
    </section>
    <section role="copyrightpage">
        <p>Carefully selected, edited, and printed, Signet Classics provide a treasury of the world's
            great writings in handsomely designed volumes.</p>
        
        <l role="copyright">Copyright © <date>1963</date> by <name role="editor">Alvin Kernan</name></l>
        <l role="copyright">Copyright © <date>1963</date> by <name role="editor">Sylvan Barnet</name></l>
        <l>All rights reserved.</l>
        
        <l>Eighth printing</l>
        
        <l>Signet trademark reg. U.S. Pat. Off. and foreign countries ....</l>
        
        <p role="imprint">SIGNET CLASSICS are published in the United States by 
                <name role="publisher">The New American Library, Inc.</name>,
                <place>1301 Avenue of the Americas, New York, New York 10019</place>
            , in Canada by
            <name role="publisher">The New American Library of Canada Limited</name>,
                <place>295 King Street East, Toronto 2, Ontario</place>
            , in the United Kingdom by
            <name role="publisher">The New English Library Limited</name>,
                <place>Barnard's Inn, Holborn, London, E.C. 1, England</place>
        </p>
        
        <p>Printed in the United States of America</p>
    </section>

    <section role="titlepage">
        <title>
            <titlepart role="seriestitle">Prentice Hall World Explorer</titlepart>
            <titlepart role="maintitle">THE ANCIENT WORLD</titlepart>
        </title>
        <p role="imprint">
          <name role="publisher">PRENTICE HALL</name>
          <place>Needham, Massachusetts</place>
          <place>Upper Saddle River, New Jersey</place>
        </p>
    </section>

    <section role="titlepage">
        <title>
            <titlepart role="maintitle">The Mythical Man-Month</titlepart>
            <titlepart role="subtitle">Essays on Software Engineering</titlepart>
        </title>
        <p role="edition">Anniversary Edition</p>
        <p role="byline">
            <name role="creator">Frederick P. Brooks, Jr.</name>
            <place>University of North Carolina at Chapel Hill</place>
        </p>
        <p role="imprint">
            <name role="publisher">ADDISON-WESLEY</name>
            <place>Boston</place>
            <place>San Francisco</place>
            <place>New York</place>
            <place>Toronto</place>
            <place>Montreal</place>
            <place>London</place>
            <place>Munich</place>
            <place>Paris</place>
            <place>Madrid</place>
            <place>Capetown</place>
            <place>Sydney</place>
            <place>Tokyo</place>
            <place>Singapore</place>
            <place>Mexico City</place>
        </p>
    </section>

    <section role="titlepage">
        <title>MC-GRAW HILL SCIENCE</title>
        <p role="edition">MACMILLAN/MCGRAW-HILL EDITION</p>
        <p role="creator">RICHARD MOYER</p>
        <p role="creator">LUCY DANIEL</p>
        <p role="creator">JAY HACKETT</p>
        <p role="creator">PRENTICE BAPTISTE</p>
        <p role="creator">PAMELA STRYKER</p>
        <p role="creator">JOANNE VASQUEZ</p>
        <p role="creator">NATIONAL GEOGRAPHIC SOCIETY</p>
        <p role="imprint">
            <name role="publisher">McGraw-Hill School Division</name>
            <place>New York</place>
            <place>Farmington</place>
        </p>
    </section>
Retrieved from "http://www.daisy.org/zw/ZedAI_Attribution"
Personal tools