jdev - 2026-02-08

Berlin sprint will be 19. to 21. of June. Please register yourself here: https://wiki.xmpp.org/web/Sprints/2026-06_Berlin#Attendees

Weird question: am i safe to assume that stuff like ``` <foo xmlns="ns1" xmlns:p="ns2" xmlns:q="ns3"> <p:bar q:attr="value"> ... </p:bar> </foo> ``` will never arrive? In other words, am i safe to assume that namespaces will not require inheritance?

Trying to write an XMPP-specific XML parser and is stuck with this question

im pretty sure childs inherit the namespace of the parent

Hmm, looks like i'll have to implement full-on namespace resolution…

i dont think xmpp does anything special here, what the XML spec defines is what is allowed.

Otherwise i could just store only those namespaces that are declared textually inside the element

but there are probably people that know this better

afaik the only specialness about xmpp xml is just that you have to progressively parse instead of trying to parse the entire connection as one long stanza lol

All the hard parts of XML are also invalid in XMPP subset of XML, so it's parser is mostly implementable as a single visibly pushdown automata with some extra logic, unlike a full-blown XML parser

Just use a real XML parser :P

But also yes you need full namespaces for sure

> Just use a real XML parser :P It's not fun :) ↺

are you also aiming for security, along with fun, alexkurisu?

the argument against using a existing xml parsers, as far as i know is just that often disabling all the stuff you dont need for xmpp and are potentially dangerous, are often hard

> the argument against using a existing xml parsers, as far as i know is just that often disabling all the stuff you dont need for xmpp and are potentially dangerous, are often hard Also, separate stanza splitters are pain ↺

> are you also aiming for security, along with fun, alexkurisu? Kind of ↺