Code bloat. What is it?

[paperwhite13]

In the second case, do you think pagelists should not be included for books like Random in Death? Is that your good practices advice? Again, what is your point?

[paperwhite13]

While you're putting together your alternate good practice advice, here's an academic article that has something to do with your second question.

This article offers a reflection on the author’s experience of teaching a novella by Nora Roberts, Spellbound, to an undergraduate English subject Genre Fiction/Popular Fiction at the University of Melbourne.

[paperwhite13]

Here's another about one of the books from the in Death series, proving that nowadays anything can and will be studied in school. Also, think about how many creative writing courses are being tought about her style, given how successful she is--all participants should literally be on the same page. These are just some of the more obvious examples.

Worth noting how the HTML version of the article is broken up by [End Page #] tags, to coordinate with the PDF.

[KevinH]

The opf metadata when pagelists are used is supposed to include the exact physical edition (isbn) that the epub pagelist matches. Textbooks and academic articles are the main users of pagelists and they rarely have paperback editions without matching page layouts.

[JSWolf]

Originally Posted by KevinH

The opf metadata when pagelists are used is supposed to include the exact physical edition (isbn) that the epub pagelist matches. Textbooks and academic articles are the main users of pagelists and they rarely have paperback editions without matching page layouts.

Random in Death does have an ID as to what version this came from.

<dc:source id="src-id">urn:isbn:9781250289544</dc:source>

[KevinH]

The standard positioning of the pagelist anchor tag is just before the first word on that physical page, so that going to that id is just as if you turned to that page and saw the top of page. The anchor tags take up zero layout space.

They are very useful to have. Nicely, it enables epubs to use glossaries, indexes, and tocs page number links just like in the printed page versions.

[KevinH]

Originally Posted by JSWolf

Random in Death does have an ID as to what version this came from.

<dc:source id="src-id">urn:isbn:9781250289544</dc:source>

And under epub3 metadata rules, there should also be a meta property "source-of" which refines the dc:source id "src-id" with the value of "pagination".

FWIW

[JSWolf]

Originally Posted by KevinH

And under epub3 metadata rules, there should also be a meta property "source-of" which refines the dc:source id "src-id" with the value of "pagination".

FWIW

There is.

<meta property="source-of" refines="#src-id">pagination</meta>

[KevinH]

Under the latest rules you may see something like the following being used instead of refines (which some people hate and that were almost dropped from later epub3 specs).

<meta
    property="pageBreakSource">
   urn:isbn:9780010010001
</meta>

Although I have never seen that in the wild.

[JSWolf]

Originally Posted by KevinH

Under the latest rules you may see something like the following being used instead of refines (which some people hate and that were almost dropped from later epub3 specs).

<meta
    property="pageBreakSource">
   urn:isbn:9780010010001
</meta>

Although I have never seen that in the wild.

I've not seen it as well.

[paperwhite13]

Originally Posted by KevinH

And under epub3 metadata rules, there should also be a meta property "source-of" which refines the dc:source id "src-id" with the value of "pagination".

FWIW

Hi, is there a difference between these?

• <dc:source id="SourceISBN">
  
• <dc:source id="src">
  
• <dc:source id="src-id">

Would I risk anything using <meta property="pageBreakSource"> instead of dc:source + refine?

[paperwhite13]

DAISY warns that with it being so new, using <meta property> may result in epubcheck errors, but the page must be outdated, because replacing

<dc:source id="src-id">urn:isbn:9781250289544</dc:source>
<meta property="source-of" refines="#src-id">pagination</meta>
<meta property="identifier-type" refines="#src-id" scheme="onix:codelist5">15</meta>

with

<meta property="pageBreakSource">urn:isbn:9781250289544</meta>

passed epubcheck. And I realized that the answer to my previous question is no, there is no difference, you just refine the id, however it's named, right?

[KevinH]

Yes that is correct.

[Ebookus]

Man! the title for this should have been "Code bloat, what is it? (grab some pop-corn and enjoy the show)".

At this point, I think the plot here is more interesting than that of "Random in Death".