SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
Veröffentlicht am
CRUMLISH & MALONE
When status updates first emerged in the context of instant
messenger programs, they were inherently fleeting,
temporally tied to the immediate moment and then discarded.
It really doesn’t make that much sense to keep an infinite log
of Available, Busy, Idle, Offline, and so on for the life of the
user or the application. But as other status-capturing
interfaces have evolved, the idea of at least maintaining a
stream of recent history and then possibly mixing status
reports with other snapshots of inline activity has taken hold
as a way of displaying presence.
When status updates first emerged in the context of instant messenger programs, they were
inherently fleeting, temporally tied to the immediate moment and then discarded. It really
doesn’t make that much sense to keep an infinite log of Available, Busy, Idle, Offline, and so
on for the life of the user or the application. But as other status-capturing interfaces have
evolved, the idea of at least maintaining a stream of recent history and then possibly mixing
status reports with other snapshots of inline activity has taken hold as a way of displaying
presence.
Sie haben diese Folie bereits ins Clipboard „“ geclippt.
Regardless, this is a lot of fodder for thought. Will check out the mailing list for more.
I think it depends — generally speaking, any time something new is created in a digital environment, you can use the 'post' verb — and change the object type... i.e. 'Chris posted a new question'.
If you have a specific use case where a more specific verb is useful, you could specify multiple verbs ('post' and 'ask') but I haven't seen too many people doing that just yet.
In general, it's desirable to reuse from the existing schema to promote interoperability.
Would be interested in understanding the process for recommending new verbs for adoption - in particular, does something like 'ask' constitute a valid verb (indicative of the fact that the target object is a query) or would it be overloading the equivalent of 'post' (indicative of the fact that the target object is a note or comment).