You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Jacky Wang (王超)" <ch...@google.com> on 2009/06/12 15:36:00 UTC
Poco alignment: some minor mistakes need to be changed on the 0.9
RESTful spec?
Hi All,
I'm doing the poco alignment for PHP Shindig recently. When reading through
the spec, I found some in-consistence between the spec and the
implementation.
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.
For some tricky cases, like person.age, person.anniversary, etc. I still
don't know whether we should keep them or throw them away...
Any ideas?
Thanks,
- Jacky
--
Best Regards,
Jacky Wang
+86-10-6250-3316
+86-1381-0018-677
chaowang@google.com
Re: Poco alignment: some minor mistakes need to be changed on the 0.9
RESTful spec?
Posted by "Jacky Wang (王超)" <ch...@google.com>.
Thanks for the input! I've forwarded your mail to opensocial spec group @
http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/dab9259d623c1397/bc704b41e6f5672b#bc704b41e6f5672b
Let's finalize the decision. :D
Thanks,
Jacky
2009/6/16 Joseph Smarr <js...@gmail.com>
> Ok I've added a "Joseph Smarr's feedback" column and put notes in for all
> the current descrepencies. Looks like it should be pretty painless to get
> things fully aligned!
>
> Two things to keep in mind throughout this process:
>
> 1) The goal of the alignment, as per the spec, is that "*any compliant
> OpenSocial RESTful Protocol 0.8.1 [or greater] Provider is also a compliant
> Portable Contacts Provider*". In other words, OS must be a strict superset
> of PoCo, but PoCo need not include every field in OS (since OS is tackling a
> wider scope, and the goal is that the subset of OS that relates to PoCo
> should be the same so developers can talk to an OS API just like a PoCo-only
> API).
>
> 2) This alignment was fully agreed-to back when drafting 0.8.1, so any
> outstanding descrepencies are bugs that should have been fixed a while ago,
> but we just missed (until we were fortunate to get such a detailed
> inspection from Jackie!). So as was mentioned before, let's try to keep the
> discussion focused on the execution of fixing these bugs--we're so close
> already! :)
>
> Thanks! js
> On Fri, Jun 12, 2009 at 6:36 AM, Jacky Wang (王超) <ch...@google.com>wrote:
>
>> Hi All,
>>
>> I'm doing the poco alignment for PHP Shindig recently. When reading
>> through
>> the spec, I found some in-consistence between the spec and the
>> implementation.
>>
>> 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.
>>
>> For some tricky cases, like person.age, person.anniversary, etc. I still
>> don't know whether we should keep them or throw them away...
>>
>> Any ideas?
>>
>> Thanks,
>> - Jacky
>>
>>
>> --
>> Best Regards,
>>
>> Jacky Wang
>> +86-10-6250-3316
>> +86-1381-0018-677
>> chaowang@google.com
>>
>
>
--
Best Regards,
Jacky Wang
+86-10-6250-3316
+86-1381-0018-677
chaowang@google.com