Skip to main content

Home/ Document Wars/ Group items tagged utility

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Q&A: Nicholas Carr on the big switch to utility computing - 0 views

www.computerworld.com/...article.do

carr cloud switch utility web-platform

shared by Gary Edwards on 25 Jan 08 - Cached
  • I think we’re at the early stages of a fundamental shift in the nature of computing, which is going from something that people and businesses had to supply locally, through their own machines and their own installed software, to much more of a utility model where a lot of the computer functions we depend on are supplied from big, central stations, big central utilities over the Internet.
Gary Edwards

(WO/1995/013585) COMPOUND DOCUMENT FRAMEWORK - 0 views

www.wipo.int/...wo.jsp

cdf css xhtml

shared by Gary Edwards on 11 Jan 08 - Cached
  • Summary of the Invention It is an. object of the present invention to provide a document processing system in which object-oriented frameworks are utilized to implement particular document processing techniques, including an object-oriented compound document system. These and other objects of the present invention are realized by a document framework which supports at the system level a variety of compound document processing functions. The framework provides system level support of collaboration, linking, eternal undo, and content based retrieval. These and other objects are carried out by system level support of document changes, annotation through model and linking, anchors, model hierarchies, enhanced copy and pasting, command objects, and a generic retrieval framework.
Gary Edwards

Standard or Not, OOXML Has a Lot Going for It | Redmond Developer News - Desmond - 0 views

reddevnews.com/...weblog.aspx

burtongroup cdf css desmond odf okelly ooxml opendocument w3c xhtml

shared by Gary Edwards on 20 Jan 08 - Cached
  • Ultimately, O'Kelly said it best in his report: "The relative success of ODF and OOXML, in any case, will be determined more by its utility and which community effectively exploits W3C standards than it will by one or the other more effectively navigating through ISO standards procedures."
Gary Edwards

Microsoft Hit By U.S. DOT Ban On Windows Vista, Explorer 7, and Office 2007 - Technolog... - 0 views

www.informationweek.com/...showArticle.jhtml

exchange/sharepoint government msoffice odf opendocument standards vista vistachain vistastack

shared by Gary Edwards on 12 Dec 07 - Cached
  • »  E-Mail »  Print »  Discuss »  Write To Editor late last year -- can be resolved. "We have more confidence in Microsoft than we would have 10 years ago," says Schmidt. "But it always makes sense to look at the security implications, the value back to the customer, and those kind of issues." The DOT's ban on Vista, Internet Explorer 7, and Office 2007 applies to 15,000 computer users at DOT proper who are currently running the Windows XP Professional operating system. The memo indicates that a similar ban is in effect at the Federal Aviation Administration, which has 45,000 desktop users. Compatibility with existing applications appears to be the Transportation Department's major concern. According to a separate memo, a number of key software applications and utilities in use in various branches of the department aren't Vista compatible. Among them are Aspen 2.8.1, ISS 2.11, ProVu 3.1.1, and Capri 6.5, according to a memo issued by staffers at the DOT's Federal Motor Carrier Safety Administration. Any prolonged ban on new Microsoft technologies by the federal government could have a significant impact on the software maker's bottom line, as Microsoft sells millions of dollars in software to the feds annually. http://as.cmpnet.com/event.ng/Type=count&ClientType=2&AdID=125682&FlightID=75634&TargetID=2625&SiteID=222&AffiliateID=283&EntityDefResetFlag=0&Segments=1411,3108,3448,11291,12119&Targets=2625,2878,7904,8579&Values=34,46,51,63,77,87,91,102,140,222,227,283,442,646,656,1184,1255,1311,1405,1431,1716,1767,1785,1798,1925,1945,1970,2217,2299,2310,2326,2352,2678,2727,2767,2862,2942,3140,3347,3632,3636,3638,3890,3904,4080,448
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      DOT chief technology officer Tim Schmidt DOT's CIO Daniel Mintz Federal Department of Transportation
  • Gary Edwards on 12 Dec 07
     
    Whoa, those government desktops add up quickly.  This Vista ban will immediately effect over 50,000 desktops, with tens of thousands more possibly impacted by the IE 7.0 ban.  The MS Exchange/SharePoint Hub juggernaut is based on IE 7.0, which is not available for Windows 2000 - MSOffice 2000 desktops.

    Lack of Vista Stack compatibility with non Microsoft application is given as the reason for the ban.  But notice the "alternatives" to Vista mentioned; Novel SuSE and Apple Mac.  What kind of interop - compatibility do they offer?  My guess is ZERO!

    The reality is that the DOT is trapped.  My advice would be stay exactly where they are, keeping the current MSOffice desktop installs running.  Then, install the Foundation's daVinci ODF plugin for MSOffice. 

    This will insure that Windows OS and  MSOffice bound business processes can continue to function without disruption.  Win32 APi based applications like those mentioned in the article can continue.  Critical day to day business processes, workgroup and workflow related activities can continue without disruption or costly re engineering demanded by a cross platform port.

    What daVinci doe sdo is move the iron triangle that binds Windows-MSOffice applications to business processes and documents, to an ODF footing.  Once on a ODF footing, the government can push forward with the same kind of workgroup - workflow - intelligent docuemnt - collaborative computing advnaces that the Vista Stack was designed to deliver.  Only this push will involve the highly competitive "the customer is sovereign" environment of ODF ready desktop, server, device and Web 2.0 systems.  End of Redmond lock-in.  End of the costly iron triangle and the force march upgrade treadmill that so enriches Microsoft.

    So what's not to like?  We can do this.
    ~ge~

    http://docs.google.com/View?docID=dghfk5w9_20d2x6rf&revi
Gary Edwards

Brian Jones: Open XML Formats : Specifying the document settings - 0 views

blogs.msdn.com/...ing-the-document-settings.aspx

contradictions ecma eooxml inconsistencies interoperability iso microsoft oasis odf openxml

shared by Gary Edwards on 12 Dec 07 - Cached
  • # re: Specifying the document settings @ Thursday, January 11, 2007 5:11 AM Brian, the fact that you are encouraging people not to use those compatibility flags does not matter at all here. There obviously will be documents with those flags turned on, right? Otherwise you wouldn't have put this in the standard. So it's just a corner case, but still: This means ONLY your office suite will be able to display those documents correctly, even if a competing program implemented the whole specification. Why? Because you didn't specify how those flags affect the display of the document (a hell of a specification you have there...). I still haven't seen any answer to this valid criticism. It's a competitive advantage for Microsoft since the standard is incomplete and your company is the only one that has the missing parts. - Stephan Stephan Jaensch
  • Gary Edwards on 12 Dec 07
     
    Nice catch by Stephan Jaensch.  He caught Brian Jones trying wriggle out of corner Rob Weir has trapped the mighty Microsoft Blogmeister in.  The last line of Stephan's question to Brian Jones says it all; the incompleteness and undocumented aspects of the EOOXML specification give Microsoft an incredibly unfair competitive advantage regarding the billions of binary MSOffice documents in circulation and vital to critical day to day business operations the world over. 

    The quote from Stephan:  "I still haven't seen any answer to this valid criticism. It's a competitive advantage for Microsoft since the standard is incomplete and your company is the only one that has the missing parts."

    The response from Brian?  We're waiting.  We've been waiting.  With each passing day the EOOXMl specification looks more like a monopolist endagered species protection order than the open standard Microsoft is trying to palm it off as.

1 - 5 of 5
Showing 20▼ items per page