Skip to main content

Home/ OpenDocument/ Group items tagged disclosure

Rss Feed Group items tagged

Jessica Cruise

Why Is Rihanna Disclosure Most Force? - 0 views

  •  
    Is Rihanna sending mixed messages on retainer aggression? Since her relationship with producer Chris University ended--after he was arrested for punching her in the present, Rihanna's lyrics hold, at present, seemed to vindicate aggression. In "Love The Way You Lie," her rap piece with Eminem, she justified staying in an abusive relation. In her last recording, "S&M," she uses pictorial images and lyrics to puddle her frame for retaliation. The recording has reportedly been banned in 11 countries. In a November 2009 interview with 20/20, Rihanna said she was distribution her story of discourtesy in hopes of serving boy like girls. "I will say to any woman deed through housewifely aggression, 'Turn out of this. Examine at it 3rd being for what it real is,'" she said.
Gary Edwards

OOXML in Norway: The haywire process | Geir Isene : Straight talk on IT - 0 views

  • I had read the essay by Jon Bosak (SUN Microsystems) on why SUN voted as it did in the US. He lays out a very different strategy. His view is that the battle is lost to completely reject OOXML as an ISO standard. ISO can only reject it with comments, and that is equivalent to giving Microsoft a todo-list on how to fix the draft so as to get it approved. Microsoft has sufficient manpower to easily tackle that. Most of us had missed what Mr. Bosak saw: OOXML promises interoperability with earlier closed binary formats (the Word Doc, older Excel file formats etc.). But it doesn’t deliver. How on earth could someone be able to convert old binary files to the new format without having the specification of the old formats and a mapping to OOXML. If you are to translate some text from Chinese to English, it doesn’t much help to only know English.
    • Gary Edwards
       
      A "Yes with comments" is a yes for the ISO approval of MS-OOMXL. If ISO approves MS-OOXML, it won't matter what Bosak's "comments" strategy is. Microsoft and the Vista Stack will be off to the races. The full disclosure of the MS binary document secret blueprint won't matter much at that point.
  • “Ah c’mon Bosak, you are chickening out, we must stop this dead in the track”
    • Gary Edwards
       
      There you go Geir!

      Sun and Bosak have held the door open for MS-OOXML since 2002, when Sun blocked an effort to write the ODF Charter to include as a priority, "compatibility with existing file formats". This of course would include the billions of legacy MS binary documents.

      The thing is that those who work in the conversion-translation field will tell you that it is currently impossible to pipe converted legacy binary documents and OOXMl docs for that matter into ODF. Just as Microsoft claims, ODF in it's current state is insufficient and unable to handle the rich feature set of the MSOffice developers platform.

      The problem could of course be easily fixed by the inclusion in ODF of five structural generics. In the past year, there have been no less than five iX "interoperability enhancement" proposals submitted to the OASIS ODF TC for discussion and consideration. As uber universal interop expert Florian Reuter points out in his blog, these iX proposals did not fare so well.

      What Florian doesn't point out is that it was Sun who opposed any and all efforts to improve compatibility with existing Microsoft binary and OOXML documents. Just as they have done for nearly five years now.

      Sort of puts the Sun-Bosak support for ISO approval of MS-OOXML in a different light. ~ge~
  •  
    see the sticky notes on this one
Gary Edwards

Microsoft Watch - Corporate - Microsoft's Stunning Court Defeat - 0 views

  • "The Court considers that the Commission was correct to conclude that the work group server operating systems of Microsoft's competitors must be able to interoperate with Windows domain architecture on an equal footing with Windows operating systems if they are to be capable of being marketed viably. The absence of such interoperability has the effect of reinforcing Microsoft's competitive position on the market and creates a risk that competition will be eliminated."
  • Here, U.S. oversight of Microsoft will continue until at least November 2009, largely because of server protocol licensing. The so-called "California group" of states—those that didn't settle the U.S. antitrust case—and other parties will likely ask the court here to align the two disclosure programs, extending the ruling's impact well beyond Europe.
    • Gary Edwards
       
      I wonder if this is correct? My understanding is that the California Group will be brushed aside by the Feds?
  •  
    Microsoft Watch Joe Wilcox is on the job.  This particular hgihlighted quote speaks volumes.  The USA anti trust settlement famously allowed Microsoft to commercialize interoperability through expensive licenses -  $8 Million per year for just the basic package.

    It looks like the EU would force those interoperability API's out into the open.  I wonder how this position will impact the November 12 th hearing on lifting the USA anti trust oversight?  We have the EU saying the monopolist is illegally maintaining their monopoly through various interop barricades.  And, the USA about to declare that the interop barricades no longer exists, therefore, the monopolist should be free to wreck havoc. 

    The stage looks set for a vey dramatic final act.

Gary Edwards

Q&A: Former Mass. CIO feels \'bittersweet pride\' after battles with Mi... - 0 views

  • Q&A: Former Mass. CIO feels 'bittersweet pride' after battles with Microsoft, legislature Gutierrez says he would make same choices again that he did in ODF and IT funding fights
  •  
    Whoa, Wiki Ricki is right.  This is a great article!  A must read interview with Louis Gutierrez.  I wonder though, since it was ComputerWorld and the Boston Globe that filed the August 2006 Freedom of Information Act invocation to get all the Massachusetts conversations and meetings, no doubt they were carryign some heavy ammunition into this interview.  Up until this interview it's been next to impossible for the public or press to get truthful information.  This is a good start, and i for one wonder just how far Massachusetts execs are willing to go with their public disclosures?
Gary Edwards

Slashdot | OpenDocument Foundation To Drop ODF in desperate search for something that w... - 0 views

  • This fight is a distraction. Recognize both formats as legacy defacto standards and move on. This is actually a very common precursor in a standards process. CDF provides an opportunity to do the job right. People should not be translating OOXML into ODF, there simply isn't the value there. It is much more likely that OOXML will be a live format in twenty years time than ODF. We have a common standards based document language today - HTML. OK so I have a bias here but there is much more HTML than anything else. HTML is just a document format and it is somewhat presentation oriented but modern XHTML is changing those problems.
  • The problem for "you" is that Microsoft is the one who has 400 million or so installs of the dominant de facto office suite in the planet. "You" can either try to get them to play nice with you by applying pressure intelligently, or you can organize an exciting jihad to stick it to them. In a make-believe world where companies choose technology based on, well, technical merits and openness, the second approach will usually work. In the real world though, the former option would have been a better idea. But when you have well-paid shills like Rob Weir (courtesy of IBM) and his co-religionists who rarely take a break from hating Microsoft (except for lame attempts at making fun [robweir.com] of Microsoft) it's difficult to get away from the join-us-or-die approach. It just feels so right, I guess. I'm going OT here but seriously, Weir is just the cat's meow. Every single time Microsoft has challenged his hyperbolic rants and outright lies he's essentially ignored them or just penned some more. He thinks the OpenDocument Foundation is an irrelevant fly-by-night fanboy club (which I guess is possible), but he has no problem quoting obscure African groups [robweir.com] and his groupie bloggers to prop up his "Microsoft is evil and Office sucks and remember, IBM had nothing to do with this post" arguments. If the man spent 1/10th as much time writing some code or documentation as he does bitching about the Office toolbar buttons, ODF would have conquered the world by now. With people like that at the helm it's not difficult to see why a document format controlled by a single company and an elite group of testy technorati has gotten to where it is now. Not that I think OOXML is a particularly good idea, but at least there's someone out there with the balls to point out that the emperor is buck naked. I guess they better get ready for the DoS attacks, hate mail and death threats.
  • Blame Sun for this. Sounds like a populist position, or maybe troll flamebait. I'll be generous and assume the former, despite the fact your post seems like a digest from an anti-ODF briefing paper. Disclosure: My job [sun.com] includes the task of receiving complaints about Sun and trying to get Sun to fix whatever causes the problem. If you have proof of any of your accusations, let me know. I may have some of my facts wrong below as I'm working from memory; I'd welcome correction. With a few small additions, ODF could have supported Office formats as well, but Sun would not allow this. That is indeed the constant assertion that the three guys who comprise the Foundation make. However, I have personally asked members of the ODF working group at OASIS and they tell me its not so. The Foundation guys wanted to add structures to ODF to preserve untranslateable tags in translated documents so they could be regenerated on the reverse translation. Sounds OK at first glance, but in practice it results in very brittle software solutions that work well in demos but not in real life. The proposal was thus rejected by the whole working group (not just the Sun employees). Rejected, that is, in conversation. A complete solution was never proposed for voting. To say Sun would not allow it ignores the actual dynamic of the working group (see below). Their policy is that ODF will support what is needed for StarOffice, and nothing more. Naturally every member of a standards group in the traditional standards process is looking out for the code base where they implement a standard, and will have serious questions of any feature that they regard as unimplementable. The features actually put to a vote by the guys from the Foundation would have resulted in very brittle implementations, highly dependent on the version of MS Office with which they were coupled. It may have been possible to come up with a solution that reduced this problem, but the discussion was not sustained. The assertion you make is not true in the general case.They control the ODF technical committee Untrue. The ODF TC [oasis-open.org] can have no more than three members from any one organisation and is not under the control of any organisation. The Foundation guys actually flaunted that rule at one point and sent many, many more representatives - OASIS had to step in to fix it. That intervention is one of the issues they have with OASIS, in fact. Sun happens to employ the people who act as Chair and Secretary to the TC but the voting remains democratic.and their patent license allows them to stop the ODF TC if the ODF TC goes in a direction Sun does not like. I've heard that interpretation of the patent non-assert covenant [oasis-open.org] that Sun has made regarding ODF, but it's untrue. Sun covenants not to enforce any patents against ODF implementations based on any spec it participates in. To the extent that versions of the spec after Sun's departure are based on version in which Sun was involved, that covenant remains in effect even in the unlikely event of Sun leaving the TC. Sun can't stop the TC from continuing its work. Are you relaying this all as hearsay, or do you actually have data to back up your accusations? If you have, I'd like to see it (genuinely).
    • Gary Edwards
       
      Sun currently has SIX voting members on the TC. This statement is crap and easily disproven by the facts of actualy voting records. It's also true that Sun members have voted as a block since December 16th, 2002 The Foundation, at the height of it's work sponsored 28 particpants. Never once did the Foudnation member vote as a block. Never. Fopundation member are responsible for the OASIS ODF Open Formula Sub Committee and the ODF Metadata Sub Committee. This work would not exist without the sponsorship of the Foundation. It is true that a rule change OASIS inititated in December of 2006 cut the sponsorship of Foundation members from 15 to 2. And no more than 2! this effectively ended the Foundation's role in OASIS. The rule change was the elimination of the 501c(3) exception. Under normal rules, OASIS Corporations can sponsor as many employees as they like under a single membership. Under 501c(3) IRS rules, volunteers are considered the equivalent of employees. All OASIS had to do was eliminate the 501c(3) membership category and the Foundation was dead. And this is exactly what they did.
Paul Merrell

Matusow's Blog : Open XML, ODF, PDF, and XPS in Office - 0 views

    • Paul Merrell
       
      Whoopee! Everyone gets to add vendor-specific extensions to standards like ODF to enable some quality of Sharepoint/Exchange/Outlook interop in their apps, just as soon as Microsoft gets around to offering adequate specfications. History teaches that may be a very long time, and of course the relevant Microsoft patent RAND terms apply, because the disclosures are made outside the context of a standard that requires otherwise. And of course the OASIS RF on RAND policy does not forbid new ODF features subject to RAND terms and the policy is silent on the subject of vendor-specific extensions. Methinks FOSS may have just lost its "open standard" ODF.
  • Office is NOT implementing ODF 1.0 from ISO. That spec is not representative of the marketplace today, it is not what is implemented in OpenOffice, it is not what IBM is using for Symphony, and it is not referenced in the Massachusetts ETRM policy.
    • Paul Merrell
       
      As I have been arguing, there are no full featured implementations in existence of the ISO/IEC:26300 OpenDocument standard and every government that has adopted the international standard as its own internal standard or procurement specification is subject to legal challenge because of the lack of implementations.
  • In my opinion, the continued interest in innovation presented by those solutions will speak much louder than the formats themselves.
    • Paul Merrell
       
      You can have standards and you can have innovation. But you can't have interop if you embrace and extend standards. The need for stable, fully-specified formats for document interchange purposes apparently is not part of Microsoft's plan. Scant wonder, neither ODF nor OOXML is designed for document interchange among competing vendors' apps. They are both standards designed to allow a single vendor to maintain dominant market share among implementors of those standards. Microsoft will soon diominate market share in both so-called "standards." The embrace of a standard is necessary to extend and extinguish it.
  • ...3 more annotations...
  • While this is a big deal announcement for the Office product team (check out Doug Mahugh's blog), my take on it is predictably focused on the longer-term interoperability factors.
  • the API that will allow ANY document format to register itself with Office and be set as the default will be made available as planned. Additionally, the work with DAISY and other specialized document formats will move forward as well.
    • Paul Merrell
       
      I was wrong. The API is for more than ODF plugo-ins.
  • The documentation of client/server protocols for Office-related technologies (such as SharePoint and Exchange/Outlook communications) will remain available to the public.
  •  
    "Clearly the Press Announcement today from Microsoft will bring about another wave of discourse on the future of document formats. " Jason Matusow presents the long-term view of the announcement's significance.
Graham Perrin

Orcmid's Lair: Microsoft ODF Interoperability Workshop - 0 views

  • 2008-08
  • Microsoft's first built-in support
  • approach to adding Open Document Format support directly into Office 2007
  • ...20 more annotations...
  • the balancing act that Office-ODF interoperability requires
  • absence of non-disclosure agreements
  • I saw no down side
  • all ODF TC members who desired to come had a place
  • interaction with the ODF community
  • priorities that apply in making trade-offs
  • five guiding principles that govern ODF support in Word, Excel, and PowerPoint
  • balancing of different interests: standards groups, corporations, institutions, government agencies, regulatory bodies, and general users
  • an application being quite friendly with its own ODF but not with that of other significant implementations
  • Balancing of competing considerations is not trivial
  • current OpenOffice.org implementations fail to check whether a formula conforms to its own extension
  • the central feature of typical document processing software is the internal, in-memory representation of the software's document model
  • features may be lost on output
  • features may be lost on input
  • rely on features that succeed with the internal representation
  • degraded or lost entirely in the chosen external representation
  • losing some of them when saving
  • Florian Reuter argued an interesting gracefully-failing extension technique that, on reflection, I believe could avoid breaking changes against earlier ODF specifications of namespaces, their elements and their attributes too
    • Graham Perrin
       
      I'd like to learn more about this.
  • a serious, open conversation is beginning
  • discussions did not arrive at conclusions
  •  
    I read this more than a year after the event but still, it's interesting.
1 - 7 of 7
Showing 20 items per page