On Wednesday 21 March 2007 7:39 am, Bruce D'Arcus wrote:
> I'm wondering about a simpler approach still. I am thinking of
> properties like just citation, shortCitation and bibliographicEntry. In
> that scheme, if we have a citation like (Doe, 1999, 2000; see also
> Smith, 1993):
>
> - ref 1 and 3 are the default citation string
> - ref 2 is the short form
> - ref 3 would also be a "see also" type, and so grouped and prefixed
> in standard ways that could be overridden
>
> So the RDF in package would look like:
>
> <b:Book rdf:about="urn:isbn:34982376">
> <b:citation>Doe, 1999</b:citation>
> <b:shortCitaton>1999</b:shortCitaiton>
> ...
> </b:Book>
>
> Any thoughts? Could things be as simple as I am thinking?
It may be. Footnote citations are also in two forms, the long form for
Initial Citations, the short form for Subsequent Citations so the suggested
format seems to work for that case.
A couple of questions come to mind-
1. Locator formatting (page numbers etc). If CiteProc is handling the locator
formatting I would guess that intend that the RDF in package would look like:
<b:Book rdf:about="urn:isbn:34982376:123-128">#An entry for each
ref/location <b:citation>Doe, 1999:123-128</b:citation>
<b:shortCitaton>1999:123-128</b:shortCitaiton>
...
</b:Book>
If not and the WP interface handles this then the WP interface needs to deal
with the different locator types formats that are style dependent. I.E. p,
page, pp, pages, 123-128, or 123-8 etc.
2. With a basic two sting input field suppression like Suppress Author, Date
etc. would have be based on a set of assumptions like the Author text string
consists of the characters to the first numeric character or the end of the
input, Dates are the first 4 numeric digits following a comma ? This could
get complex as we need to cope with all possible styles, multiple authors and
different data formats.
It was issues like these that led me to think that Bibliography Service API
would need to be supplied with-
<b:Book rdf:about="urn:isbn:34982376":123-128> #An entry for each
ref/location <b:citation>Doe, 1999:123-128</b:citation> #Also
Initial Citation <b:shortCitaton>1999:123-128</b:shortCitaiton> # Also
Subsequent Citation <b:CitationLocation>:123-128</b:CitationLocation>
<b:CitationAuthorName>Doe</b:CitationAuthorName>
<b:CitationDate>1999</b:CitationDate>
<b:IbidText>Ibid.</b:IbidText>
...
</b:Book>
Thus suppressing date or author, or locator becomes a simple string matching
action. And Ibid. with location is IbidText + CitationLocation, as in 'Ibid.,
123-128'
Shifting locator formatting to the WP interface simplifies the CiteProc
requirements to
<b:Book rdf:about="urn:isbn:34982376">
<b:citation>Doe, 1999</b:citation> #Also Initial Citation
<b:shortCitaton>1999</b:shortCitaiton> # Also Subsequent Citation
<b:CitationAuthorName>Doe</b:CitationAuthorName>
<b:CitationDate>1999</b:CitationDate>
<b:IbidText>Ibid.</b:IbidText>
...
</b:Book>
at the cost of building a mini CiteProc for locator formatting into the WP
interface or having a separate requestLocatorFormatting service for CiteProc
to perform whenever a new or change location is added: I think the latter may
be the best option.
David
--
-------------------
David N. Wilson
Co-Project Lead for the Bibliographic
OpenOffice.org Project
http://bibliographic.openoffice.org
-------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
