On 14/08/10 11:02, James Cummings wrote:
> On 14/08/10 02:15, Martin Holmes wrote:
>> Actually, I appreciate the decision to produce just a listBibl. I'm
>> always going to be copy/pasting this stuff into another document, and
>> it's nice not to have to wade through all the prefatory bits.
> Interesting... I was thinking that I'd probably do the very same thing
> and thus thinking that such metadata would be even more important. ;-)
> (why not XInclude just the listBibl?) But ok, maybe either an option
> to toggle on/off whether you want it full or not, or at least an XML
> comment at the top containing a note of things like date exported?
Well yes, creating full TEI docs and just fragments are basically the
two directions I found very hard to decide upon. What, nevertheless,
hasn't occurred to me was the idea to put the <listBibl> into the body
and basically have meta-data describing the meta-data. But I really see
your point, one file's meta-data might be another file's data.
For my use cases I like the fact that I just have a file with my
listBibl, so the XInclude is as simple as possible. I usually try to
stick to very simple includes since I once had a rather complex setup
with XPointers and xml:ids and tried to switch to a different processor
and had to realize that the extent to which XIncludes/XPointers are
implemented vary very much. Therefore I reverted to plain TEI fragments
when splitting files in several parts. I think it might be a good idea
to have the wrapping meta-meta-data as an optional wrapper.
btw. What, apart from creation date and user (where does Zotero store
this, I don't know), would be interesting for you? I am only thinking,
of course, of the things that could be extracted from Zotero.