On 9/21/06, Jakob Lechner <[EMAIL PROTECTED]> wrote:
Am Dienstag, den 19.09.2006, 08:50 -0400 schrieb Bruce D'Arcus:
> [...]
>
> Can you give me some specific use case examples that might benefit
> from such a generic structured metadata field? Citations is one. I
> could imagine contacts would be another, where you link to a contact
> record.
Let's say we have an OOo document with embedded metadata that
can be altered inline. A possible use case would be an external
application that could access the OOo document and read the embedded
metadata and use it for some other task (store it in a database).
Maybe you want to write a report in a firm. You have a document that
includes fields like "author", "subject", "date", "importance", "short
description", etc.
Then this report could be automatically processed and the field values
could be fed into a some sort of report db.
Nice!
I will try to implement some sort of prototype to show what is possible.
I'd like to start with the front-end for fields that includes GUI
adaption and data structures for managing fields that are inserted into
the document.
The back-end, i.e. the actual data source and the interface between
front-end and back-end could be done in a separate step.
Yes, that makes sense.
I'd be glad for any proposals or hints about things that I should take
care of.
See the archive I have attached to the message archived at this link.
<http://lists.oasis-open.org/archives/office-metadata/200608/msg00016.html>
It reflects how I've been thinking about storing the metadata. So
basically there are domain or feature specific metadata files that get
registered in the manifest with a "text/rdf+xml" mimetype, and I
imagine specific functionality could be responsible for different
chunks of metadata (though because a common model, they could be
linked).
Let me know if you have any thoughts about that, and about the field
to link to it.
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
