Proposed XMPP Extension: Pubsub Extended Discovery
The XMPP Extensions Editor has received a proposal for a new XEP. Title: Pubsub Extended Discovery Abstract: This specification extends the discovery requests used with the XMPP PubSub protocol by introducing mechanisms to discover linked nodes, descendants, or metadata. URL: https://xmpp.org/extensions/inbox/pubsub-extended-discovery.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.
URL: https://xmpp.org/extensions/inbox/pubsub-extended-discovery.html
You know I love me a data form, data forms are my jam. However I wonder if a single-field data form with a field name in clarke notation in a non-user-facing position wouldn't be better served as a namespaced element? ie: <parent xmlns="urn:xmpp:pubsub-relationships:0">urn:xmpp:microblog:0</parent>
Le mardi 29 octobre 2024, 14:02:07 heure normale d’Europe centrale Stephen Paul Weber a écrit :
URL: https://xmpp.org/extensions/inbox/pubsub-extended-discovery.html
You know I love me a data form, data forms are my jam. However I wonder if a single-field data form with a field name in clarke notation in a non-user-facing position wouldn't be better served as a namespaced element? ie:
<parent xmlns="urn:xmpp:pubsub-relationships:0">urn:xmpp:microblog:0</ parent>
Only one or 2 fields are returned (by default) to save bandwidth when other data are not needed, but it's actually the standard metadata namespace as defined at https://xmpp.org/extensions/xep-0060.html#entity-metadata . If you set `full_metadata` to "true", you'll actually get all fields. Best, Goffi
participants (3)
-
Daniel Gultsch -
Goffi -
Stephen Paul Weber