Re: [office-metadata] clarifying fields and metadata

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

On Mar 13, 2007, at 9:21 AM, Svante Schubert wrote:

>> That's different though. Here I presume you mean by meta:property  
>> essentially a display property. I'd expect that in many cases, that  
>> would be up to implementations to define, and it wouldn't be needed.
> By using especially the 'text:meta-label' instead of common ODF  
> elements using RDFa (like text:p or text:meta with about/property)  
> there is already a differentiation for this text-portion.
> This was the reasons to introduce this element. By doing so the  
> application has the chance to address and possibly view the content  
> differently.

Am just saying it should be an optional attribute.  Plug-ins, for  
example, would often have default rendering styles defined.

> Why not take 'meta:property' to describe the label you are using?

Because it's semantics are different. It encodes a predicate, while  
here you want to say which predicate to use for display.

> In case we would not have an extra citation field, the various forms  
> of citation fields could be distinguished by the RDF predicate.

Right, but if we consider my citation case, it might not make sense to  
define the display property there necessarily, except in situations  
where the display might be locally modified from the default (e.g. a  
user decides they want to suppress the author name on one particular  
citation).

Consider formatting rules like:

For citations, use "[author family name(s)], [year]:[cited pages]".

Where there are multiple references in a citation, sort by author-date.

Where there are multiple references in a citation from the same author,  
suppress author names for all but the first.

I'm not sure. Would you advocate *requiring* this?

<text:meta-label  
meta:classification="http://opendocument.xml.org/meta/fields/citation";>
(
<text:meta:label
	meta:about="urn:isbn:98347823"
	text:display-property="http://opendocument.xml.org/meta/fields/ 
citation#citation-full">Doe 1999</text:label>,
<text:meta:label
	meta:about="http://ex.net/1";
	text:display-property="http://opendocument.xml.org/meta/fields/ 
citation#citation-short">1999</text:label>
)
</text:meta:label>

>> I'd say we want an optional attribute called text:display-property.
> Could you define the function of a text:display-property attribute?

To define the content to display.

>> In any case, my example was the medical use case, where a doctor is  
>> adding triples to their content.
>>
>>> and moving the triple
>>> <http://ex.net/contacts/1> <http://medical.org/patient>  
>>> <http://ex.net/contacts/2> .
>>> into RDF/XML?
>>
>> This is an interesting question indeed.
>>
>>> IMHO by giving the label a RDF predicate describing the label the  
>>> need of the meta:resource is no longer given and the usage of less  
>>> attributes makes it easier for the user.
>>
>> It definitely doesn't make it "easier for the user", as in each case  
>> they want to make the same statement. From a UI standpoint it  
>> shouldn't make any difference really.
>>
>> I think if it makes it easier for anyone, it's us!
> ODF users might get confused, if there is a third attribute  
> meta:resource aside meta:about and meta:property or if there is only a  
> single meta:about.

No, but where it is is irrelevant. If they want to say person x is a  
patient of doctor y, they have to be able to say that. It doesn't  
matter how we encode it.

> Actually I was, when I first saw it. I really like the clearness and  
> consistency of one triple each element. My 2 cents.
>>
>> OK, let me propose a strawman for people to consider:
>>
>> text-meta-label = element text:meta-label { text-meta-label-attlist,  
>> generic-odf-text }
>>
>> # if property/resource are present, triple is defined in content
>> text-meta-label-attlist = meta-about, ( meta-property, meta-resource  
>> )?
>>
>> As Michael said, we also need the two other attributes.
>>
>> The question is whether we allow the statements in content, or  
>> whether we require them be stored in the RDF/XML and explicitly say  
>> in the proposal something about Svante's idea of "moving the  
>> triples".
> Svante