Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
Republishing before Silence
 
Command Line Utilities: What Would Purr Do?
 
Retiring InfoNuovo.com
 
Confirmable Experience: What a Wideness Gains
 
Confirmable Experience: Consider the Real World
 
Cybersmith: IE 8.0 Mitigation #1: Site-wide Compat...
 
DMware: OK, What's CMIS Exactly?
 
Document Interoperability: The Web Lesson
 
Cybersmith: The IE 8.0 Disruption
 
Cybersmith: The Confirmability of Confirmable Expe...

This page is powered by Blogger. Isn't yours?
  

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2005-12-07

 

Second-Guessing Microsoft on ECMA: Shape-Shifting the ODF

Consortiuminfo.org Standards Blog: Terms of Microsoft’s Ecma Submission.  I don’t want to get into the particulars of a set of speculations based on leaked documents from unidentified sources (by an attorney, no less), but there is a point about the presumption of product-agnostic specifications that I do want to flag.  Andy Updegrove’s blog doesn’t allow comments, so I’ll put my observations right here.

Andy makes the following observation about the alleged scope of Microsoft’s ECMA Submission of the Office XML Schemas:

There are two aspects of the scope that I find to be significant. The first is the use of the limiting words "which is fully compatible with the Office Open XML Formats." In short, the effort will not be permitted to create a standard that is (as is the case with ODF) intended to be the best possible product-agnostic format standard, but to create a standard that describes the material submitted by Microsoft. On the plus side, the charter does anticipate an ongoing maintenance effort that is not expressly tied to future Microsoft product developments.

  1. I have no problem with the requirement that the 1.0 result be fully compatible with the Office Open XML Formats.  I see no sense in Microsoft doing anything else.  Sorry.  I think it is a big job to do what it takes to provide the level of specification it requires for standardized usability of those formats.   I won’t be debating that.  I think it is useful and valuable to do that.  I don’t think it competes with OpenDocument in that regard, which is not so founded or limited.  We can stack up the results later.  Getting the results is the important work for now.
  2. I do want to understand why this false comparison is offered:Create a standard that is (as is the case with ODF) intended to be the best possible product-agnostic format standard.”  And who says the result of the OOX formats can’t be product-agnostic, even with the constraint of preserving MS Office content?

On what authority is it claimed that OpenDocument was intended to be that?  And how do we move from that intention (which I cannot find anywhere in the charter or reports of the Technical Committee) to its fulfilment by ODF?  Furthermore, who says Microsoft should be doing that or even offering up a specification for an open format that meets such a high standard.  (And if they did something so foolish and accomplished that, exactly how would that make OpenDocument advocates happy?)

I don’t believe that providing the best-possible product-agnostic format was in scope for ODF.  I certainly don’t believe that such an intention was realizable, if at all, without there being visible and clear evidence for the concerted effort it would have taken to realize such an intention.  I find this supposition to be magical thinking based on a presumed capability that could have emerged from the OpenDocument effort at best as a miraculous coincidence.

Andy Updegrove is an attorney and reported to be one for OASIS.  I think Andy can easily determine whether or not the charter for the “Open Office XML Format TC” through its many revisions ever placed such a challenge on the committee.  It is also useful to know whether and how the Technical Committee reported out that accomplishment and how the achievement was measured.  For the technical details, maybe Andy has some expert sources he can cite that will reveal to us how this amazing accomplishment is to be verified.

I would like to see that.  I haven’t found it in the public record of the development, and I don’t find it in the specification itself.  I welcome pointers.  I promise to look carefully at any evidence that is offered.

 

 

2005-12-06

 

Lining Up Open Formats for Office Documents

Toward Open Format Adoption.  The work to develop open office-document formats caught my attention in June, when Microsoft attracted attention to the already-licensed Office 2003 XML Reference Schema licenses and announced that Office “12” would use improved formats as its defaults, with use available under the same licenses.   I didn’t give the OASIS OpenDocument 1.0 announcement any of my attention until then.

Meanwhile, I developed a comparison table that reflected my best understanding of the relative status of the OpenDocument Format (ODF) and Office Open XML (OOX) undertakings.  When Sun Microsystems introduced a covenant not to sue over implementations of ODF, I made my first update.  Microsoft recently followed with their own version of a covenant and I have updated the table once again.

I have also refined my analysis of the ways that the currently-available (and promised future) specifications, schemas, and software implementing the formats (or elements thereof) are impacted by the offered licenses.  I then sketch how that provides room to move forward to adoption and support in ways that are valuable to me.  That’s all provided in my latest on-line analysis.  I am sure that there will be more reason for updates, but perhaps not at such frequent intervals.

Here’s the portion of the latest comparison table that covers the Royalty-Free patent and covenant-not-to-sue provisions:

 

Patent Freedom Approach

OASIS Open Document Format (ODF)

Microsoft Office Open XML (OOX) Format

with Sun IPR notice of 2002-12-11

with Sun Patent Statement of 2005-09-29

with 2005-11-22 covenant not to sue and future ECMA/ISO Submission

with Microsoft Schema Reference licenses (copyright and patent)

royalty-free patent licensingSun Microsystems "essential claims" royalty-free licenseSun Microsystems will not enforce any of its patents, present or futurecovenant not to sue applies, with or without following license conditionsMicrosoft "necessary claims" royalty-free license
patent-license scope limitationonly where unavoidable in order to implement the specification, and only to implement the specificationany implementation of ODF 1.0 and subsequent versions in which Sun participates to an extent that OASIS rules apply in regard to IPRunder the covenant, those portions of a software product that read and write the formatonly where unavoidable in those portions of a software product that read and write files that are fully compliant with the specification of the schemas
patent reciprocity requiredYes.No.  License is terminated for any party that attempts to assert patent rights against any ODF implementation.No.  Suing Microsoft or affiliates for infringement of a related patent claim will terminate the license for the complaining party.  The covenant not to sue will also be voided with regard to the suing party.
patent-license noticenone requiredlicense usable but not required under the covenantspecific statement required

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $