You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Pan Jie (JIRA)" <ji...@apache.org> on 2008/12/05 20:46:44 UTC
[jira] Created: (SHINDIG-768) change name field from "formatted" to
"unstructured"
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.
[jira] Commented: (SHINDIG-768) change name field from "formatted"
to "unstructured"
Posted by "Chris Chabot (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SHINDIG-768) change name field from "formatted"
to "unstructured"
Posted by "Adam Winer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673394#action_12673394 ]
Adam Winer commented on SHINDIG-768:
------------------------------------
Should probably be closed as invalid. The wire format and JS APIs *are not* the same thing in 0.8.1. Formatted is the right term for the wire format, which the PHP code is (I assume) dealing with. The JS automatically swaps in "unstructured".
> 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: 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.
[jira] Resolved: (SHINDIG-768) change name field from "formatted"
to "unstructured"
Posted by "Paul Lindner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lindner resolved SHINDIG-768.
----------------------------------
Resolution: Invalid
> 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: 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.
[jira] Updated: (SHINDIG-768) change name field from "formatted" to
"unstructured"
Posted by "Pan Jie (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pan Jie updated SHINDIG-768:
----------------------------
Attachment: 20081205.patch
> 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.