[ 
https://issues.apache.org/jira/browse/SHINDIG-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen updated SHINDIG-1878:
----------------------------------

    Description: 
Version 2.5 of OS is out. I've done a comparison between the data/model 
entities currently in code and the specification and found several 
discrepancies listed out in an attached file.


  was:
Version 2.5 of OS is out. I've done a comparison between the data/model 
entities currently in code and the specification and found several 
discrepancies listed out below.

Primary Social Data:

Activity
        entity is deprecated
        titleId field no longer exists
        updated field no longer exists
ActivityStreams
        no issues
AppData
        no issues
Group
        no issues
Message
        type is a string, not an enumeration
Person
        some plural fields, such as accounts, addresses, appData are List<?>, 
while others are List<ListField>
        thumbnailUrl is a Url, inconsequent with other Urls like profileSong 
and profileVideo
        Missing mandatory properties:
                alternateNames
                connected
                contactPreference
                dn
                location
                nativeName
                preferredName
                published
                relationships
                updated
        Optional properties:
                anniversary is missing
                bodytype is a string, not an enumeration
                children is a Plural-Field<String>, not a string
                drinker is a string, not an enumeration
                gender is a string, not an enumeration
                lookingFor is a string, not a list of enumerations
                note is missing
                pets is a Plural-Field<String>, not a string
                orgIdentifier is missing
                politicalViews is a Plural-Field<String>, not a string
                smoker is a string, not an enumeration

Additional Social Data:

Account
        no issues
ActionLink 
        is completely missing
ActivityObject
        no issues
Address
        building is missing
        floor is missing
        primary field does not exist
Album
        no issues
AppId
        no issues
FieldMetadata
        is completely missing
GroupId
        no issues
MediaItem
        duration is an integer value, not a string
        file_size is a long value, not a string
        num_comments is an integer value, not a string
        num_views is an integer value, not a string
        num_votes is an integer value, not a string
        rating is an integer value, not a string
        tagged_people is a List<String>, not a string
        tags is a List<String>, not a string
        url is a string, which is inconsequent with the use of URLs in other 
entities
MediaLink
        url is a string, which is inconsequent with the use of URLs in other 
entities
Name
        additionalName does not exist
        middleName is missing
        pronunciation is missing
        pronunciationUrl is missing
ObjectMetadata
        is completely missing
Organization
        department is missing
        endDate could also be a string, not a date only
        location is missing
        primary field does not exist
File
        is completely missing
PropertyMetadata
        is completely missing



moved original comments to a separate file as to keep formatting.
                
> Discrepancy between OpenSocial spec 2.5 and Shindig 
> ----------------------------------------------------
>
>                 Key: SHINDIG-1878
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1878
>             Project: Shindig
>          Issue Type: Bug
>    Affects Versions: 2.5.0-beta4
>            Reporter: J.W. Janssen
>         Attachments: SHINDIG1878.txt
>
>
> Version 2.5 of OS is out. I've done a comparison between the data/model 
> entities currently in code and the specification and found several 
> discrepancies listed out in an attached file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to