Indexing XMPP Extension Protocols (XEPs)?

[Flowdalic]

Description

I wonder if indexing XMPP Extension Protocols (XEPs) would be an option for bib.ietf.org. We, i.e., the XMPP Standards Foundation, currently provides bibxml files for all published XEPs at https://xmpp.org/extensions/refs/. Currently as one file per XEP, but it would be easy to also provide an archive with all bibxml files (e.g. https://xmpp.org/extensions/refs/all.tgz).

If you are interested, then please reach out to the XSF (editor), or just respond to this issue. I'll make sure that it reaches the right people.

Code of Conduct

• I agree to follow the IETF's Code of Conduct

[ronaldtse]

@Flowdalic we (the Relaton project) would be very interested in distributing the bibliographic information of XEPs. All we need is confirmation that the bibliographic data is openly licensed that allows re-distribution.

Once Relaton is allowed to distribute the data, the BibXML Service can consume it easily.

[Flowdalic]

Thanks for the fast reply. We are always happy to have consumers of the XEP bibliography and I believe the XSF should be able to provide such a confirmation.

Could you elaborate how the Relaton project is related to bib.ietf.org? Will bibliopgrahy consumed by Relaton automatically appear on bib.ietf.org?

[ronaldtse]

Thanks @Flowdalic for the rapid reply.

The BibXML Service (bib.ietf.org) serves bibliographic data that is indexed from sources that use the Relaton format. Relaton is a bibliographic information model from ISO 690. Once there is permission from the authoritative source that the data can be provided in or converted into the Relaton format, it is easy to extend the BibXML Service can easily consume (and serve) them.

Of course, even when the data source is in the Relaton format, it will depend on IETF (ping @rjsparks ) on whether they wish to offer XEP data on the BibXML Service.

Clarification: our team helped implement the software that runs the BibXML Service, but the service itself is fully run by IETF staff.

[Flowdalic]

Thanks for the clarification. Would it be enough if we put a text file at e.g. https://xmpp.org/extensions/refs/LICENSE that states something like

The bibliopgrahic data available under https://xmpp.org/extensions/refs/ is available openly and free of charge

(suggestions for the license text are welcome).

[ronaldtse]

@Flowdalic I believe so (but I'm not a lawyer!):

• If the LICENSE file states one of the open content licenses, it would be even clearer (e.g. CC).
• I would also suggest using a license that does not allow forking/content changes -- because this is authoritative bibliographic data.

[ronaldtse]

Thank you to @Flowdalic the XEPs bibliographic data are now under CC0, which allows redistribution.

[Flowdalic]

Thank you to @Flowdalic the XEPs bibliographic data are now under CC0, which allows redistribution.

Just to make sure, technically the bibliopgrahic data is not yet under CC0: the board of the XSF first has to approve this and xsf/xeps#1220 needs to be merged.

[ronaldtse]

Got it @Flowdalic -- now that xsf/xeps#1220 is merged, we shall await your confirmation that the XSF board approves the change.

[Flowdalic]

Got it @Flowdalic -- now that xsf/xeps#1220 is merged, we shall await your confirmation that the XSF board approves the change.

The Board approved the change, hence the PR was merged. Unfortunately, it was reverted due to technical reasons. There is now xsf/xeps#1222 that fixes those.

[ronaldtse]

Thank you @Flowdalic !