Hi, On Fri, Sep 08, 2017 at 09:27:26AM +0200, Goffi wrote: > > Hi, > > I'm thinking again about this date/time thing. I see that there is already > https://xmpp.org/extensions/xep-0149.html which define a simple start/stop > using XEP-0082 which seems more simple and adapted to XMPP (there are too > many > informations and things that we can found elsewhere in XMPP with iCal/XCal > based solutions).
I believe there could be many use cases to XCal/iCal in XMPP. Having raw iCal would allow clients to have seamless buttons like "add to calendar" or similar, and xCal to iCal is trivial, although we probably do not want to allow custom XML extensions. > > The current XEP-0149 is not really adapted for being used everywhere (it uses > shim), so maybe a new XEP using the same mechanisms would be nice. Although SHIM is a bit unpleasant to look at, I don't think that’s the real problem for adoption of 0149, so I am not sure a XEP doing the same thing without the SHIM wrap would be worth the effort and fragmentation. > Also I note that there is not "date" field in data form, I think this is > really > missing. +1; Although the date information can be conveyed in a different manner, there is no way to currently specify that the time should not be taken into account. > What do you think, would it make sense to do a simple time period XEP using > start/stop instead of doing a XCal/ICal thing ? I'm thinking about many use > cases, but mainly events and announces (e.g. "the server will be down for > maintenance between XXX and YYY). As a service operator that XEP would be useful (inside a <message/> element so that it can be read by users without support); the event description format can be changed between now and finalization of the XEP so I don't think it matters too much. Mathieu _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
