Skip to main content

Home/ OpenDocument/ Group items tagged oasis

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

WICD Full 1.0 - CDF Desktop Profile - 0 views

www.w3.org/WICDFull

cdf odf ooxml w3c wicd

shared by Gary Edwards on 13 Nov 07 - Cached
  • WICD Full 1.0 is targeted at desktop agents
  • The WICD Full 1.0 profile is designed to enable rich multimedia content on desktop and high capability handheld agents.
  • The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "may", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 (see http://www.ietf.org/rfc/rfc2119.txt). However, for readability, these words do not appear in all uppercase letters in this specification.
    • Gary Edwards
      Gary Edwards on 13 Nov 07
       
      This will make marbux happy!
  • Gary Edwards on 13 Nov 07
     
    Now this is interesting.  I wonder if IBM and the OASIS Lawyer have seen this page?
Gary Edwards

Look what Google can do now: OOXML! - 0 views

www.star-telegram.com/...396637.html

cdf google ibm iso oasis odf ooxml opendocument openoffice sun symphony

shared by Gary Edwards on 20 Jan 08 - Cached
  • Instead of dialing 411 on your phone and paying the service fee, dial 800-GOOG-411
  • Send the name of the business and the city or the ZIP code to GOOGLE. (Type GOOGLE into the address or number field, like you would if you were using a phone number.) Google will text you back with the address and phone number.
Gary Edwards

Alan Cox on open-source development vs. proprietary development | The Open Road - The B... - 0 views

erichmusick.com/...antic_disposition.html

oasis odf opendocument

shared by Gary Edwards on 24 Oct 07 - Cached
  • Ophelia explains he possessed at one time a "noble mind" and was a "soldier," and a "scholar" – all the terms by which any young man at that time would like to be known (3.1.64). Now, though, Hamlet lashes out at others, speaks harshly with those to whom he is supposedly close, and even thoughtlessly kills a man.
    • Gary Edwards
      Gary Edwards on 24 Oct 07
       
      Ouch!
  • Though Hamlet fails to disclose his reasoning behind displaying the "antic disposition," his words and actions point to a few possible motives
    • Gary Edwards
      Gary Edwards on 24 Oct 07
       
      aha! Ulterior motives!
  • though this be madness, yet there is method in 't"
  • ...3 more annotations...
  • As his madness controls more and more of his life, Hamlet treats those whom he should treat with dignity and respect as if they were trash.
    • Gary Edwards
      Gary Edwards on 24 Oct 07
       
      Jody Goldberg, Miguel de Icaza, Michael Meeks, and the two guys without a garage at the Foundation
  • Hamlet vows to slander Ophelia
    • Gary Edwards
      Gary Edwards on 24 Oct 07
       
      There you go!
  • If Hamlet had never put on the "antic disposition," he may not have gotten revenge, but the play would not have ended in tragedy – Hamlet, himself, as well as those he loved, would not have died.
Gary Edwards

IBM In Denial Over Lotus Notes - Forbes.com - 0 views

www.forbes.com/...cz_dl_0406notes.html

exchange ibm lotus microsoft

shared by Gary Edwards on 19 Oct 07 - Cached
  • The marketing folks in IBM's Lotus division are starting to sound like the Black Knight in Monty Python and the Holy Grail, who insists he's winning a fight even as he loses both arms and legs: "'Tis but a scratch," the Black Knight declares after one arm is lopped off. "Just a flesh wound," he says after losing the other. "I'm invincible!" The same goes for IBM's (nyse: IBM - news - people ) Lotus, which keeps declaring victory even as Microsoft (nasdaq: MSFT - news - people ) carves it up.
  • Gary Edwards on 19 Oct 07
     
    Want to know the real reason why IBM and Microsoft are going at it hammer and tong over document formats?  Here it is.  Lotus Notes is getting clobbered by the Exchange/SharePoint juggernaut. 

    The article is old, but the point is well taken.  Today the Exchange/SharePoint juggernaut i sover 65% marketshare.  IBM is struggling to protect the Lotus Stack against an impossible foe.

    The thing is, Microsoft E/S will ALWAYS have better integration with the MSOffice - Outlook desktop monopoly base (550 M and counting).  Most of this "integration" is due to the high fidelity exchange of documents in Microsoft's proprietary XML mode known as MS-OOXML.   Forget the charade that MS-OOXML is an open standard called Ecma 376.  MSOffice and infamous XML Compatibility Pack Plug-in do not implement Ecma 376.  The Pack implements MS-OOXML.

    One key differnece between MS-OOXML and Ecma 376 us that MS-OOXML is infused with the Smart Tags components.  These are for metadata, data binding, data extraction, workflow, intelligent routing and on demand re purposing of docuemnt components.  In effect, MS-OOXML :: Smart Tags combines with proprietary .NET Libraries, XAML and soon enough Silverlight to replace the entire span of W3C Open Internet Technologies. 

    Can you say "HTML"?

    Okay, so why does this matter to IBM and the future of Lotus Notes?

    The end game of the document format wars is that of a stack model that converges desktop, server, devices and web information systems.  The MS Stack uses MS-OOXML as the primary transport of accelerated content/data/multi media streams running across the MS Stack of desktop, server, device and web application systems.  It's the one point of extreme interoperability.

    It's also a barrier that no non MS applicatio or service can penetrate or interoperate with except on terms Microsoft dictates. 
Gary Edwards

Podcast: ODF, OOXML and CDF .... The OpenDocument Foundation Responds | Between the Lin... - 0 views

blogs.zdnet.com/...index.php

cdf foundation ibm iso oasis odf ooxml opendocument openoffice sun symphony

shared by Gary Edwards on 21 Jan 08 - Cached
  • David continues his deep dive into the curious case of the OpenDocument Format and the OpenDocument Foundation.
  • Gary Edwards on 21 Jan 08
     
    Dragged through the mud
Gary Edwards

Open Document Foundation Dumps ODF for CDF - Open for Business - Lora Bentley - 0 views

www.itbusinessedge.com/...osb

cdf odf ooxml w3c

shared by Gary Edwards on 06 Nov 07 - Cached
  • Five years after it was formed specifically to promote OpenDocument Format as an alternative to Microsoft Office formats, those behind the Open Document Foundation are abandoning the OASIS- and ISO-approved document standard in favor of the World Wide Web Consortium’s Compound Document Format.
Gary Edwards

BetaNews | Course Change for OpenDocument Developers Seen as Emerging Rift - Scott Fulton - 0 views

www.betanews.com/...1

cdf odf ooxml w3c

shared by Gary Edwards on 04 Nov 07 - Cached
  • A presentation made two weeks ago by two members of OASIS' OpenDocument technical committee, and founding members of the OpenDocument Foundation, made it clear that the foundation would be turning its attention away from developing the ODF format and translators for it. Instead, in a course change instigated as far back as last May, the Foundation is steering back toward a project launched in 1995 by the World Wide Web Consortium, in hopes of recapturing the momentum toward document interoperability for all existing word processor users.
Gary Edwards

ODF and differences of opinion | TalkBack on ZDNet - 0 views

talkback.zdnet.com/5208-11048-0.html

cdf odf ooxml w3c

shared by Gary Edwards on 04 Nov 07 - Cached
  • Just because we are garage challenged doesn't mean we can't find the back door to the big house :) The larger issue at stake here is not whether or not we have a garage, or what our contribution to ODF has been over the course of five years as active members of OASIS ODF. What it really comes down to is the implementation of ODF in the real world.
  • Gary Edwards on 04 Nov 07
     
    Lengthy comment explaining once again why we moved from ODF to CDF. 
Gary Edwards

ODF 1.2 Metadata? You're Dreaming! Microsoft starts rolling out more OOXML translators... - 0 views

talkback.zdnet.com/5208-12558-0.html

cdf ge mary-jo metadata microsoft odf ooxml opendocument shish

shared by Gary Edwards on 11 Dec 07 - No Cached
  • Sorry Shish, you're wrong about ODF 1.2 Try ODF 1.5 or ODF 2.0, maybe. The metadata requirements for ODF 1.2 actually did include two way lossless translation capability. Unfortunately these features did not survive the final cut, and were not included in the April 2007 submission. You might also want to check the February 23, 2007 metadata proposal from Florian Reuter. That also would have delivered the goods and perhaps put ODF that grand convergence category of usefulness across desktops, servers, devices and web systems currently the exclusive domains of MS-OOXML and CDF+. Florian had devised a means of using metadata to describe the presentation aspects of content and structural objects. Very revolutionary. And based on the simple notion that bold, font, margins etc. are simply metadata about content and style objects. Where the train came off the track had to do with the concept of an XML ID means of linking metadata to content. Not that there was anything wrong with this mechanism. It's actually quite clever. What went wrong was that Sun insisted that only those elements approved and supported by OpenOffice would be allowed to make use of XML ID metadata. For independent developers, this is a serious constraint. Because of this constraint, the metatdata sub committee started off with six elements supported by OOo that metadata could be appied to. IBM then came in and asked for eleven more elements having to do with charts and graphs. The OpenOffice crew decided they could support this, so in they went. Then an interesting question was posed, "How are independent developers supposed to submit elements for metadata consideration?"
Paul Merrell

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

blogs.msdn.com/...odf-pdf-and-xps-in-office.aspx

shared by Paul Merrell on 22 May 08 - Cached
    • Paul Merrell
      Paul Merrell on 22 May 08
       
      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
      Paul Merrell on 22 May 08
       
      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
      Paul Merrell on 22 May 08
       
      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
      Paul Merrell on 22 May 08
       
      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.
  • Paul Merrell on 22 May 08
     
    "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.
Paul Merrell

Gray Matter : Microsoft adds "Save as ODF" to Office 2007 Service Pack 2 - 0 views

blogs.technet.com/...ffice-2007-service-pack-2.aspx

interop microsoft odf strategy

shared by Paul Merrell on 22 May 08 - Cached
  • There are really two central catalysts for these actions. One of these is the feedback we have received from the regulatory environment. There is a high degree of interest in our working with other software vendors to improve information exchange through the use of standardized technologies.
  • In our early testing we are observing that every product implementing these standards has some level of variation from the written spec. If you've been around standards for a while, you'll know this is common, and requires dialog to establish best practices & patterns. This is our reason for joining the OASIS, AIIM and ISO committees,
  • Because ODF side-stepped the compatibility question, we were left to solve (continue solving) that challenge elsewhere; the aversion to dealing with legacy content created a real problem for customers who want to transition to more open file formats.
  • ...1 more annotation...
  • Office 14 will update our support for IS29500. The timing for this might seem strange, but I do hope the rationale is clear. ODF 1.1 is a completed specification. The final version of IS29500 is not published today. While we do support a significant portion of IS29500 already, the BRM changes and other issues raised in public forums will inform us on how to best move forward with IS29500… and it gives me a little time to address the compatibility considerations that will be an important part of any file format related changes in Office.
  • Paul Merrell on 22 May 08
     
    Microsoft's Gray Knowlton on the reasons for the Redmond decision to provide native support for ODF 1.1. But most noteworthy, I think, is Knowlton's statement indicating that Microsoft aims at improving interop through best practices & patterns, i.e., application-level interop initiatives, as opposed to amending the ODF standard to specify conformity requirements essential to achieve interoperability, as required by JTC 1 Directives, international law, and antitrust law. In other words, big vendor negotiations around interop rather than giving software users and independent developers a seat at the table.
Gary Edwards

Is ODF the new RTF or the new .DOC? Can it be both? Do we need either? - O'Reilly Broad... - 0 views

broadcast.oreilly.com/...ocument-file-format-lands.html

odf ooxml html-css-svg

shared by Gary Edwards on 24 Oct 08 - Cached
  • Unless governments and other stakeholders can get beyond the narrow view of documents and interoperability as merely being exchanging data from one similar application to another, and move towards the view that documents and web resources need to be end points on the same interoperable spectrum, we are selling ourselves short. It is here that standards bodies should be more help: but I don't know that they can be unless there is a stronger commitment to supporting each others' visions better. W3C's mission statement is concerned with bringing the web to its full potential, and W3C have traditionally used this to justify shying away from old-fashioned compound file-based issues: the lack of standards for the *SP (JSP, ASP, PHP) class of documents is a symptom of this, and it is notable that much of XML's uptake came because it did take care of practical production issues (i.e. issues pertaining to the document as it existed before being made available as a resource —PIs and entities—and after it had been retrieved—character encodings.) The industry consortia such as ECMA and OASIS are organized around interest groups on particular standards, which makes it easy to fob off discussion of interoperability. And even ISO, where the availability are topic-based working groups with very broad interests should provide a more workable home for this kind of effort, have a strong disinclination to seek out work that involves liaison with other standards groups: satisfying two sets of procedures and fitting in with two sets of deadlines and timetables can be impractical and disenfranchising for volunteers and small-business/academic experts.
  • Gary Edwards on 24 Oct 08
     
    Jon Bosak, who founded the XML and ODF efforts among many other achievements, recently wrote an article concerning the position of ODF, Open XML and PDF Jon's public writings are rare, well-considered and always of interest. As with other Sun-affiliated people in recent times, Jon has been exemplary in that even though he has a side, he does not take sides. I think I can agree with much of what he says, though I would note Don't forget about HTML.
Gary Edwards

Forget file formats. The battle is Sharepoint | The Open Road - The Business and Politi... - 0 views

www.cnet.com/8301-13505_1-9949736-16.html

microsoft oasis odf ooxml sharepoint

shared by Gary Edwards on 22 May 08 - Cached
  • People are agog that Microsoft has announced support for Open Document Format (ODF), but I'm not sure why. This was a foregone conclusion once Microsoft figured out how to move lock-in above the file level to the content network. In other words, to Sharepoint. Microsoft has been hell-bent on getting enterprises to dump content into its proprietary Sharepoint repository, calling it the next Windows operating system. I call it the future of Microsoft lock-in.
Paul Merrell

Patrick Durusau on ODF and interoperability - 0 views

lists.oasis-open.org/...msg00005.html

durusau interop interop myth sources odf

shared by Paul Merrell on 05 Jun 08 - Cached
  • Interoperability is one of the primary reasons why I like XML in general and ODF in particular.
Paul Merrell

What to do now - Rick Jelliffe - 0 views

www.oreillynet.com/...what_to_do_now.html

harmonization jelliffe odf ooxml

shared by Paul Merrell on 30 May 08 - Cached
  • Now that ODF and OOXML are both set to be on the ISO/IEC books, it is useful to consider what the next productive steps are. For genuine ODF Supporters who are concerned that ODF has languished a little out of the limelight during 2007, there are a lot of useful things to be done. You don’t even need to join the OASIS groups or your local National Body or SC34 to begin. I suggest here are some things that will help the ODF effort coming into ODF 1.2.
Paul Merrell

untitled - 0 views

www.dpawson.co.uk/...090612.html

ODF specificity quality testability

shared by Paul Merrell on 18 Jun 09 - Cached
  • Most (quality) specifications provide clear instructions using those magic words SHALL, SHALL NOT, and MAY where those words have a defined meaning for an implementor. Paragraphs are clearly identified as either normative or informative. That way an implementor knows what they must and may implement to claim conformance against a specification. This approach has been well established over time as a sensible way for spec writers and implementors to work
  • Most (quality) specifications provide clear instructions using those magic words SHALL, SHALL NOT, and MAY where those words have a defined meaning for an implementor. Paragraphs are clearly identified as either normative or informative. That way an implementor knows what they must and may implement to claim conformance against a specification. This approach has been well established over time as a sensible way for spec writers and implementors to work That is the way quality specifications are written. For example, ISO/IEC's JTC 1 Directives (link to PDF) requires that international standards designed for interoperability "specify clearly and unambiguously the conformity requirements that are essential to achieve the interoperability." With that clarity, conformance is testable and can provide confidence of interoperability. A suite of tests may be developed and applied to an implementation to determine which tests pass, which fail, and hence arrive at an objective pronouncement on conformance of an implementation against the entirety of the specification.
  • In a quality specification, it should be feasible to select a normative paragraph, identify a conformance test for it, and make a clear statement that this test proves that an implementation meets (or fails to meet) that requirement. Call it a test plan: define the tests (test specification), define the expected set of results, and define what constitutes a "pass" of each test that establishes conformance. The plan then provides the matrix of test spec against requirement. Simple.
  • ...4 more annotations...
  • Rob Weir of IBM chaired (apology for the misuse of that last word) the formation list and then simply announced what the charter would be rather than seeking consensus among the list participants. As part of this process before that charter was produced and while I still naively believed that consensus was a goal, I sat down with ODF 1.1 and did a paragraph-by-paragraph review for testability. The numbers were quite revealing. I completely reviewed only the first four major sections and found very few clear requirements. The majority were mere statements with no normative language used to identify what was required or optional. Implementors would have to make their own interpretation.
  • It's ironic that the chair viewed as good news the fact that there were far fewer testable paragraphs than he had predicted. But his prediction of 10,000 test cases is probably far closer to how many testable paragraphs there should be; my counts were actually bad news.
  • All of the above leads to the interesting question of just how the chair expects to accomplish much that is useful in regard to ODF conformance testing before the specification is amended to tighten up the language and add clear requirements. The syntax conformity is already handled by validation against the schema, but the semantics are woefully under-specified.
  • Summary: ODF 1.1 isn't verifiable as a specification. From a fairly cursory review of the latest draft, ODF 1.2 will follow the same path. With OASIS now being more demanding regarding conformance requirements on every specification and with ISO/IEC taking a closer interest in liaison with the ODF TC, I find it hard to see how the ODF TC co-chairs can maintain this view toward verification.
Graham Perrin

Doug Mahugh : 1 + 2 = 1? - 0 views

blogs.msdn.com/...1-2-1.aspx

shared by Graham Perrin on 13 May 09 - Cached
  • five prioritized guiding principles for Office’s ODF implementation
  • When Will Office Support OpenFormula?
  • nobody knows yet when ODF 1.2 will be published as an OASIS or ISO standard
  • ...4 more annotations...
  • risk that the results might not be the same
  • Open XML / ODF Translator Add-Ins for Office can be used with Office 2007 SP2
  • Sun ODF Plugin
  • apparently works with SP2
« First ‹ Previous 101 - 117 of 117
Showing 20▼ items per page