Re: [jats-list] Page range coding for books

["Beck, Jeff (NIH/NLM/NCBI) [E] beck@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Thanks Jan and Nikos,

We are collecting feedback on BITS through this form.

http://www.mulberrytech.com/BITS/BITS-Feedback.html


We welcome all suggestions.

Thanks
Jeff

On 12/16/14, 10:56 AM, "Nikos Markantonatos nikos@xxxxxxxxxx"
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

>Hi Jan.
>
>Your question reveals an interesting shortcoming of the DTD. If
><page-count> element allowed for a PCDATA body, then what you ask for
>could be encoded as:
>
><counts>
><page-count count="106">vi+100</page-count>
></counts>
>
>But this is not possible with the current BITS DTD, so all you can do
>for now is:
>
><counts>
><page-count count="106"/>
></counts>
>
>therefore missing out on the analysis of the book page counts. You may
>want to raise this one with the BITS maintenance committee.
>
>Regards,
>Nikos Markantonatos
>Atypon
>
>
>On 12/16/2014 04:20 PM, Jan Driesen jan.driesen@xxxxxxxxxxx wrote:
>> We want to code book-metadata / books (in BITS) that are numbered
>>partially in roman numerals (TOC, introduction, ...) and after that arab
>>numerals, which restart from 1.
>> When describing the extent of the book in the books' metadata, such is
>>normally done as: vi+100
>> This means the book has vi (6) pages numbered in roman numerals (pages
>>i to vi) and 100 pages numbered in arab numerals (pages 1 to 100). In
>>total the book has 106 pages (so 106 could be the
>>/book/book-meta/counts/page-count).
>> An example (non affiliated):
>>https://books.google.be/books?id=uVoOZyqE5o4C&printsec=frontcover#v=onepa
>>ge&q&f=false showing vii+337 pages
>>
>> What would be the appropriate way to tag such data?
>>
>>
>> Many thanks,
>>
>>
>> Jan Driesen
>>
>>
>
>
>--
>Confidentiality Notice:  This email and any attachments are for the sole
>use of the intended recipient(s) and contain information that may be
>confidential and/or legally privileged.  If you have received this email
>in error, please notify the sender by reply email and delete the
>message.  Any disclosure, copying, distribution or use of this
>communication by someone other than the intended recipient is prohibited.