I'm just polling for interest; I said I'd write this up properly
elsewhere, but is there interest in the following:
A Snippet is a small item of content. It is normally referenced within
a chatroom or 1:1 chat. I'm only going to define use in MUC;
The implementation consists of using two pubsub nodes, the Summary
node and the Content node, called snippets/${chatroomjid}/summary and
spinnets/${chatroomjid}/content respectively.
To post a snippet, a client:
a) Publishes an item containing a URI (typically a data scheme URI may
be used) to the Content node. Clients SHOULD let the server pick the
item id.
b) Publishes an item containing metadata (content-type, size, title,
description, and maybe preview data scheme URI?) to the Summary node
under the same item id.
c) Sends a Reference (XEP-0372) to the chatroom.
(We might have a snippets-aware service do some of the above).
Clients can then:
* Display inbound snippets. Since all content is a URI, web-based
clients SHOULD use a sandboxed iframe, so XHTML should be fine.
Previews might be available, or else lower-bandwidth clients can
choose to download on demand.
* Query and enumerate all snippets shared to a specific chatroom.
This design shamelessly steals from XEP-0346, which I don't
particularly like (in terms of pubsub node naming) but this is an
admission that I can't think of anything better. Of course, MIX solves
this in a neater way.
Dave.
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
