Monthly Archive for July, 2005

Page 2 of 2

European Patent Law Rejected


I was first made aware of the ‘software patent’ issue when Tobias Oetiker changed the front page of his MRTG site to protest against it. It now seems the European Parliament did the wise thing and kept its hands of the issue.

The European Parliament on Wednesday rejected a proposed law to create a single way of patenting software across the European Union, a blow to big companies who had pushed hard for its adoption.
The so-called software patent directive, rejected by a 648-14 vote with 18 abstentions, would have given companies EU-wide patent protection for computerized inventions (…).
But lawmakers said the measure would stifle enterprise and did not promote innovation, and that human knowledge can’t be patented. The move kills the legislation since the EU head office, which had drafted it, does not plan to set forth a new version. (…)
Companies such as Nokia and Siemens fought hard for adoption of the bill, saying patent protection would give them incentives to invest in research and development. Open-source advocates campaigned against it, saying that individuals and small businesses could be bankrupted by expensive legal battles with software giants over fuzzy patent law.
from European Patent Law rejected(Wired)

What kind of laws would give a fictional HugeCorp Inc even more ‘incentives to invest in research and development’:

  1. every thought an employee has at HugeCorp Inc, belongs to the company. Practically this means that, if ever an employee wants to claim an idea as his, he has to be able to prove it was conceived of in his free time.
  2. if an employee, certainly someone from the R&D department, leaves the company, he should sign a non-disclosure/non-competition contract. If HugeCorp Inc has doubts about the person’s willingness to shut up and do absolutely nothing with the knowledge that was gathered while working at their premises, the former employee’s memory can be erased, either chemically or with a hammer.
  3. whenever a new product or technology is developed at HugeCorp Inc, consumers can be forced to buy it. The normal process of customer adoption allows for inventions to be unprofitable because of such silly reasons as: too expensive, too user-unfriendly, no demand, better substitute available. This makes R&D riskful and should be eliminated.
  4. it is forbidden to reverse engineer anything that was developed at HugeCorp Inc. This includes decompiling software code, performing input/output analysis or disassembling electronic or mechanical devices. Replacing batteries in a watch, changing a tire on a car and decoding an imperfect DVD-encryption are therefor forbidden, except by persons explicitly accredited by the manufacturer.
  5. whatever inventions are developed at universities or other academic institutions may never be commercialised or released on a free basis to the outside world. They should be handed over to HugeCorp Inc for a symbolical sum (let’s say, a 19″ flat screen for the supervising professor, and free drinks for anyone involved in the development), where it will be prepared for commercial purposes (i.e. DRM and licensing mechanisms will be built in). If the product sells really well, a new wing will be donated for the department that inspired the development, and it will get a name like “HugeCorp Research Institute“.
  6. the “open source” movement is too large to be killed silently, but it should be possible for HugeCorp Inc to have some of its employees interfere incognito in the development process and introduce bugs, annoyance and controversy. Traditional practices like defamation, bribery, blackmail … can also be used to discredit open source personalities.
  7. any invention that has, could have, could be thought to have or eventually maybe might slightly have, a negative effect on the balance sheet of HugeCorp Inc, and that was not developed by HugeCorp itself, cannot be commercialized or released publicly. The person(s) responsible for its conception can be sued for that act, or under some other pretence, can be rendered life very difficult. Unless, of course, they work for EvenHugerComp Inc, in which case HugeCorp just keeps quiet in the hope not being sued themselves.
  8. The company cannot be held responsible for any personal damage its employees would suffer while researching and developing. If the employee does not like that, he can always resign and go work somewhere else. (In which case rule #2 is still valid)
  9. The company cannot be held responsible for the detrimental effects of its inventions on the environment, the market or its customers. If any damage is done, some other company can step in and sell the service of fixing it.
  10. The company cannot be held responsible for the actions of its employees, except if these actions would have a positive impact on the balance sheet.

GEZOCHT: medewerkers voor brussel.blogt.be


(post in dutch)

AANDACHT, AANDACHT!

Ik ben op zoek naar enkele partners in crime om een brusselse stadsblog op te zetten, de tegenhanger van de excellente gent.blogt.be en mechelen.blogt.be sites.

OEVER WA GOET ET?

  • een groepsblog door en/of voor brusselaars, waarmee bedoelt wordt: zowel zij die in Brussel wonen als zij die in Brussel werken, geboren zijn, school lopen of tout court in Brussel geinteresseerd zijn.
  • met daarin: een mengelmoes van actualiteit, cultuur, politiek, parkeertips, interviews met lokale (anti-)helden, fotografie, poezie, cafépraat, essays – geschreven door een bende vrijwilligers
  • in eerste instantie nederlandstalig (het heet dan ook niet bruxelles.blogue.be)

WIEN MOENIK HEMME?
Als je een paar van de volgende criteria kunt afvinken, neem dan zeker met mij contact op:

  • een goeie pen (wat ervaring als blogger, journalist, redacteur van de schoolkrant helpt zeker; het gebruik van zinnen als ‘de geïmplanteerde gedragingen in zijn niet-geseculariseerde santenkraam‘ is er wat over)
  • een passie voor Brussel: je identificeert je met Brussel, je bent trots er te wonen, of er geboren te zijn. Als er vrienden op bezoek komen, laat je ze enthousiast de tofste hoekjes zien, en je kent het verschil tussen het Justititiepaleis en de basiliek van Koekelberg (de laatste is die met het kruis op het tsjoepeke).
  • tijd en goesting om stukjes tekst te schrijven en een licht maar onmiskenbaar genot om uw eigen werk gepubliceerd te zien
  • een originele invalshoek: elke week een gesprek met een Brusselse barman, een interview met een beginnend muziekgroepje, een brusselse versie van TV Touché maar dan geschreven, een foto van de afgrijselijkste graffiti, …
  • je hebt een eigen mening over wat er gebeurt in ‘t stad en je wil die graag delen
  • je komt regelmatig met mensen in aanraking die wat te vertellen hebben over Brussel (over den oorlog, of den skieven architekt, of het verkeerscirculatieplan) en je zou het leuk vinden om daar iets van op papier (scherm) te zetten
  • je hebt een goed excuus nodig om de ganse avond op cafe te gaan en met wildvreemden te beginnen praten (“Zaade gaa van dees cotee?“) en vindt het niet erg daarna, na 2 Perdolans en een kop koffie, iets over te schrijven.

Ik zou willen starten met een groepje van 5-10 redacteurs, die een of meer keer per week iets uit hun mouw willen schudden. Streefdatum is 1 september (of vroeger, als we volk genoeg op de wagen hebben). Je kan me bereiken op brussel@forret.be.

Technorati:

Adwords generator tool


I just finished another webpage for my forret.com tools collection: the Adwords Generator tool. Inspired by seeing a colleague losing his time with Excel trying to create a full list of keywords for his Google Adsense campaigns, I created an easy web interface to do just that: give in lists of keywords of key phrases, and let the Adwords tool create all the possible combinations.

You would use it in this way: say you want to promote a podcast client application for Windows (like the new Doppler 3.0).

  • you would use the 1st box to list ‘podcast’ and all its synonyms:
    podcast, audioblog, mp3 blog
  • you would use the 2nd box to list all synonyms for ‘client’
    client, podcatcher, aggregator, downloader, viewer
  • you could use the 3rd box to list the versions of Windows your software runs on:
    Windows 2000 (or Win2k), Windows XP (or WinXP), Windows 2003 (or Win2003)

Combining everything together gives you a list of 90 keyphrases: Adsense keywords for a Windows podcast client. You can even add the “phrase matching” or [exact matching] options (see adwords.google.com for more info).

You can also look up suggestions for new keywords through tools from Google Adsense and Yahoo Search Marketing (formerly Overture). A nice addition to my toolbox!

Technorati: