diff --git a/www/contribute/metadata.php b/www/contribute/metadata.php index b240af3b..a984bb75 100644 --- a/www/contribute/metadata.php +++ b/www/contribute/metadata.php @@ -97,11 +97,10 @@ require_once('Core.php');

Arrange the <dc:subject> elements sequentially in a block.

  • -

    After the block of <dc:subject> elements, include a block of <meta property="meta-auth"> elements with values representing the URL at which you found the categorizations for each individual subject.

    -

    For example, if we found the Library of Congress categories for an ebook at the Project Gutenberg ebook’s “bibrec” tab, then you would use the URL of the Project Gutenberg ebook.

    +

    After the block of <dc:subject> elements, include a block of <meta property="authority"> and <meta property="term"> elements with values representing the source and particular ID of the subject. authority is almost always LCSH (Library of Congress Subject Heading).

  • -

    The <meta property="meta-auth"> element must refine each individual <dc:subject> element, even if the URL is the same for all of them.

    +

    The <meta property="authority"> element must refine each individual <dc:subject> element.

    • This example shows how to mark up the subjects for A Voyage to Arcturus:

    <dc:subject id="subject-1">Science fiction</dc:subject> <dc:subject id="subject-2">Psychological fiction</dc:subject> <dc:subject id="subject-3">Quests (Expeditions) -- Fiction</dc:subject> <dc:subject id="subject-4">Life on other planets -- Fiction</dc:subject> <meta property="meta-auth" refines="#subject-1">https://www.gutenberg.org/ebooks/1329</meta> <meta property="meta-auth" refines="#subject-2">https://www.gutenberg.org/ebooks/1329</meta> <meta property="meta-auth" refines="#subject-3">https://www.gutenberg.org/ebooks/1329</meta> <meta property="meta-auth" refines="#subject-4">https://www.gutenberg.org/ebooks/1329</meta> diff --git a/www/contribute/semantics.php b/www/contribute/semantics.php index 3c8e2251..d91e839c 100644 --- a/www/contribute/semantics.php +++ b/www/contribute/semantics.php @@ -303,15 +303,15 @@ font-weight: normal; <link href="../css/local.css" rel="stylesheet" type="text/css"/> </head> <body epub:type="backmatter z3998:fiction"> - <section id="endnotes" epub:type="rearnotes"> + <section id="endnotes" epub:type="endnotes"> <h2 epub:type="title">Endnotes</h2> <ol> - <li id="note-1" epub:type="rearnote"> + <li id="note-1" epub:type="endnote"> <p>The first endnote goes here.</p> - <p>Here's another line for the first endnote. <a href="chapter-1.xhtml#noteref-1" epub:type="se:referrer">↩</a></p> + <p>Here's another line for the first endnote. <a href="chapter-1.xhtml#noteref-1" epub:type="backlink">↩</a></p> </li> - <li id="note-2" epub:type="rearnote"> - <p>The second endnote goes here. <a href="chapter-1.xhtml#noteref-2" epub:type="se:referrer">↩</a></p> + <li id="note-2" epub:type="endnote"> + <p>The second endnote goes here. <a href="chapter-1.xhtml#noteref-2" epub:type="backlink">↩</a></p> </li> </ol> </section> @@ -323,18 +323,18 @@ font-weight: normal;

  • Each <li> requires the following attributes:

  • The href attribute points to the direct anchor reference to the endnote.

  • If an endnote contains a citation offset with a dash (for example, “—Ed.”), separate the citation from the text with a single space and enclose it in the <cite> tag:

    - <li id="note-1" epub:type="rearnote"> -<p>Here’s an endnote. <cite>—<abbr class="eoc">Ed.</abbr></cite> <a href="chapter-1.xhtml#note-1" epub:type="se:referrer">↩</a></p> + <li id="note-1" epub:type="endnote"> +<p>Here’s an endnote. <cite>—<abbr class="eoc">Ed.</abbr></cite> <a href="chapter-1.xhtml#note-1" epub:type="backlink">↩</a></p> </li>
    • -

  • The final <p> element in an endnote contains a link back to the referring anchor. Don’t just point it to the file, make sure it points to the exact link that we came from. For example, chapter-1.xhtml#note-1, not chapter-1.xhtml. If the link is the last element in a longer <p> tag, it must be preceded by one space character; if it is the only child of a <p> tag (for example if the previous text was a <blockquote>) then it can be on its own line. It must have the epub:type set to se:referrer. The text of the link is always the “↩” character.

    • +

  • The final <p> element in an endnote contains a link back to the referring anchor. Don’t just point it to the file, make sure it points to the exact link that we came from. For example, chapter-1.xhtml#note-1, not chapter-1.xhtml. If the link is the last element in a longer <p> tag, it must be preceded by one space character; if it is the only child of a <p> tag (for example if the previous text was a <blockquote>) then it can be on its own line. It must have the epub:type set to backlink. The text of the link is always the “↩” character.