The Report Generator (“RPG”) is a new program from SAFE that automatically generates draft expert reports and declarations for litigation. Reports have several generic sections such as an expert’s experience and descriptions of the technologies involved in the examination, which can be shared amongst reports. By automating the compilation of the generic information into a formatted and structured draft report, the expert can focus on performing the analysis and writing the case-specific arguments.
When using the RPG, an expert selects the type of case, type of report, types of technologies involved, types of tools used, and expert background profiles from a GUI. Then a Microsoft Word draft report is generated that includes all of the selected generic information intermixed with blank sections where case-specific information should be filled in manually.
Currently, many experts either dig through their prior works to find specific descriptions or write them from scratch each time. Maintaining a library of generic report elements is a challenge, especially when multiple experts are involved. RPG acts as a version control system between multiple experts who can upload and download detailed descriptions of experts, technologies, and tools from a central server. The reports are generated according to specific formats, so an entire team of experts can easily produce reports that are consistently formatted with the most up-to-date descriptions.
RPG also keeps synced descriptions of CodeSuite, so it can include the most up-to-date descriptions and pricing of the tools without having to search the S.A.F.E. website or CodeSuite help files.
If you’re interested in trying out RPG, contact our Sales Department.
Many in the intellectual property business have been holding their breath waiting for this case to be decided. Many countries don’t allow software patents at all and most countries don’t allow business method patents. The United States allows both, but the lines, limits, and legality have been changing over the past years. The Court of Appeals for the Federal Circuit (CAFC) decided that Bilski’s patent on a method for handling energy hedge funds was not patentable because patents must be tied to a particular machine or transform an article from one thing or state to another. This “machine-or-transformation test” is probably as confusing to you as it is to the thousand of inventors and attorneys who had to understand it. Bilski appealed to the Supreme Court and on Monday the Supreme Court decided. Bilski loses his patent, but not because of the machine-or-transformation test. Abstract ideas have never been patentable and that’s what Bilski’s patent is, according to the Supreme Court. They also ruled that the machine-or-transformation test is only one test for patentability, not the only test as the CAFC had stated. They also ruled that business methods are patentable, as long as they are not abstract ideas.
Still confused? So are many others. Except for Bilski who now knows for sure that he doesn’t have a patent. Looking at it as an inventor, I see that the court has broadened the scope of patentable materials, which is good, but has made the test for patentability muddier which means I will spend even more time and more money arguing with patent examiners. Looking at it as an expert witness for patent litigation, this ruling is sure to cause a lot more disagreements, which means a lot more litigation, which means a lot more business for me.
An excellent discussion of the Bilski ruling can be found at Patently-O, written by Dennis Crouch, Associate Professor at the University of Missouri School of Law. His regular columns on patents are the best ones available anywhere.
Last month we announced CodeMeasure, our new standalone tool for measuring software growth. This month we announced the release of CodeSuite 4.0 that includes CodeCLOC for measuring how software evolves across versions of code. CodeCLOC uses the same algorithms that were implemented in CodeMeasure and that were developed for the landmark software transfer pricing case Symantec v. Commissioner of Internal Revenue.
You’re probably wondering what is the difference between CodeMeasure and CodeCLOC. CodeMeasure is a simple, inexpensive program for generating the CLOC measurement statistics for multiple versions of a program. CodeCLOC, intended for litigation, compares only two versions of code but produces a detailed database of results that can be further filtered and analyzed using CodeSuite or your own custom tools. The results from CodeCLOC can be presented in court and the CodeCLOC database can be presented to the opposing party for verification.
CodeSuite 4.0 also has a few other nice features including a revamped user interface. There’s also a new function to generate statistics from any CodeSuite database and the command line interface has been enhanced for integrating with other programs. CodeSuite 4.0 is available for download here and can be purchased on a term license or project basis. CodeCLOC is priced at $20 per megabyte. A one year term license for CodeSuite is $100,000.
Over the years I’ve run into expert witnesses and attorneys who have told me about software copyright infringement cases where the only clues that copying occurred were patterns of spaces and tabs (“whitespace”). The idea is that if a truly ambitious thief wanted to cover his tracks, he would modify the stolen code so much that there was no longer a visible trace of copying. However, the clever software sleuth could find patterns of whitespace that the thief had missed; although virtually nothing remained, the invisible tabs and spaces could produce a conviction.
This always sounded intriguing, but I wondered whether anyone had ever tested this theory. We could find no articles or papers on the subject, except for one inconclusive paper, and I dreaded to think that some programmer was convicted based on an untested theory. I decided to have my consulting company, Zeidman Consulting, do some carefully controlled research. If the results turned out well, SAFE Corporation would add whitespace pattern algorithms to CodeSuite to further enhance its ability to detect copying.
Our results were published in a paper entitled Measuring Whitespace Patterns as an Indication of Plagiarism that was recently presented at the ADFSL Conference on Digital Forensics, Security and Law. Our results are summarized in the final paragraph:
This whitespace pattern matching method can be used to focus a search for evidence of similarity or copying, but this method cannot stand by itself.
What we discovered is that even very different files have often have similar whitespace patterns. At Zeidman Consulting we’ve used whitespace patterns to confirm copying that was already detected through the use of CodeMatch to find correlated programming elements. In those cases, the whitespace patterns offered further confidence in our findings and in some cases showed which program had been developed first. For a copy of the paper, email us at info@SAFE-corp.biz.
Our next research project is to look at sequences of whitespace within files. Maybe there we’ll find some clues to copying. But for now our results show that whitespace patterns without any other evidence should not be used to determine that copying occurred.