Tuesday, November 20, 2007

How the OMG technology process works

I was asked by a number of people how the OMG standardization process works.

I have found a link to a power point presentation which explains the essence of how the OMG technology process works
and it's the official OMG word rather than just my interpretation of it.

Here's the link to a Power Point presentation (as .pdf ) which does not require an OMG username/password to access: OMG Process

Char Wales explained me that the work they are doing in the Object DB technology WG fits into that structure.

Labels: ,

Tuesday, November 13, 2007

The European Commission will call for new ICT project proposals from December 2007 to April 2008.

The European Commission will call for new ICT project proposals from December 2007 to April 2008.

FP7 ICT Call-3 is underway with a foreseen date of publication in early December 2007.

With an indicative call budget of 265 Mio Euro the 3rd ICT Call will address the following objectives:

-ICT-2007.2.2: Cognitive Systems, interaction, robotics.
-ICT-2007.4.3: Digital libraries and technology-enhanced learning.
-ICT-2007.4.4. Intelligent Content and Semantics.
-ICT-2007.8.4 Science of complex systems for socially intelligent ICT.
-ICT-2007.8.5 Embodied intelligence.
-ICT-2007.8.6 ICT forever yours.
-ICT-2007.9.2 International Cooperation.
-ICT-2007.9.3 Trans-national co-operation among NCPs.

More detailed information on ICT Call-3 will be available on CORDIS as soon as the call is published in December.

Labels:

10+1 Questions on Innovation to Bjarne Stroustrup

One of the main driving force which influenced the introduction of new generation database systems, such as ODBMS, was Object Oriented Programming (OOP). C++ is notably one of the most important. I had the pleasure to interview Bjarne Stroustrup who invented C++.

Bjarne Stroustrup is the designer and original implementer of C++ and the author of "The C++ Programming Language" and “The Design and Evolution of C++”. His research interests include distributed systems, design, programming techniques, software development tools, and programming languages. He is actively involved in the ANSI/ISO standardization of C++.
Dr. Stroustrup is the College of Engineering Chair Professor in Computer Science at Texas A&M University. He retains a link with AT&T Labs – Research as an AT&T Fellow. Member of the National Academy of Engineering. ACM fellow. IEEE Fellow.
Bjarne Personal Page

1. What is "Innovation" for you?

I basically agree with Edison: “1% inspiration and 99% perspiration”. There are few great ideas, and many good ones. Even the great ones require much work to validate them and to make them into useful tools for someone. I think he called it “invention”, though, but the main point is that you need a good idea (or several) carefully refined and embodied in some form of gadget, tool, or system to make a real innovation. An idea by itself isn’t much. Think how far the idea of “atoms” have come since the early Greeks. Think how far computing has come since Turing’s paper. And those were two of the most revolutionary ideas in history – the 99% perspiration is probably an underestimate.

Obviously, I associate “innovation” with technology, rather than pure science or art, though I have no doubt that the notion of an idea needing serious thought, development, and experimentation to become more than “just a good idea” applies universally.

2. Who are your favorite innovators?

OK, let’s get back to earth and look at ideas and innovations of a more manageable magnitude. Consider the relatively few and simple ideas that became Unix, such as “have each program do one thing well and combine them using streams of characters”. The Unix pioneers, McIlroy, Thompson, Ritchie, Aho, Kernighan, Feldman, Morris, and many more created a system and a set of related ideas and tools that live on today inside most of our software based systems.

3. What do you consider are the most promising innovations of the last 3 years?

That’s hard to say. As a rule of thumb, a major success exists in embryonic form 15 years before it becomes a major success. The one with the most ramifications to programming and software systems is multi-cores. We now have to get serious about quite fine grained concurrency, and we have never been very good at that.

I have a camera, a cell phone, an MP3 player, and a laptop. It is obvious that some synthesis of these three will happen. We see it happening: last week someone in Amsterdam showed me a talk I gave in Canada in August on his iPod. I want such a gadget that is good at each of the tasks, rather than just a compromise that is mediocre at each and relatively large. For example, as long as a camera phone features 3Mpixels and a lousy lens, it’s unacceptable as a camera.

These two examples are huge. They are not individual innovations but sums of many and drivers of further innovation. Design – aesthetic concerns – will be important. I’m very keen on solid, functional, and beautiful designs. A beautiful and functional system contains innumerable small innovations and refinements. These are easy to overlook because they so quickly become taken for granted. For example, for decades, shower-curtain rods were straight, running parallel with the rim of the shower area to ensure than water didn’t splash out. This led to most people – literally – having too little elbow room until some genius though of having the rod curve outwards. Brilliant! Water that splashes out is caught be the curtain and runs back into the tub – and life is just a little bit better for a few hundred million people.

4. What does it help to become a successful innovator?

A solid technical education, a sense what is practical, persistence, impatience with dogma, a willingness to take (calculated) risks. In many cases, an aesthetic sense that deems existing solutions inadequate and guides innovation. You can’t innovate in the abstract, every innovation is a response to problems.

I think idealism often plays a part. Individuals who are just out for themselves are too easily diverted in short-term money-making schemes or corporate climbing.

5. Is there a price to pay to be an innovator? Which one?

To be an innovator in a technological field, you have to have a serious technical education and work hard at developing your ideas. You become a “geek”. That’s great and often involves desirable personal traits, such as trustworthiness, stamina, and a skeptical attitude towards unproven ideas in general. Unfortunately, those are not universally appreciated traits – especially among technophobes – so it can carry a social cost. You must also devote serious time and effort to “technical details” that are often not appreciated by managers or people in general – even if their lives or livelihood depend on them. On the other hand, survey after survey have shown engineers to be among the most stable and satisfied groups in society, so maybe the negative aspects are overrated.

6. What are the rewards to be an innovator?

Satisfaction of having made a positive contribution to the world, and sometimes status and wealth. Most of the successful innovators I have met also built up a network of friends and colleagues that can sustain them for life. I think that the “lone wolf” image of an innovator is misleading. Many of the most successful innovators are at the center of a network of exceptional people.

7. What are in your opinion the top 3 criteria for successful innovation?

Curiosity, persistence, and – of course – luck.

8. What would you recommend to young people who wish to pursue innovation?

Get a good degree in a technical subject – science or engineering – and then get a bit of practical experience trying to put ideas into working products. Also exposure to an aesthetic field, such as literature, architecture, furniture design, image composition.

9. In your opinion how can we create a culture that supports and sustains innovation?

That’s harder than it appears. Most cultures highly value and encourage regularity, predictability, providing the right answer to conventional questions, respect of authority, not wasting time on “extraneous matters”, etc. This is especially true in educational settings. Major innovation more often arise from asking unconventional questions and working hard to find elegant answers.

We need to tolerate and encourage people to “take a walk in the forest” (as A.G. Bell expressed it) repeatedly in their education and career. We are too keen on giving people well-specified tasks and having them set definite short-to-medium-term goals. Sometimes, there has to room to do a task, a project, a course “just for fun”, etc., and there must be rewards for coming up with something unusual. A culture goes stale fast if the greatest awards typically go to people who never take a chance and never look up from assigned tasks.

10. What do you think stops/slows down innovation?

Lots of specific tasks; tight deadlines. Lack of general direction; lack of deadlines. Lack of rewards, trivial rewards. Emphasis on huge, life altering, monetary awards for the very few. Emphasis on individuals moving from technical work into management.

10+1. Do you think becoming an innovator can be taught? If yes, how?

I think I have seen it done. In Bell Labs technical managers and senior researcher often spend serious time Mentoring a new researcher. I think “innovation” is more suited to one-to-one discussions than to courses; also, what is required successful innovation in one field and in one company isn’t necessarily the same as is required elsewhere in industry or in academia. The selection of a mix of topics to work on – such as, short-term, long-term, risky, and low-hanging fruit – can be crucial. I doubt that the more personal aspects of innovation, such as calculated risk taking, perseverance, and curiosity can be taught, at least not to adults.

Labels: ,

Monday, November 5, 2007

Object Database Technologies Users and Vendors Roundtable

Here is an interesting information. As you may know, after a long period of no activity some work on standards for Object Database Systems resumed under the umbrella of the Object Management Group (OMG).

For those of you who are interested in standards, and willing to actively participate in such activites, here is an opportunity:

I have received this note from Mike Card:

"The OMG is hosting an Object Database Technologies Users and Vendors Roundtable in Burlingame, CA at the Hyatt Regency San Francisco Airport on Tuesday morning, December 11th 2007.

I will provide an update with the exact start time and the name of the ballroom/ conference room where the round-table will be held as the date gets closer.

The purpose of this meeting will be to get industry and user reaction to the work done so far by the OMG Object Database Technology Working Group (ODBTWG). Our group has been investigating the research done by
Prof. Kazimierz Subieta of the Polish Japanese Institute for Information Technology in Warsaw, Poland. Prof. Subieta’s team has come up with a so-called
Stack-Based Architecture (SBA) for defining the contents of an object database and the semantics of an abstract stack-based query processor and its associated query language (SBQL). Their work is the object equivalent of the relational calculus in that it provides a precisely-defined, semantically complete set of definitions of what objects are, how they are
stored and how they can be queried. We would like to base any future object database standard on the object model he has developed so that the language bindings, query languages, etc. that follow are well-defined, self-consistent, and complete. Doing this would address many of the criticisms leveled at the earlier ODMG standards.

The ODBTWG has prepared a white paper on our approach to future object database standardization and our incorporation of Prof. Subieta’s ideas which you can download from: ODBMS.ORG

Prof. Subieta will be in attendance at this meeting and we will have him give an overview and brief demonstration of his work, concrete implementations of which have been built for various EU projects.

We will then open the discussion up to all participants, we are especially eager to hear thoughts from object database vendors about Prof. Subieta’s ideas and to explain how we think his ideas could be incorporated into future object database standards. We would welcome discussions on what future object database standards should or should not look like, open-source collaborative projects such as reference implementations or conformance test suites, trends in the object database marketplace, etc. In short, we are seeking industry participation and nothing will be off-limits.

If you are interested to attend, there is a $150 registration fee for this event, to register please visit here

There should be a link there soon to register for this event.

Michael P. Card, Syracuse Research Corporation

Labels:

10+1 Questions On Innovation to: Hector Garcia-Molina

This time I asked the 10+1 questions to a distinguished database colleague, Hector Garcia-Molina.

Hector Garcia-Molina is the Leonard Bosack and Sandra Lerner Professor in the Departments of Computer Science and Electrical Engineering at Stanford University, Stanford, California. He was the chairman of the Computer Science Department from January 2001 to December 2004. From 1997 to 2001 he was a member the President's Information Technology Advisory Committee (PITAC). From August 1994 to December 1997 he was the Director of the Computer Systems
Laboratory at Stanford. From 1979 to 1991 he was on the faculty of the Computer Science Department at Princeton University, Princeton, New Jersey. His research interests include distributed computing systems, digital libraries and database systems. He received a BS in electrical engineering from the Instituto Tecnologico de Monterrey, Mexico, in 1974. From Stanford University, Stanford, California, he received in 1975 a MS in electrical engineering and a PhD in computer
science in 1979. Garcia-Molina is a Fellow of the Association for Computing Machinery and of the American Academy of Arts and Sciences; is a member of the National Academy of Engineering; received the 1999 ACM SIGMOD Innovations Award; is on the Technical Advisory Board of DoCoMo Labs USA, Yahoo Search & Marketplace; is a Venture Advisor for Diamondhead Ventures, and is a member of the Board of Directors of Oracle and Kintera.



1. What is "Innovation" for you?

Finding a way to do things better, where "things" can be anything and "better" may means faster, more pleasantly, more accurately, more effectively.

2. Who are your favorite innovators?

Jim Gray is my favorite innovator. He may not be widely known outside the computer science research community, but his work made possible today's data management systems. He has also been a great mentor to many young scientists.

3. What do you consider are the most promising innovations of the last 3 years?

It takes more than 3 years to know if something really has an impact, so I am struggling to single out three recent innovations.

4. What helps to become a successful innovator?

You have to be a bit of a rebel and quite self confident. Do things differently and pursue your dreams even if people think you are wasting your time.

5. Is there a price to pay to be an innovator? Which one?

Not when you are finally successful and recognized. But before you reach that point, you can become poor or ostracized or frustrated.

6. What are the rewards to be an innovator?

Financial in some cases, prestige in others, self-satisfaction in other cases, perhaps all three!

7. What are in your opinion the top 3 criteria for successful innovation?

Solve a problem or fill a need.
Solve a problem or fill a need.
Solve a problem or fill a need.

8. What would you recommend to young people who wish to pursue innovation?

Get a good education, and if possible spend time at places where innovation is a tradition, so you can see how it is done.

9. In your opinion how can we create a culture that supports and sustains innovation?

Shine the spotlight less on movie stars, athletes, criminals, and more on people who contribute to society.

10. What do you think stops/slows down innovation?

Not giving people enough freedom to explore things; burdening them with mindless tasks.

10+1. Do you think becoming an innovator can be taught? If yes, how?

I do not know how to teach innovation by lecturing or by answering questions like these. The desire to innovate seems to be something one is born with, but it can be enhanced "by example", that is, by living in an environment that nurtures and incentivizes creativity and innovation.

##

Labels: ,