XSF Communications Team - 2025-10-07


  1. gnemmi

    cal0pteryx, around?

  2. gnemmi

    emus, ?

  3. gnemmi

    could you please merge https://github.com/xsf/xmpp.org/pull/1566 before we publish?

  4. emus

    cal0pteryx, Alex: Daniel could you help Alex to check why his Doap file isnt rendered correctly?

  5. emus

    https://raw.githubusercontent.com/agnauck/XmppDotNet/refs/heads/agnauck-doap-file/doap.xml

  6. emus

    > could you please merge https://github.com/xsf/xmpp.org/pull/1566 before we publish? Yes

  7. gnemmi

    emus, Thank you very much! 🤗

  8. Guus

    Hi commteam! winfried and I have started an article, that we'd like to shepherd , evolve, and distribute through you. There is an ongoing effort to create a national standard for implementing chat in the Dutch healthcare sphere. We, unsurprisingly, think that XMPP should be used as a basis for that standard (ongoing work of that standard is already considering XMPP).

  9. Guus

    We have been working on a call for cooperation, to be published by the XSF, inviting the groups that are developing those standards to work with the XMPP community.

  10. Fishbowler

    Got any info on what they want from chat?

  11. Fishbowler

    I've done some work in the UK and EU in healthcare (although not XMPP related), and might have some thoughts, but they might be a bit broad and unrelated.

  12. Fishbowler

    I suspect dwd to have some v relevant thoughts too, if he can be summoned to peek at it.

  13. Guus

    (harg, what a time for my network to act up)

  14. arne

    That are very good news Guus !

  15. Guus

    A first draft (which is unfinished, but sets out much of the details we deem important) is available here: https://pad.nixnet.services/uM01SeYWSFuf08_1YS_tXw?both

  16. Guus

    Can we work together to get this done?

  17. arne

    Would it make sense to give examples where it is already used? I'm not sure if the military is a good example but there maybe other institutions where it is actively used?

  18. arne

    Like in universities or in research

  19. winfried

    > Got any info on what they want from chat? unfortunately I can't share any internal documents right now, I'm chairing the working group setting the norm so I'm pretty tied down But the focus is on setting security norms/controls for messaging in general and e-mail and chat specifically. The chat working group I'm chairing is very reluctant to mandate one interop standard, so it is now moving towards standardizing functionalities and security features that should be present when doing interop/federating...

  20. Fishbowler

    I guess I'm skirting around the edges of: Would they be interested in IoMT interop? Would they be interested in some kind of HL7 FHIR / other data exchange?

  21. winfried

    structured data exchange is part of a different set of norms: https://www.nen-egiz.nl/

  22. guus.der.kinderen

    Winfried, what are reasons why the working group is reluctant to shy away from mandating one interop standard?

  23. winfried

    > I guess I'm skirting around the edges of: Would they be interested in IoMT interop? Would they be interested in some kind of HL7 FHIR / other data exchange? integrating those into XMPP (and pushing XMPP there) would be great from a technical point of view, but will be a longshot from a proces point of view, standardisation of these has been very focused on the transports suggested by HL7/FHIR. What might be interesting is integrating XADES into XMPP, what opens the route for EIDAS services into XMPP.

  24. guus.der.kinderen

    Are the reasons for the workgroup to shy away from mandating one interop standard sufficiently countered by the article that we are drafting? "Use XMPP!"

  25. winfried

    > Winfried, what are reasons why the working group is reluctant to shy away from mandating one interop standard? The workinggroup tries to follow as much as possible widely adapted standars. For e-mail that is SMTP, but for IM that is less clear cut. The Dutch ministry of health (who has asked for and pays for this standard) is very reluctand to intervene in the market. And parallel to this norm some vendors are working on interop based on Matrix, some vendors don't feel at ease with XMPP (I guess because of its steep learning curve).

  26. guus.der.kinderen

    With XMPP, you arguably don't intervene in the market, as there are a gazillion vendors, as opposed to a solution where you have basically a vendor lock-in.

  27. guus.der.kinderen

    Anyway, we digress. I'm hoping that with commteam, we can shape up this article. For now, it is well past my bedtime. Goodnight!

  28. winfried

    Then you haven't seen the Dutch ministry of health yet! They are reluctant to make a choice between interop between audited organisations or public interop because they are afraid to make a choice...

  29. guus.der.kinderen

    XMPP can do both! Don't have to make a choice! (apart from choosing for XMPP)

  30. winfried

    yes!

  31. winfried

    But please draft a nice blog / open letter... I'll be present in the background and help as far as my position permits