Metadata text fields

[Svante Schubert <Svante.Schubert@Sun.COM>]

Bruce had already answered correctly several questions regarding the
metadata text fields 'meta:text-set' and 'meta:text-get', I would like
to add in the following some comments and examples.

Scenario 1 - meta:text-set
This field sets a text as meta data (literal) and was named analog to
other ODF fields consisting of a 'set' postfix. There could be certainly 
other names for this field being proposed.

It is used, when in-content metadata should be attached to text, in 
other words when a text in the content is equal to the literal in the
metadata. This text might be editable or read-only - that's an
Office implementation detail. However, there might be a plug-in that 
provides a user interface that is customized for the mata data that 
shall be added.
This plug-in has furthermore the responsibility to keep the literal 
consistent with further metadata in the document (e.g. RDF/XML).

The text can be formatted in various ways, e.g. in a text "Patrick
Durusau" the capital letter might have a different color and therefore
the text might consist of various ODF elements.
The RDF object literal would be created by concatenating all text nodes
together.
Furthermore there might be different nested meta:text-set fields. The
example above might consist of three fields for name "Patrick", 
"Durusau" and "Patrick Durusau".

The new meta text field makes it easy for an ODF application to 
distinguish text portion, which have to be kept consistent with other 
metadata and should be made read-only, if no RDF application is 
available to guarantee consistency.


Scenario 2 - meta:text-get
This field displays a label generated from a RDF application (plug-in) 
based on existing metadata in the content.

The field was named analog to other ODF fields consisting of a
'get' postfix. There could be certainly other names for this field being 
proposed.

An example for this field are citation fields, which might
be expressed in different ways as a 'long' or 'short' citation field.
The user could configure the layout of this field, which would be
created based on metadata. Furthermore, could the user exchange the
layout for all fields by the plug-in, which would exchanged the fields
for all occurrences in the text.

The mapping of metadata to label is based on a algorithm known by the
plug-in. This algorithm might be quite complex, e.g. the label 'last
Friday of the year' might be based on a date and created by a plug-in.
In case the plug-in is not available to handle this field, the label
should be made read-only, although this might be implementation specific.

Hope that could clarify some things.
Best regards,
Svante