(Spec. 0.9) Issues in Message

[Kless]

[1] The 'status' field has the next options: NEW, READ, DELETED.

So I think that should be used an Enum (opensocial.Enum.messageStatus)
as it's used in another fields when they've several options to choose.

[2] I think that the description is not very clear in the 'type'
field: "The title of the message, specified as an
opensocial.Message.Type"


[1] http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocial-Specification.html#opensocial.Message.Field.STATUS

[2] http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocial-Specification.html#opensocial.Message.Field.TYPE

[Lane LiaBraaten]

On Sat, Jun 20, 2009 at 5:04 PM, Kless <jona...@googlemail.com> wrote:

[1] The 'status' field has the next options: NEW, READ, DELETED.

So I think that should be used an Enum (opensocial.Enum.messageStatus)
as it's used in another fields when they've several options to choose.

I agree with the sentiment but I'm not sure it's worth the effort at this point for 2 reasons:

1) We're moving to OSAPI, which doesn't use any enums
2) This is the first time I've heard of this issue, so I wonder if anyone is using this field (or cares if it's an opensocial.Enum or not).

[2] I think that the description is not very clear in the 'type'
field: "The title of the message, specified as an
opensocial.Message.Type"

Agreed...this should be 'The type of the message'
Tracking this here: http://wiki.opensocial.org/index.php?title=Errata_in_v0.9#Typo_in_Message.Field.TYPE

-Lane