[
https://issues.apache.org/jira/browse/SHINDIG-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Smarr updated SHINDIG-538:
---------------------------------
Attachment: shindig-pc-diff.txt
Here's a patch to shindig-php to bring its request parametrs and output schema
into alignment with PortableContacts. This change does not add OAuth support,
but does pretty much everything else needed to align the specs.
Specifically, this change contains:
- refactoring model classes with generic ListField for plural fields and
ComplexField interface for complex fields
- updating schema classes (add ims, accounts, displayName, consolidate
schools/jobs in organizations, standardize on value as main sub-field, etc.)
- renaming profileDetails to fields and standardizing its value as a map from
fieldName => 1 for each field
- standardizing on @all as the special field-value that means "return all
available fields"
- added new CollectionsOptions class to hold all filtering/sorting/paging
request options (ala Java shindig)
- outputting itemsPerPage in JSON mode
- adding pretty-print JSON output option (not currently hooked up to a query
option, but could/should be)
- framework for declining a request for filtering/sorting/updatedSince and
specifying such in the output
- properly url-decoding query parameters when constructing request info
BTW, I have a corresponding patch ready for the partuza test-container that
implements these new changes, which I will separately submit to the partuza
project.
> PortableContacts alignment
> --------------------------
>
> Key: SHINDIG-538
> URL: https://issues.apache.org/jira/browse/SHINDIG-538
> Project: Shindig
> Issue Type: Bug
> Components: RESTful API (PHP)
> Reporter: Chris Chabot
> Priority: Blocker
> Attachments: shindig-pc-diff.txt
>
>
> In the 0.8.1 spec revision we decided to align the OpenSocial REST API with
> PortableContacts to improve data portability.
> This means both the src/social-api/opensocial/model's, and the service
> adapter return structure changed to match the specifications.
> See http://portablecontacts.net/draft-spec.html for an overview on
> PortableContact's spec, and
> http://docs.google.com/View?docid=dcc2jvzt_37hdzwkmf8 for some of the changes
> this had on how the REST protocol works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
