Hi Sean,

I talked to my colleagues that work with PoCo, they will follow up in
the other group.

Thanks,
Julian.

On Mar 30, 10:31 pm, Sean Sullivan <[email protected]> wrote:
> I posted the bug report on the portablecontacts mailing list before I
> posted it on google-contacts-api.
>
> Joseph Smarr (the PoCo spec lead) suggested that I send the bug report
> to Google.   If google-contacts-api is not the appropriate channel,
> can you direct me to the correct channel?
>
> Sean
>
> On Mon, Mar 30, 2009 at 2:20 AM, Julian (Google) <[email protected]> wrote:
>
> > There is a specific group for PoCo, I recommend you to post there:
> >http://groups.google.com/group/portablecontacts
>
> > Thanks,
> > Julian
>
> > On Mar 29, 3:55 am, Sean Sullivan <[email protected]> wrote:
> >> Hello,
>
> >> I sent a couple of requests to Google's Portable Contacts endpoint. I
> >> noticed that Google's XML response contains a <person> element:
>
> >> <?xml version="1.0" encoding="UTF-8"?><response
> >> xmlns="http://ns.opensocial.org/2008/opensocial";><person
> >> xmlns="http://ns.opensocial.org/2008/opensocial";>
> >>  <displayName>Joe The Plumber</displayName>
> >>  <emails>
> >>    <type>CUSTOM</type>
> >>    <value>[email protected]</value>
> >>  </emails>
> >>  <id>118910240772174568914</id>
> >>  <name>
> >>    <familyName>The Plumber</familyName>
> >>    <givenName>Joe</givenName>
> >>  </name>
> >>  <nickname>Joe</nickname>
> >> </person></response>
>
> >> The PoCo specification doesn't define a <person> element.  Instead,
> >> PoCo defines an element called <entry>
>
> >> Can you fix this bug?
>
> >> Thanks.
>
> >> Sean
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Contacts API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-contacts-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to