This looks reasonable & straight forward to me, at first glance.
However, I think that it should also be using XEP-0122 (Data Forms Validation)
to indicate a
geoloc datatype is expected.
Having been implementing data form related things recently, I've found that two
places to
determine a fie
> 1. Is this specification needed to fill gaps in the XMPP protocol stack or to
> clarify an existing protocol?
This is a feature that has received a lot of end-user requests, and we have no
other good way to do it, so yes.
If anyone is going to ever implement this feature, let's have a thought
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Data Forms Geolocation Element
Abstract: This specification defines an XMPP protocol extension for including
geolocation data in XEP-0004 data forms.
URL: http://xmpp.org/extensions/inbox/geoloc-dataform.html
The XMPP Cou
This message constitutes notice of a Last Call for comments on XEP-0186
(Invisible Command).
Abstract: This document specifies an XMPP-compatible protocol for user
invisibility.
URL: http://xmpp.org/extensions/xep-0186.html
This Last Call begins today and shall end at the close of business on
Wed, 18 Jun 2014 10:21:36 +0100
Kevin Smith wrote:
> The recipient-side filtering seems OKish, but could lead to situations
> where the publishing servers blindly send out to all possible
> recipient JIDs and let the recipients deal with whether to send to the
> clients or not - clearly not OK.
Guys, could you please be more specific on what's wrong with XEP-33
because I don't really understand your concerns.
I don't think that it will be better to use my own protocol to put the
subscribers' JIDs into the event, right? So what are the options?
Thanks.
On 06/18/2014 04:21 PM, Kevin Smit
FYI
-- Forwarded message --
From: Kevin Smith
Date: Thu, Jun 19, 2014 at 10:45 AM
Subject: Minutes 20140618
To: XMPP Council
Logs: http://logs.xmpp.org/council/2014-06-18/
1) Roll call
Lance, Tobias, Kev, Matt present, Fippo absent
2) Date of next meeting
2014-07-02 15:00Z
3)