Activity Statements are generally not time bound.
that is, for example, the statement:
{
"actor": {"displayName": "James"},
"verb": "read",
"object": {"displayName": "A book")
}
Holds true whether I am currently reading a book or read it a year ago. The "published" and "updated" properties indicate when the statement was made but does not indicate when the actual activity occurred (or whether it is currently occurring).
To provide time bounding, two additional properties could be used for an activity statement (see the schema doc for details).. basically, if we add a "startTime" and "endTime" to the activity statement, we can provide some indication of the window of time within which an activity began and ended...
{
"actor": {"displayName": "James"},
"verb": "read",
"object": {"displayName": "A book"),
"startTime": "2012-10-16T12:00:00Z"
}
Looking at this, and seeing that there is no endTime, and seeing that startTime is in the past, I can likely assume that the activity is ongoing currently. If the endTime was specified then we can assume the activity occurred in the past. If the startTime specifies a future date, then we can assume the activity is pending.
It's going to be entirely up to the application to figure out the appropriate representation in human-readable text, however.
- James