Citations with CTS and Microformats: Difference between revisions

From The Digital Classicist Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:


With citation markup added: "vd. <a class="citation" target="_blank" href="http://fragments-repo.appspot.com/CTS?request=GetPassagePlus&withXSLT=true&urn=urn:cts:greekLit:tlg0008.tlg001.fhg01:1&inv=fhg-inventory.xml">Ath. <em>Deipn.</em> I</a>".
With citation markup added: "vd. <a class="citation" target="_blank" href="http://fragments-repo.appspot.com/CTS?request=GetPassagePlus&withXSLT=true&urn=urn:cts:greekLit:tlg0008.tlg001.fhg01:1&inv=fhg-inventory.xml">Ath. <em>Deipn.</em> I</a>".
The markup examples in this page use CTS URNs to provide identifiers for authors, works and work editions (see the [http://chs75.chs.harvard.edu/registries/cts/chsCanon CHS Canon] for a full list).


===Pattern 1===
===Pattern 1===
Line 47: Line 49:
===Pattern Comparison===
===Pattern Comparison===


This solutions in patterns 2 and 3 are more loosely coupled than the one in pattern 1. The citation is still linked to a resource, but the encoding includes enough information for a client-side component to create links to alternative resources.
* The solutions in patterns 2 and 3 are more loosely coupled than the one in pattern 1. The citation is still linked to a resource, but the encoding includes enough information for a client-side component to create links to alternative resources.  
 
The idea is to store in the @title a machine-understandable value representing a citation segment as described in the [http://microformats.org/wiki/abbr-design-pattern Microformats abbr-design pattern].
 
The &lt;cite> element is used to include further semantics.


In this example CTS URNs are used to provide identifiers for authors, works and work editions (see the [http://chs75.chs.harvard.edu/registries/cts/chsCanon CHS Canon] for a full list).
* The idea is to store in the @title a machine-understandable value representing a citation segment as described in the [http://microformats.org/wiki/abbr-design-pattern Microformats abbr-design pattern].  


===Parsing Microformats===
===Parsing Microformats===

Revision as of 14:53, 27 September 2010

The page Citation_in_digital_scholarship describes a convention for indicating citations that relies on the 'class' and 'title' attributes when implemented in (x)html.

This page describes an extension of that convention to encompass adding Microformats and CTS identifiers to conformant citations.

Sample sentence: "vd. Ath. Deipn. I".

With citation markup added: "vd. <a class="citation" target="_blank" href="http://fragments-repo.appspot.com/CTS?request=GetPassagePlus&withXSLT=true&urn=urn:cts:greekLit:tlg0008.tlg001.fhg01:1&inv=fhg-inventory.xml">Ath. Deipn. I</a>".

The markup examples in this page use CTS URNs to provide identifiers for authors, works and work editions (see the CHS Canon for a full list).

Pattern 1

<a class="citation" target="_blank" href="http://fragments-repo.appspot.com/CTS?request=GetPassagePlus&withXSLT=true&urn=urn:cts:greekLit:tlg0008.tlg001.fhg01:1&inv=fhg-inventory.xml">
 Ath. Deipn. I
</a>

This solution is somehow tightly coupled, i.e. the citation is linked to one resource.

Pattern 2

<cite class="ctref">
 <span class="ctauthor"> 
  <span class="projid">urn:cts:greekLit:tlg0012
  <abbr class="name" title="Homer">Hom. 
 </span>
 <span class="ctwork">
  <span class="projid">urn:cts:greekLit:tlg0012:tlg001
  <abbr class="title" title="Iliad">Il. 
 </span>
 <abbr class="range" title="20.131-20.137">20.131-7
 <span class="edition">
  <abbr class="description" title="Allen" /
 </span>
</cite>

This pattern is presented and discussed in [1].

Pattern 3

<a class="citation" target="_blank" href="http://fragments-repo.appspot.com/CTS?request=GetPassagePlus&withXSLT=true&urn=urn:cts:greekLit:tlg0008.tlg001.fhg01:1&inv=fhg-inventory.xml">
  <cite class="ctref">
   <abbr style="font-style:normal" class="ctauthor" title="urn:cts:greekLit:tlg0008">Ath. 
   <abbr class="ctwork" title="urn:cts:greekLit:tlg0008.tlg001">Deipn. 
   <abbr class="range" title="1">I 
   <abbr style="display:none" class="edition" title="urn:cts:greekLit:tlg0008.tlg001.fhg01">Kaibel
  </cite>
</a>

This pattern is presented and discussed in [2].

Pattern Comparison

  • The solutions in patterns 2 and 3 are more loosely coupled than the one in pattern 1. The citation is still linked to a resource, but the encoding includes enough information for a client-side component to create links to alternative resources.

Parsing Microformats

Some extensions or add-ons exist for different browsers that allow for some understanding for microformatted content embedded in web pages.

References

  • Romanello 2007. M. Romanello, "A semantic linking system for canonical references to electronic corpora," in International Conference on Electronic Corpora of Ancient Languages : proceedings of the international conference, Prague, November 16-17, 2007, P. Zemanek, Ed., Prague, 2007, pp. 107-120. [Online]. Available: http://eprints.rclis.org/16239/1/Romanello2008.pdf
  • Romanello 2008. M. Romanello "A Semantic Linking Framework to Provide Critical Value-Added Services for E-Journals on Classics." ELPUB 2008: Open Scholarship: Authority, Community, and Sustainability in the Age of Web 2.0 - Proceedings of the 12th International Conference on Electronic Publishing: http://elpub.scix.net/data/works/att/401_elpub2008.content.pdf.
  1. (Romanello 2007)
  2. (Romanello 2008)