Re: [office-metadata] Metadata text fields

[Bruce D'Arcus <bruce.darcus@OpenDocument.us>]

On Feb 23, 2007, at 10:12 AM, Elias Torres wrote:

...

>> You are proposing simply that it be the string "Patrick Durusau". So
>> we define the content of in-content literals as a string, rather than
>> an XML literal say.
>>
>> This is indeed something we need to decide.
>
> Right. In RDFa, currently, when you get the element's content as a 
> literal,
> it's an XMLLiteral. However, there's this poorly defined
> datatype="plaintext" that does what you want: to get just the text 
> content
> all of the element. We might need to improve on RDFa, but that's a 
> better
> way than forcing everything to a single element to get that behavior as
> opposed to adding just an attribute.

And we've already said a data-type property would be valuable, so 
problem solved (though we might want to specify a default data-type?).

...

>> So I wonder why we don't forget about this field, and just allow the
>> literal pattern to appear on some specific list of elements? We
>> might, then ....
>>
>>> Scenario 2 - meta:text-get
>>> This field displays a label generated from a RDF application (plug-
>>> in) based on existing metadata in the content.
>>
>> ... have one new field whose job it is to display information about
>> *resources*.
>>
>> I want to say in my document that Patrick is the author, but I have
>> Patrick vCard record already in RDF/XML in the package, so I do
>> something like:
>>
>> <meta:field
>>    meta:about="urn:uuid:8134713815475740574" <!-- document URI -->
>>    meta:property="dc:creator"
>>    meta:resource="http://ex.net/people#patrick";>Patrick Durusau</
>> mta:field>
>
> +1. From what I gather from Svante's email we definitely need a 
> read-only
> solution for both ODF applications and plug-ins to have space in the
> content to render content. But that's very different from *actually*
> encoding information. I'd would go as far as suggestion that all we 
> need
> is:
>
> <meta:field
>     meta:id="foo">Patrick Durusau
> </meta:field>
>
> If the plugin is not present, then ODF application renders the content 
> of
> the field, else the plug-in(s) can find their metadata in the RDF/XML
> files.

So this is actually similar to Svante's earlier impulse for some 
indirection, right?

How would you encode the RDF/XML in this case?

Bruce