Citations with CTS and Microformats: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
Ath. <em>Deipn.</em> I | Ath. <em>Deipn.</em> I | ||
</a> | </a> | ||
This solution is somehow tightly coupled, i.e. the citation is linked to one resource. | |||
===Pattern 2=== | ===Pattern 2=== | ||
| Line 21: | Line 23: | ||
</cite> | </cite> | ||
</a> | </a> | ||
This solution is more loosely coupled than the previous one. 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 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]. | ||
Revision as of 13:00, 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".
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
<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"> Ath. Deipn. I Kaibel </cite> </a>
This solution is more loosely coupled than the previous one. 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 Microformats abbr-design pattern.
The 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 CHS Canon for a full list).
Parsing Microformats
[TBD]