OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-metadata] clarifying fields and metadata




>>>> 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?
To me it seems as we are trying to add two RDF statements in one 
text:meta-label (= the new attribute name is fine for me).

I assume that "Jane Doe" is the patient, who is described as 
"http://ex.net/contacts/2";.
Why not say the following:

    <text:meta-label
        meta:about="http://ex.net/contacts/2";
        meta:property="ex:salutation">Dear Jane Doe</text:meta-label>

and moving the triple
<http://ex.net/contacts/1> <http://medical.org/patient> 
<http://ex.net/contacts/2> .
into RDF/XML?

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.

Svante


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]