Microsoft Can't DRM Docs Fast Enough
grcumb writes "As part of the DoJ Anti-trust settlement, Microsoft was ordered to provide freely available documentation for its communications protocols. InfoWorld is reporting that not only are they late in delivering the required APIs, but it's because they want to convert everything to the read-only Web Archive (MHT) format, which can only be viewed in MSIE. InfoWorld reports that, "In July, Microsoft said it would complete revisions of the documentation required by the court in the autumn, a season generally reckoned to include the months of September, October and November in North America, but may now have to extend work on a beta or test version of the new documentation into December...." So we have to wait longer for a format that makes the content harder for developers (developers! developers!) to use. Maybe they didn't read the documentation ..."
RFC 2557: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
There's a Mozilla KB entry about MHTML support and open bugs for load and save (IDs 18764 and 40873; bugzilla won't accept links from Slashdot). Plus the maf extension to support MHTML.
Microsoft's policy is that all downloadable documents and specifications etc. should be signed, so you can verify that the document hasn't been tampered with. Usually they implement that by embedding a word document in an (signed) Windows executable. MHT seems to be an improvement.
" I'm not sure what the article is talking about" - then READ it. You would find the following:
.mht file and the signed publishing license into a file called a compound file. This file, which has an .rmh file extension, is used by the Rights Management Add-on for Internet Explorer to permit viewing of RMS-protected content in Internet Explorer. For more information, see Compound Files. You can use your own format if you are not using the add-on."
from Microsoft: "The Web application puts both the encrypted
"The plaintiffs have three main areas of concern about the documentation.
First among these is that Microsoft, asked to open up and document the interfaces to its communication protocols for licensees, has chosen to issue the documentation in a rights-protected file format called MHT, readable only with its own Web browser, Internet Explorer. This means licensees can neither annotate nor effectively search the information, according to the plaintiffs. "
The DRM is not the compression part. The files are encrypted. If you DID RTFA, you would have read:
And that MS is offering aThe problem with this dev toolkit is that it is MS only, so that means no Linux, Mac, *BSD or Solaris for the DRM of these MHT files. These documents are for developers who may want to interact with MS's proprietary communications protocols, and some of them may be working on different OSes to make those other OSes use MS's proprietary communications protocols. Now they will be forced to use MS windows to get to the documentation.If Tyranny and Oppression come to this land,
it will be in the guise of fighting a foreign enemy. -James Madison
Bug 18764 has 73 votes and many duplicates, which makes it fairly popular. It isn't the the most voted-for bug though; some have well over 100 votes.
bug 40873 (Save As MHTML) has 180, so it's a top 10 bug.
You might try the MAF extension to Firefox.
"This is an archive extension that allows complete web pages to be saved in a single archive file. MAF stands for Mozilla Archive Format and the extension uses RDF to save page meta-data such as the original URL of the page and the date/time the page was put in the archive. It also allows pages to be saved in a separate MHTML compatible format for interoperability with IE systems."
We may not imagine how our lives could be more frustrating and complex—but Congress can. – Cullen Hightower
Programming for classic MacOS was hard. Programming for NeXTSTEP/OPENSTEP was easy. Programming for OS X is easy. Certain the implementation of Cocoa isn't given away, but the interface and excellent documentation is. Besides, with protocols and categories it is often unnecessary to subclass objects, thus making understand them less necessary. It's also nice that GUI code is unnecessary in most circumstances.
English is easier said than done.
What's so difficult about a read-only format?
There is nothing wrong with a read-only format. There is a problem with the read-only format they have chosen. "Freely available" were the words used in the instructions. These documents can only be viewed in IE with a special plug-in from MS. IE runs on 2 platforms, Windows and MacOS (sort of). MS has deprecated the mac version, leaving Windows the only actively maintained platform for reading this documentation. Windows costs money.
If I complied with a court order to provide documentation, by putting the documents in a safe deposit box and offering to sell people copies of the key, I'd be rotting in a cell by now. Bill Gates should spend at least one night in the lock-up for this crap.
SLASHDOT: news for people who can't concentrate on work or have no life at all and got tired of yelling back at the TV.