On Sun, 25 Oct 2026 at 05:44, Daniel Gultsch <daniel@gultsch.de> wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Portable Import/Export Format for XMPP Components Abstract: This document specifies a file format for importing and exporting component data to and from XMPP software
This has little of any concrete nature, and according to my current understanding of Council rules applied to ProtoXEPs should therefore be rejected. First, as described, this is useless for both pubsub and MUC. It goes as far as describing an "item" subelement, but then fails to explain what this represents for either. One assumes it might be a room for MUC, and a node for pubsub, but what would then go inside each is entirely unspecified. It feels like, for any kind of useful schema to be produced, that having explicit "room" and "node" elements would be more useful (in which case this specification is essentially useless). Alternately, mandating a single payload element, or specifying at least that only the first was the payload element, seems essential. Second, even if it had covered pubsub and MUC at all, it fails to cover the "other services" it claims to. This is, to quote, simply a "document that says things". This is a shame, as solving the missing MUC and Pubsub support in PIE would be a useful thing for the XSF to work on and would indeed fill an important gap. If it were to be accepted counter to these previously stated rules, then I'd recommend the following while experimental: 1) Drop the "name" of the item, and replace it with "jid", "node", or both, to match disco#items. I would be inclined to specify that the first child is the payload (mandatory to understand), and any others are optional extensions. 2) Drop the type of the component in favour of "category" and "type", again from XEP-0030. 3) Get at least the basics of MUC and/or Pubsub. I'd think MUC is config and affiliations, and Pubsub is config, affiliations, subscriptions, and items. I think all of those can be in the form they'd be returned by relevant IQ. Seems easy enough as a first cut, though undoubtedly implementation and discussion will surface more. All these get wrapped in a payload element to act as a schema support. Dave.