JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DIGITALCLASSICIST Archives


DIGITALCLASSICIST Archives

DIGITALCLASSICIST Archives


DIGITALCLASSICIST@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DIGITALCLASSICIST Home

DIGITALCLASSICIST Home

DIGITALCLASSICIST  September 2015

DIGITALCLASSICIST September 2015

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Canonical Text Services: a new archetype?

From:

Neel Smith <[log in to unmask]>

Reply-To:

The Digital Classicist List <[log in to unmask]>

Date:

Sun, 13 Sep 2015 18:51:17 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (202 lines)

Thanks for the questions with helpful specific examples.

CTS URNs let you identify passages and works with the degree of specificity
of your choosing.  In your example, the notional-level URN

urn:cts:latinLit:phi0959.phi005:27

is an assertion that "line 27" is a valid reference to a "notional" work 
-- as you
succinctly express it, this is a formalization of ubiquitous practice like
"Ov. Rem. 27".

There is no "binding" of notional works to any specific version; there 
is no instantiation of an
archetype.  So what do we do if, as in your example, two editors 
disagree about a "notional" text,
with one editor rejecting line 27 and another accepting it?  Since 
"notional" texts mean
nothing without some concrete supporting evidence, at some point someone 
must cite a version!
As you note, CTS URNs also allow that, so I think your important 
question really is more about
best scholarly practices than technological protocols:  when is it 
appropriate to
cite at a notional level, and when not?  I think that some of the 
perceived difficulty
in this practice is rooted in the ways we have used critical editions in 
the past,
since critical editions already represent reconstructions that may be 
pretty distant
from any concrete version known in MSS or papyri.

The other helpful examples you mention are similar in the sense that I 
think the
explicit semantics of the CTS URN shines a light on traditional citation 
practices
that are sometime more ambiguous than we have realized.  In the Homer 
Multitext project,
I deal routinely with differing versions of the *Iliad* that might have 
plus/minus
verses, or have verses in different orders, for example, and it has been 
wonderfully
helpful to be able to express that, and to automate comparison across 
specific versions
of texts.

It's tempting to overload *citation* with various kinds of *analysis*, 
such as attribution,
but we should keep those distinct.  Whether you think Aeschylus is the 
author of the
Prometheus Bound or not makes no difference in how we *identify* the 
work:  it's the
use of common identifiers that lets us identify what we interpret 
differently!  So
in the greekLit namespace, urn:cite:chs:textgroup.tlg0085 refers to a 
group of works
traditionally called "Works of Aeschylus", but implies nothing about 
your views on attribution:
urn:cts:greekLit:tlg0085.tlg003 can be our common identifier for 
"Prometheus Bound" whoever
you think the author is.

I hope this quick reply makes some sense.

Neel Smith



On 9/13/15 2:51 PM, Paolo Monella wrote:
> Dear all,
>
> I'm reading scholarship and technical reports on the CTS (Canonical 
> Text Services) protocol, and I have a question that I thought would be 
> best answered/discussed on the list.
>
> How does the CTS protocol deal with the possible variations of texts 
> in the philological community?
>
> I'll make one main practical example (preferring - hopefully - clarity 
> over brevity):
>
> Verses 25-26 of the Remedia Amoris by Ovid are suspected to be 
> spurious, so they are sometimes published in brackets in editions such 
> as the online PHI 5.3 in http://latin.packhum.org/loc/959/5/0#0
>
> puer es, nec te quicquam nisi ludere oportet:  23
>      Lude; decent annos mollia regna tuos.     24
> [Nam poteras uti nudis ad bella sagittis:      25
>      Sed tua mortifero sanguine tela carent.]  26
> Vitricus et gladiis et acuta dimicet hasta,    27
>      Et victor multa caede cruentus eat:       28
>
> However, the PHI edition upon which some CTS implementations rely to 
> assign numbers to verses includes vv. 25-26 in the text, so the next 
> verse "Vitricus et gladiis et acuta dimicet hasta" is numbered as 27, 
> and so on.
>
> If I'm not wrong, a possible CTS URN for verse 27 would be:
> urn:cts:latinLit:phi0959.phi005:27
> Where:
> - phi0959 refers to Ovid in the PHI Canon;
> - phi005 refers to the Remedia Amoris as the 5th work by Ovid in the 
> same Canon;
> - 27 is verse number 27 of the notational text (i.e. not a specific 
> version of the text, but the 'abstract' notational text).
>
> To manufacture this URN, I'm mostly relying on 
> http://www.homermultitext.org/hmt-docs/cite/cts-urn-overview.html
> Please do correct me here and anywhere I'm wrong!
>
> I think that the underlying assumption (valid, in fact, in most cases 
> for Greek and Latin classical texts) is that "versions of a text are 
> related to a notional text in a conceptual hierarchy" (quoted from 
> http://katahdin.cs.dartmouth.edu/reports/TR2009-649.pdf paragraph 2, 
> point 3)
>
> The protocol also provides you with the option of referring to a 
> specific version of the text.
> For example, in the Perseus Digital Library "Text URI"
> http://data.perseus.org/citations/urn:cts:latinLit:phi0959.phi005.perseus-lat1:Rem. 
>
> refers to the specific version/edition of the text of the Remedia 
> Amoris identifed as "perseus-lat1".
> I think this very good, as different editions have different texts.
>
> My question, instead, is about the option, included in the standard, 
> to have URNs like
> urn:cts:latinLit:phi0959.phi005:27
> where there is no reference to a specific version/edition of the text, 
> but the reference is to verse 27 of the canonical notational text of 
> the Remedia Amoris.
>
> I suspect that this option will be largely implemented, as it is a 
> really convenient and effective way to formalize semi-formal 
> references ubiquitous in classical scholarship such as "Ov. Rem. 27".
>
> The latter URN (urn:cts:latinLit:phi0959.phi005:27) looks OK today, as 
> the scholarly community currently agrees that verses 25-26 are part of 
> the text.
>
> However, what will happen if in the future new research creates a 
> consensus on the thesis that verses 25-26 are spurious? Or if editor 
> Joanne Brown publishes in 2016 her own scholarly edition where verses 
> 25-26 are considered spurious and expunged from the text? In these 
> cases, most new editions (or just Brown's 2016 edition) would have the 
> following text:
>
> puer es, nec te quicquam nisi ludere oportet: 23
> Lude; decent annos mollia regna tuos.         24
> Vitricus et gladiis et acuta dimicet hasta,   25 (formerly 27)
> Et victor multa caede cruentus eat:           26 (formerly 28)
>
> My understanding is that a system implementing the CTS protocol would 
> refer to the verse "Vitricus et gladiis et acuta dimicet hasta" as:
>
> 1) urn:cts:latinLit:phi0959.phi005.brown2016:25
> if referring to verse 25 in the text of the "brown2016" edition of the 
> text, assuming that J. Brown provides, like Perseus does, a formal way 
> to reference her own text by means of CTS URNs;
>
> 2) urn:cts:latinLit:phi0959.phi005:27
> if referring to that verse without reference to any specific version 
> of the text, but simply referring to the abstract notational text.
>
> In other words, my understanding is that the reference URN (when _not_ 
> referring to a specific version to the text, but to the abstract 
> notational text, i.e. in case 2 above) would remain bound forever to 
> the archetypal text based on which the original verse numbers have 
> been assigned -- that is TLG and PHI.
>
> Am I right? Or is there a way in which the protocol deals with this?
>
> I won't dwell any longer on this, so I'll just quickly list other 
> possible applications of this issue:
>
> - verse displacement (e.g. an editor thinks that verses 1-2 should be 
> displaced after verse 8);
>
> - poem divisions/boundaries (some think that Propertius' elegy 2.22 is 
> one poem, some split it into two poems Prop. 2.22a Prop. 2.22b);
>
> - suspected (or certainly) spurious works that PHI still attributes to 
> an author (urn:cts:latinLit:phi0959.phi015 would refer to the 
> Epicedion Drusi, so it is listed under author phi0959, Ovid, though 
> with the notation [sp.]);
>
> - works that PHI does not attribute to an author, but that might be 
> found to belong to that author in the future 
> (urn:cts:latinLit:phi0692.phi003 would refer to the Culex and is 
> listed under author 0692, the Appendix Vergiliana, instead of author 
> 0690, Vergilius);
>
> - all other philological/papyrological discoveries that may affect the 
> identification of authors (e.g. TLG distinguishes between two 
> different "Aeschylus Trag.", identified as tlg0031 and 0085, the 
> famous one), the attribution of works to authors and of sections 
> (verses/poems/chapters etc.) to works.
>
> Thank you,
> Paolo
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
January 2006
December 2005
October 2005
September 2005
August 2005
July 2005
June 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager