[Standards] servers.xml (was: website transition)
On Tue, Sep 9, 2008 at 12:07 AM, Andreas Monitzer <[EMAIL PROTECTED]> wrote: > On Sep 08, 2008, at 21:36, Peter Saint-Andre wrote: > >> I had totally forgotten about that feature request. > > Yes, that's what I hear every time I remind somebody of the jabber.org-team > :) > Yeah, apologies for this :) To be fair, we have been preoccupied with other, larger issues, until now. >> We do have a plain XML file: >> >> http://www.jabber.org/servers.xml >> >> But perhaps that's not what you need. > > Well, I'd need the additional info available on the detail pages, too: > e.g. http://www.jabber.org/web/Jabber.org > > esp. the description, location and lat/long. > How is this, collected from the wiki with a Lua script I knocked up: http://www.jabber.org/servers_wiki.xml Some more semantics could be introduced if necessary. For example, I have left wiki links as wiki links. I don't know how you would rather XML-ise those. >> Right now I'm hand-editing servers.xml... > > Uh, you should know better than that... > XML was designed to be human writeable :) Regards, Matthew. PS. I realised we're on the wrong list for this really, let's move it over to webteam.
[Standards] UPDATED: XEP-0198 (Stream Management)
Version 0.4 of XEP-0198 (Stream Management) has been released. Abstract: This specification defines an XMPP protocol extension for active management of an XML stream between two XMPP entities, including features for stanza acknowledgements, pings, and stream resumption. Changelog: Added support for session resumption; re-organized the document; changed name to stream management; changed provisional namespace. (jjh/jk/psa) Diff: http://is.gd/2nym URL: http://www.xmpp.org/extensions/xep-0198.html
Re: [Standards] website transition
Actually, if you really need it, you can transform the XML file (and other ones) yourself, it can't be so hard. Pavel On Tue, 9 Sep 2008 01:07:21 +0200 Andreas Monitzer <[EMAIL PROTECTED]> wrote: > On Sep 08, 2008, at 21:36, Peter Saint-Andre wrote: > > > I had totally forgotten about that feature request. > > Yes, that's what I hear every time I remind somebody of the > jabber.org- team :) > > > We do have a plain XML file: > > > > http://www.jabber.org/servers.xml > > > > But perhaps that's not what you need. > > Well, I'd need the additional info available on the detail pages, too: > e.g. http://www.jabber.org/web/Jabber.org > > esp. the description, location and lat/long. > > > Right now I'm hand-editing servers.xml... > > Uh, you should know better than that... > > andy > -- Pavel Šimerda Freelancer v oblasti počítačových sítí, komunikace a bezpečnosti Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
Re: [Standards] website transition
On Sep 08, 2008, at 21:36, Peter Saint-Andre wrote: I had totally forgotten about that feature request. Yes, that's what I hear every time I remind somebody of the jabber.org- team :) We do have a plain XML file: http://www.jabber.org/servers.xml But perhaps that's not what you need. Well, I'd need the additional info available on the detail pages, too: e.g. http://www.jabber.org/web/Jabber.org esp. the description, location and lat/long. Right now I'm hand-editing servers.xml... Uh, you should know better than that... andy
Re: [Standards] website transition
A regularly-run XSLT would help... MattJ is good in writing them ;). Don't beat me, friend (to MattJ). Pavel On Mon, 08 Sep 2008 13:36:37 -0600 Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > Andreas Monitzer wrote: > > On Sep 08, 2008, at 19:55, Peter Saint-Andre wrote: > > > >> If you find any website problems, please let us know! > > > > Yes, my feature request dating back to the website version even > > before the move to drupal still isn't implemented, even though I > > was repeatedly told that it's on the todo list since back then :( > > > > My request was to have an RSS or Atom feed of the public server > > list, so I can display that list in Adium in the registration > > dialog. > > I had totally forgotten about that feature request. > > We do have a plain XML file: > > http://www.jabber.org/servers.xml > > But perhaps that's not what you need. > > > Of course, moving to a wiki makes the whole thing even worse, since > > there's no easy solution to that problem now (since the completely > > nonsemantic wiki code is the only data source). > > I could do some kind of html extraction, but that would break as > > soon as someone does an edit that changes the website slightly. > > > > All the data I need is there, I just can't access it... > > Correct. Right now I'm hand-editing servers.xml... > > /psa > -- Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
Re: [Standards] website transition
+1 for lighttpd, I always liked it. Pavel On Mon, 08 Sep 2008 11:55:50 -0600 Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > Matthew Wild and I just completed the transition of "apollo" (the > jabber.org/xmpp.org webserver) from Apache to lighttpd. Concurrently > we also migrated jabber.org and xmpp.net from Drupal to MediaWiki. So > far everything seems to be working great. If you find any website > problems, please let us know! > > /psa -- Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
[Standards] UPDATED: XEP-0250 (C2C Authentication Using TLS)
Version 0.2 of XEP-0250 (C2C Authentication Using TLS) has been released. Abstract: This document describes how to negotiate TLS extensions when using TLS for end-to-end XML streams between two clients. It covers X.509 certificates with an without CA, the use of OpenPGP, Shared Remote Passwords (SRP) and how to use one extension to bootstrap a trust relationship. Changelog: Use keyinfo from version 0.8 of XEP-0189. (dm) Diff: http://is.gd/2n4J URL: http://www.xmpp.org/extensions/xep-0250.html
[Standards] UPDATED: XEP-0189 (Public Key Publishing)
Version 0.8 of XEP-0189 (Public Key Publishing) has been released. Abstract: This specification defines a method by which an entity can publish its public keys over XMPP. Changelog: Change KeyInfo element from W3C XML Signature to ASCII and add signature support (dm) Diff: http://is.gd/2n3o URL: http://www.xmpp.org/extensions/xep-0189.html
Re: [Standards] website transition
Andreas Monitzer wrote: On Sep 08, 2008, at 19:55, Peter Saint-Andre wrote: If you find any website problems, please let us know! Yes, my feature request dating back to the website version even before the move to drupal still isn't implemented, even though I was repeatedly told that it's on the todo list since back then :( My request was to have an RSS or Atom feed of the public server list, so I can display that list in Adium in the registration dialog. I had totally forgotten about that feature request. We do have a plain XML file: http://www.jabber.org/servers.xml But perhaps that's not what you need. Of course, moving to a wiki makes the whole thing even worse, since there's no easy solution to that problem now (since the completely nonsemantic wiki code is the only data source). I could do some kind of html extraction, but that would break as soon as someone does an edit that changes the website slightly. All the data I need is there, I just can't access it... Correct. Right now I'm hand-editing servers.xml... /psa smime.p7s Description: S/MIME Cryptographic Signature
Re: [Standards] website transition
On Sep 08, 2008, at 19:55, Peter Saint-Andre wrote: If you find any website problems, please let us know! Yes, my feature request dating back to the website version even before the move to drupal still isn't implemented, even though I was repeatedly told that it's on the todo list since back then :( My request was to have an RSS or Atom feed of the public server list, so I can display that list in Adium in the registration dialog. Of course, moving to a wiki makes the whole thing even worse, since there's no easy solution to that problem now (since the completely nonsemantic wiki code is the only data source). I could do some kind of html extraction, but that would break as soon as someone does an edit that changes the website slightly. All the data I need is there, I just can't access it... andy
[Standards] DRAFT: XEP-0243 (XMPP Server Compliance 2009)
Version 1.0 of XEP-0243 (XMPP Server Compliance 2009) has been released. Abstract: This document defines XMPP server compliance levels for 2009. Changelog: Per a vote of the XMPP Council, advanced specification to Draft. (psa) Diff: http://is.gd/2mBY URL: http://www.xmpp.org/extensions/xep-0243.html
[Standards] DRAFT: XEP-0242 (XMPP Client Compliance 2009)
Version 1.0 of XEP-0242 (XMPP Client Compliance 2009) has been released. Abstract: This document defines XMPP client compliance levels for 2009. Changelog: Per a vote of the XMPP Council, advanced specification to Draft. (psa) Diff: http://is.gd/2mBV URL: http://www.xmpp.org/extensions/xep-0242.html
[Standards] ACTIVE: XEP-0223 (Best Practices for Persistent Storage of Private Data via Publish-Subscribe)
Version 1.0 of XEP-0223 (Best Practices for Persistent Storage of Private Data via Publish-Subscribe) has been released. Abstract: This specification defines best practices for using the XMPP publish-subscribe extension to persistently store private information such as bookmarks and client configuration options. Changelog: Per a vote of the XMPP Council, advanced specification to Active. (psa) Diff: http://is.gd/2mBQ URL: http://www.xmpp.org/extensions/xep-0223.html
[Standards] ACTIVE: XEP-0222 (Best Practices for Persistent Storage of Public Data via Publish-Subscribe)
Version 1.0 of XEP-0222 (Best Practices for Persistent Storage of Public Data via Publish-Subscribe) has been released. Abstract: This specification defines best practices for using the XMPP publish-subscribe extension to persistently store semi-public data objects such as public keys and personal profiles. Changelog: Per a vote of the XMPP Council, advanced specification to Active. (psa) Diff: http://is.gd/2mBM URL: http://www.xmpp.org/extensions/xep-0222.html
[Standards] website transition
Matthew Wild and I just completed the transition of "apollo" (the jabber.org/xmpp.org webserver) from Apache to lighttpd. Concurrently we also migrated jabber.org and xmpp.net from Drupal to MediaWiki. So far everything seems to be working great. If you find any website problems, please let us know! /psa smime.p7s Description: S/MIME Cryptographic Signature
Re: [Standards] UPDATED: XEP-0060 (Publish-Subscribe)
BTW, I've been waiting for this version (and its clarifications to handling of +notify features) before advancing XEP-0222 and XEP-0223 to Active, so I will do that now. XMPP Extensions Editor wrote: Version 1.12 of XEP-0060 (Publish-Subscribe) has been released. Abstract: This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an event notification (with or without payload) is then broadcasted to all entities that have subscribed to the node. Pubsub therefore adheres to the classic Observer design pattern and can serve as the foundation for a wide variety of applications, including news feeds, content syndication, rich presence, geolocation, workflow systems, network management systems, and any other application that requires event notifications. Changelog: [See revision history] (psa) Diff: http://is.gd/2bzr URL: http://www.xmpp.org/extensions/xep-0060.html smime.p7s Description: S/MIME Cryptographic Signature
