More on US Patent 5,838,906 (Eolas)
IMHO, the patent covers the following:
- The 'automatic' invocation of an external interactive program in response to seeing some data stream within the 'source' document - not in some document 'attached' to the source document, but the original document.
- There must be external (to the original document) data for the external program to access.
- There can be communication between the host browser and the external program.
- The external program can contact, by some means, for whatever purpose, a process running on the (originating) server.
What is not covered.
- Invocation of non-interactive code (e.g. provision of utility functions with no interactive function).
- Automatic download and installation of the required code for the external program.
- Invocation of code that does not access the external data source. Applets etc that simply provide alternative forms, UI, visualisation from client side collected data are not covered.
- Invoked code that cannot communicate with the invoking browser nor appear within the browser window.
I must admit that I don't understand how OLE/OpenDoc is not prior art - just saying 'make OLE/OpenDoc work on a network' doesn't appear much, if anything, of an invention, http is nothing more than a simple file system - but there we go, I don't understand the US patent system. Nor do I understand how client/server RPC is supposedly an invention in 1994.
There were multimedia apps in the UK in the early 1990s on RISCOS that did video playback in the window - one in particular (Genesis) was very text file based (it had text documents that refered to external data) and could have very simply supported (i.e. no changes to the underlying code) what Eolas claim assuming that Acorn/anyone had written a module (http:) that worked like other RISCOS filing systems (adfs:/scsifs:/netfs:/strangedevicenamefs:) - Genesis did whole file reads so this would have been a doddle. I wrote a different one called Magpie that did similar things but worked on a single file for the whole MM document, so supporting http: would have been a bit more difficult. The data was stored in a compressed binary format (computer stored text does not equal binary data - discuss). What's funny is I've been meaning for years to rewrite Magpie using HTML - I did some of the work a few years ago - but now I won't be able to because of this patent, just because HTML runs over http - perhaps if I write it in HTML but it won't access a server, just the local file system then it won't breach the patent....
posted at: 12:55:44 AM
|
|