Danny Ayers <dann...@gmail.com> Thu, 29 Nov 2007 10:30:05
In passing I'll note that Julian's list:
- Local system ID (in this OpenSocial Container)
- Email-1, Email-2, Email-n, (optionally obfuscated with SHA1)
- OpenID-1, OpenID-2, OpenID-n,
- Unique ID on Service S as multiple pairs. eg Facebook-501829088,
Twitter-jbond, Skype-julian.bond, etc
- is already covered by FOAF.
Which is a strong case for containers to routinely include the FOAF
namespace and FOAF data in their implementations of the People Data API.
Same goes for VCard.
Google. Please pay attention to this discussion. The current People Data
API is thin. And gd:extendedProperty isn't enough.
The other issue I have is about schemes for what data to include.
There's a FOAF convention to provide a single file for a person
containing:-
- Full data about that person
- Limited data about their friends, linking to the full file for each.
The People Data spec seems to suggest two files.
1) Full data about a single person
2) Full data about their friends but not including them.
I prefer the FOAF layout.
8 messages in com.googlegroups.opensocial-containerRe: [OpenSocial] Re: Towards a univer...