From: Alex Harsanyi <alexharsanyi@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: wsdl test files and licensing
Date: Wed, 12 Nov 2014 21:45:21 +0800 [thread overview]
Message-ID: <CAH-ciFq25XnumfQqNf_f1hebszA5eCyty6ZKT9S8HTzBj61R1Q@mail.gmail.com> (raw)
In-Reply-To: <87oascr3es.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
2014-11-12 20:47 GMT+08:00 David Kastrup <dak@gnu.org>:
> Michael Albinus <michael.albinus@gmx.de> writes:
>
> > the soap-client people have written a test suite shich is obviously
> > useful. I would like to merge it into Emacs. This will take time,
> > because before this happens it shall use ert for running the
> > tests. But that's another story.
> >
> > As test data, there are several *.wsdl files as well as soap request
> > examples (these are *.xml files). All of them are not licensed, except
> > Debbugs.wsdl taken from the GNU ELPA debbugs package.
>
> What does "are not licensed" mean? If it means "there is no license to
> distribute them", obviously we cannot distribute them. That's a
> no-brainer.
>
I will try to clarify what the situation is:
Each SOAP server provides a WSDL document which contains the definition of
the messages and their XML structure as accepted by the server.
soap-client.el (and other soap-clients) read this document and use it to
generate the XML requests and process the XML replies from the server.
While the WSDL itself is XML format, it is intended to be read by
computers, not humans (quite often, the documents are also generated
automatically from programing language interfaces). These WSDL documents
are available to be downloaded from the SOAP servers themselves and are
necessary to be able to communicate with these servers.
We have a test suite which has about 11 WSDL documents from different
providers saved locally. They are used to ensure that soap-client.el can
parse real-world WSDL documents. None of these documents have any
copyright notice on them, except for Debbugs.wsdl and another one which has
an "All Rights Reserved" notice.
I wasn't sure if these documents can be distributed at all, so I kept the
test suite private, instead of adding it to the public repository which
hosts soap-client.el. Michael suggested we ask for clarification on
emacs-devel, which he did :-)
Best Regards,
Alex.
[-- Attachment #2: Type: text/html, Size: 2585 bytes --]
next prev parent reply other threads:[~2014-11-12 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 12:10 wsdl test files and licensing Michael Albinus
2014-11-12 12:47 ` David Kastrup
2014-11-12 13:42 ` Tassilo Horn
2014-11-12 13:45 ` Alex Harsanyi [this message]
2014-11-12 14:07 ` David Kastrup
2014-11-12 14:42 ` Michael Albinus
2014-11-12 14:50 ` David Kastrup
2014-11-12 15:05 ` Michael Albinus
2014-11-12 23:58 ` Alex Harsanyi
2014-11-13 14:34 ` Michael Albinus
2014-11-12 14:20 ` Stefan Monnier
2014-11-12 14:50 ` Stephen J. Turnbull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH-ciFq25XnumfQqNf_f1hebszA5eCyty6ZKT9S8HTzBj61R1Q@mail.gmail.com \
--to=alexharsanyi@gmail.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.