[
https://issues.apache.org/jira/browse/SHINDIG-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655225#action_12655225
]
Chris Chabot commented on SHINDIG-768:
--------------------------------------
if i'm not mistaken the person name changes were discussed in much detail on
the mailing list, and not all of these changes are valid after all.
Could you possibly sift through the mails in the shindig mail archives and find
out what we should or shouldn't adjust?
sorry for all the confusion ;/
> change name field from "formatted" to "unstructured"
> ----------------------------------------------------
>
> Key: SHINDIG-768
> URL: https://issues.apache.org/jira/browse/SHINDIG-768
> Project: Shindig
> Issue Type: Bug
> Components: RESTful API (PHP)
> Reporter: Pan Jie
> Priority: Minor
> Attachments: 20081205.patch
>
>
> Same with SHINDIG-764, r723617
> Original description:
> According to
> http://www.opensocial.org/Technical-Resources/opensocial-spec-v081/opensocial-reference#opensocial.Name,
> the opensocial Name object must support
> the following fields:
> ADDITIONAL_NAME
> FAMILY_NAME
> GIVEN_NAME
> HONORIFIC_PREFIX
> HONORIFIC_SUFFIX
> UNSTRUCTURED
> "UNSTRUCTURED" is missing and "FORMATTED" is added.
> Also fixes unittest for address UNSTRUCTUREDADDRESS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
