On Sun, 24 May 2009 20:10:39 +0100
Michael Barker <m...@middlesoft.co.uk> wrote:
> > Now the specification file contains interface descriptions like
> > this:
> >
> >> <field name="mechanism" type="shortstr">
> >> selected security mechanism
> >> <doc>
> >> A single security mechanisms selected by the client, which must be
> >> one of those specified by the server.
> >> </doc>
> >> ...
> >> </field>
> >
> > The used and needed source code file autogenerated-api-qpid-0-8.cs
> > now contains for example:
> >
> >> /// <summary>
> >> ///
> >> /// A single security mechanisms selected by the client,
> >> which must be /// one of those specified by the server.
> >> ///
> >> /// </summary>
> >> string Mechanism { get; }
> >
> > The description was copied from the non-free specification (and no
> > otherwise defined licensed for the documentation strings) into the
> > generated C# interface definition.
> >
> > This makes this C# code as is non-free, too.
> >
> > This is exactly the same matter when developers implement RFC
> > standards and copy documentation from it into their source. The
> > license of the specification is not an open-source license.
>
> Is patching the generator so that the document comments are not
> present in generated code sufficient to clear the DFSG?
Yes, as long as there isn't anything included verbatim from the
specification file. (as method names and such aren't copyrightable btw)
> If so, I'll
> look into that as the next thing I do.
That would be great! :)
> Otherwise, could you give me
> some pointers for any other things that I should look at. I'll pass
> this information onto the RabbitMQ guys too.
>
> I've had a look over the QPid stuff and it appears that the python
> client doesn't make use of generated code, but the Java, C++ and C#
> version do, so I will check out their implementation too.
>
> Regards,
> Michael Barker.
--
Regards,
Mirco 'meebey' Bauer
PGP-Key ID: 0xEEF946C8
FOSS Developer mee...@meebey.net http://www.meebey.net/
PEAR Developer mee...@php.net http://pear.php.net/
Debian Developer mee...@debian.org http://www.debian.org/
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
