Gary Edwards's Library tagged → View Popular
High-latency, low-bandwidth windowing in the Jupiter collaboration system
Operational Transforms (OT) is used by Microsoft CustomXML and Google Wave! The original idea was first presented by Zerox Parc researchers in 1995, prior to the i4i patent. The Jupiter System includes the Jupiter Window Tool Kit, wich is all about OT. XML came much later with the i4i patent for encoding XML with OT positioning.
Insert(pos, text)Delete(pos, num-of-chars)
See Google Wave API: http://www.waveprotocol.org/whitepapers/operational-transform
Credit Florian Reuter for this find!!!!!
Patent Ruling Against Microsoft Hinges on Meaning of Custom XML
Marbux discovered this gem, joining the argument with an insightful but disagreeing post. I however agreed with the articles author, Jeff Cogswell, that both the judge and jury confused the XML pane feature set with metacode mapping claims in the now infamous i4i 449 patent. If Marbux is right, then HTML-CSS, ODF, and RDF/XML-RDFa are also infringing on this patent. Which i4i claims is not the case.
Except: Here's one part of the ruling: ...
Microsoft Corporation is hereby permanently enjoined from ... selling, offering to sell ... any Infringing and Future Word Products that have the capability of opening a .XML, .DOCX, or .DOCM file ("an XML file") containing custom XML.
The odd wording here is "custom XML," which appears several times in the ruling. Based on the comments in response to eWEEK's articles on the ruling, as well as comments I've seen elsewhere, a great deal of people think the problem was that Microsoft uses XML as its format. But that isn't the case. The ruling focuses on the use of custom XML. The ruling is not about the fact that Word uses XML. If it did, there would be a worldwide disaster, considering how prevalent XML is.
But what exactly is custom XML? To start with, let's look at the claims of the patent itself and try to make a connection. The patent, which was written back in 1994, covers a new way of providing formatting in a word processing program. To understand the claims of the patent, it's important to note the distinction between what the inventors call content and what are called metacodes (which are ultimately formatting codes).
Microsoft planned to bury XML developer, says federal judge | The Industry Standard
Maybe the most informative article to date regarding the Microsoft-i4i "custom XML" patent infringement case. Greg Keizer is trying to dig into the trial records and judicial response. Looks like for Microsoft, it's business as usual.
excerpt: Microsoft knew of the patent held by i4i as early as 2001, but instead set out to make the Canadian developer's software "obsolete" by adding a feature to Word, according to court documents.
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in i4i
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo
