From: "Bruce D\\'Arcus" <bdarcus.lists@gmail.com>
Subject: Re: bib amd mods
Date: Tue, 20 Jun 2006 17:25:10 +0000 (UTC) [thread overview]
Message-ID: <loom.20060620T191304-386@post.gmane.org> (raw)
In-Reply-To: <44982967.8050201@wxs.nl>
Hans Hagen <pragma <at> wxs.nl> writes:
> since we're talking databases here, i think the focus should be on what
> kind of (intermediate) format suits typesetting best (could be different
> from the databse structure)
There may be trade-offs, but if you get too typesetting-oriented,
you cause other problems.
[...]
> but that's still the database part of it, isn't it ( i never really used
> rdf - only looked at it)
An example description:
<Paper rdf:about="http://ex.net/1">
<title>Paper</title>
<author>
<Person>
<givenName>John</givenName>
<familyName>Smith</familyName>
</Person>
</author>
<presentedAt>
<Conference>
<title>ABC Conference</title>
<endDate>2004-03-12</endDate>
<startDate>2004-03-15</startDate>
</Conference>
</presentedAt>
</Paper>
This is indeed more "database-oriented", complete with the capability
to normalize all of that by breaking out persons and such into separate
descriptions and linking them. But it's not hard to process for
formatting either (easier than MODS I think).
> so csl is the formatting spec thing (the oo site is not that
> informative; i always like to *see* code -)
Correct. Subversion repo for the entire project (including schema
for CSL, and the start of a Ruby port of citeproc) is here:
<http://sourceforge.net/svn/?group_id=117435>
Bruce
next prev parent reply other threads:[~2006-06-20 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 14:17 Hans Hagen
2006-06-20 15:19 ` Ulf Martin
2006-06-20 16:01 ` Bruce D'Arcus
2006-06-20 16:59 ` Hans Hagen
2006-06-20 17:25 ` Bruce D\'Arcus [this message]
2006-06-20 17:19 ` Ulf Martin
2006-06-20 17:40 ` Bruce D'Arcus
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=loom.20060620T191304-386@post.gmane.org \
--to=bdarcus.lists@gmail.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).