Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Thu, 26 Jan 2006 21:26:00 -0000	[thread overview]
Message-ID: <20060126211252.GA17685@nevyn.them.org> (raw)
In-Reply-To: <200601262103.k0QL3Jdo030305@elgar.sibelius.xs4all.nl>

On Thu, Jan 26, 2006 at 10:03:19PM +0100, Mark Kettenis wrote:
> > Date: Thu, 26 Jan 2006 11:38:32 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > I'm not going to pursue this for now because of IP issues; the terms on
> > the SPIRIT documents make me leery of using them for an open source
> > program, at least without talking to a lawyer about it first.
> 
> Are these documents public?  If not we should stay away from this
> stuff.  But if they are public, I can't see why we cannot implement an
> interface specification.

You have to register and agree to their terms to get a copy:
www.spiritconsortium.com.  However anyone can register, which
wasn't obvious to me the first time I looked.

Implementing an interface specification is not necessarily OK depending
on one's jurisdiction and what patents are involved; that's one of the
reasons there's a lot of people who object to software patents :-)  It
is entirely possible to write an interface such that any use of it
would require a patent license, or more than one.

I'm not saying that that's the case here, but the disclaimer certainly
suggests that it may be:

b) COMPLIANCE WITH THE SPIRIT SPECIFICATION MAY REQUIRE USE OF ONE OR
MORE FEATURES COVERED BY PATENT RIGHTS OR OTHER INTELLECTUAL PROPERTY
RIGHTS OF A CONSORTIUM MEMBER OR THIRD PARTY. THE MEMBERS TO THE
CONSORTIUM HEREBY EXPRESSLY DISCLAIM ANY LIABILITY FOR INFRINGEMENT OF
INTELLECTUAL PROPERTY RIGHTS OF OTHERS BY VIRTUE OF THE CONSORTIUM
SPECIFICATIONS, NOR DO THE MEMBERS TO THE CONSORTIUM UNDERTAKE A DUTY
TO ADVISE USERS OR POTENTIAL USERS OF THE CONSORTIUM SPECIFICATIONS OF
SUCH NOTICES OR ALLEGATIONS.

Anyway, my curiousity has been effectively engaged.  I'll take a look
at it.  If necessary I can find some US legal advice about the terms.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-26 21:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26  7:01 Daniel Jacobowitz
2006-01-26 12:45 ` Andrew STUBBS
2006-01-26 13:41   ` Daniel Jacobowitz
2006-01-26 16:24     ` Andrew STUBBS
2006-01-26 16:41       ` Daniel Jacobowitz
2006-01-26 17:34         ` Paul Koning
2006-01-26 17:44         ` Andrew STUBBS
2006-01-26 18:55           ` Daniel Jacobowitz
2006-01-26 21:05         ` Mark Kettenis
2006-01-26 21:26           ` Daniel Jacobowitz [this message]
2006-01-26 21:57             ` Mark Kettenis
2006-01-26 22:02               ` Daniel Jacobowitz
2006-01-26 22:32                 ` Bob Rossi
2006-01-26 20:39 ` Mark Kettenis
2006-01-26 20:43   ` Bob Rossi
2006-01-26 21:41     ` Mark Kettenis
2006-01-26 20:52   ` Daniel Jacobowitz
2006-01-26 21:12     ` Bob Rossi
2006-01-27  0:47 ` Bob Rossi
2006-01-27 18:04 ` Eli Zaretskii
2006-01-27 18:41   ` Daniel Jacobowitz
2006-01-27 18:57     ` Eli Zaretskii
2006-01-27 19:06       ` Paul Koning
2006-01-28  6:33         ` Daniel Jacobowitz
2006-01-28 13:54           ` Jim Blandy
2006-01-29  4:09             ` Eli Zaretskii
2006-01-29  4:27             ` Paul Koning
2006-01-28  5:24       ` Daniel Jacobowitz
2006-01-29  4:33 Paul Schlie
2006-01-29  6:18 ` Jim Blandy
2006-01-29 23:21   ` Daniel Jacobowitz
2006-01-29 23:24   ` Paul Schlie

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=20060126211252.GA17685@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox