Re: [office] Fwd: [dev-biblio] metadata implementation ideas

[Patrick Durusau <patrick@durusau.net>]

Bruce,

Bruce D'Arcus wrote:
> Interesting question about what to do with the existing element for
> citations. I see a few options:
>
> 1) deprecate it in ODF and associated implementations (AFAIK, only OOo
> supports it) in favor of text:meta-field
>
> 2) change it to accept xml:id and behave like text:meta-field.
>
Well, I really don't like different elements with the same 
semantics/behavior as defined by a standard. It is an unnecessary 
complication.

ODF 1.2 should deprecate it. With a note that it will not survive in ODF 
1.3. Just as fair warning.

Hope you are having a great day!

Patrick

> My hunch is 1 is preferable. Any thoughts?
>
> Bruce
> ---------- Forwarded message ----------
> From: Gannon Dick <xxxx@yahoo.com>
> Date: Jul 5, 2007 6:52 PM
> Subject: Re: [dev-biblio] metadata implementation ideas
> To: dev@bibliographic.openoffice.org
>
>
> So, will the legacy <text:bibliography-mark> tag be preserved or not in
> the OpenOffice Writer ?
>
> --- Bruce D'Arcus <bdarcus@gmail.com> wrote:
>
>> The ODF TC has in principle approved enhanced metadata support [1]
>> for
>> ODF 1.2. This is fantastically cool stuff, and gives ODF:
>>
>> 1. a simple, flexible, and extensible data model (RDF)
>> 2. the ability to use it to describe not just the document, but
>> pieces
>> within the document (tables, images, etc.), including ...
>> 3. a new generic field
>>
>> WRT to implementing it in OOo, some suggested reading:
>>
>> <http://www.idealliance.org/proceedings/xtech05/papers/04-01-04/>
>> <http://librdf.org/>
>>
>> Redland seems to have the characteristics that would be good for OOo:
>>
>> flexible licensing, builds as C++, can use expat or libxml as the xml
>>
>> parser, support for contexts (allows named graphs), and it's mature.
>>
>> There are also mature libraries in Java as well, but I'm assuming
>> that'd
>> be less ideal given OOo's C++ base.
>>
>> So upon loading an ODF 1.2 metadata-enhanced file, OOo would just
>> load
>> each RDF file into an in-memory model as a subgraph, work with the
>> data
>> as needed using the Redland APIs, and then write it back out on save.
>>
>> Because of the context support, Redland can track which file to write
>>
>> which statements to.
>>
>> So, for example, I imagine citation support would use the new generic
>>
>> text:meta-field and deal with two subgraphs: one for the field per se
>>
>> (written to "citations.rdf"), and the other for the bibliographic
>> source
>> metadata ("bibliography.rdf").
>>
>> Anyway, just some ideas ...
>>
>> Bruce
>>
>> [1]
>>
> <http://www.oasis-open.org/committees/download.php/24327/ODF-Metadata-Proposal.pdf> 
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@bibliographic.openoffice.org
>> For additional commands, e-mail:
>> dev-help@bibliographic.openoffice.org
>>
>>
>
>
>
>
> ____________________________________________________________________________________ 
>
> Looking for a deal? Find great prices on flights and hotels with
> Yahoo! FareChase.
> http://farechase.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@bibliographic.openoffice.org
> For additional commands, e-mail: dev-help@bibliographic.openoffice.org
>
>

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Acting Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Co-Editor, OpenDocument Format (OASIS, ISO/IEC 26300)