W3C home > Mailing lists > Public > semantic-web@w3.org > March 2007

Re: yet another RDF vCard

From: Harry Halpin <hhalpin@ibiblio.org>
Date: Tue, 27 Mar 2007 01:14:51 -0400
Message-ID: <4608A84B.2000305@ibiblio.org>
To: Kjetil Kjernsmo <kjetil@kjernsmo.net>
Cc: Garret Wilson <garret@globalmentor.com>, semantic-web@w3.org

Apologies, been a bit swamped in GRDDL, but vCard will be updated once
we push GRDDL Primer and GRDDL Test Cases out the door...

However, the way we decided to deal with this was simply to use v:name
to deal with the whole name, and keep "v:n" for the "components" of a
name, but not put an xsd:string as the range - and this maps to the use
of vcard in the hcard microformat as well. Since many names do not map
easily, as you have rightfully pointed out, to the "components" of the
name, the way to sort names that have multiple components each with
their own sorting rules is simply to specify a "v:sort-string"

So, the current vcard proposal would have precisely what you said:


Of course, merging different name collations with differing sorting orders is difficult, requiring at least rules, and so beyond the scope of a simple RDF spec like the vcard ontology. 

I'm definitely interested in test-cases and examples for when I update the spec, so please do send them to me and the list.

Kjetil Kjernsmo wrote:
> On Monday 26 March 2007 21:16, Garret Wilson wrote:
>> On the other hand, though, the entire ontology has been so restricted
>> as to become hardly usable in an international environment. A case in
>> point is the v:Name class, which only allows a single instance of
>> each name component. The names-in-FOAF discussion has already pointed
>> to the Dublin Core analysis (
>> http://dublincore.org/documents/name-representation/ ) of the rich
>> variety of naming conventions around the world. The current
>> http://www.w3.org/2006/vcard/ns proposal could hardly handle the name
>> of His Majesty King Abdullah II bin Al Hussein of Jordan. Sure, I
>> know that we could take a couple of those name components, separate
>> them with commas, and stick them into one of the existing v:Name
>> components, but if we're going to do that why don't we do away with
>> the v:Name class altogether and stick a literal vCard string into one
>> component, like this:
>> <v:n>Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P."</v:n>?
> Actually, that's the topic that we devoted most of the time on an ad hoc 
> face to face meeting in Boston in January with TimBL, Harry Halpin and 
> myself present, as well as several others on IRC and phone. 
> Tim himself has a whole array of titles, and we discussed examples like 
> the one you had. We resolved that Harry would produce an update soon, 
> but I guess he has been swamped in other work. 
> But at least, you know that it is an active topic. 
> Best,
> Kjetil


Harry Halpin,  University of Edinburgh 
http://www.ibiblio.org/hhalpin 6B522426
Received on Tuesday, 27 March 2007 05:14:59 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:00 UTC