IBM Snags Patent On Half-Day Off of Work Notifications
theodp writes "The USPTO appears to have lowered the bar on obviousness, awarding a patent to IBM Tuesday for its System for Portion of a Day Out of Office Notification. 'Out of office features in existing applications such as Lotus Notes, IBM Workplace, and Microsoft Outlook all implement a way to take a number of days off from one day to many days,' acknowledges purported patent reformer Big Blue. 'Yet, none of these applications contain the feature of letting a person take a half-day or in more general terms, x days and x hours off.' Eureka! And yes, the invention is every bit as obvious as you can imagine."
Then I demand a patent on going to work.
To offset political mods, replace Flamebait with Insightful.
It's time for pitchforks and torches at the USPTO...
THE SOFTWARE, IT NO WORKY!!!
Imagine being the guy that wrote this patent with a straight face. Must suck to be soulless.
I'm wondering if anybody knows if IBM has a patent on employees having to ask to go to the bathroom. That was one of the more unique aspects of working at IBM, in my experience.
I don't respond to AC's.
if any one has patented the process of taking a crap yet?
I can already do this in Outlook, and have done so on several occasions... how is this new?
I was going to state how even our in house payroll software lets us put in for portions of a days leave, but then I realised this is about automated out of office notifications - and I'd have to admit, obvious as it is most of the ones I've seen work with dates, not portions of dates.
Outlook has had this for ages. You simply schedule a meeting for an arbitrary period of time and set the availability to 'out of office'. How is this any different?
I'll take my royalties at my Post Office Box.
I may not remember correctly, but doesn't Office 2007 and above have an option where you can set what time to enable/disable the out of office message? That would seem to cover this patent. When was the application made?
What do folks at the USPTO do, exactly? You would think any reasonably-intelligent person would reject this on obviousness grounds and not even need to find prior art.
I have outlook 2010 and it already does this, unless I'm missing something...
From the end of the Microsoft Documentation:
If you selected the “Only send during this time range” option in step 4, the Out of Office Assistant feature will continue to run until the date and time set for the End Time in step 5 is reached.
Otherwise, the Out of Office Assistant will continue to run until you repeat step 1 and select the “Do not send Out of Office auto-replies” option.
The dialog in question even looks like the one in the patent...
At least it seems that the patent is not that generic, their claims are specific to EJB.
Where's the payoff for the avalanche of poor patents? IBM isn't getting paid, the USPTO isn't better off, so are the politicians getting paid? Why is this system continuing? Two reasons I can see: protection for the largest companies against new start-ups, and getting foreign countries to adopt US Patent laws and extort their corporations. But is that really it, is that the whole game? IBM isn't full of idiots and the politicians are (always) working an angle, so why this continued patent madness?
tomorrow who's gonna fuss
I can add that IBM's Lotus Notes 8.5 -- released in 2009 -- already had the ability to specify hours of a partial day.
Beware of the Leopard.
AND now under the new system we will know who to drop down to part time list. P.S no benefits for part timers
what are they talking about? Outlook does this now...it's called setting the hours....maybe I am missing the exact feature this article refers to...
...with IBM tools, at my current client project. Can I then file a patent for not going to work ?
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
Or are you one of those "Emma, come 'n look at this - you ain't gonna believe it!" types?
"Method and system for taking a crap."
1. Eat food (see our related patent application for "Method and system for eating food";
2. Wait. (period of time depends on food eaten and any contamination such as salmonella, see our related patents and our "brown paper" on "Montezuma's Revenge")
3. Do what comes naturally.
A good chunk of these BS/trivial patents stem from devs gaming the system.
Many corporations, and I imagine IBM is one of them, have patent bounties that are paid out in a multi-tier system:
- propose a patent application that passes the internal corporate review board: small $ bonus
- get the patent app files: bigger $ bonus
- have the patent granted: big $ bonus
I've known a few devs who have made a nice chunk of change in annual bonuses because they've learned the system. From devs on the line, through management & in-house counsel, there is zero disincentive to filing these applications, and a lot of potential personal upside.
Did they only have to pay for half a patent also? The other half was off course bloody obvious.
Nae king! Nae laird! Nae yurrupiean pressedent! We willna be fooled again!
from the linked jpg:
Subject: Out for the afternoon
Body: I will be back tomorrow!
More like:
Subject: Sanity is out for the afternoon
Body: Sanity will NOT be back tomorrow!
The USPTO is allowing IBM to profit from the polar opposite of true innovation.
Quick! Snap up the patents for minutes, seconds, milliseconds, microseconds...
The patent office's real job is to keep all of society locked in their cubes, think of dumb things that produce nothing but will make a ton of money, forget that society even exists, and depend solely on food delivery and masturbation for survival. So, let us patent "method for masturbation." Yes, the traditional one. What, me invent something?
Build your own energy sources from scratch. http://otherpower.com/
"I will be $planned_function from $begin_time_date to $end_time_date. $optional_custom_message"
FFS, I implemented this with procmail and a couple of shell scripts fed off my PalmPilot schedule back in ancient times.
Have gnu, will travel.
Even in 2006, this would have been an obvious solution for anyone in the field.
You can specify to the HOUR when you will be out of office until.
How does this not cover half days?
Turn On Out of office message: January 4 @ 5pm
Turn Off Out of Office Message: January 5 @ 12pm
See what I did there? Genius!
I just filed a patent application about filing stupid patents...
- We's gonna be rich, ma!
If companies don't patent every possible angle of everything then a troll will get that patent and go on the attack. The patent office has lowered the bar to the point that everything and anything is patentable and MUST be patented for self protection. This patent is purely the fault of Congress for ignoring the patent offices downward spiral to economic zombie. Braaaaains! Braaaaaaaaains!
Because this:
is clearly obvious?
.. a system to deliver quarter-day off notices ..
Hey don't blame me, IANAB
1. A system for generating an electronic notification containing a portion of a day out of office notice, comprising: an application server node operably associated with a database server having an application data supporting personal information management (PIM) system, the application server node configured to execute a personal information management application, the application server node further configured to store the personal information management application; an application programming interface (API) programmatically associated with the personal information management application for allowing requests for services to be transmitted to the personal information management application; at least one of a rich client delegate and a remote enterprise Java bean (EJB) housing the API, the rich client delegate and the remote EJB are programmatically associated with the application server node and the personal information management application, the rich client delegate being configured to receive and transmit data to the API via a network; at least one client computer operably associated with the application server node via the network, each client computer having a user interface (UI) that is programmatically associated with the personal information management application and the API such that a user may input date with timestamp to-the-minute data corresponding to an out of office time period into the UI and transmit the date with timestamp to-the-minute data from the client computer to the API; and wherein one rich client delegate is programmatically supported by a business logic member, the business logic member being configured to receive the date with timestamp to-the-minute data entered by the user via the UI by way of the supporting business logic member, the rich client delegate further configured to transmit the date with timestamp to-the-minute data to the API of the remote EJB; wherein the application server node further includes a mail transfer agent (MTA), the mail transfer agent being programmatically associated with the personal information management application and the API; wherein the mail transfer agent includes three phases, (i) a receiving phase for the an Simple Mail Transfer Protocol (SMTP) server (ii) a handling phase for handling name resolution, group expansion and content analysis, and (iii) a delivering phase for performing local and external mail delivery, wherein the delivery phase includes a delivery extension member for allowing plug-ins to add new functionalities, the delivery extension member being programmatically associated with the personal information management application and the API; wherein the MTA includes an out of office filter member, the out of office filter member being programmatically configured to be a plug-in to the delivery extension member, wherein the MTA includes an out of office service; and wherein the rich client delegate and the remote EJB are configured to receive the transmitted data from the client computer and forward the data to the API.
And that's a lot more than that one single figure.
Just because other people can think of an invention does not mean the patent should not be filed. A patent is largely about someone creating something novel nobody has thought of, or more likely got their patent filed first in the case where the invention is easily repeatable.
What should rule out a patent is previous art. If someone else implemented this feature prior to IBM filing for the patent, or it can be proven that someone else implemented this feature before an IBM product implemented the feature, then the patent is not valid. Maybe the patent office may not be doing due diligence on awarding patents in this case as I have seen examples of this in other products.
I agree there is a problem with the current patent system, but every time someone complains about patents they usually don't have the right information. There is nothing about filing a patent which states the invention cannot be obvious. If nobody bothers to create a product using the idea, or nobody bothers to file an patent for it, then the its only obvious to the people that were to lazy make the idea a reality.
I haven't thought of anything clever to put here, but then again most of you haven't either.
Subject says it all.
This is just a random thought: what if there were a limit to the quantity of patents that one entity's portfolio (individual or CORPORATION) could maintain. This would prevent all the ambiguous patents being filed. Yes I can hear it already: "But some inventors are on a roll and come up with all kinds of ideas!" So let them. If you have come up with 5 great ideas, assuming this is the limit, pick and choose what you think would be best monetized to make room for another. Possibly allow concurrent patents to exceed the limit, but only for a limited time. It could also have the fringe benefit of forcing companies to specialize again instead of T.V. makers also creating automobiles, bombs, drugs, and facial cream.
I feel like I've been taking crazy pills.
Mdaemon all ready allows you to set notifications with a start time and end time.
"A learning experience is one of those things that says, 'You know that thing you just did? Don't do that.'" - DNA
At work I've developed a system for exactly this in 2004. It was based on procmail. It is obvious.
I want a patent on "1" and "0".
"And yes, the invention is every bit as obvious as you can imagine."
The standard defense against this type of claim-without-support is that if it were obvious, and given that there are _lots_ of eyeballs on the subject matter, and given that it is highly useful, then someone would have already done it. Therefore, since nobody has done it before, it was not obvious.
The "it's obvious" rant is almost universal when someone sees an idea that they (a) know is good, and (b) understand. As an inventor and generally creative type myself, I can't tell you how many times people will say that something is obvious once I have explained it clearly to them, even though had I not done so, they would never have made the same invention in their lifetime. The corollary is that there is a high probability that they will then believe that the idea was their own. I once showed a choreographer the ending to her dance with which she was struggling; after its first performance, someone congratulated her on her work, especially the ending, and she took full credit even though I was standing at her side at the time.
You remind me of the parable of Colombus going into a bar and being given grief for discovering new lands. "Anyone could have done that... its obvious" say the patrons. And Colombus then proceeds to challenge anyone there to stand an egg on end. The patrons try as they may, the egg always rolls to its side and never stands straight. "It's impossible" they say. "Not impossible!" says Colombus, as he smashes the bottom of the egg to force it to stand on end, "merely not obvious." And then, of course, the patrons say "well, anyone could have done that." And Colombus responds "but no one did." (I probably messed this up... I can't tell a story to save my life... slashdot, please correct as necessary, kthx)
The Admin and the Engineer
That's a great story. Thanks.
OP
Four years ago I and the person who was going to replace me when I retired built a TimeRecs app that kept track of partial vacation or time off days for any dates and times in the future as well. It was build using APEX and dynamic HTML, so employees could access it with their browsers.
Running with Linux for over 20 years!
The standard for obviousness for the Slashdot echo chamber is "I sort of understood the vastly oversimplified summary"
I don't think it's clear, but it seems obvious. Is this anything more than a verbose description of a server sending OOO emails with some specific technologies mentioned?
I am going to patent "x days and x hours and x minutes off"
oh wait...I can go even further to seconds...damnnn
So he cheated...
Similar story, set on a basketball court: Melvin says to Poindexter, "I bet you can't make a basket with me guarding." Poindexter says "you're on", then whips out his brass knuckles, knocks out Melvin with an uppercut, and makes a basket at his leisure.
So in order to go to work I would have to pay you a licence fee? Fsck that I quit!
IMHO, it is not as bad as it looks from the comments here. I've read the patent itself, and the patent is not on the feature as such, but on a very specific implementation of it, with rich clients (that's filed in 2006!) - so web implementations are clearly not covered, with EJBs (so any other implementation is not covered too), and with a dozen of other (IMHO rather stupid) things (like having MTA on the same node as application server). With all of this, IMHO patent is overspecific and stupid, rather than overgeneric and obvious, and overspecific and stupid patents (as a rule of thumb) are not harmful to anybody except that for the owner. It is just like if somebody will make a patent of hammering the nails of specific size with a microscope of such and such model - it is (likely) a valid patent (non-obviousness likely established by referring to going against existing teachings), but it is very unlikely to cause any practical harm.
BTW, usually obviousness is treated as a matter of law, and not a matter of fact, so "jury in East Texas" probably won't be able to decide on obviousness (it is a matter of law decided by judge and appealed to CAFC if necessary).