Re: encoding bibliographical references to numbered entries

MLH <[email protected]>
Newsgroups gmane.text.tei.general
Message-ID <HE1PR03MB1547C69ABB935A44A22A6A58CD9B0@HE1PR03MB1547.eurprd03.prod.outlook.com>
Thanks James et al. I should have noticed that they were only suggested values! 'entry' makes sense to me in this case although it would be interesting to hear what other people have done.


re. Elisa's suggested about <biblScope>: my impression was that <biblScope> and <citedRange> had rather different functions, the first describing the pages (or whatever) occupied by a whole cited work (e.g. chapter in a book), and the second describing the pages cited from that work in a given reference. For example:

A. N. Other, "Example book section", in Example Book, <biblScope>pp. 123-234</biblScope>, at <citedRange>pp. 125-6</citedRange>


Matthew


________________________________
From: James Cummings <[email protected]>
Sent: 13 December 2016 10:23
To: Martin de la Iglesia; [email protected]; [email protected]
Subject: Re: encoding bibliographical references to numbered entries

Hi Martin, Matthew, et al.

Just because there is not the suggested value you want does not
mean that you cannot use other values! It just means that the TEI
has not suggested that value as one of the examples you might
want to use.

Indeed, @unit on both biblScope and citedRange is there because
those elements both claim membership of
the att.citing class.
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.citing.html
As you'll see there, the datatype of @unit is teidata.enumerated.
Whenever I see that datatype in the attributes I'm recommending
people use I suggest that they constrain it to be a set list of
values.  See the note on
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-teidata.enumerated.html
which suggests this.

So in Matthew's case in creating his ODD he might wish to suggest
a (fixed or 'semi' fixed) list of attribute values which includes
'number' as a value.  (If indeed 'number' is the right term for
this kind of thing rather than 'entry' or 'orderedEntry' or
whatever else might seem reasonable.)

However, I think we're miscommunicating. I read Matthew's
original email not as asking for an alternative to using @unit on
citedRange or biblScope but wanting a suggestion for an
alternative term to put in the unit attribute.

Matthew:  I'd say the unit is 'entry' myself.

-James


On 13/12/16 09:47, Martin de la Iglesia wrote:
> I'm afraid <biblScope> doesn't solve the problem: @unit is also
> available in <biblScope> and there is no suggested @unit value
> for the kind of number Matthew is looking for.
>
>
> Martin
>
>
> --
> Martin de la Iglesia
> Metadata and Data Conversion
>
> Georg-August-Universität Göttingen
> Göttingen State and University Library
> D-37073 Göttingen
>
> Papendiek 14 (Historical Building, Room 1.206)
> +49 551 39-14070 (Tel.)
> +49 551 39-3468 (Fax)
>
> [email protected]
> http://www.sub.uni-goettingen.de
>
>
> Am 12.12.2016 um 15:16 schrieb Elisa:
>> Matthew-- I think you'll want <biblScope> for this. It's a
>> wonderfully versatile element, since you can use it for all
>> kinds of ranges. See
>> http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-biblScope.html
>>
>> Best,
>> Elisa
>> --
>> Elisa Beshero-Bondar, PhD
>> Director, Center for the Digital Text
>> Associate Professor of English
>> University of Pittsburgh at Greensburg
>> 150 Finoli Drive, Greensburg, PA 15601 USA
>> E-mail: [email protected] | Development site: http://newtfire.org
>>
>> Typeset by hand on my iPad
>>
>> On Dec 12, 2016, at 6:14 AM, MLH <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>>
>>> Hello all,
>>>
>>> Is there a standard way of encoding bibliographical entries
>>> where (instead of a page) a numbered entry or range of
>>> numbered entries is cited?
>>>
>>> For example:
>>>
>>> <bibl><title>Bibliotheca Hagiographia Latina>, 5625-6</bibl>
>>>
>>> <citedRange> does not have "number" (or an equivalent) as an
>>> accepted value of @unit - is there an alternative?
>>>
>>> Thanks
>>>
>>> Matthew
>>>
>>>
>


--
Dr James Cummings, Academic IT Services, University of Oxford,
TEI Consultations: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.