Awesome job going through that Jacky!

The list looks quite comprehensive, and more importantly, correct too me.
Since this affects both the spec and the php and java reference
implementations I would like to invite everyone to take a quick gander at
the spreadsheet, and once we all agree about what is or isn't correct, we
can go and make the adjustments that are required.

Wha'da'ya'all think?

    -- Chris


>
>
> On Fri, Jun 12, 2009 at 3:25 PM, Jacky <jacky.chao.w...@gmail.com> wrote:
>
>>
>> Hi All,
>>
>> I'm doing the poco alignment for PHP Shindig recently.  When reading
>> through the spec, I found some small mistakes on the 0.9 RESTful spec
>> as following:
>>
>> - in 3.2 Person / 3.3 Group / 3.4 Activity / 3.5 AppData
>>  All items should use "entry" in XML format, instead of "person",
>> "group", "activity" or "appdata".
>>
>> - need to change all "Singluar" into "Singular".
>>
>> - Sometimes the description and XML schema are not consistent.
>>  I've composed a complete side-by-side comparison matrix of Portable
>> Contacts, OpenSocial 0.9 Spec (description), OpenSocial 0.9 XML
>> schema, Java Shindig and PHP Shindig on http://bit.ly/PocoAlignment.
>> And it seems like the following attributes need to be adjusted:
>>
>> Person: age, appdata, hasApp
>> Name: additionalName
>> Address: extendedAddress, poBox, primary
>> Organization: address, field, location, primary, salary, subField,
>> webpage
>> Account: primary
>>
>> Thanks,
>> - Jacky
>> --~--~---------~--~----~------------~-------~--~----~
>> You received this message because you are subscribed to the Google Groups
>> "OpenSocial and Gadgets Specification Discussion" group.
>> To post to this group, send email to
>> opensocial-and-gadgets-s...@googlegroups.com
>> To unsubscribe from this group, send email to
>> opensocial-and-gadgets-spec+unsubscr...@googlegroups.com<opensocial-and-gadgets-spec%2bunsubscr...@googlegroups.com>
>> For more options, visit this group at
>> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en
>> -~----------~----~----~----~------~----~------~--~---
>>
>>
>

Reply via email to