Interwoven Patents Code Versioning

webengr writes "It seems like the USPO is pretty lenient when it comes to awarding software patents. CVS has been around for a long time, but now Interwoven has been awarded a new patent covering version control of web assets. The claims include, 'The use of a hierarchical file system and an object repository for representing and hosting content and its structure,' and 'The combined concepts of file history, versioning, comparison, and merging as it relates to content, provide an archive of all individual changes as well as collections of changes so they can be versioned and audited.'"

Comments

Lenient? No.

[burgburgburg]

Asleep at the wheel, recklessly driving us all over a cliff of patent infringement lawsuits? Yeah, that's fair.

Ugh.

[Anonymous Coward]

When will the patent office get a clue? Doesn't *anyone* there make even the slightest attempt to search for prior art? A 5 minute google search should have invalidated this patent.

Re:Ugh.

[HBI]

2) Over 90% of the serving members of the 3 branches of government were lawyers. Lawyers and old-money own the government(now more than ever). Do you think they will regulate themselves?

Where did that come from? Even *appointed* officials aren't 90% lawyers, and rank and file government employees sure as hell even aren't *mostly* lawyers. It's a tiny, tiny fraction of the total government work force.

USPTO sucks, but let's not get carried away here.

article in case of server meltdown

[mrhandstand]

pertinent info frfom article

Interwoven's U.S. patent (#6505212)

A system for asset management comprised of multiple workareas, each configured to maintain a virtual copy of content as it would appear when published;

A staging area to which content is submitted from multiple work areas and where any conflicts between content can be resolved;

Branches and sub-branches (for different projects or initiatives) that contain individual workareas, staging areas, and editions which allows for massively parallel development on a single platform;

The use of a hierarchical file system and an object repository for representing and hosting content and its structure;

Virtualization of all content regardless of location as well as Web and application servers - this allows contributors to make changes "in context" of the entire site;

The combined concepts of file history, versioning, comparison, and merging as it relates to content, provide an archive of all individual changes as well as collections of changes so they can be versioned and audited.

Re:article in case of server meltdown

[Anonymous Coward]

Regardless of what Interwoven's site says, here are the 13 actual claims that define the scope of their exclusive rights. Pick the braodest among these and see if prior art exists that discloses each and every limitation. If so, great.

The point to remember, gentle reader, is to put zero stock in the company-paraphrased/sweeping language on their website. To quote (or at least paraphrase) a famous patent law scholar and judge, "The name of the game is the claim." IAAL, a patent one at that.

1. A system for file management for files containing website content comprising:

a work area configured to allow a user to create and maintain web content to be displayed on a website, the work area being a file system having read and write operations to enable a user to edit virtual representations of files having web content that is located in the work area; and

a staging area adapted to receive and integrate the web content submitted from the work area when the web content of the work area does not conflict with other web content submitted to the staging area and configured to retain versions of web content submitted from the work area.

2. The system of claim 1, further comprising a plurality of work areas configured to allow different users to create and maintain web content to be displayed on a website, wherein the staging area is adapted to receive web content changes of files modified in the work areas and is configured to check for conflicts in web content received from two or more work areas.

3. In a system having a plurality of file systems containing web content, for use in a system for developing virtual copies of web content to be displayed on a website, a method for maintaining the history and ancestry of the web content of an item in each of the file systems in which the item is included, the method comprising:

associating a history object with a first item containing information related to the revision history of the item web content;

associating information related to the ancestry of the item web content; and

maintaining an entry in the history object for each file system in which the item is included that identifies the web content associated with the first item in that file system so that conflicts with other items and their associated web content may be ascertained.

4. The method of claim 3, further comprising:

associating new web content in one of the plurality of file systems with the item;

modifying an entry in the history object corresponding to that file system to indicate that the item is associated with the new web content; and

adding a reference to the previous web content in the new web content.

5. The method of claim 4, further comprising:

determining whether a second item is in conflict with the first item by determining whether web content in the second item are previous web content of the first item.

6. A method for developing a website by resolving potential conflicts in web content submitted to a web content staging area by a work area where virtual copies of web content are developed, comprising:

modifying data associated with a selected object in a work area that is related to web content to be published on a website;

determining whether other web content is in conflict with web content developed by the work area;

resolving the any conflicts among the different web content; and

submitting web Content from the work area to the staging area where web content is staged before being published on a website.

7. A system for developing a website comprising:

a work area defined within a memory location and configured to enable a user to edit virtual copies of web content by editing files containing web content within the work area and to submit web content to be staged for publication on a website; and

a staging area defined within a memory location and configured to receive web content submitted by a work area, to determine whether conflicts exist between web content submitted by any one work area and other content to be staged in the staging area, and to integrate web content submitted from a work area when the web content of the work area does not conflict with other content submitted to the staging area and to maintain versions of web content sent from a work area.

8. A system according to claim 7, wherein the work area may be characterized as a file system stored within memory and having read and write operations to enable a user to edit files containing web content in the work area; and

wherein the staging area may be characterized as a file system for staging web content developed in a plurality of work areas and stored within memory and capable of receiving web content from a work area, the staging area including a versioning mechanism configured to maintain versions of web content received from a work area and an integration mechanism configured to integrate web content received from a plurality of work areas when the web content does not have conflicts.

9. A method for modifying website content, wherein the method is configured for use in a web content modification system having at least one. work area for modifying virtual copies of web content and a staging area for integrating web content submitted by one or more work areas, the method comprising:

modifying virtual copies of web content of a selected object in a work area;

analyzing the web content of the work area to determine whether it is in conflict with other web content submitted to the sting area; and

in response to said other web content not being in conflict with the web content of the work area, submitting the web content modified in the work area to the staging area; and

in response to said other web content being in conflict with the web content submitted by the work area, not submitting the web content to the staging area.

10. The method of claim 9, further comprising, in response to said other web content submitted to the staging area being in conflict with the web content of the work area, rejecting the web content from being submitted to the staging area.

11. The method of claim 9, further comprising, in response to the other web content submitted to the staging area being in conflict with the web content submitted to the staging area by the work area, refraining from submitting the web content of the working area to the staging area for integration with other web content.

12. The method of claim 9, wherein analyzing the web content of the work area to determine whether it is in conflict with other web content submitted to the staging area further includes analyzing the web content of the work area to determine whether the web content of the work area shares a common ancestry with other web content submitted to the staging area by a work area, wherein if the web content of the work area shares a common ancestry with the other web content, no conflict exists, and wherein if the web content of the work area does not share a common ancestry with the other web content, a conflict exists.

13. The method of claim wherein analyzing the content of the work area to determine whether it is in conflict with other content submitted to the staging area further includes:

analyzing the content of the work area to determine whether it is the same content as and whether the content of the work area shares a common ancestry with other content submitted to the staging area;

if the web content of the work area is not the same as the other web content submitted to the staging area, a conflict exists and the web content from the work area may not be submitted to the staging area;

if the web content of the work area is the same as the other web content submitted to the staging area, a conflict does not exist and the web content from the work area may be submitted to the staging area;

if web the content of the work area does not share a common ancestry with other web content submitted to the staging area, a conflict exists and the web content from the work area may not be submitted to the staging area; and

if the web content of the work area shares a common ancestry with other web content submitted to the staging area, a conflict does not exist and the web content from the work area may be submitted to the staging area.

Re:article in case of server meltdown

[Ashran]

1.) Mirror Page Content
2.) ???
3.) Karma

Re:article in case of server meltdown

[Anonymous Coward]

I don't think that Interwoven's patent should be dismissed out of hand just because it incorporates the functionality of a traditional SCM system. As someone else remarked, improving on an existing idea CAN be legitimately patented.

Doing large-scale web development poses special problems that are not covered by conventional SCM systems.

For example, it's simple to preview a single web page you are working on in isolation--you just point your browser at the URL for the page. But what if you are replacing an existing part of a complex web application, and are working as a member of a team? Yes, an SCM system will help you keep track of the files and integrate the source changes. What it will NOT do is give you an environment in which you can use a web browser to debug your piece of the project. You have to set up a private development environment manually, and that's a real pain--you have to make sure all the URLs pointing to the various pieces are correct for your test environment in each file. You have to make sure that when you press the "Submit" button, the right CGI program is called (the one you are working on, or the "real" functional one, depending on what you are trying to do), and that the correct page comes up when a link is triggered. You have to make sure all the external references point to files you want to use for testing--i.e., that the correct Java Script files are being included, and so on ad infinitum. And you have to make sure that none of this interferes with the current application that is open to real users, or with your fellow developers. Like I said, a PAIN.

After unit development is done, you want to integrate everybody's work and do beta testing. Again, you can build a conventional application tree using a conventional SCM for this, but the SCM won't do it for interactive testing in a web environment. Once again, you have to change all the references so they point to the right places, and make sure everything works together. More PAIN. My head hurts. OUCH.

Lastly, you have to take the whole ball of wax and drop it in place of the existing application for real use. Again, an SCM will give you the finished code--but it won't fix the URLs in the code and create the web hierarchy in the right place for you. This must be done manually, and you have a good chance of screwing up and breaking the application. Maybe if I drill a hole right HERE in my forehead it will let the evil spirits out and I will stop hurting.

And when you've finally installed the new code and find out that something that worked perfectly well in Beta doesn't work in production because it interacts with something else on the same server that you didn't even know was there all along, you are screwed. If Interwoven's software will help me back out the changes and retrieve the previous working version before half a million people notice, I would be very grateful to them at this point. Really, I can do without my first-born.

Is the phrase 'web assets' significant ?

[aron_wallaker]

I'm just wondering if the patent being granted is someone hinged on Interwoven's claim to be the first to do version control for 'web assets' (ie, HTML, images) as opposed to source code.

The fact that there's no technical difference between version control on an HTML file and version control on a 'C' file seems to be the sort of thing that's lost on the patent office.

Re:Is the phrase 'web assets' significant ?

[jfx32]

Zope has built in version control for it's 'web assets', and I am pretty sure they predate Interwoven at doing so.

Re:Is the phrase 'web assets' significant ?

[treke]

what do you expect, patent clerks arent exactly Albert Einstein

Re:Patents out of control

[cindik]

I think I shall patent "a means of using a patent to create ownership of an obvious method of using existing devices or methods so as to stifle innovation and help lawyers buy new cars"

Ha. This will have no effect on me!

[Sun Tzu]

Unless one of the claims covers working on programs in one big file (tm) and saving off another copy with a new extension (1,2,3,4,5,...) with every significant change.

Heh, I knew my slackerly habits would pay off eventually!

Send us your Linux Sysadmin articles

Lost work at the patent office

[Anonymous Coward]

Nobody at the US Patent office must version control their documents. Maybe thats how patents get awarded so easily?

And in a related story...

[TrollBridge]

"It seems like the USPO is pretty lenient when it comes to awarding software patents."

And in our next story, Microsoft is now widely perceived to be the playground bully of computer software.

lenient ? are you kidding ?

[Booie Paog]

"It seems like the USPO is pretty lenient when it comes to awarding software patents." no kidding. the USPO appears, in some cases, to not only be lenient, but to be completely oblivious to the purpose of having patents, as well as having wild interpretations of patent law. software patents, the way that they are currently handled, is incorrect, with regards to the original means that was set out by even Thomas Jefferson himself. to be able to patent compiled binary code, without regards to the source, or ENTIRE details of the mechanism that the software is implying is insane, and will continue to destroy the legal ability to innovate based on derivative work.

New Rules

[glh]

I think the patents should be reformed in the following way:

1. Submit the patent idea to the patent office- as a "pending patent".

2. Patent office does a search (web or otherwise) on prior art, billing the individual/corporation that submits the patent at a standard rate. If no prior art is found, the patent office does not bill. The company is able to challenge any claims to prior art. Each challenge to a claim at prior art costs a certain fee.

3. Patent is awarded to the individual/corporation.

Basically the idea behind this is that companies will be charged for their stupidity. It will discourage patents on ideas that are already "out there" (patented or not). At the same time, it will *not* discourage individuals from ligitimate patents as they will be reimbursed for the "prior art search fee".

In addition, the Patent Office still gets its money and they begin providing real value.

Until something like this happens, we will all have to groan as the patent office continues to do stupid stuff and lawyers get richer.

Re:New Rules

[Slime-dogg]

Or, conversely

1. USPO submits claim to Slashdot as a news item.
2. Comments follow, listing examples of prior art.
3. Highest moderated comments are then re-submitted to the USPO, with a summarized recommendation based on all mid-high moderated comments

I don't think that I've seen patents go through /. and not read examples of prior art in the commentary.

Maybe

[YanceyAI]

Some of you guys should get a job reviewing patent applications. You seem to know more about prior art & novelty than these patent officers do.

jeez

[maxbang]

I just patented the process of "using organic photoreceptors to relay electronic signals via sheathed sodium channels to a core carbon based processing unit to elicit saturation of iron-rich fluids in nether regions of humanoid body, and further organic electrical manipulation of calcium mechanics to stimulate fluid-engorged region." I'm willing to settle for $20,000 per license violation.

Comment removed

[account_deleted]

Comment removed based on user account deletion

Suing the patent office

[SWroclawski]

What I would like to see is if the patent holder then goes after someone for use of the patent and the defendnat challenges the patent in court, and if the defendant is correct and the patent is invalidated- the patent office itself should be liable for court costs, plus any lost revenue due to any possible injunction during the trial.

Enough of these cases and the patent office may begin to reforem itself in when and where it grants a patent.

- Serge Wroclawski

Link to patent

[forand]

Here is a link to the actual patent.

The PTO has no incentive *not* to grant patents

[Sanity]

Their attitude is to grant patents left right and center, and let the courts sort it out. The have no real incentive to try and find prior art.

The problem is that in the time between the dumb patent being granted, and the courts sorting it out, severe damage can be done to people's freedom to innovate.

Recall that over the past 100 years (and beyond), significant advances in technology have almost always been despite IP laws, not because of them*

*Some examples:

• The modern movie industry set up in Southern California to escape from Edison's patents
• The VCR was fought tooth and nail by the movie industry even though 2/3rds of their revenue now come from video rentals and sales
• The proliferation of the commodity PC was only possible when IBM's BIOS was reverse engineered thus evading trade secret laws
• The Internet is currently under siege from copyright holders
• One of the worlds fastest growing operating systems, Linux, explicitly rejects the concept of intellectual property in its license

Re:The PTO has no incentive *not* to grant patents

[awol]

One of the worlds fastest growing operating systems, Linux, explicitly rejects the concept of intellectual property in its license

Unfortunately, no it doesn't. Indeed, Linux (and GNU) explicitly relies on IP to make the GPL binding. This is the problem, even the answer to IP, Free Software, requires IP in order to live because of the existence of IP in the first place. It is a classic Catch 22 situation

Re:The PTO has no incentive *not* to grant patents

[Anonymous Coward]

I don't think you're looking deeply enough. I think Stallman would be delighted if copyright was defanged, or totally removed. Until that time, the best he could do is to use it against itself.

It's much more of a philosophical thing. If everything was "free" then we wouldn't need the GPL.

This Move is Ironically Anti-Innovation

[McLuhanesque]

Deep in the company's website, they state, " With this patent, Interwoven joins the class of top tier software companies that recognize that market leadership is directly related to continued innovation combined with the protection of intellectual property. Patents represent the most effective and powerful way to ensure that a company protects its long-term investment in research, design and innovation."

Unfortunately, the fallacy of the first part of that self-serving statement is that history demonstrates the contrary: Innovation, especially in the area of software innovation, has been most successful in an atmosphere of sharing, openness, mutual support and peer-recognition. This is well-documented by Manuel Castells, Lawrence Lessig and others. Patents impede the advance of innovation by preventing potential competitors from innovating. With patent protection, innovation is limited to those who can afford the overhead of traaversing the patent minefield (as Stallman puts it). Those who choose to share innovation with the restriction that those who benefit also share their follow-on innovations - even when innovations pertain to other than software disciplines, accelerate the innovation process, and thereby support the development of a sustainably expanding economic infrastructure.

I do agree with the company's second statement: Patents are "most effective and powerful way to ensure that a company protects" its stuff. It just does very little for the rest of society, and for the economy in general.

This will never work

[MmmmAqua]

...there's too much prior art.

Oh, wait...

Re:PTO Link

[hpulley]

here is a clickable link to the patent at the USPTO.

Here's how to fix the patent process

[Schik]

Every patent that is filed for is posted on slashdot. If nobody says "I was doing this back in...", then they get the patent.

Next on Fox: "Leave it to Beaver, thePatent Clerk"

[Colonel Panic]

Beaver: "Hey Wally, getta load of this! It's another one of them swell software patents!"

Wally: "Well, you remember what the memo said, if it's got the the word 'web' in it then you should accept it, otherwise you're gonna get it when the commisioner gets back."

Beaver: "Not only does it have 'web' it's got 'web assets' and 'version control', what the heck is that?"

Wally: "No idea, but it sounds good. Hey just stamp the thing with the 'ACCEPTED' stamp and let the lawyers sort it out; we're gonna be late for beer at The Prior Art tavern."

Beaver: "Yeah, wouldn't want them lawyers to be outta work, now would we. Well, that's ten I've accepted before lunch, let's get to The Prior Art, pronto!"

a real technological lynchpin

[GunFodder]

The patent for the integrated circuit was hotly contested between Fairchild and Texas Instruments when Jack Kilby and Robert Noyce both invented the integrated circuit at about the same time. The battle dragged on and by the time it was resolved it was totally irrelevant since both companies were making tons of ICs.

Re:wrong incentive

[ctxspy]

No it is not.

The parent is incorrect.

It's a non-refundable fee -- this fee is actually meant to compensate for the USPTO guys doing a prior art search.

-Tomaj

Only way to sort this out...

[IainHere]

I propose applying to the USPO for a patent on

"A system to allow full disclosure of innovative techniques or technologies, while permitting the applicant exclusive license to said technologies for a certain period."

They're bound to grant it, and once they do, you sue them into oblivion for infringing it.

To be fair you last item isn't true

[kfg]

The GPL embraces the concept of intellectual property law and uses it to forward the philosophical point of view that the *code* ( not the coder) should always be free.

If the GPL rejected the concept of intellectual property it would called "public domain."

The GPL is very much *not* the same as the public domain, since it forces contractual obligations. It can only do this because the code is *someone's intellectual property.* You use the code under license. Not right.

This is why we have BSD/GPL/Aritistic license religious wars.

The power of the GPL ( whether you think it's good or bad is up to you. Please note I'm only bringing up facts here, not making value judgements) is that with no concept of intellectual property you would have *no* rights to obtain source code. The GPL uses intellectual property law to force the code "free."

KFG

Open Source Patents

[DonkeyJimmy]

Does there exist a section of the open source community dedicated to seeking out obvious and prior-art patents for the purpose of making those ideas public domain (thus protecting us from companies doing the same but not making them public domain)? If not, there should.

Palm Vs Xerox

[bstadil]

An interesting development on the Patent issues is the latest battle between Xerox and Palm.

Xerox won the day as far as Infringement is concerned, however the appeal court "agreed with Palm's argument that the lower court failed to find out if Xerox's patented technology was indeed unique." and ordered that portion back to the trial court.

If Xerox looses the validity of the Graffiti patent it will set a much needed precedent and pave the way for future legal strategies in dissputes.

Attack the Patent rather than defend non Infringement.

Why is everyone overreacting?

[Dragonshed]

(I am not AL, nor am I ANAL)

First off, read the actual patent, not the press release.

The patent does indeed include version control elements, but further defines exactly what their product does. See section 2, for example:

"The system of claim 1, further comprising a plurality of work areas configured to allow different users to create and maintain web content to be displayed on a website, wherein the staging area is adapted to receive web content changes of files modified in the work areas and is configured to check for conflicts in web content received from two or more work areas. "

There are very many products out there that do version control. But, there are very few that provide robust Content Management, which includes version control, but also includes a system to quickly and directly retrieve content for a web site/application and other such ammenities described in the patent. You would never do such a thing with CVS, unless you're insane.

What this does endanger is projects like Zope with it's CMS framework, which does alot of what is described in this patent. Versioning, browsable "file system" (html browsable, not unix mountable :p), submission and workflow associated with the content, embeded webserver, etc. These are features which parallel Interwoven's offerings (albeit at a smaller scale).

So, having said all this, I don't see why everyone is freaking out. The patent obviously addresses a complex Content Management system, not a simple version control system. I'm sure a simple-minded judge would be able to tell the difference once given the facts.

Re:Why is everyone overreacting?

[Un pobre guey]

I am as upset about idiotic patents as the next guy, but I agree with the several posts that point out that there are some novel elements to the patent that are built upon prior art. You can use as much prior art in your patent as you like. What you are patenting, and can defend in court, are the novel aspects not found in the prior art and which are not obvious to skilled practitioners. At some point, someone needs to make a few bucks on an invention in order for there to be incentives to generate new technology.

The historically interesting aspect of licenses such as the GPL lies in the possibility that some people would forego the monetary profits for the greater good of both the inventor and the community. If you want to make a buck, fine. If you want to share with and among others, fine too.

Unfortunately, the USPTO is becoming less able to function as the arbiter of the rules, and this is what causes the system to degrade. In fairness to those poor schmucks, it is not realistic to expect young, underpaid, undertrained, inexperienced patent examiners (or even not so old or inexperienced) to be able to consistently and without errors or omissions spot all issues relating to obviousness and prior art. The volume of patent submissions also thwarts the system, at least as it pertains to high tech patents.

dont get panties in uproar

[chron]

I've used TeamSite for years.. and checked out the patent. everyone needs to settle down. Interwoven uses some clever tricks in the caching and indexing in their management system that go above and beyond what something like CVS does.

This is what they're pantenting. TeamSite was actually built on top of CVS when the project started, but the standard content manageement scheme is not what's being patented here..

Re:Total troll...

[47PHA60]

If you're going to make this assertion, you should say exactly what is "so much more" about this patent. I read Interwoven's press release. They say that the patent contains 13 claims.

I read all 13 claims of the patent (go to the Patent and trademark office and do a "Quick Search" for patent #6505212, and saw an exact description of all the features CVS and Clear Case users have enjoyed for years. Six years ago I built a system using PVCS to manage source code and a 7 platform build system, and three years ago I adapted it to CVS for management of a website managed by 45 writers and programmers. It included a staging area, individual or team work areas, and the ability to search versions by content.

Following the 13 claims are the details of the patent; there is nothing there that cannot be done with CVS and some perl or python scripts. The "virtualization module" is similar to perl I wrote to run the site. The user typed in the URL with the CVS label and they would get the site in their browser as it appeared when labeled. Clear Case did the same thing with a file system view.

Nothing personal against Interwoven; if their product works it's worth the money, but it does not deserve a patent.

My prior art: Versioned website dating to 1996

[douglips]

And I can prove it:

support% sccs prs -e index.html
SCCS/s.index.html:

D 1.157 01/08/14 09:17:44 amorrow 157 156 00002/00002/00111
MRs:
COMMENTS:
kill target=_blank

[five years of history removed for brevity]

D 1.3 96/08/05 11:24:03 dvs 3 2 00001/00001/00089
MRs:
COMMENTS:
Highlighted "More" to emphasize that the list of links is incomplete.

D 1.2 96/08/02 12:42:21 dvs 2 1 00000/00002/00090
MRs:
COMMENTS:
Removed link to old interface

D 1.1 96/08/02 12:12:47 dvs 1 0 00092/00000/00000
MRs:
COMMENTS:
date and time created 96/08/02 12:12:47 by dvs

That is incorrect

[Srin Tuar]

The GPL would be unnecessary if there were no copyright law.

If there is no "copyright", then why would you need a "copyleft"?

GPL is supposed to spit in the face of copyright law. The beauty of it is that it does this by depending upon it.

If there were no copyright, then closed source would still be inviable: because anyone could copy it around. The difference would be that the BSD, LGPL, and GPL licenses would be effectively compatible, and I could finally see goddam SVG enabled in mozilla by default, etc.

The reason the GPL does not need copyright, is that eliminating copyright would eliminate the incentive to violate the GPL. Thats a catch 22.

Re:Can the USPO be sued? IANAL but...

[CrazyDuke]

You can not sue the government, or a governmental agency, without the permision of the government. You can, however, sue an employee of a government if they are personally negligent.

Re:my revision to your patent

[ideal]

Oh! I figured it out!

• Companies get idiotic patents
• Companies get lawyers to sue everybody
• Lawyers get rich
• Lawyers buy cars ... which cars? SUVs, of course, so ...
• Terrorists get rich.

It's all a plot by the terrorists! They've taken the USPTO! Run for the hills! AAAAAAAHHHH!


:-) I hope nobody really reasons that way :-)

I've got a solution

[PhilHibbs]

Set up a cron job that executes twice a week, and posts a "Patent system still fucked" story on Slashdot. That'll save a lot of effort.

In defense of the USPO

[Grotus]

A lot of posters have been criticising the USPO for not scrutinizing the contents of patents passing through their system closely enough. I would suggest that having the USPO carefully examine each patent passing through its system for prior art, obviousness, etc. goes way outside the bounds of their job.

IMO, as long as the patent is properly addressed, has sufficient postage, and doesn't set off the anthrax detectors, the USPO should move it straight through the system just like the rest of the mail.

Now the USPTO, on the other hand...