Re: bibliographic issues

From: Alf Eaton <alf_at_hubmed.org>
Date: Tue, 2 Aug 2005 15:56:56 +0200

On 02 Aug 2005, at 15:47, Eric Miller wrote:

>
> On Aug 2, 2005, at 9:35 AM, Alf Eaton wrote:
>
>
>> On 02 Aug 2005, at 15:24, Eric Miller wrote:
>>
>>
>>
>>> Getting various content providers to agree on *a few* properties
>>> when it comes to describing peoples for bibliographic
>>> description, however, is a small but useful step. For the content
>>> providers that are reading this list, I'm wondering if the
>>> following might be a simple core folks could agree on...
>>>
>>> <foaf:Person>
>>> <rdf:value>Jim Gettys</rdf:value> <!-- default value for apps
>>> that don't know foaf -->
>>> <foaf:givenname>Jim</foaf:givenname>
>>> <foaf:surname>Gettys</foaf:surname>
>>> </foaf:Person>
>>>
>>> Alf, Matthew? others? What do you think?
>>>
>>>
>>
>> I think the description of a person's name needs to have 3 fields
>> (at least): 'name', 'given name' and 'family name'.
>>
>
> Can you explain what what you mean by 'name' is in the above sentence?
>
> The RDF/XML example above uses the rdf:value as a 'default' value
> for a particular resource. In the above case this is useful when
> applications consume this snippet of data but don't really know
> anything about the foaf properties (think 'alt' attribute
> associated with HTML 'img' element). I'm wondering if this serves
> the same function as what you mean by 'name'?

Yes, by 'name' I mean the same as you have in rdf:value, or what FOAF
calls foaf:name (as opposed to foaf:nick) and vCard calls vcard:FN.

alf.
Received on Tue Aug 02 2005 - 13:53:40 EDT

This archive was generated by hypermail 2.3.0 : Thu Aug 09 2012 - 16:39:18 EDT