I did't read much about the patents, but using common sense I think these are the elements considering:
Step 1: Build up a database with information on products, articles and programs to link to, and put them in a database webserver.
-> Common technology
Similar to yellow pages or a shopping engine.
Step 2:
Generating a barcode for an article, product or TV-program
-> Common technology
e.g. the 128 standard allows all kinds of barcodes to be generated. Even the UPC or EAN codes can be applied.
Step 3: Printing a barcode
-> Common technology
Step 4: Reading of barcode by scanner
-> Common technology
The barcode is translated into ascii-code
Step 5: Sending the code to the database webserver.
The webserver sends a page back to the user browser with a 'redirect' command in it. This brings the user to the article or product.
-> Common technology
But here is the trick. Which webserver will be connected to???
Three options:
a. The barcode scanner has a predefined webserver.
b. The PC, telephone, palm pilot or other device have the webserver defined
c. The user selects the webserver.
Celular phone companies would be able to predefine the webserver. Like they do now with the info-offerings through the internet. Such as the WAP platforms of Infospace.
This is the same as an ISP who let users connect to their portal. As you know, users with more experience change the default page to their favorite portal or create their own startpage.
I just wanted to show my opinion that I don't think their is any step were you need some special technology which can be patented. You may be able to patent a certain combination of steps. But their are many other methods to get the same result. Compare to the 1-click buying patent of Amazon. That does not prevent others to sell over the internet.
The most difficult step is step 1. How to create and maintain a global database with all products and information that has a barcode on it. This is a discussion we had earlier. Inktomi is trying it with the shopping engine. Infospace with their yellow pages. Udex with their very structured product database. Arriba in the B2B field. Agile Software Corp. offers applications for synchronization of codes in the supply chain. Commerce One (through their merger with Appnet) is developing an internet application for the product databases of the United Code Council. uccnet.org uc-council.org
It is very, very difficult to maintain a complete, up to date database with information of all suppliers (of the world).
This leads to a more philosophical question: is it possible to direct all information through one channel, controlled by a technology company that maintains the key?
The answer is that one single company can at best manage only part of the information. And if they manage a large part, most probably they will have this lead only for a short time, as competitive offerings will emerge.
The internet shows that the most power lies in the co-existence of multiple offerings. Of technology and information. The UCCnet approach is based on cooperation between all the parties involved. It is impossible that one company defines a standard that implies that others have to pay a fee to use this standard.
Besides neom, there are others operationg in this field, like Barpoint: siliconinvestor.com
Barcodes will become much more important in the near future. It is an easy and reliable and low cost coding system. Each product may get its own portal on the web, reachable through its barcode. But most likely this will be enabled through existing databases that add an URL field next to the barcode field.
Without doubt it is an interesting field. Neomedia has its roots in only a small area of it. Automatization and printing technology.
Barcode reading seems to be a standard input technology where no fees can be applied. Managing a product database does allow to apply fees. Neom has tried to set up the paperclick database, but without much success. Now it is licensing its technology. It may work short term, but long term I don't see how they get a stronghold on the market.
Kind regards,
Pareto |
