Skip to main content

Home/ OpenDocument/ Group items tagged html

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

XForms with Google Widgets (GTW) - IBM developerWorks : XML : - 0 views

www.ibm.com/...libraryview.jsp

gwt xforms

shared by Gary Edwards on 12 Oct 07 - Cached
  • Integrate XForms with the Google Web Toolkit, Part 3: Using GWT to create XFormsThis four-part series demonstrates how to use the Google Web Toolkit (GWT) and XForms together to create a dynamic Web application. Part 1 looked at the two technologies and how both had JavaScript underpinnings. Part 2 shows how to create a small application with two pages. One page uses GWT to show a list of artists managed by a record company. The second page uses XForms to display the albums recorded by a particular artist. Part 3 uses GWT and XForms on the same page. See how to take advantage of each technology's bindings to JavaScript by using JavaScript to achieve interactivity between GWT and XForms.
Gary Edwards

Is Open Source Dying? - 0 views

www.eweek.com/...0,1895,2148866,00.asp

iso linux odf ooxml open-source xml

shared by Gary Edwards on 21 Jun 07 - Cached
  • But behind the scenes, things are not quite as rosy. The Commonwealth of Massachusetts, which lived up to its left-leaning credentials (didn't Microsoft CEO Steve Ballmer famously upbraid open-source proponents for being Communists?) broke important ground by mandating that state agencies switch to open-source platforms. There's just one problem: They can't seem to manage the transition. Sources close to the situation tell me that former state CIO Peter Quinn's resignation happened at least in part because of delaying tactics by vendors who publicly support open source but do their best to scuttle it behind the scenes.
  • Gary Edwards on 21 Jun 07
     
    Interesting topic which i've covered more fully with the OpenStack Blog : Connecting the Dots
Gary Edwards

InfoWorld Tech Watch | InfoWorld | Messaging standard OK'd for Web services | June 21, ... - 0 views

weblog.infoworld.com/...012609.html

shared by Gary Edwards on 21 Jun 07 - Cached
  • OASIS considers WS-ReliableMessaging critical for SOA, in that it can handle a variety of SOA requirements. WS-ReliableMessaging can be extended to enable integration with capabilities such as security. SOAP binding for interoperability is included. WS-ReliableMessaging is part of a series of Web services specifications dubbed WS-* that have been championed by companies such as Microsoft.
  • Gary Edwards on 21 Jun 07
     
    Check out the comments below this article.  There are links to Ian Foster of Globus and to the Marbux license disseration posted with the OpenDocument Foundation's NO VOTE at OASIS.
Gary Edwards

Ballmer threatens Linux and open source with patents again - Flock - 0 views

www.linux-watch.com/...NS3513440381.html

shared by Gary Edwards on 10 Oct 07 - Cached
  • To handle IP conflicts between open source and proprietary software organizations, Ballmer wants to see what he calls "an intellectual property interoperability framework between the two worlds." He did not give any specifics on what such a framework would look like.
  • Gary Edwards on 10 Oct 07
     
    You've got to be kidding me!  Balmer wants to establish "an intellectual property interoperability framework" that open source communities would honor?  I think that's called "open standards" implemented according to the ISO, W3C and International Trade Agreement Interoperability conformance requirements.

    Why doesn't Microsoft start with an honest effort to comply with where the rest of the world has long been?

    ~ge~

Gary Edwards

Taking an incremental approach to SOA | Avoiding costly "rip out an dreplace" - 0 views

news.zdnet.com/2424-9595_22-167085.html

cdf convergence davinci interoperability soa

shared by Gary Edwards on 28 Sep 07 - Cached
  • Current implementation issues One of the biggest hurdles to implementing a realistic SOA is understanding what the business units and end users are doing today. This understanding is critical to the success of any SOA project since the new services must match exactly what each business unit is doing today. Neglecting these business processes and replacing them with individual services will most likely lead to hundreds of non-used services and frustrated business units.
  • Gary Edwards on 28 Sep 07
     
    Excellent article from NetManage's Archie Roboostoff.  He lays out all the difficulties and mistakes experienced with SOA efforts.
Gary Edwards

Open Malaysia: Rick Jelliffe - myths debunked? - 0 views

www.openmalaysiablog.com/...rick_jelliffe_m.html

shared by Gary Edwards on 17 Jun 07 - Cached
  • Additionally, ODF was not ratified with SVG, MathML, XLink, Zip and other W3C standards all together at the same time. Instead the prior W3C standards were already well established and approved in their own right and in their own time with the relevant experts of their specific domains vetting it. MSOOXML also incorporates proposed "standards" which failed in the marketplace and now is offered a "backdoor" to standardisation process by piggy backing this nebulous specification. (See VML vs SVG, and MathML vs Microsoft Office MathML) So there is a myth being built that ODF and its constituent parts are just as large as MSOOXML, and therefore MSOOXML is OK. I for one would rather MSOOXML be even larger; to cater for unknown tags like "lineWrapLikeWord6" or a Macro specification. However what troubles me is that the special relationship between Ecma and ISO should be abused with the fast tracking of this large specification.
  • Gary Edwards on 17 Jun 07
     
    Yoon Kit brings up an interesting point about the ISO consideration of MSOOXML (Ecma 376);  ISO approval of MSOOXML would backdoor a good many MS proprietary technologies that compete directly with W3C XML standards.

    YK gives the example of MS VML, which competes with the W3C SVG standard used by ODF.  He could have also cited that legacy versions of MSOffice (98-2003) make use of VML as the default graphic format, while MSOffice 2003 9with XML plugin) and MSOffice 2007 (by default) implements DrawingML as the replacement for VML. 

    So, would ISO approval of Ecma 376 backdoor VML and DrawingML in as "standards"?  Or MSOffice MathML?   One has to wonder since they are essential to MSOOXML.

Gary Edwards

Commercializing Interoperability -- gary_edwards's comment on "Linux leaders plot count... - 0 views

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

shared by Gary Edwards on 15 Jun 07 - Cached
  • Is Microsoft commercializing "interoperability"? Is interoperability through privileged access to the interop API's now a strategic asset to be traded with partners in crime?
  • Gary Edwards on 15 Jun 07
     
    The first post in the ZDNet series discussing the many deals Microsoft is cutting with prominent LiNUX vendors.  My point is that interoperability plays a prominent role in each of these deals, and, the deals also involve partners supporting Microsoft directed interop between OpenOfficeXML and OpenDocument.  Coincidence? 

    I think not!

Gary Edwards

Singing Kumbaya -- gary_edwards's comment on "Linux leaders plot counterattack on Micro... - 0 views

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

shared by Gary Edwards on 15 Jun 07 - Cached
  • have you noticed that IBM is softening their position on "harmonization"? There are a number of events to consider that might have influenced this change in tone:
  • Gary Edwards on 15 Jun 07
     
    More in that same "LiNUX Leaders plot counter attack on Microsoft" thread at ZDNet.  This time the issue is what has caused IBM to sing a differnet tune?  The tune known as "harmoniation".
Gary Edwards

Billions of Legacy Binary Documents -- gary_edwards's comment on "Linux leaders pl... - 0 views

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

ecma-376 iso microsoft odf officeopenxml ooxml opendocument xml

shared by Gary Edwards on 19 Jun 07 - Cached
  • The point is that ODF has to be flexible enough so that the demand side of the equation can successfully convert their MSOffice documents to ODF. More important than simple one-way conversion is the need for high fidelity round trip conversion.
  • Gary Edwards on 19 Jun 07
     
    This is a follow up comment to a question cocerning my previous post, "commercialization of interoperability".  The question from "mosborne" is as follows:

    A different viewI'm not on the ODF TC, but I have followed its evolution through the information publicly available at Oasis.

    My outside view of some of the various interoperability discussions you mention is different than yours. I saw a resistance to adoption of features if the sole reason was because OOXML did it that way. The dissenting members wanted a more substantial reason, not simply to add OOXML "features" to ODF.

    If the goal is to simply make ODF like OOXML, then what is the point? You would have conceded all control to Microsoft since they have effective control of OOXML.It's an interesting question, but not well informed.  The threads at OASIS ODF having to do with interoperability are focused on efforts to have our cake and eat it too. 

    The List Enhancement Proposal thread played out over a six month period.  And yes, it is true that Sun fought the Novell proposal because they felt new and innovative features for OpenOffice/StarOffice were more important than the interoperability CIO's and IT departments are demanding.   But that misses the more important point that Novell was able to craft their interoperability proposal exactly so that the precious advanced feature sets of applications that command les sthan 1% marketshare would be accommodated.

    What Sun and most others on the ODF TC don't get is that the markets have no use for these new and innovative feature sets unless and until they can transition their documents and business processes out of MSOffice.  If workgroup bound end users can't do that first, it won't matter how
Gary Edwards

PlexNex: Achieving Openness - 0 views

fussnotes.typepad.com/...achieving_openn.html

ecma-376 iso microsoft odf officeopenxml ooxml opendocument xml

shared by Gary Edwards on 19 Jun 07 - Cached
  • "ECMA 376" is a set of file formats subject to ECMA and now to ISO. "Office 2007" is a set of file formats which extend "ECMA 376" file formats. Office 2007 file formats are undocumented per se. ECMA 376 are. ECMA 376 file formats are documented but only at a syntactic level. To realize the true meaning of every single attribute is to realize that the documentation is more like 600,000 pages, not 6,000. Of particular difficulty is to keep some kind of control over the virtually infinite combinations of such attributes. Quick analysis of the underlying schemas reveals that simple concepts such as text formatting is expressed in no less than 6 different and incompatible ways. This leads to thinking that the file formats were only designed to comply with existing legacy formats that themselves are the result of 15 years of inside/outside library aggregation (some of the libraries were bought from non-Microsoft vendors). In fact, the truth is, ask any reverse engineer third-party who worked with legacy formats, they'll tell you Microsoft essentially added angle brackets around the binary serialization in legacy formats. This makes for a very cool XML-based file format, not an international standard.
  • Gary Edwards on 19 Jun 07
     
    Whoa, Stepen Rodriguez knocks this one out of the park.  What an impressive dissembling of MS OfficeOpenXML and it's poor sister subset, Ecma 376.  Incredible. 
Gary Edwards

The OpenChange Project: reader comment from Gary Edwards - CNET News.com - Flock - 0 views

www.news.com/5208-13580_3-0.html

exchange openchange openstack

shared by Gary Edwards on 20 Sep 07 - Cached
  • Unfortunately much of the world is unaware of the OpenChange Project launched by members of the SAMBA Community. OpenChange is a young project, but there are working solutions already. And everything is Open Source Software portable across multiple operating systems.
  • Gary Edwards on 20 Sep 07
     
    Comment to article about Microsoft Exchange and OSS
Gary Edwards

Microsoft and Its Rivals Take 'Office' Politics Global - WSJ.com - 1 views

online.wsj.com/...SB118843789318613086.html

eu odf ooxml

shared by Gary Edwards on 20 Sep 07 - Cached
  • Gary Edwards on 20 Sep 07
     
    Another article from Charles Forelle of WSJ on Microsoft's efforts to corrupt the international standards process
Gary Edwards

ODF tied to OpenOffice? Say it isn't so! -- gary.edwards's comment on "IBM Symphony fal... - 0 views

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

ibm lotus-symphony odf ooxml openoffice

shared by Gary Edwards on 19 Sep 07 - Cached
  • Gary Edwards on 19 Sep 07
     
    Good discussion on IBM's recent release of OpenOffice as Lotus Symphony. OpenOffice Community Marketing Lead, John McCreesh, steps into it though with an errant quote. Sadly, i have to take him to task.
Gary Edwards

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

www.microsoft-watch.com/...fts_stunning_court_defeat.html

anti-trust cdf interoperability microsoft odf ooxml

shared by Gary Edwards on 17 Sep 07 - Cached
  • "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
      Gary Edwards on 17 Sep 07
       
      I wonder if this is correct? My understanding is that the California Group will be brushed aside by the Feds?
  • Gary Edwards on 17 Sep 07
     
    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

INTERVIEW: Craig Mundie -- Microsoft's technology chief, taking over from Bill Gates - 0 views

www.apcmag.com/...logy_chief_taking_over_from_bi

cdf odf officeopenxml ooxml opendocument

shared by Gary Edwards on 15 Sep 07 - Cached
  • In this exclusive interview with APC, Mundie says the notion of all software delivered entirely through the web browser is now widely recognised as being 'popular mythology'. He also stakes the claim that Google's existence and success was contingent on Microsoft creating Windows. He talks about what's coming down the pipeline for future versions of Windows, and his belief that Windows can get still more market share than it has today. He also discusses the issues around the recent controversy over the Office Open XML file format.
  • So Vista is in its diffusion cycle and until there is enough of it out there, you won't really see the developer community come across.
    • Gary Edwards
      Gary Edwards on 15 Sep 07
       
      Uh, the diffusion we really should be focused on involves the OOXML plug-in for MSOffice, IE 7.0, MSOffice 2007, and the Exchange/SharePoint Hub. 

      The Exchange/SahrePoint juggernaught is now at 65% marketshare, with Apache servers in noticeable decline.

      So it seems the improtant "diffusion" is going forward nicely.  The exploitation of the E/S Hub has also started, and here the Microsoft deelopers have an uncahllenged advantage.  Most of the business processes being migrated to the E/S Hub are coming off the MSOffice bound desktop.  Outsiders to the MS Stack do not have the requisite access to the internals that drive these MSOffice bound business processes, so they have little hope of getting into the "exploitation" cycle.

      This aspect was on full display at the recent Office 2.0 Conference in San Francisco.  The only way a O2 provider can position their service as a collaborative addon to existing business processes is to have some higher level of interop-integration into those processes beyond basic conversion to HTML.

      Most O2 operatives struggle to convince the market that an existing business process can be enhanced by stepping outside the process and putting the collaboration value elsewhere.  While this approach is disruptive and unfriendly, it tends to work until a more integrated, more interoperable coolaboration value becomes available.

      And that's the problem with O2.  Everyone is excited over the new collaboration possibilities, but the money is with the integration of collaborative computing into existing business processes.  This is a near impossible barrier for non Microsoft shops and would be competitors.  If you're Microsoft though, and you control existing formats, applications and processes, the collaboration stuff is simple value added on.  It's all low hanging fruit that Microsoft can get paid to deliver while O2 players struggle to f
  • So far, we have delivered about 60 million copies. That would represent about six per cent of the global Windows install base. So it has probably got to get up another few percentage points before you will start to see a big migration of the developer community.
    • Gary Edwards
      Gary Edwards on 15 Sep 07
       
      What is he talking about? Does a developer write to Vista? Or do they write to MS Stack ready .NET - OOXML-Smart Documents, XAML, Silverlight stuff?
  • ...2 more annotations...
  • Rather, what will happen is that you'll have, a seamless integration of locally running software in increasingly powerful client devices (not just desktops) and a set of services that work in conjunction with that. A lot of what we are doing with the Live platform not only allows us to provide the service component for our parts, but also gives the abilities for the developer community to perfect their composite applications and get them deployed at scale.
    • Gary Edwards
      Gary Edwards on 15 Sep 07
       
      Bear in mind that these "service components" are proprietary, and represent the only way to connect MS clients to the rest of the MS STack of applications.
  • Microsoft's business is not to control the platform per se, but in fact to allow it to be exploited by the world's developers. The fact that we have it out there gives us a good business, but in some ways it doesn't give us an advantage over any of the other developers in terms of being able to utilise it.
    • Gary Edwards
      Gary Edwards on 15 Sep 07
       
      Oh right! The anti trust restrictions will not be lifted until November. Have to be careful here. But how is it Craig that non Microsoft devlopers and service providers will be albe to access and interoperate with important "service components"?
  • Gary Edwards on 15 Sep 07
     
    Great inteview, i'll comment as i make my way down the page.  Hopefully others will do the same.
Gary Edwards

Antitrust: Commission imposes € 899 million penalty on Microsoft for non-comp... - 0 views

europa.eu/...pressReleasesAction.do

anti-trust eu microsoft ooxml openxml

shared by Gary Edwards on 07 Mar 08 - Cached
  • Antitrust: Commission imposes € 899 million penalty on Microsoft for non-compliance with March 2004 Decision
Gary Edwards

Compound Document Formats Group Charter - 0 views

www.w3.org/...charter.html

cdf da-vinci foundation opendocument w3c

shared by Gary Edwards on 07 Mar 08 - Cached
  • be widely implementable in browsers and authoring tools
Gary Edwards

Harmonizing ODF and OOXML using NameSpaces | Tim Bray's Thought Experiment - 0 views

www.tbray.org/...Office-XML

bray florian-reuter namespaces odf ooxml opendocument openxml

shared by Gary Edwards on 09 Feb 08 - Cached
  • First, what if Microsoft really is doing the right thing? Second, how can we avoid having two incompatible file formats? [Update: There’s been a lot of reaction to this piece, and I addressed some of those points here.]
  • On the technology side, the two formats are really more alike than they are different. But, there are differences: O12X’s design center, Microsoft has said repeatedly, is capturing the exact semantics of the billions of existing Microsoft Office documents. ODF’s design center is general-purpose reusability, and leveraging existing standards like SVG and MathML and so on.
  • The capabilities of ODF and O12X are essentially identical for all this basic stuff. So why in the flaming hell does the world need two incompatible formats to express it? The answer, obviously, is, “it doesn’t”.
  • ...1 more annotation...
  • The ideal outcome would be a common shared office-XML dialect for the basics—and it should be ODF (or a subset), since that’s been designed and debugged—then another extended vocabulary to support Microsoft features , whether they’re cool new whizzy features or mouldy old legacy features (XML Namespaces are designed to support exactly this kind of thing). That way, if you stayed with the basic stuff you’d never need to worry about software lock-in; the difference between portable and proprietary would be crystal-clear. And, for the basic stuff that everybody uses, there’d be only one set of tags. This outcome is technically feasible. Who could possibly be against it?
  • Gary Edwards on 09 Feb 08
     
    Tim Bray suggests using namespaces to brdige the comatibility gap between ODF and OOXML.
  • Gary Edwards on 09 Feb 08
     
    This log is connected to a recent post from Florian Reuter, XML Namespaces are designed to support exactly this kind of thing ...
Gary Edwards

Wizard of ODF: Proposal to amend TC charter, re interoperability with non-conformant ap - 0 views

www.oasis-open.org/...msg00022.html

harmonization interop interoperability oasis odf ooxml opendocument

shared by Gary Edwards on 07 Mar 08 - Cached
  • 7. it must provide all feasible functionality required to suppport full fidelity conversions from and to existing office document binary file formats.
Gary Edwards

Wizard of ODF: The Foundation on Interop and the List Proposal Vote Deadline - 0 views

www.oasis-open.org/...msg00040.html

anti-trust ecis foundation odf ooxml opendocument openxml

shared by Gary Edwards on 09 Feb 08 - Cached
  • Oh, my. Both IBM and Sun voted for the proposal that broke the Foundation's plugin that was going to add full-fidelity native ODF file support to Microsoft Office. So it's sounding to me like at least two of the TC members who voted for the Sun/KOffice proposal didn't check in with the ECIS lawyer before they broke interoperability with Microsoft Office. Do you think Microsoft won't use this evidence in the DG Competition antitrust proceeding, Michael? Let's see, you guys are prosecuting Microsoft for not supporting ODF in Microsoft Office while you block Microsoft Office from supporting ODF. Yeah, I think DG Competition is going to hear about this one from Microsoft. They'll probably hear about what you said about compatibility being a trade off too. Oh, yeah. Microsoft's lawyers are going to love this. Look at the ECIS public statement about interoperability's importance.
  • Gary Edwards on 09 Feb 08
     
    If ever there was a discussion thread of consequence at the OASIS ODF TC, this is it. This is where the ODF interoperability nightmare burst into the daylight of a showdown vote. The interop issues were clear. OpenDocument TC members voted between interoperability and/or application specific innovation. Application specific innovation trumped interoperability. Again. And wha ta sad day it was. The thing is, the recent ECIS antit trust action against Microsoft comes at the request of IBM and Sun. They allege that Microsoft is violating standards requirements for interoeprability, and has launched a series of corrupt activities to push through a non interoperable standard. They are right. Microsoft is guilty. The problem is that Microsof tcan easily point to Sun and IBM activities at OASIS ODF, and make the same allegation! Using this thread as evidence! Furthermore, this thread is evidence that if Microsoft had tried to implement ODF, their efforts to establish interop would have been met with the same response from IBM and Sun that the OpenDocument Foundation recieved. Or so they could argue. Houston, we have a problem. IBM and Sun could have fixed the ODF interop problems at any time during the past five years. Yet, the world is waiting. Meanwhile, this willfull negligence and lack of desire to address pressing market needs for full interop has served to hold the door open for OOXML. And now these negligent acts llook to be the basis of a Microsoft counter claim. Oh well ..
« First ‹ Previous 81 - 100 of 191 Next › Last »
Showing 20▼ items per page