Closed ammist closed 12 years ago
Presumably the posts/updates would be marked as 'expired' rather than being physically deleted, and then expiry-aware clients would show them appropriately?
This sounds like this belongs in an annotation and not the core api. I know annotations are kind of abstract at this point but I'm going to close this issue. This seems like it's useful for a very small subset of posts and so probably doesn't belong in the core Post object.
That makes sense. What's the process for discussing a standard annotation for this particular feature? Or should we go ahead and create our own formats?
On Thu, Aug 23, 2012 at 2:34 PM, Mark Thurman notifications@github.comwrote:
This sounds like this belongs in an annotation and not the core api. I know annotations are kind of abstract at this point but I'm going to close this issue. This seems like it's useful for a very small subset of posts and so probably doesn't belong in the core Post object.
— Reply to this email directly or view it on GitHubhttps://github.com/appdotnet/api-spec/issues/106#issuecomment-7984959.
We're hoping to get back to annotations next week (this week has be lots of administrative stuff). For annotation formats that are really common, we'd like to define and standardize them in a 'wellknown' shared namespace (https://github.com/appdotnet/api-spec/blob/master/objects.md#post-annotations). But apps will also be able to define their own formats.
For an expiration time, I think ISO8601 has that covered pretty well.
For posts and status updates that have time-based component, it would be helpful to "expire" them. For example, "This coupon is valid till Sunday Sep 9" or "Justin Bieber is signing autographs at the Mall until 4 PM".