W3C home > Mailing lists > Public > public-digipub-ig@w3.org > June 2015

Re: use case: page based scholarly reference?

From: Ivan Herman <ivan@w3.org>
Date: Thu, 11 Jun 2015 11:31:53 +0200
Cc: Liam Quin <liam@w3.org>, Tzviya Siegman <tsiegman@wiley.com>, Dave Cramer <dauwhe@gmail.com>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-Id: <95900885-4176-468B-A762-EED431E84564@w3.org>
To: Bill Kasdorf <bkasdorf@apexcovantage.com>

> On 10 Jun 2015, at 21:50 , Bill Kasdorf <bkasdorf@apexcovantage.com> wrote:
> 
> Confirming Liam's points, and adding that the page-break indicators are a requirement for the EDUPUB profile of EPUB; they're considered essential for accessibility, which is essential in educational contexts.
> 
> I put them in almost all the models I create for clients, for that reason and for the various citation reasons (cross references, index references, citations in the literature), though I will admit that putting them in the model doesn't mean the client necessarily uses them.
> 
> Apex routinely puts them in EPUBs we create, btw, unless the client wants us not to.

That is great. Are there other issues from your practice for scholarly publishing that should be listed in our case, too?

Ivan


> They're considered best practice, mainly because of the accessibility concern. And doing them as empty elements enables them not to interfere with rendering (though some clients _want_ them to appear--usually scholarly ones).
> 
> -----Original Message-----
> From: Liam R. E. Quin [mailto:liam@w3.org]
> Sent: Wednesday, June 10, 2015 3:30 PM
> To: Ivan Herman
> Cc: Tzviya Siegman; Dave Cramer; Bill Kasdorf; W3C Digital Publishing IG
> Subject: Re: use case: page based scholarly reference?
> 
> On Wed, 2015-06-10 at 14:02 +0200, Ivan Herman wrote:
>> Based on the scholarly publishing topic of the last telco, I am
>> wondering how to formalize a requirement and under which category does
>> it belong…
>> 
>> In scholarly publishing precise (scholarly) reference is a must.
>> This, as of today, usually includes references to page numbers. This
>> can take specific formats,
> 
> One way this is handled with digital editions today is to have an empty element for page breaks (or to use that element to contain foliation and other page apparatus such as running headers). E.g. TEI uses pb for a page break.
> 
> Then the page breaks are shown e.g. with a discrete symbol in the text or in the margin.
> 
> This same problem exists in printed critical editions of texts and transcriptions of manuscripts, of course.
> 
> Liam
> 
>> 
>> - In some areas and under the reference format required by some
>> journals, a reference to an article includes a page number. E.g.,
>> 
>>        A. Evans, et al., “3D graphics on the web: A survey,”
>> Computers & Graphics, vol. 41, pp. 43–61, Jun. 2014.
>> 
>> 
>> - In humanities, when quoting from a book, a reference (often in a
>> footnote) includes a page number:
>> 
>>        D. Heater: World Citizenship and Government. Macmillan Press,
>> London, 1996. 12-13.
>> 
>> One of the reasons, I guess, why publisher still offer a PDF format
>> for their downloads is, I guess, because the page numbers become fixed
>> relative to a journal or a proceedings, even if these latter
>> practically never hit anyone's bookshelf.
>> 
>> This is so deeply structured in scholarly references, that fully
>> online publisher have to cheat with this. Eg, PeerJ has the
>> article[1]; one can download, from the site, a BiBTeX reference for
>> the paper, to be used by others, and this is of the form (I removed
>> details):
>> 
>> @article{10.7717/peerj-cs.1,
>> title = {Achieving ...},
>> author = {Starr, Joan and ...},
>> year = {2015},
>> month = {5},
>> volume = {1},
>> pages = {e1},
>> journal = {PeerJ Computer Science},
>> issn = {2376-5992},
>> url = {https://dx.doi.org/10.7717/peerj-cs.1},
>> doi = {10.7717/peerj-cs.1}
>> }
>> 
>> Note the phony 'e1' page identification.
>> 
>> I am not sure what this translates into in a requirement for the
>> identification part, namely that 'reasonable' units within the
>> publication should have an easily identifiable URL, or URL structure
>> (note that the examples above actually define ranges and not only one
>> page). This may be a page but that is a fluid notion in this case,
>> that may not be appropriate for scholarly purposes. But I am a bit
>> uncertain how to formulate it before putting it into the use case
>> directory…
>> 
>> WDYT?
>> 
>> Ivan
>> 
>> 
>> 
>> [1] https://dx.doi.org/10.7717/peerj-cs.1
>> 
>> 
>> 
>> ----
>> Ivan Herman, W3C
>> Digital Publishing Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> ORCID ID: http://orcid.org/0000-0003-0782-2704
>> 
>> 
>> 
>> 


----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704





Received on Thursday, 11 June 2015 09:32:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:02 UTC