Greeting Stephen! There is no special use case other than a dedicated node ID.
The purpose is a a concensus node ID which should ease on interoperability betweeen systems. Suppose project Betula (links directory system) adds intergration with XMPP PubSub, and choses "betula" as node ID. https://codeberg.org/bouncepaw/betula/issues/9 BukuBot might expect "buku_public_links" and Movim might expect "movim_social_links" for bookmarks. An inconsistent node ID would hinder interoperability. Having a consensus node ID for this purpose would allow sharing of data without coordinating between projects, only referring to an XEP. Generally, I would suppose that it would be almost the same if not exactly the same as XEP-0472 in structure and data type. If you still think it is not needed, for the time being, please inform me and I will neglect this proposal. It is good to read from you. Best regards, Schimon On Fri, 7 Jun 2024 13:33:45 +0000 Stephen Paul Weber <[email protected]> wrote: > There doesn't seem to be a need for a well-known node name for this? > Unless I'm missing the use case... > _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
