Useful information:
http://ragingbull.quote.com/mboard/boards.cgi?board=VCSY&read=314569
By: moonpunk  12 Dec 2011, 03:44 PM CST Rating:  | Msg. 314569 of 314577 (Reply to 314567 by ccm2406) Jump to msg. # |
| I would agree. While unorthodox there are a number of perfectly legal ways in which a patent may be throttled back. The child for 629 would be an extremely powerful concept with Emily as the 744 framework would be transportable to any existing languages. Since this is as good a place as any to start I'm going to place the following here so thinking might be jogged as to what we're looking forward as a "next generation" computing concept. Traditional solutions such as using XML tagging to identify portions of data for processing have had limited success over the past decade because the processing necessary to consume those tags has been limited to private internal systems with no real means of interoperability between different systems beyond standardized XML vocabularies. Those methods amount to design by committee implementations that are always late and never scale properly. A new method of dealing with data flow between different systems is needed. The following is from the Emily patent application 09888329 specifications. Quoted passages from the specification will be marked by brackets [xxxx] to differentiate from my comments which are separate from the bracketed passages. [0011] It is not workable to impose standards on the B2B process (such as standard catalogs and purchase orders) that radically affect the internal workings of participating organization. B2B e-commerce systems will work only if they can be inexpensively layered upon the privat policies of a company. Any B2B system that attempts to make drastic changes in the internal workings of the organization runs a high risk of being rejected for the simple reason that participants view their carefully crafted internal systems as part of their "competitive edge." Furthermore, although buyers may want e-commerce, suppliers will resist it in the absence of any mandating authority until the cost of e-commerce is compensatory. The discussion continues on to include agent technology already patented as 7076521 and then begins focusing on the reason for focusing on the use of XML to build a programming medium more effective than the traditional methods. From entitled: Detailed Description of the Preferred Embodiments [0040] Before discussing the details of the preferred embodiments, it is useful to provide a brief background on an emerging standard called XML (Extensible Markup Language). XML is similar to HTML (Hypertext Markup Language, which is the language that web pages are written in. However, XML is more flexible than HTML with regard to how tags are named, and how data content can be constructed. Like HTML, XML can be pulled from a web site using HTTP (Hypertext Transport Protocol). XML provides a small advantage to HTML in that it is more readable by programs (although slightly less readable by humans). XML has become a hot topic, mainly because it simplifies the construction of programs that pull data from the web. Also, XML is one of the few standards that provide assistance in the construction of B2B systems. The discussion continues into detail as to the Server/Client architecture in passing XML between sites. Section [0047] describes a minimal implementation of Emily using an "enabler agent" (a described embodiment in patent 7076521) residing on a XML server and a data collector (a described embodiment in patent 7076521) on a client. "The enabler agent 102 works in tandem with a server database 112, to provide data from the server database in a standard, platform independent format. The data collector 104 works in tandem with a client database 122, to receive data in a standard, platform independent format and store the data in the client database 122. The data communication system works in either a one-to-one, one-to-many, many-to-one or many-to-many environment. Each server communicates data to one or more clients. Each client receives data from one or more servers." [0048] "The data communication is not limited to e-commerce, however. The system can be generalized to cover many other situation where information needs to be transferred between independent entities." The discussion continues to describe such a system working in a hospital environment. The "enabler agents" may be specialized to any manner of granular independent data exchange. The "data collectors" may likewise be specialize to any manner of granular independent data collection. While this may at first appear to be a prior art server/client transaction model I would like to point out the traditional appearance of such a method can be found in a very rudimentary form in Ajax. Microsoft used the fundamental XMLhttpRequest method used to develop Microsoft's Silkroute patented technology to attempt to prevent the patenting of 706521 but the Silkroute method is very limited since XMLhttpRequest is a typically one-way process. 521 does the work of a processing web server where Ajax is only a tranaction process. 521 can be fed any manner of program code while Ajax remains as a fixed linking method. The 521 enabler-agent/data-collector configuration is only a basic implementation and the combinations of agents and collectors may be very sophisticate and complex. The reason for this is that Ajax/XMLhttpRequest is a very simple request/transfer process used predominantly to speed up the refresh of granular parts of a web page as marked by XML tags. This gives the interface the look and feel of a speedier desktop interface. However 521 is a full processing kernel capable of carrying out the duties of a transactional web server whether it sits on a "server" or a "client". The local machine hardware/OS does not matter as 521 is able to reside on any platform by using XML as a native language for adaptation of the required 521 virtual machine. This is also superior to typical run-time virtual machines since those machines are purpose built for specific installations and must be manually changed to run on other installations. 521 continues the concept of "arbitrary" found in sister patents 744 by use of a novel use of XML. The specification spends much time demonstrating how Emily can be used in a typical B2B architectures. While this discussion originates from circa 1999/2000 the reality is that "B2B" constructs have not changed fundamentally since then while many different approaches have been tried with "limited success" (per discussion about Hadoop by HP related authors). The entire discussion up to this point describes the use of the runtime processor in various implementations. There might be some confusion as to the Emily runtime (09888329) and the MLE runtime (521) as they appear to be the same - both being able to be an "enabler agent" and a "data collector". From my point of view 521 works as a granular processing web-server able to pre-process data transactions and exchanges while 09888329 works as a language enabler specifically intended to run the Emily language which is native XML. The actual discussion about the use of XML as programming code begins in [0089] with the heading Emily Framework Scripting Language. [0089] With reference to Fig. 12, a flow diagram illustrating a typical method performed by the Emily scripting language is shown. The Emily scripting language may be used for processing a markup language file having one or more tagged portions. The method comprises opening a first markup language file... and parsing the first markup language file for one or more portions...The language interpreter then stores each portion of the first markup language file into one or more objects in an electronic memory... [0091] The Emily languge comprises a command language set allowing selection, viewing and other processing of the one or more objects...A subset of commands may comprise one or more commands for processing one or more folders, subfolders, portions, or sub-portions of the first markup language, the subset comprising one or more executable batch files containing a subset of the set of commands. One or more executable batch files may be incvluded within a second markup language file, the subset of commands in the executable batch file comprising commands for including one or more of the objects containing portions of the first markup language file in the second markup language file. Here we see Emily using web pages as source for objects parsed by the Emily interpreter from web pages (which may be any kind of HTML/XML/code-language conglomeration. And we now know those objects to be objects of content objects of form and objects of functionality as spelled out in 744. When the reader considers using XML as a programming language reading this particular section begins to unfold the kind of power Emily presents to the developer. Instead of having to contend with multiple languages to build web applications Emily presents the ability to build web pages and to build applications out of web pages and objects by using markup language alone. With Emily that language may be a single language fitted to the particular subject matter used by a SME. We're going to return to this capability to demonstrate the real power of using markup and web pages as a foundation and platform for building applications. But the specification continues by describing a set of basic http commands that are used by Emily as a part of the architecture for managing the various parts of the framework. This is a synergy from the REST philosophy that makes Emily an integral part of a web operation instead of being an add-on or additon to the internet architecture. This ensures close integration with existing legacy systems of any age or configuration and makes Emily much more powerful than new languages such as HTML5 which rely on enhanced browsers to work. This kind of legacy enhancement opens the door to modernizing browsers and operating systems that run on a vast majority of existing computers and will never be changed due their hardware limitations and the cost of replacement and loss of productivity. In this sense a Windows 98 machine running the most basic browsers may be modernized to perform machine-centric processing on par (albeit a bit slower) with modern machines. By opening up a distributed (many to many) granular service architecture on all existing machines the reality of resources for parallel processing takes on an entirely new complexion. I will continue shortly but I stop here to allow the reader to take in just what this kind of language/runtime and attendant MLE processors running as a benign/benevolent layer on top of the existing OS/file structure/application library/browser resources can mean to real "cloud" computing. This kind of pooled internet processing power means cloud farms may be treated as expensive proprietary traps from which the common human's processing on global supercomputer scales can be done virtually free cost. - - - - - View Replies » |
Posted by Portuno Diamo
at 4:09 PM EST
