Portable Contacts

[Evan Prodromou]

We've had some good experience blending http://portablecontacts.net/ data into Activity Streams "person" objects for StatusNet.

Can I suggest we use "portablecontacts_net" as the extension namespace for this specification? I think that's all we need.

It is unfortunate that our native "person" schema is so weak. For most important contact data, I suspect we're going to be spreading our efforts over schema_org, opengraph, and portablecontacts_net namespaces.

Maybe we need to promote a san subset of these schemata into ActivityStreams "person"?

-Evan

[Evan Prodromou]

"sane subset".

-Evan

[James M Snell]

"portablecontacts_net" works... "poco" might also work... 

However, I think defining some sane subset as you suggest would be fine also. The thing I want to avoid, however, is coming up with Yet Another Person Model. There are already too many around and whatever we define for person, it's not likely to become The Defacto way of doing it. Continuing to leverage external vocabularies like schema.org is the Right Thing To Do, I think.

- James

-Evan

--
You received this message because you are subscribed to the Google Groups "Activity Streams" group.
To view this discussion on the web visit https://groups.google.com/d/msg/activity-streams/-/Zq_63pnZpLAJ.
To post to this group, send email to activity...@googlegroups.com.
To unsubscribe from this group, send email to activity-strea...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/activity-streams?hl=en.

[Joseph Smarr]

Yeah I think "poco" or "portablecontacts" would be fine. I doubt anyone is gonna release a competing spec at a different TLD. ;) 

Glad to hear it's working well for you! People often ask me "what's new with PoCo", and I say "not much...I think we nailed it already!" :D

[Kevin Marks]

The opensocial crew already integrated poco and activity Streams, probably worth checking how they got on.

[Kevin Marks]

I'd push back against using schema.org as it has a weird inheritance model. (volcanoes have fax numbers)
PoCo was based on actually existing fields in social networks and addressbook standards.

Vcard 4 picked up a fair bit of the PoCo work.

[Joseph Smarr]

Alternatively, the schema.org folks have been quite responsive to input on improving their people schema given the PoCo learnings, so I've been meaning to push on that (but haven't gotten around to it yet).