[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: US Patent 6,687,897


lemelson list patents
James Anderson wrote:
> hmm, 15, 16, and 21. is that the invention?
	Every one of the claims should be a distinct "invention". If
only 15, 16 and 21 were "inventions" then only those three claims
should have been granted by the patent.

> of 15, 16: aha! these claim the use of a list menu to 
> effect the selection from a multiplicity of the script options.
	The "List Menu" described is basically just the menuing system
of the circa-early-80's ALL-IN-1 product and many other products,
tools, etc. that came afterwards. Building menu driven interfaces on
compound document systems is not a new idea.

> as 6,687,897 claims no mechanisms beyond those described in 
> standards-track documents at the time of its filing, it will
> be entertaining to see an attempt to enforce it.
	No. It will not be "entertaining." It will be a complete waste
of everyone's time while in the meantime, anyone who attempts to use
the methods described in this patent will be forced to spend excessive
amounts of time studying the patent and explaining to management,
investors, etc. why the patent should be ignored. This is a tremendous
negative impact on innovation.
	My personal opinion is that the W3C should gather prior-art
and arguments and file with the PTO for a review of this patent and
the others like it. It should be done *now* -- the sooner the better.

> rdf/owl are now recommendations. i can't wait to read about 
> the next wave of patents.
	It may already be too late, however, the wise course of action
would be for the W3C or some other organization that cares about RDF
to begin the process of building a comprehensive SIR (Statutory
Invention Registration) that can be filed to block as many patents as
possible. As I've mentioned in earlier notes, the SIR should contain a
specification that attempts to record as much as possible of all the
possible applications of RDF and methods of application that anyone
can think of. The process of building the SIR should be done like with
other internet documents -- i.e. open, permanently recorded
discussions via mailing list, etc. so that the discussions themselves
(considered "published materials" by the PTO) can be used in
establishing prior-art for anything that slips through the cracks.
	
	bob wyman


-----Original Message-----
From: james anderson [mailto:james.anderson@s...] 
Sent: Saturday, February 14, 2004 8:19 AM
To: xml-dev@l...
Subject: Re:  US Patent 6,687,897



On Friday, Feb 13, 2004, at 23:03 Europe/Berlin, Bob Foster wrote:

> Michael Kay wrote:
>
> > I find it completely bizarre that this kind of thing can get past 
> > the "obviousness" test.
> >
> > The US Patent Office is clearly not applying stringent enough
> criteria.
> > What I would like to know is, is it a conspiracy (protectionism
for
> the
> > US software industry, jobs for the lawyers), or is it just
> incompetence?
>
> I believe it's just that your definition of "obvious" and the legal
> definition are far apart.
>
> Programmers are inventors by nature. They routinely replace
> algorithms, formats, languages, protocols, etc. with not quite 
> interchangeable equivalents to improve performance, reduce overhead,

> expand interoperability, etc. More rarely, they create a new one of 
> these things. So they view replacement by near-equivalents and 
> creation of new alternatives as very different processes.
>
> A patent lawyer's view of "obvious" is very different. According to
> http://www.bitlaw.com/patent/requirements.html, patent examiners
test 
> the nonobviousness requirement by seeing if prior patents can be 
> combined to produce the claimed invention. They don't take an
opinion 
> poll of people skilled in the art. If the prior art does not include

> all the elements in the claim, it will not fail this test.

6,687,897 has 27 claims.
of 1 and 2: do they describe any improvement to even just the prior
art 
which has already been mentioned in this forum?
of 3 and 4: do they describe any improvement to
WD-html-in-xml-19981205 
and those of its successors prior to 20001201?
of 5 through 14, 17, 18, 19: do they describe any improvement to 
WD-xml-961114 and those of its successors prior to 20011201?
of 15, 16: aha! these claim the use of a list menu to effect the 
selection from a multiplicity of the script options.
of 20 and 22 through 27: do they describe any improvement to 
WD-xml-961114 combined with WD-DOM-971009 and their successors prior
to 
20001201?
of 21: aha! this claims an improvement to WD-html-in-xml-19981205 etc.

which puts script elements directly under the root element.

hmm, 15, 16, and 21. is that the invention?

>
> They will also consider whether the invention can be derived from an
> existing invention by simply substituting one "material" for
another. 
> Bob Wyman thinks this should stop patents like the one in question, 
> but I don't see it. If the "material" substituted brings any 
> measurable improvement to an existing process, then use of the 
> material is patentable (or DuPont would have gone out of business
long 
> ago). An equivalent, I'm afraid, means almost exactly equivalent,
like 
> the substitution of one inert ingredient for another.

if any of the claims were to have used the word "by" in any sense
other 
than generic agency, there might be some argument for "improvement". 
the claims are all "that" something is done. none of them describes 
either a process or a mechanism. patents which claim nothing more than

"that" cannot meet a usefulness requirement. where they claim no 
mechanism, it is not possible judge usefulness, as one cannot judge a 
non-existent mechanism.

the recent ruling in the automatic identification / lemelson case[0] 
points out at how this issue will make patents of this sort both very 
hard to defend, and an embarrassment to both the filing agent and the 
examiner. one reason the lemelson foundation's income stream is likely

to come to an abrupt end, is that the purportedly infringing products 
do not embody the claimed mechanism. it was not sufficient to claim
any 
mechanism which accomplished a similar end. to the extent that 
lemelson's patent's mechanisms could be interpreted, they specified
the 
extent of the claims. another reason lemelson failed, is that his 
patents do not enable a practitioner to carry out the invention. as 
6,687,897 claims no mechanisms beyond those described in 
standards-track documents at the time of its filing, it will be 
entertaining to see an attempt to enforce it.

rdf/owl are now recommendations. i can't wait to read about the next 
wave of patents.

[0] 
http://www.psionteklogix.com/assets/downloadable/lemelson_decision.pdf


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.