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

Hello,
      I was thinking of foaf:account and foaf:onlineAccount, the latter of
which is unstable but it says it is preferable to using foaf:account for
online accounts.  Also one thing that might be good is to have a more clear
term (or have an additional term) than foaf:accountServiceHomepage.  For
example, I might want to list my url on facebook, linkedin, where I have
both a userid and a profile link.  Foaf:accountServiceHomepage seems like it
would be http://facebook.com/ or http://linkedin.com and not
http://facebook.com/myname - when you read the text for these properties
that is what is described, so it isn't clear what one would use for one's
profile page associated with the online account.
      It would be good to have a mapping between foaf and vcard.  There is a
term in the Open Vocabulary for businessCard.  Maybe this could be
incorporated into foaf.  The domain of vcard is not foaf:Person, it is
vcard:Vcard, a class.  I suggest a foaf:hasVcard which would link to the
vCard class associated with a person.  
      Similarly, a foaf:resume or foaf:cv to link to a person's resume/cv.  

Thanks,
Bruce
         
  
 

-----Original Message-----
From: foaf-dev-bounces-RyYwo1q5J+qsOXdr9/[email protected]
[mailto:foaf-dev-bounces-RyYwo1q5J+qsOXdr9/[email protected]] On Behalf Of Bob Ferris
Sent: Tuesday, June 12, 2012 3:16 AM
To: foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]
Subject: Re: [foaf-dev] Wishlists / requests for next rev of FOAF spec?

Hi,

On 06/03/2012 09:49 PM, Kjetil Kjernsmo wrote:
> On Wednesday 30. May 2012 18.00.26 Dan Brickley wrote:
>> Yeah, it's about time we shipped a new one.
>>
>> Anyone else got suggestions?
>
> I always wanted a foaf:personal_phone, which would be a subproperty of 
> foaf:phone and an IFP/key/or something. My phone number is probably 
> one of my strongest identifiers these days.
>
> Also, perhaps some terms should change status. I would suggest the 
> following upgraded to stable:
> foaf:Document
> foaf:Image
> foaf:based_near
> foaf:depiction
> foaf:depicts
> foaf:img
> foaf:mbox_sha1sum
> foaf:name
> foaf:nick
> foaf:page
> foaf:phone
> foaf:schoolHomepage
> foaf:thumbnail
> foaf:topic_interest
> foaf:weblog
> foaf:workplaceHomepage

+1 for upgrading the majority of these terms to stable. However, I would
exclude the homepage relations (foaf:schoolHomepage and
foaf:workplaceHomepage), because one would rather link a workplace and/or
school resource today (which can even have a more detailed description), or?
Re. modelling the "like" relation, I would also suggest to have a look at
the Association Ontology [1], whose approach was a bit different because it
modelled the "like" relation from the object direction and which is a bit
more verbose.

Cheers,


Bo


[1] http://purl.org/ontology/ao/core#
_______________________________________________
foaf-dev mailing list
foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]
http://lists.foaf-project.org/mailman/listinfo/foaf-dev