Description
The "status" Object type represents a human-readable update of the author's situation, mood, location or other status.
A status is similar in structure to a note, but carries the additional meaning that the content is primarily describing something its author is doing, feeling or experiencing.
Link to atom spec: http://martin.atkins.me.uk/specs/activitystreams/activityschema#anchor9
Derives From
Note
Properties
Property name
|
Type
|
Required
|
Property Description
|
JSON field
|
Atom field
|
RSS field
|
| mood |
mood |
no |
How the creator of the status was feeling |
|
context:mood |
|
| location |
location |
no |
|
|
geo:point or ?? |
|
content
|
string
|
yes
|
The entire status
|
|
atom:content
|
|
owner
|
object
|
no
|
Author of the status if different than activity actor
|
userid for now but needs to be global
|
atom:author
|
|
id
|
string
|
yes
|
Unique id for the object. Must be different than the activity id
|
id
|
atom:id
|
|
url
|
URI
|
yes
|
Permalink to the status. Usually allows commenting on this page and shows existing comments
|
links[0] ?
|
atom:link rel="alternate"
|
|
| published |
W3CDTF timestamp |
no |
Time the status was created |
published or time ? |
atom:published |
|
| updated |
W3CDTF timestamp |
no |
Last modification time |
updated |
atom:updated |
|
| source |
object |
no |
|
|
atom:source |
|
| related links |
array |
no |
Related links |
links |
atom:link rel="related" |
|
Verbs
URI
http://activitystrea.ms/schema/1.0/status
Examples
Real world examples of "status" posts:
- Foursquare shout (and previously, Dodgeball shout)
Notes
If a status contains links as most of them do the publisher should include them in the related links array. Also if the note is a status update then the Status object type should be used.
Open Questions
- How do systems distinguish between a user posting a note, a status and a bookmark ? A status should not have links but how to distiguish between note and bookmark
- consider distinguishing between "status" and "note" by how ephemeral the information is. "status" posts tend to be far more present tense, ephemeral. "notes" are more like short unstructured articles that may (tend to) still have relevance/meaning long after being posted. if you're not sure if something is a "status" or a "note", it's likely just a "note". -Tantek
- Many of these have media associated with them how is this represented ? Does using thumbnail make sense for this ?
Implementations
AOL, Yahoo Messenger, MySpace, Facebook, Messenger
Maintainers
Who maintains this page, or should be contacted if there are questions or feedback?
Comments (3)
Chris Messina said
at 9:34 pm on Jul 18, 2010
Another example of this is the Foursquare "shout".
Tantek said
at 6:08 pm on Jul 21, 2010
I think some implementation guidance would help here. E.g. if the implementation can't be sure that the user is providing situation, mood, location or other temporal status, then use the Note object-type instead. Thus Twitter should use Note when they support Activity Streams.
Tantek said
at 10:33 am on Sep 19, 2010
Another distinction (reasoning from the use cases of AIM status and Foursquare shout) between a "post"ing a "status" and "post"ing a "note" is that a status tends to be much more ephemeral than a note. That is, a status indicates something that may only be "true" for a brief period of time following (perhaps a big preceding) the "published" time of the "post"ing. A "note" however, is closer to simply being a a short unstructured "article" (i.e. without title, headings, paragraphs).
You don't have permission to comment on this page.