From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bibliographic Databases
Date: Fri, 18 Apr 2008 19:46:20 +0200 [thread overview]
Message-ID: <4808DE6C.2090700@elvenkind.com> (raw)
In-Reply-To: <20080418151754.GN5346@hermes.commontology.de>
Hi,
Andreas Wagner wrote:
> Just out of curiosity: What are your reasons for preferring this over TEI:
MODS was a logical choice mostly my background (scientific publishers
=> MARC databases => MODS), and that BruceD'Arcus liked it. Btw,
his blog is full of bibliographic articles, if you are interested:
http://community.muohio.edu/blogs/darcusb/
(but it looks like he has switched over to RDF now)
I am not really set to any particular xml format, and there are
more mainstream choices (risx comes to mind).
But the few times I've had to work with TEI stuff I found that you
can easily get much more than you bargained for. Bibliographic data
is not easy on its own, and a format that allows (almost promotes)
extra tags to be embedded also is not helping at all.
Look at this:
http://www.tei-c.org/release/doc/tei-p5-doc/html/ref-author.html
Just the 'core' module is already pretty complex, but 'namesdates'
and 'linking' are definately also required for a useful bibliographic
database.
The nice, consise examples in the TEI docs are misleading because
<author>Lucy Allen Paton</author>
is useless, more specifics are needed. We need at least this:
<author>
<persName>
<forename>Lucy</forename>
<forename>Allen</forename>
<surname>Paton</surname>
</persName>
</author>
But with the use of <persName>, there are suddenly a gazillion
ways an author can encode the same name (and it does not
preclude any of the other ways to encode a name).
http://www.tei-c.org/release/doc/tei-p5-doc/html/ND.html#NDPER
Etc. etc. Imagine having to support that in a simple context module.
Cheers, Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-18 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 14:19 Robin Kirkham
2008-04-17 19:10 ` Andreas Wagner
2008-04-18 8:08 ` Taco Hoekwater
2008-04-18 8:15 ` Wolfgang Schuster
2008-04-18 15:17 ` Andreas Wagner
2008-04-18 17:46 ` Taco Hoekwater [this message]
2008-04-18 23:23 ` Andreas Wagner
2008-04-20 14:35 ` Bruce D'Arcus
2008-04-20 14:52 ` Bruce D\'Arcus
2008-04-19 19:21 ` George N. White III
2008-04-20 9:13 Robin Kirkham
[not found] <mailman.0.1208685601.23025.ntg-context@ntg.nl>
2008-04-21 12:03 ` Dietrich Rordorf / MDPI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4808DE6C.2090700@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).