← Back to post

Edit history

Most recent

For dealing with handled/handling help requests we have three options, one: we think is easily achievable and pretty-much ok, and easily processed in fall-back scenarios. Two: that would be ridiculous (but for the example, extending the definition of Accept). Three: A proper extension introducing new Verbs, that might also be useful in other contexts (ticketing systems)? So. What do we do?

From a help request, picking it up would be:

  1. A reply with marker. The Guardian replies to the help-Note (inReplyTo the help-object) with shaer:helpStatus: "handling" | "resolved". Federates using existing reply paths, non-shaer-software sees a regular reply, ward and fellow-guardians see it as intended.
  2. TentativeAccept/Accept on the help-Note-id. "I'm picking this up" = TentativeAccept, "Resolved" = Accept, directed to the ward + co-guardians. Semantically a stretching exercise (Accept is normally intended to be used on Follow/Offer).
  3. A shaer:Resolve/shaer:Ack-activity. More explicit but new verb. More spec and implementation work, might be more/less useful outside of shaer:.

What are your thoughts?

Original

For dealing with handled/handling help requests we have three options, one: we think is easily achievable and pretty-much ok, and easily processed in fall-back scenarios. Two: that would be ridiculous (but for the example, extending the definition of Accept). Three: A proper extension introducing new Verbs, that might also be useful in other contexts (ticketing systems)? So. What do we do?

From a help request, picking it up would be:

  1. A reply with marker. The Guardian replies to the help-Note (inReplyTo the help-object) with shaer:helpStatus: "handling" | "resolved". Federates using existing reply paths, non-shaer-software sees a regular reply, ward and fellow-guardians see it as intended.
  2. TentativeAccept/Accept on the help-Note-id. "I'm picking this up" = TentativeAccept, "Resolved" = Accept, directed to the ward + co-guardians. Semantically a stretching exercise (Accept is normally intended to be used on Follow/Offer).
  3. A shaer:Resolve/shaer:Ack-activity. More explicit but new verb. More spec and implementation work, might be less useful outside of shaer:.

What are your thoughts?