jdev - 2021-02-17

XEP-0030 uses "/" in all the examples to separate nodes, but that's just an example right? I just realized that I don't think I've ever seen a service with nodes and reading the text I can't tell if you can reference a specific node down the tree like a path or if you have to know the name of the node and it might not have any relation to the node it's a child of

(I mean, obviously you have to know the name of the node, but is the node name absolute or does it actually have path semantics)

Nodes are opaque [*citation needed]

TIL there's a section about that

Cool, going with the opaque thing since that's what I assumed. I hate it when all the examples appear to show something that might be convenient, but may or may not actually be part of the spec.

Thanks for sanity checking me.

Yeah if you organize nodes into a tree I'm pretty sure there's no requirement to use any specific syntax for it.

It also mentions that disco info requests to nodes should have type='branch' or type='leaf', but it's just a throwaway comment and not in the schema… I don't think I've ever actually seen or implemented the node stuff so I'm very confused by this.

This was in PubSub, was it not?

https://xmpp.org/extensions/xep-0248.html

TIL, XEP-0248

AIUI one successful break-out from '60

No, I'm just implementing XEP-0030, but maybe I should dig into a pubsub node and just see how it works as an example

"branch" and "leaf" are of the kind that goes into a registry, not schema. So https://xmpp.org/extensions/xep-0030.html#registrar-reg-identity-init

oh, nevermind, that makes sense. I guess the schema wouldn't have the full enum since the registry can be modified

oh damn, 10:00. Time for $DAYJOB. Oh well, thanks for the help; hopefully I'll be able to finally get this done soon.