| « | December 2006 | » | ||||
 |
||||||
| S | M | T | W | T | F | S |
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
accident proneToday December 6, 2006 marks one year ago when Vertical Computers returned to life and made my pinksheet shares live again.
Let's hear three cheers for VCSY. HIP HIP HIP. We're still waiting for the Hurrah. You'll get the remainder of the cheers then.
http://www.devx.com/ibm/Article/31499
: : : : : http://www.devx.com/ibm/Article/31499
Instructive Information on Viper.
http://www.db2mag.com/showArticle.jhtml?articleID=191600158
Developers will have an easier time handling unstructured OR structured data with these capabilities.
Pfffwweet
A good topic for discussion and a good blogger.
http://headrush.typepad.com/creating_passionate_users/2006/11/why_web_20_is_m.html#comment-25904542
Why Web 2.0 is more than a buzzword
Posted by Kathy Sierra on November 26, 2006
Many people hate the phrase "Web 2.0" even more than they hate what they believe it represents. No, that's not quite right... many people hate the phrase precisely because they think it represents nothing. Or they're annoyed by the idea of a web version number. Or they think it's "elitist." Or they're convinced it's so much marketing hype. But what if it's not an empty phrase? What if it's simply a way of representing a concept that some people DO understand? What if it's like so many other domain-specific terms that sound like nonsense to everyone else?
That doesn't mean zillions of people haven't abused the term for everything from sounding tech-savvy to getting a piece of the hype-fueled-please-god-bring-back-the-bubble-and-I-promise-I-won't-piss-it-away-this-time VC pie. And it doesn't mean that there's all that much consensus even among those who think they DO know what "Web 2.0" means. But to say it means nothing (or WORSE--to say it's just a marketing label) is to mistake jargon (good) for buzzwords (bad). Where buzzwords are used to impress or mislead, jargon is used to communicate more efficiently and interestingly with others who share a similar level of knowledge and skills in a specific area.
Part of the benefit of being "into" something is having an insider lexicon.
It's not about elitism--it's about efficiency. It's not about impressing others--it's about a shared understanding of specific concepts. It's about being able to talk about ideas or processes or even parts with fewer words and (potentially) greater meaning. If two heart surgeons debate the merits of a new medical procedure, I'd be lost. Hell, I'm over my head when the conversation turns to cooking. But I can talk about cantles and pommels, and I know exactly what topline means in the context of collection. And I can talk about recursion and dependency-injection and backward-chaining. Just don't ask me how to carmelize.
Dinner conversations around my house often are about one of those two things--programming or horses--and most non-horse, non-developer folks might wonder if we're just making s*** up. But if you took away our jargon, the conversations would not just be slower, they'd be dumber. We couldn't converse on some of the more sophisticated, complex, higher-level ideas about horses or software development. The experience wouldn't be as rich, productive, or engaging. Strip away the specialized words and you strip away part of why being better is better.
One of the biggest mistakes I see community builders make (however well-intentioned) is fretting over inclusivity and newbie-friendliness. They want the beginners to feel welcome, and few experiences are more daunting than stepping into a new domain where you have no idea what anyone's talking about. It feels... uncomfortable. Confusing. Discouraging. But in our quest to cut the jargon and perceived (or even real) elitism, we risk ruining one of the biggest benefits of sticking with it. Not only should we allow domain-specific jargon or expert-speak, we should be driving it! We should help invent short-cuts and specialized words and phrases to make communication among our most passionate--our experts--even more stimulating and useful.
If you're afraid of newbies feeling intimidated or unwelcome, by all means give them a separate safe zone. Whether the newbie space is the default while the advanced users have their own special area (site, forum, club, whatever), or just the opposite--the advanced users are the default and the newbies get their own special beginner area, the key is to not sacrifice your advanced users in an effort to make beginners feel better. That's a short-term benefit to the beginner but a long-term wet blanket over those who might otherwise be more motivated to move up the ranks.
So... back to "Web 2.0"--I'll admit that this one's trickier than most domain-specific phrases because it wraps many different--and big and ill-defined--concepts. But when Tim O'Reilly and Dale Dougherty (the guy who first coined the term) talk about Web 2.0, it represents something real and specific and meaningful. Over time, a lot of other people (especially those who've spent time around them, including me) have come to understand at least a part of what they've encapsulated in that one small phrase. "Web 2.0" may be the least understood phrase in the history of the world, but that still doesn't make it meaningless.
Think of all the other words or phrases that mean nothing to us simply because we're not in that profession or hobby. Pop Quiz: From which domains do these sets of words or phrases come from? (And hey, try to see how much you can get without Google.)
A) The flop, the turn, and the river
B) purlwise, stockinette, double-pointed
C) snowman, gimmie, duck hook
D) blowbag, escutcheon, gas cock
E) grind, fakie, bluntslide
F) abseil, hexcentric, friend
G) sente, tiger's mouth, "black is thick"
H) break, build, "train wreck"
I) vermin type, use-activated, swarm subtype
J) ruck, maul, blood-bin
K) HIWAS, option approach, DOD FLIP
L) clipping, phantom power, patch bay
M) flashback, freelist, Scott
N) Class M, dilithium, positronic
First person to get all of them gets a surprise.
[UPDATE: once you look at the comments, you'll see everyone else's answers so... watch for the spoilers.]
[UPDATE: OK, new challenge... since everyone guessed mine so quickly, I'd love to hear YOUR idea for a set of three words/phrases from some domain/profession/hobby that the rest of us have to guess...]
Oh well. What's a good demo without at least one good boner?
http://fuvoo.com/FuvooPermaLink.aspx?PostID=169
Mister Ed: You will notice the URLs don't work because I say so. You will have to learn to cut and paste URLs to get your information. Trust me. It's good for you. Consider it exercise.
After thinking PHeaven was going to thrust our little cadre out in to the snow... they didn't and we aren't. BUT PH doesn't have some of the nifty visual and housekeeping capabilities as this place so I think we'll roll up the old bedroll and trek over to here for a while.
Sorry if you thought we were gone. We just went into "stealth" mode for a while.
Most clinical trials are designated as phase I, II, or III, based on the type of questions that study is seeking to answer:
These phases are defined by the Food and Drug Administration in the Code of Federal Regulations.
Phase 4 is continued further accumulative study beginning when the device has finished Phase 3 trials successfully. If the device doesn't pass Phase 3 successfully, the device can not be released for public use in the United States. If the tests are successful, the device may be used in the United States and presumably worldwide although the EU would have their own certification procedures.
You don't start with 1000-3000 test patients. You start with small patient batches, test the results, verify the results and proceed to the next batch with modulated criteria or halt tests to make modifications. If modifications are made, the test resets to the previous criteria until there is a satisfactory pass. If after X tries the results are not promising, you stop and modify or abandon.
This is why clinical trials can last for years. Eye progress and watch for problems.
According to this:
this study started in November of 2005 and expected to begin with 20 terminally ill individuals.
Inclusion Criteria:
Exclusion Criteria:
Previously on ProgrammersHeaven.
Re: As A Laughing Place is on life support...
By: Portuno_Diamo on October 08, 2006 at 5:02:24 PM
Read 1 times (Updated daily).
: I thought this appropriate.
:
: First, a bit of nostalgia for the old time information. Hallelujah.
:
: http://72.14.253.104/search?q=cache:qq9_adxBfNwJ:sec.edgar-online.com/2001/04/02/0001015402-01-000902/Section16.asp+alung+terry+washburn&hl=en&gl=us&ct=clnk&cd=1
:
: Always segment an individual's work with the biggest in his ranking.
:
: Then wonder why he "left". Was it because he got kicked out or is that a "spin"?
:
: Because SOMEbody has come into some monies.
:
: http://www.clinicaltrials.gov/ct/show/NCT00288964;jsessionid=14C624D69B73FB8FC78E069D3D134691?order=1
:
: We will come across situations in life where we could have used something like this.
:
Something in here?
http://www.pittsburghlive.com/x/tribune-review/business/s_186001.html
A fresh breath of air
By Dave Copeland
PITTSBURGH TRIBUNE-REVIEW
Wednesday, March 24, 2004
The technology for treating lung patients has been in use for more than 50 years in hospitals. Of the one million people placed on a ventilator machine each year, 10 percent develop pneumonia, and 80 percent need to be sedated to allow for insertion of the ventilator tube into their breathing canals.
Patients can't eat or talk when on a ventilator. And of the patients who develop pneumonia, 50 percent die.
But for its purpose, and for the time being, it's the best technology available.
A start-up company on the South Side is working to change that.
ALung Technologies Inc. is developing a new technology -- esstenially an artificial lung -- that its founders hope will replace the ventilator, which is so intrusive some patients sign legal documents that essentially say they would rather die than be ventilated.
"The bottom line advantage is it provides lung support while allowing your lung to rest and heal. A ventilator takes a lung that's already damaged and makes it work harder," said Dr. William Federspiel, a co-founder of ALung and director of the University of Pittsburgh's artificial lung research laboratory. "The analogy we always use is that if you break your leg, the doctor doesn't tell you to go out and start immediately exercising."
Federspiel, an engineer, connected with Dr. Brack G. Hattler in the mid-1990s and began working on a prototypes of the artificial lung. Hattler had some early patents from work on trying to develop an alternative to ventilation in the 1980s.
Hattler said he began working on prototypes back in the 1980s. All of the time since then, he said, has been spent improving the product and getting it ready for use in humans.
"We essentially made the devices in our own garages. We tested them in animals and, low and behold, the concept worked -- but not very efficiently," Hattler said. "What we showed at that time is that the concept was correct, but it wasn't at a level where it would be significant for patients."
Working together, Hattler and Federspiel developed what has become known as the Hattler Catheter. Inserted into a major artery through the upper thigh, the catheter feeds oxygen to the heart and takes carbon dioxide away, allowing an injured or damaged lung to heal.
In addition to improving patient comfort, the Hattler Catheter has some distinct advantages: patients are usually on mechanical ventilation for an average of 11 days at an average cost of $53,885, while the doctors expect the average patient on the catheter to be on the device for six days, at a cost of $24,493.
With about one million patients requiring ventilation each year in the United States, the two doctors recruited Nicholas Kuhn as chief executive and president of ALung to help raise capital and tap into an estimated $3 billion market.
"We've been pretty successful in positioning the company as a spin-out of the university," Federspiel said. "It's an interesting story about how it often takes a couple of different personalities with different skill sets to get a product off the ground."
In December, ALung moved into a new office in the Terminal Building on the South Side. The company has grown from two employees to 10, and expects to have 27 employees by next year.
"The university has no mechanism for taking technology and making it a reality where it would be available to patients, and that's really where it needs to be," Hattler added. "It's to the credit of the university that they have seen the necessity of allowing these ideas to be spun out and developed by industry. Hopefully, we'll be part of the Pittsburgh success story."
Kuhn has helped to raise close to $4 million to date. ALung expects to need $10 million to $12 million more to complete human trials, which are scheduled to begin this year. The company could gain regulatory approval and move the Hattler Catheter to market as early as 2006.
Kuhn also has helped the company tap into another potential market. He has been working with the Department of Defense to develop military applications. A soldier injured in a chemical attack, for example, could be placed on the catheter until his lungs had healed.
"If we had had this product ready before the last war, the army probably would have wanted to order a significant number of catheters," Kuhn said. "A soldier shot in the chest when he's wearing a flak jacket often gets a bruise on his lungs, which can cause fluid to build up. The catheter could be used in a situation like that."
"We think we can save hundreds of thousands of lives a year with this," Hattler said. "To be able to do that -- without even thinking about a company -- is very exciting."
Dave Copeland can be reached.
------------------
end
Happy hunting all.
Re: who is richwade?
By: Portuno_Diamo on October 04, 2006 at 8:34:51 PM
Read 1 times (Updated daily).
Reply Edit Delete message Bookmark Thread
: : Do you know who the Richwade poster is?
: : Anyway in case you missed it(which I doubt),but here's a couple of cut and pastes...
: :
: : VCSY Message list | Reply to msg. | Post new msg. « Older | Newer »
: : By: danfl_11
: : 19 Sep 2006, 10:58 PM EDT
: : Msg. 169308 of 170156
: : Jump to msg. #
: : rich, when is the next pr coming?
: :
: : « VCSY Message list | Reply to msg. | Post new msg. « Older | Newer »
: : By: richwade
: : 19 Sep 2006, 11:31 PM EDT
: : Msg. 169312 of 170156
: : (This msg. is a reply to 169308 by danfl_11.)
: : Jump to msg. #
: : octapuss 9th.
: :
: : then today...
: : By: danfl_11
: : 03 Oct 2006, 10:29 PM EDT
: : Msg. 170109 of 170156
: : Jump to msg. #
: : hmmmmmmmmm...October 9th??
: : http://www-306.ibm.com/software/info/television/websphere/index.jsp
: :
: : Enabling XML and SOA Applications with DB2 Viper
: : This Webcast teaches you about XML app development for the upcoming DB2 Viper. You will also learn about how to work with XML data in DB2 Viper through XQuery and SQL/XML using various development environments (Eclipse, .Net, etc.) and programming languages (Java, C/C++/C#, PHP, etc.).
: :
: : « VCSY Message list | Reply to msg. | Post new msg. « Older | Newer »
: : By: richwade
: : 04 Oct 2006, 01:08 AM EDT
: : Msg. 170116 of 170156
: : (This msg. is a reply to 170109 by danfl_11.)
: : Jump to msg. #
: : november 6th will be the big day.
: :
: : ******So if we get an October 9th Press Release,who is this guy and what do we expect on November 6th?
: : _____________________________
: : Is that the date IBM official release
: : of the viper????
: : Almost got tos'ed by I think TePe
: : Got sick of his wineing SxxT and
: : came back at him sorta strong. RB
: : warned me to be careful on posts.
: :
: :
: :
:
:
This stuff from the above link. Worth the watch/read.
Some items from http://download.boulder.ibm.com/ibmdl/pub/software/info/television/us/videos/websphere/transcripts/soa_entrypoints.pdf
September SWTV Video Transcript
...update on our SOA (Service Oriented Architecture) announcements that we made about four months ago. If you remember at that time, everything started with innovation, as it does today, with 87% of CEOs saying that change is needed in order to innovate and make their companies more competitive in the marketplace.
...Service Oriented Architecture is the way to enable change in your organization.
How do you make it easy to get started for enabling your cutomer to innnovate, or to change.(?)
How do you make it easy to get started for enabling your customer to innovate, or to change.(? the transcript doesn't use question marks and it drives me nits.)
...in April... (IBM) made a couple of announcements aroudn business-centric SOA.
(Analysts rating of IBM:)
IBM in the leadership area of Forrester's latest ESB (Enterprise Service Bus ) wave
IBM rated as visionary for BPMS (Business Process Management) Magic Quadrant by Gartner
[ESB Whitepaper: http://www.tibco.com/mk/2006/googesbsoa21-jul-06us.jsp?gclid=CPSGh7T64IcCFSdCDgodSm1log]
[ESB defined: http://en.wikipedia.org/wiki/Enterprise_Service_Bus {read it and weep, heh heh heh}]
...how do you make sure that you've got the right processes and you can simulate and monitor what's going to happen from those.(?) And around information, about how do we manage all that information that exists out there today.(?) ("all that information that exists out there today" meaning please include the unstructured data that is the other 80% of the 100% represented by the tip of the ideberg in the 20% that fits in a box.)
-----------------------------------------------------------------------------------
Enterprise Service Bus (ESB)
From Wikipedia, the free encyclopedia
(Redirected from Enterprise Service Bus)
Jump to: navigation, search
In computing, an enterprise service bus (ESB) refers to a software architecture construct, implemented by technologies found in a category of middleware infrastructure products usually based on standards, that provides foundational services for more complex architectures via an event-driven and standards-based messaging engine (the bus).
(the wheels on the bus go round and round.)
Salient characteristics
Although the exact definition of an ESB varies, most agree that the following characteristics are common:
-It is not an implementation of service-oriented architecture.
-It is usually operating-system and programming-language agnostic; for example, it should enable interoperability between Java and .NET applications.
-It uses XML (eXtensible Markup Language) as the standard communication language.
-It supports web-services standards.
-It supports messaging (synchronous, asynchronous, point-to-point, publish-subscribe).
-It includes standards-based adapters (such as J2C/JCA) for supporting integration with legacy systems.
-It includes support for service orchestration and choreography.
-It includes intelligent content-based routing services (itinerary routing).
-It includes a standardized security model to authorize, authenticate and audit use of the ESB.
-To facilitate the transformation of data formats and values, it includes transformation services (often via XSLT) between the format of the sending application and the receiving application.
-It includes validation against schemas for sending and receiving messages.
-It can uniformly apply business rules, enriching messages from other sources, the splitting and combining of multiple messages and the handling of exceptions.
-It can route or transform messages conditionally, based on a non-centralized policy (i.e. no central rules-engine needs to be present).
-It is monitored for various SLA (Service Level Agreement) threshold message latencies and other SLA characteristics.
-It (often) facilitates "service classes," responding appropriately to higher and lower priority users.
-It supports queuing, holding messages if applications are temporarily unavailable.
-It is comprised of selectively deployed application adapters in a (geographically) distributed environment.
---------------------------------------------------------------------------------
Did we miss anything?
http://en.wikipedia.org/wiki/EI
I like this one: "Ei is the german word for egg "
http://en.wikipedia.org/wiki/Enterprise_nervous_system
...and we're getting stratosfearic for the expert journalists. Need to bring it down a little closer to earth to be believable, now, boys. Really. Alien technology about to take over the world? hah hah cough That's rich. What's this here racket ship do, anyway? What's this button?
We might as well get informally associated with this because that's next:
http://en.wikipedia.org/wiki/Enterprise_application_integration
I'm fascinated by:
"EAI is a tool paradigm
EAI is not a tool, but rather a system and should be implemented as such. "
(I take that as: Enterprice Application Integration is a tool world that needs to be handled as a world and not as a collection of tools, you dumba$$. Don't go buying bogus tools thinking you're going to get the same results, people. You were warned. The waterhole is pizined, pilgrim. Best tank up your canteen with swamp water. At least you can eat the critters.)
