Slashdot Mirror
"Easy Work-Around" For Microsoft Word's Legal Woes
CWmike writes "Microsoft can likely use an 'easy technical work-around' to sidestep a recent injunction by a Texas federal judge that bars the company from selling Word, a patent attorney said today. 'The injunction doesn't apply to existing product that has already been sold,' said Barry Negrin, a partner with the New York firm Pryor Cashman LLP who has practiced patent and trademark law for 17 years. 'Headlines that say Microsoft can't sell Word are not really true,' said Negrin, pointing out that the injunction granted by US District Court Judge Leonard Davis on Tuesday only prohibits Microsoft from selling Word as it exists now after Oct. 10. 'All Microsoft has to do is disable the custom XML feature, which should be pretty easy to do, then give that a different SKU number from what's been sold so it's easy to distinguish the two versions.'"
Really if MS decided to lobby against patent trolls they could have saved themselves the trouble in the first place.
Taxation is legalized theft, no more, no less.
Nah, removing the ooxml code is easy. Telling your customers "all of the documents you've saved since 2006 won't be readable by new installations" is the hard part. This is a non-story, we all know obviously they can take the code out, but it doesn't help their users who have docx documents.
Maybe they could offer a downloadable component like they have for old versions of Word?
Also, what does this mean for openoffice?
Spoken like a true end-user. As a developer, almost every single time I've ever said something would be "easy to do" code-wise it has come back to bite me in the ass. I've learned not to use that phrase for anything, especially for things that really do seem easy to do. Now it is "I'll see what is involved in that request and get back to you." End-users always seem to think things will be easy to change. Disabling a feature in a widely used application like Word that likely has a ton of legacy code in it is probably not as easy as one might think. I'd also be skeptical about this statement considering it is coming from the opposing lawyer and not from one of MS's own engineers.
God, schmod. I want my monkey man!
Or does he not quite understand the reaction of a few million angry customers, who've just discovered that "Word" now doesn't read "Word documents" and have been blandly told "Oh, we changed the SKU number from 3454234 to 3454235, didn't you notice? You should have seen KB65564 for clarification of Microsoft Office Product SKUs."
Seriously, doing that would make the whole Vista Ready vs. Vista Capable debacle look like a 10 dollar parking ticket. What a stupid plan.
I'd assume that whichever judge imposed the injunction would take a very dim view of MS offering a "product + download" to circumvent the injunction; but IANAL, and there could be some subtlety that makes that legal(incidentally, I can well imagine that, if it applies to the OOXML plugins for 2003, there'll be some weeping and gnashing of teeth among certain major corporate customers).
Your honor, we've moved all the offending code to hot_coffee.dll, and made sure that it is not accessible to users...
If Ms got rid of the ability to add custom XML, they would never be able to Extend the specification they proposed, and so Extinguish competition while everyone else plays catch up.
I trust Microsoft as far as I could comfortably spit a dead rat
We all write our comments in Word. Because the Internet Explorer doesn't have a spell checker.*
* (just a guess)
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
Word patent troll edition.
Every time you post an article on Slashdot, I kill a server. Think of the servers!
We all write our comments in Word. Because the Internet Explorer doesn't have a spell checker.*
* (just a guess)
Wat are u tlaking abot, I dont nede a spellcheker.
They could hire someone to dig through the IBM research journals and patents on the General Markup Language and its successor SGML, and find some prior art. They might even have some prior art of their own related to RTF. This patent sucks; it's on a basic technique that anyone writing a program to read a document with inline tags would at least consider, and I find it hard to believe it wasn't actually used on occasion.
Wow. Just wow. Do yourself a favor next time, and look up the slightest bit of info. The US District Court is a FEDERAL court.
Apparently, ODF is safe from this patent.
So the patent works like this: Instead of storing markup within a document, you instead store the markup separately from the raw data and then map each markup element to a character position in the raw data, like this:
:P
--Original document--
<foo>This is a foo</foo><foo><bar>This is a foo bar</bar></foo>
--i4i patented storage--
Raw document:
This is a foo This is a foo bar
Metadata Map:
1 <foo> 0
2 </foo> 13
3 <foo> 14
4 <bar> 14
5 </foo> 31
6 </bar> 31
The idea is that you should be able to edit the raw data, or the markup, independently of one another. The patent outlines three core scenarios: 1) Taking an existing document with inline markup and separating the text and the markup, 2) Generating a "separate data and markup" document from scratch, and 3) Combining the markup and raw data of a doc generated from scenario 1 or 2 back together to produce a document with the markup inline.
So why is this neat? The patent claims that you can edit both the content and the markup independently of one another. Except that you would require a specialized editor that manipulates both components to be able to do this and still maintain the "mapping" of markup to raw data. Hate to say it, but I can already do this on normal, inline-markup documents using notepad, or any WYSIWYG HTML editor.
The other claim is that you could apply any map to any raw data. Except that, unless the character positions of semantic elements in the raw data were exactly where the "Metadata Map" expected them to be, the result would be a huge mess. Practically speaking, the application of a metadata map to multiple documents (since the map is based on character position) would most likely require additional inline tags to align the separate metadata to the content, thus defeating the whole purpose of the patent. Or maybe you could establish a "standard sentence length" in order to allow one map to be applied to different documents - that would be great.
I'm having a hard time understanding how the technology described in this patent is actually useful at all, let alone how Microsoft has infringed on it.
The "easy technical workaround" for Microsoft is to dump their crappy OOXML format (which infringes this patent) and switch completely to ODF (which doesn't seem to).
Maybe this patent lawsuit is the reason why Microsoft started supporting ODF in the first place.
Except the company suing them aren't patent trolls. If you took a minute to check out their site, they legitimately offer services that directly relate to what they're suing about.
First off I would have to disagree that your assertionis correct (see below). But at the same time I would assert that the technique in question might be on the hairy edge of patentable, making them legitimate--maybe.
Okay so what is the patent about? Well it's not about using XML to store documents. It's about a somewhat specific way of storing xml for documents in file systems or streams that has gains some efficiency over the conventional XML format. Specifically you write the documents plain text out as raw plain text without any XML tags. Then in separate location you write our all the xml tags. After each tag you write a pointer to the chearacter position in the plain text where the tag needs to go. The claim is this means that if you change formats you don't have to re-write the file with the plain text thus making it a lot faster to update (and you can imagine stream on the cloud). The second patented feature is that this allows one to store multiple "views". That is one could have multiple different xml tag sets for the same text body. Besides simply being a view, this is useful also for undo's
So you can see this pertains basically to "fast saves" of big documents, and possibly to cloud applications.
It's pretty easy to imagine other ways to skln this cat if you had too. FOr example, store diffs which I think is how the older MS fast saves work anyhow. But in the cloud world I bet just using XML views rather than diffs is slightly more javascript freindly given all the existing XML based code. plus it makes i more of an open standard.
SO while MS could work around this, it will make the resulting document less open format. a terrible irony.
One could question howver if this is really patent worthy. I'd say maybe. it does have tangible advantages and back when it was patented it might have been the first time for xml to be encoded this way (I have no idea on that). But it also seems kinda obvious. Many XML documents sort of do that in a way already. They insert some labeled format tag which we call a "style" then put the detailed XML description of that "style" in the document header. SOr example apple's pages does that, and presumbaly most processors with style sheets have done that. But that's still a bit different than actuall pointers.
So maybe maybe it's patent worthy. I'd say no. but it's arguable.
ANyhow getting back to the parent's assertion that they market this, well thats nonsense. this is a technique that once you tell it to someone is generic. No one would hire you to implement it for their own product so you can't sell any services here. And any specific implementation is irrelevant. FOr example this is not going to affect their competitiveness in selling a word processor.
Some drink at the fountain of knowledge. Others just gargle.