OpenSocial RESTful and Social Apps, some strange things.

[gabrie...@gmail.com]

1)
Why do we have differences between "social apps" and "RESTful"
(I mean for example: http://opensocial-resources.googlecode.com/svn/spec/0.8/opensocial/person.js)

And Restful Protocol 0.81
Where I have for example ArrayOfIm
<xs:element minOccurs="0" name="ims" type="tns:ArrayOfIm"/>

Would these differences be fixed on person.js 0.81?

2)
Why do I have on Restful XSD 0.81
<xs:complexType name="ArrayOfAccount">
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" name="account"
type="tns:account" />
</xs:sequence>
</xs:complexType>

That is not used? (We only have one Account)

protected Account accounts; ==> With a "s" at the end of accounts...

(I use JAXB XSD<->Java Mapper)

[Scott Seely]

The RESTful Person is supposed to map closely to the PortableContacts
spec. The REST spec and the JS specs haven't been aligned yet. We have
this planned for 0.9.

[gabrie...@gmail.com]

Thank you for your answer, great :-)

So the best things is that we rely on the XSD (and try to map our
architecture as near as possible to this XSD)?
(I know that it's not the final spec.)

Regards,
Gabriel

[Scott Seely]

Yes, that's the best thing to do. Also, please post when you see
weirdness in the XSD. The feature is new in 0.8.1 and, as such, it
hasn't seen much in the way of implementer review. It's also XSD, which
causes even mighty XML gurus to yawn and look for more interesting
things to read/do.;)

-----Original Message-----
From: opensocial-an...@googlegroups.com
[mailto:opensocial-an...@googlegroups.com] On Behalf Of
gabrie...@gmail.com
Sent: Thursday, October 16, 2008 8:09 AM
To: OpenSocial - OpenSocial and Gadgets Specification Discussion
Subject: [opensocial-and-gadgets-spec] Re: OpenSocial RESTful and Social
Apps, some strange things.

[gabrie...@gmail.com]

Some details.
Comments and Typo in the XSD
Based on : (http://www.opensocial.org/Technical-Resources/opensocial-
spec-v081/restful-protocol)

1)
If the Account provider support OAuth,
should we add the authorization token in "Account"?

2)
In elements stored in a list, should we add a unique id to each
elements?
For exemple, I want to display a specific element of my carrier in
another network, I need a way to know the element I've selectionned.

3)
A MediaItemType could also be a html file, a document (like a cv)?

4)
In a ArrayOfPersonUrl I have
public List<PluralPersonField> getUrl() {
It should be an array of <Url> ?

5) case don't follow the same standard in other variables
Smoker.displayvalue should be displayValue ?
Drinker.displayvalue should be displayValue ?
CreateActivityPriority.displayvalue should be
CreateActivityPriority.displayValue?
Environement.displayvalue
MessageType.displayvalue
Escape.displayvalue
Presence.displayvalue

6)
Account accounts;
Should be an array in Person

7)
nickname should not be an ArrayOfNicknames?
(I have multiple nicknames...)

8)
>> In the html page: The following additional Plural Fields are defined, based on their specification in OpenSocial:...
Person.children is not plural
Person.pets is not plural
Person.jobInterests is not plural
Person.languages in documentation but not in XSD
Person.politicalViews is not plural

9)
Person -> Url profileSong;
Person -> String profileUrl;
Person -> Url profileVideo;
Person -> String thumbnailUrl;
profileUrl and thumbnailUrl should not be a Url like song and video?

11)
ArrayOfIm should be ArrayOfIms

12)
MediaItem.url should be Url and not a string?

13)
Person.Name.additionalName should be plural (In some cultures they
have 4-5 names...)

[Kevin Marks]

On Thu, Oct 16, 2008 at 11:21 AM, gabrie...@gmail.com <gabrie...@gmail.com> wrote:

Some details.
Comments and Typo in the XSD
Based on : (http://www.opensocial.org/Technical-Resources/opensocial-
spec-v081/restful-protocol)

1)
If the Account provider support OAuth,
should we add the authorization token in "Account"?

No, tokens aren't transitive. You need to get your own one for these accounts.
 

the Url structure is designed for things that are displayable to users, and so need the extra linkText field for display. profileUrl and thumbnailUrl are presumed to point to the container itself, not externally.
 

11)
ArrayOfIm should be ArrayOfIms

12)
MediaItem.url should be Url and not a string?

13)
Person.Name.additionalName should be plural (In some cultures they
have 4-5 names...)

I've argued that Name itself should be plural...

that said, additionalName comes from vCard, and can have comma or space separated names