Some discussion in Council as to where this fits. I'm quite happy it is useful as a XEP.
So, is this: Informational: It's a Best Practice for the community. We are recommending that projects use DOAP. Standards Track: It's a specification we want to standardize for the community to use. Section 4.2 contains new bits of XML and - presumably - would be developed via a Standards Track process. Procedural: It's something the XSF should do (ie, receive the DOAP files and process them somehow). I think there are arguments for all of these, and I've not made up my mind. What do people think? Dave. On Wed, 13 Jan 2021 at 16:13, Jonas Schäfer <[email protected]> wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: DOAP usage in XMPP > Abstract: > This specification defines how XMPP projects can provide a machine- > readable description of their abilities, and how external entities can > interact with it. > > URL: https://xmpp.org/extensions/inbox/doap-usage-in-xmpp.html > > The Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
