XMPP Council - 2014-03-27

Thoughts on http://doomsong.co.uk/extensions/render/pubsubforms.html welcome.

Kev: i'm usually not a fan of using urns+parameters as node ids, but this seems reasonable

I'm open to a better formulation if you have one.

Kev: nope, this is probably the best option. so long as everything is static, no objections

"Everything is static"?

urn:xmpp:pubsub-forms:template:0 and s/template/submitted/ are static.

i remember the commenting via pubsub did weird things with urns+parameters

Then the 'query part' is basically the identifier of the particular form that's published there.

There's no magic, the query part itself is opaque.

Or, at least, this spec doesn't say otherwise. If individual applications want to work magic using it, I don't much care (mine doesn't).

Kev: right. i'm just remembering things like: coffeetalk/comments?order=-created

Ah. No such magic here.

as long as things are ok to be done via a hash lookup, im happy

'Things'? And done by whom?

for implementations. usually a hash lookup to fetch contents for a node id

You mean for the pubsub service?

Or for client caching?

yes, and the associated disco parts

Either way, yes, this is an entirely standard xep60 service.

+1

hrm. i actually think i have some upcoming use cases for this..

Marvellous.

In terms of verbiage, how much more do you think is needed before we could publish it?

I'm torn between duplicating examples out of xep60 or not. It being only a few lines as it is at the moment is appealing :)

yeah, always need the examples

even though this is nice and concise atm

I was, if I'm honest, expecting that.

there are two things that seem would be nice to have: a specific disco node that will list these templates instead of having to search through all nodes, and mentioning that the name attribute in disco would be useful to name the templates

I'm trying to avoid requiring a custom service for this, though :/

ISTM if we /can/ build this straight out of xep60 without much inconvenience, it'd be better to do so.

have you implemented this already?

Not exactly, but more or less.

what kind of UI/UX did you have?

or rather, how did people find the form they need to fill out?

XMPP URIs? :)

Combobox of available forms, if I understand the question correctly.

But I've not rolled anything out yet.