-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indexing XMPP Extension Protocols (XEPs)? #302
Comments
@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. |
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? |
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. |
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
(suggestions for the license text are welcome). |
@Flowdalic I believe so (but I'm not a lawyer!):
|
We wheref asked [1] to state that the XEP bibliographic data is openly avaiable and free of charge if we want it to be consumed by third parties. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
We wheref asked [1] to state that the XEP bibliographic data is openly available and free of charge if we want it to be consumed by third parties. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
We wheref asked [1] to state that the XEP bibliographic data is openly available and free of charge if we want it to be consumed by third parties. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
We wheref asked [1] to state that the XEP bibliographic data is openly available and free of charge if we want it to be consumed by third parties. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
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. |
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. |
Thank you @Flowdalic ! |
We wheref asked [1] to state that the XEP bibliographic data is openly available and free of charge if we want it to be consumed by third parties. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
We were asked [1] to state that the XEP bibliographic data is openly available and free of charge if we want it to be consumed by third parties. This weas previously merged as 7477388 ("Add license for bibliographic data"), but unfortunately later reverted in 59b2a5c ("Revert "Add license for bibliographic data"", xsf#1221). However, the fix for the broken docker build is trivial: simply also copy refs-LICENSE into the container. This commit does that. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
We were asked [1] to state that the XEP bibliographic data is openly available and free of charge if we want it to be consumed by third parties. This weas previously merged as 7477388 ("Add license for bibliographic data"), but unfortunately later reverted in 59b2a5c ("Revert "Add license for bibliographic data"", xsf#1221). However, the fix for the broken docker build is trivial: simply also copy refs-LICENSE into the container. This commit does that. Fixes xsf#1219. 1: ietf-tools/bibxml-service#302 (comment)
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
The text was updated successfully, but these errors were encountered: