[Standards] Proposed XMPP Extension: DOAP usage in XMPP
Guus der Kinderen
guus.der.kinderen at gmail.com
Wed Jan 13 18:14:02 UTC 2021
My thoughts: Informational. I believe that the XSF should be concerned more
with maintaining the XMPP standards than it should be concerned with
ensuring that information regarding projects that relate to XMPP is made
available in a structured fashion (which are covered by the other two
options that you provided).
On Wed, 13 Jan 2021 at 18:31, Dave Cridland <dave at cridland.net> wrote:
> 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?
> On Wed, 13 Jan 2021 at 16:13, Jonas Schäfer <jonas at wielicki.name> wrote:
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>> Title: DOAP usage in XMPP
>> 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: Standards-unsubscribe at xmpp.org
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards