clarifying fields and metadata

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

This is a bit of a followup to the question about in content resource 
references from the other day. Let me summarize where I think we're at 
with the current proposal draft:

We have basically ways to tie content to metadata.

1) RDFa-like attributes, but which are constrained to represent 
literals. The purpose here it o create RDF statements out of content in 
the document. Example:

	<text:p
		meta:about="http://ex.net/1";
		meta:property="http://ex.net/foo";>bar</text:p>

This would generate the triple:

	<http://ex.net/1> <http://ex.net/foo> "bar" .

I think we've all gotten comfortable enough that there are 
circumstances where this will be valuable.

2) A new field (currently called meta:label) whose purpose is only to 
attach statements to content. This is really just a field tied to 
RDF/XML data, where the content of the element is generated from that 
data, and serves as a label. But there are no formal semantics 
associated with it. The attributes are a little unclear to me still, 
but think something like:

	<meta:label meta:about="http://ex.net/1";>Jane Doe</meta:label>

But we're missing something which is really a sort of hybrid situation: 
in content metadata which may be field-like. From one of our (medical) 
use cases:

	<meta:label
		meta:about="http://ex.net/contacts/1";
		meta:property="http://medical.org/patient";
		meta:resource="http://ex.net/contacts/2";>Jane Doe</meta:label>

This would generate a triple of course:

		<http://ex.net/contacts/1> <http://medical.org/patient> 
<http://ex.net/contacts/2> .

So my question is really how we define #2 formally in ODF?

Bruce