[osis-core] Question on cit/citation
Todd Tillinghast
todd at contentframeworks.com
Tue Nov 2 13:11:29 MST 2004
Patrick,
Is this case for "citation" in a Bible or a commentary like work?
Todd
> -----Original Message-----
> From: osis-core-bounces at crosswire.org [mailto:osis-core-
> bounces at crosswire.org] On Behalf Of Patrick Durusau
> Sent: Wednesday, October 27, 2004 11:32 AM
> To: Jim_Albright at wycliffe.org
> Cc: Jeff_Gayle at sil.org; osis-core at bibletechnologieswg.org
> Subject: [osis-core] Question on cit/citation
>
> Jim,
>
> Trying to collapse several questions into one.
>
> Just cutting to the cit/citation cases in this response:
>
> Jim_Albright at wycliffe.org wrote:
> > Thanks for looking at my problem domain.
> >
>
> <snip>
>
> > Citation_Line1 (etc): Question, you list lg but I assume l?
> >
> >>>>>><citation> would be preferred
> >>>>>
> >
> > BTW, we have otPassage on seg. So, would <l><seg>...</seg></l>, meet
the
> > need here?
> >
> > Err, actually just looked at the John the Baptist example and so you
> > would want something like otPassage on lg. Hmmm, then you could do
the
> > line1, line2, etc. with XSLT. Actually would reduce the amount of
markup
> > you would need since if I am in a lg type=otPassage, then lines 1,
2,
> > etc. fall out from the structure. I think that works for me if it
works
> > for you.
> >
> >>>>>yes that is where I would want it .... but citation is more
generic
> >>>>>I have cases where in the introduction a key verse in the
following
> >>>>
> > book
> >
> >>>>>is cited ... thus citation rather than otPassage.
> >>>>
> >
>
> OK, but if I understand the second case (not an otPassage) then don't
> you have a <reference>key verse</reference> in the introduction?
>
> Maybe it is a difference in terminology but I understand <reference>
to
> be a citation, at least if you mean something like:
>
> "The key verse in this book to me is <reference>John
1.1</reference>...."
>
> Close, far away, lost?
>
> > Citation_Paragraph: Looks like a block quote that contains a
paragraph,
> > which as you know can contain a reference element. I think this is
what
> > we used to call <cit> in TEI, which had a <q> followed by a <ref>
(don't
> > hold me to the names) element.
> >
> >>>>>>Citation Paragraph and Citation Line1 are related ... if we can
put
> >>>>>>a <cit> around them then we only need to put in p, l, ref ....
> >>>>>
> >
> > Not sure what would be different about using a block quote that
contains
> > a reference element.
> >
> >>>>>>>block quote is descriptive
> >>>>>>>citation is meaning based
> >>>>>>
>
> Yes, but we are making the structure (hence descriptive markup) of the
> text, not its interpretation (meaning).
>
> Besides, if we want to avoid confusion and inconsistency, then we
don't
> want to have citation and blockQuote with the same content model. Some
> people will use one and some people will use the other.
>
> >
> > Citation_Reference: Why isn't this simply a reference with a type?
That
> > is to say all references are citation_references in some sense of
the
> > term. Since we have an element for marking all references, why not
use
> > that and add a type if necessary?
> >
> >>>>>>>if we have <cit> or <citation> then just <ref> works ... the
type
> is
> >>>>>>
> > inferred by context
> >
>
> Sorry, I don't think I made that clear. A reference, at least in my
> experience is always a citation. Perhaps we are using citation
differently.
>
> Can you say a bit about how you see a citation_reference as being
> different from a reference? Whether I am inside a citation or no, it
is
> still a reference and I assume we want to treat all references the
same
> way? In other words, it does not matter if it is a citation_reference
or
> some other sort of reference, would it?
>
> Will try to answer a couple of more areas this afternoon but may not
> reach all of them today.
>
> Hope you are having a great day!
>
> Patrick
>
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau at sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
>
> Topic Maps: Human, not artificial, intelligence at work!
>
>
> _______________________________________________
> osis-core mailing list
> osis-core at bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
More information about the osis-core
mailing list