You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
data: second-wave work candidates with established citation systems #25
New files under works/ and systems/. No existing record changes.
Citation system
Seven new ones, listed below.
What is wrong or missing?
The registry holds twelve works. The ROADMAP plans to "grow the registry with more canonical
examples across theology, classics, philosophy, law, and other citation traditions."
The corpus survey (tracking issue) sorts its candidates into three waves. This issue is the second wave: works whose citation system is beyond dispute and stable for a century or
more, but whose online resolver is provider-specific and needs mapping work. The first wave
— the near-automatic reference spaces — is handled in separate issues.
Every row below is unverified. It comes from an LLM-generated survey whose sourcing is
uneven; see the tracking issue. No row is ready to implement. Each needs the treatment #16
and #19 got: open the URLs, test an invalid locator as a control, confirm the resolver
addresses the passage and not just the work.
Suggested correction or new value
Work one row at a time. Open a separate issue per work once it is verified.
Dante, Divina Commedia — dante.commedia. System: cantica, canto, verse
(Inf.1.1, Purg.13.25, Par.33.145). The cantica is part of the locator, so the
system needs a three-part regex, and Inf/Purg/Par must be a fixed vocabulary.
Resolver candidates: Dartmouth Dante Project, Princeton Dante Project, Dante Lab. The
Petrocchi text is the critical edition all three use. Open question: Dante Lab's
reader takes reader[cantica]=2&reader[canto]=5 as query parameters and stops at the
canto — it does not address the verse. Check whether any of the three addresses a
single verse.
Thomas Aquinas, Summa Theologiae — aquinas.summa-theologiae. System: pars,
quaestio, articulus (ST.I-II.q90.a1). The pars uses Roman numerals with a hyphenated
form for the Secunda secundae, so the locator vocabulary needs deciding before the
regex. Resolver candidate: Corpus Thomisticum (Universidad de Navarra), which is the
standard scholarly Opera omnia. Open question: Corpus Thomisticum has no
documented resolver API. Check whether its URLs are deterministic per article.
Justinian, Digest — digest or corpus-iuris-civilis.digest. System: book,
title, lex, paragraph (D.41.2.3pr). Note pr (principium) is a non-numeric
paragraph, so the regex must admit it alongside integers. Resolver candidate: the Roman
Law Library (Université Grenoble Alpes), whose Digest text is Mommsen/Krueger. Open
question: the site is static HTML with anchors. Confirm the anchors are per-lex and
stable.
Shakespeare — one work per play, so this row is really a sub-project. System: act,
scene, line. Open question, and it is the interesting one: Folger Through Line
Numbers (FTLN) are Folger-specific, while act/scene/line varies between editorial
traditions. The survey argues act/scene/line is the abstract identity and FTLN is a
resolver mapping. That is the right shape for TextRefs, but it needs the provider
vocabulary mapping (feat(compile): map locator variables into a provider's own vocabulary textrefs.org#71) and an FTLN concordance. Resolver
candidate: Folger Shakespeare, which documents an API that resolves a single FTLN.
Nietzsche — one work per title (nietzsche.frohliche-wissenschaft, …). System:
work sigla plus aphorism number (FW 125). Resolver candidate: Nietzsche Source
eKGWB, based on Colli/Montinari (KGW/KSA), which is the reference edition. Open
question: the URI is hash-based (nietzschesource.org/#eKGWB/FW-125). A fragment is
never sent to the server, so this cannot be confirmed by fetch and needs a browser
check. Also: the sigla belong in alternative_labels, and the work-per-title split
means the sigla, not the aphorism, carry the work identity.
Kant — Akademie-Ausgabe volume and page (AA IV, 421). Open question, and it
may be disqualifying: an AA citation addresses a page of a specific edition, not a
structural unit of the work. That is closer to the printed-page citation TextRefs
exists to replace than to Stephanus or Bekker, which are also page-based but function
as edition-independent structure. Decide whether AA is a citation system TextRefs
should carry before modelling it. Resolver candidate: the Kant-Korpus at
Uni Duisburg-Essen, whose URL pattern is deterministic (zero-padded volume, page). The survey's source for this URL pattern is a ZDF fact-check PDF. Re-source it.
Hume — hume.treatise, hume.enquiry-human-understanding. System: book, part,
section, paragraph (T 1.3.6.4, EHU 10.1). Resolver candidate: Hume Texts Online
(Peter Millican, Hertford College Oxford), the reference text the Hume Society
supports. Open question: the survey says a siglum-to-path table maps EHU 10.1 to /texts/e/10 with the paragraph as a DOM anchor. That means a per-work sigla map, not
one template. Confirm the anchors exist.
Evidence and sources
None of the above is verified. The sources are data/research/a.md and data/research/b.md,
now carried in the tracking issue. Their quality is uneven and two citations in the first
file are unusable. Treat every claim here as a lead, not a finding.
The one thing already learned the hard way, from the Perseus/Scaife companion issue: a
resolver that returns HTTP 200 may still be serving the wrong passage. Always test an
invalid locator as a control before believing a link works.
Rights or licence note
To be established per work. Several candidates are academic sites with no explicit licence,
which is a license_url:-only case at best. Record access conditions during verification.
Affected file, TextRefs ID, or URL
New files under
works/andsystems/. No existing record changes.Citation system
Seven new ones, listed below.
What is wrong or missing?
The registry holds twelve works. The ROADMAP plans to "grow the registry with more canonical
examples across theology, classics, philosophy, law, and other citation traditions."
The corpus survey (tracking issue) sorts its candidates into three waves. This issue is the
second wave: works whose citation system is beyond dispute and stable for a century or
more, but whose online resolver is provider-specific and needs mapping work. The first wave
— the near-automatic reference spaces — is handled in separate issues.
Every row below is unverified. It comes from an LLM-generated survey whose sourcing is
uneven; see the tracking issue. No row is ready to implement. Each needs the treatment #16
and #19 got: open the URLs, test an invalid locator as a control, confirm the resolver
addresses the passage and not just the work.
Suggested correction or new value
Work one row at a time. Open a separate issue per work once it is verified.
dante.commedia. System: cantica, canto, verse(
Inf.1.1,Purg.13.25,Par.33.145). The cantica is part of the locator, so thesystem needs a three-part regex, and
Inf/Purg/Parmust be a fixed vocabulary.Resolver candidates: Dartmouth Dante Project, Princeton Dante Project, Dante Lab. The
Petrocchi text is the critical edition all three use. Open question: Dante Lab's
reader takes
reader[cantica]=2&reader[canto]=5as query parameters and stops at thecanto — it does not address the verse. Check whether any of the three addresses a
single verse.
aquinas.summa-theologiae. System: pars,quaestio, articulus (
ST.I-II.q90.a1). The pars uses Roman numerals with a hyphenatedform for the Secunda secundae, so the locator vocabulary needs deciding before the
regex. Resolver candidate: Corpus Thomisticum (Universidad de Navarra), which is the
standard scholarly Opera omnia. Open question: Corpus Thomisticum has no
documented resolver API. Check whether its URLs are deterministic per article.
digestorcorpus-iuris-civilis.digest. System: book,title, lex, paragraph (
D.41.2.3pr). Notepr(principium) is a non-numericparagraph, so the regex must admit it alongside integers. Resolver candidate: the Roman
Law Library (Université Grenoble Alpes), whose Digest text is Mommsen/Krueger. Open
question: the site is static HTML with anchors. Confirm the anchors are per-lex and
stable.
scene, line. Open question, and it is the interesting one: Folger Through Line
Numbers (FTLN) are Folger-specific, while act/scene/line varies between editorial
traditions. The survey argues act/scene/line is the abstract identity and FTLN is a
resolver mapping. That is the right shape for TextRefs, but it needs the provider
vocabulary mapping (feat(compile): map locator variables into a provider's own vocabulary textrefs.org#71) and an FTLN concordance. Resolver
candidate: Folger Shakespeare, which documents an API that resolves a single FTLN.
nietzsche.frohliche-wissenschaft, …). System:work sigla plus aphorism number (
FW 125). Resolver candidate: Nietzsche SourceeKGWB, based on Colli/Montinari (KGW/KSA), which is the reference edition. Open
question: the URI is hash-based (
nietzschesource.org/#eKGWB/FW-125). A fragment isnever sent to the server, so this cannot be confirmed by fetch and needs a browser
check. Also: the sigla belong in
alternative_labels, and the work-per-title splitmeans the sigla, not the aphorism, carry the work identity.
AA IV, 421). Open question, and itmay be disqualifying: an AA citation addresses a page of a specific edition, not a
structural unit of the work. That is closer to the printed-page citation TextRefs
exists to replace than to Stephanus or Bekker, which are also page-based but function
as edition-independent structure. Decide whether AA is a citation system TextRefs
should carry before modelling it. Resolver candidate: the Kant-Korpus at
Uni Duisburg-Essen, whose URL pattern is deterministic (zero-padded volume, page).
The survey's source for this URL pattern is a ZDF fact-check PDF. Re-source it.
hume.treatise,hume.enquiry-human-understanding. System: book, part,section, paragraph (
T 1.3.6.4,EHU 10.1). Resolver candidate: Hume Texts Online(Peter Millican, Hertford College Oxford), the reference text the Hume Society
supports. Open question: the survey says a siglum-to-path table maps
EHU 10.1to/texts/e/10with the paragraph as a DOM anchor. That means a per-work sigla map, notone template. Confirm the anchors exist.
Evidence and sources
None of the above is verified. The sources are
data/research/a.mdanddata/research/b.md,now carried in the tracking issue. Their quality is uneven and two citations in the first
file are unusable. Treat every claim here as a lead, not a finding.
The one thing already learned the hard way, from the Perseus/Scaife companion issue: a
resolver that returns HTTP 200 may still be serving the wrong passage. Always test an
invalid locator as a control before believing a link works.
Rights or licence note
To be established per work. Several candidates are academic sites with no explicit licence,
which is a
license_url:-only case at best. Record access conditions during verification.