Re: [foaf-dev] Wishlists / requests for next rev of FOAF spec?

yes, it would be great to see FOAF evolve

A first thing to do would be to validate or remove all the properties with =
"testing" status.
(foaf:phone, foaf:skypeD, foaf:thumbnail ...)

Also, I've got a hard time finding elsewhere a generic class for describing=
 "a mean of contact", and have a proposal for a new class. =

Let me explain that :

When you list people's personal means of contact like phone number, skypeID=
 or emails, you might need to store some meta-info with each Contact, such =
as "call only after 8PM" or "professional email", think about other stateme=
nts about provenance or privacy.
With properties like foaf:mailbox or foaf:phone, you can only do that using=
 blank nodes. =

I stayed away from them until now, and don't feel like starting to use them.

There's something related but half-baked in vcard ontology, where there's a=
 v:Tel class (with subclasses)

I'd like a more generic class, like "foaf:Contact" so other triples could b=
e linked to it easily. We could describe it as a phone number, mobile phone=
, skype, or whatever chat-service-brand-name-to-come using sub-classes of t=
his Contact class.
vcard:Tel could be a subclass of foaf:Contact

Actually, it's very similar to foaf:OnlineAccount which is just semanticall=
y restricted to "online" means of contact. foaf:OnlineAccount could also be=
 a subclass of foaf:Contact.

a property foaf:hasContact could then connect it with any foaf:Agent

(my 0.2=80...)

--
Dominique Guardiola, QUINODE
=95 http://www.quinode.fr/
=95 Tel : 04.27.86.84.37
=95 Mob : 06.15.13.22.27