Skip to main content

Home/ In-the-Clouds-with-SOA-XML-and-the-Open-Web/ Group items tagged 2008

Rss Feed Group items tagged

Paul Merrell

Microsoft releases Office 2008 SP1, says VBA to make return - 0 views

  •  
    ""The response has been amazing -- since we launched in January, the velocity of sales for Office 2008 is nearly three times what we saw after the launch of Office 2004," said Craig Eisler, general manager of the Mac BU at Microsoft. ... As part of its announcements Tuesday, the Mac BU also said it intends to bring VBA-language support back to the next version of Office for Mac, but offered no timeframe for the update." According to the article, sales for MS Office 2008 for the Mac have tripled what MS Office 2004 accomplished. There's a bit of a wookie hidden in the claim because new Mac sales have far more than tripled since the comparable period following the release of Office 2004. So even though Microsoft Office gross sales on the Mac have increased from the period compared, there is a strong appearance that Microsoft is losing market share on the Mac, something I would be concerned about were I Steve Ballmer, not something to celebrate. Also note that the lack of VBA support in Office 2008 plus a few other Microsoft moves dealt Office for the Mac out of the Micrsooft cloud. Why Redmond might suddenly have a change of heart and deal Apple into the MS Cloud afer all is something not explained. But it is somewhat plausible that Microsoft feels the need to change its mind on VBA because it is losing market share on the Mac. My assessment? The VBA announcement is vaporware until proved otherwise, designed to slow the adoption of competing office software on the Mac, which makes the rapidly expanding OS X stack, e.g., now able to run Linux apps, a bigger threat to Windows. Microsoft is obviously losing Office market share on the Mac platform and OS X is eating Windows market share. Time for vaporware.
Paul Merrell

SEC Proposes standardizing financial reporting on XBRL --- Farewell Edgar - 0 views

  •  
    "Washington, D.C., May 14, 2008 - The Securities and Exchange Commission today voted unanimously to formally propose using new technology to get important information to investors faster, more reliably, and at a lower cost. At the center of the SEC proposal is "interactive data" - computer "tags" similar in function to bar codes used to identify groceries and shipped packages. The interactive data tags uniquely identify individual items in a company's financial statement so they can be easily searched on the Internet, downloaded into spreadsheets, reorganized in databases, and put to any number of other comparative and analytical uses by investors, analysts, and journalists. The proposed rule would require all U.S. companies to provide financial information using interactive data beginning next year for the largest companies, and within three years for all public companies." Note that reports must currently be submitted in the Edgar format, with WordPerfect the only major word processor writing directly to Edgar. See also http://www.xbrl.org/faq.aspx (.) The proposal is potentially susceptible to legal challenge at the WTO per terms of the Agreement on Technical Barriers to Trade and the Agrement on Government Procurement. If approved, XBRL would constitute a "technical regulation" within the meaning of the ATBT and a "technical specification" within the meaning of the AGP. That raises the issue of whether XBRL constitutes an unnecessary obstacle to international trade within the meaning of those treaties. This is the kind of stuff that is supposed to get sorted out by joint creation of an international standard by ATBT member nations. But both treaties are very poorly implemented in the U.S.
Gary Edwards

Live Mesh as the next information bus :: Incremental Blogger » Blog Archive » - 0 views

  • Live Mesh as the next information bus Steve Gillmor sees a bright future for Microsoft’s latest initiative: Live Mesh.
  •  
    More review of the Gilmopre Gang interview
Gary Edwards

Microsoft SOA Products & Investments: Oslo - 0 views

  • Microsoft is investing some of the top engineering talent at the company to make two key investments: Deliver a world class SOA platform across client, server, and cloud. Microsoft has been a thought leader in Web services and SOA technologies since the very beginning and has delivered industry leading technologies such as the Windows Communication Foundation and BizTalk Server. Deliver a world class and mainstream modeling platform that helps the roles of IT collaborate and enables better integration between IT and the business. The modeling platform enables higher level descriptions, so called declarative descriptions, of the application.
  •  
    SOA platform that extends across client, server and cloud. Scary stuff that preceeded the Live Mesh - Silverlight announcement at Web 2.0 (2008)
Gary Edwards

Google Search To Surpass Size of Microsoft Windows in 2009 - Silicon Alley Insider - 0 views

  • Google's search business will pass Microsoft's Windows business by early next year (at the latest). Good thing Microsoft has another huge, wildly profitable monopoly: Office. Add that to the calculation, and Microsoft can breathe easy for a few more years: GOOGLE SEARCH vs MICROSOFT WINDOWS + OFFICEQuarterly Revenue Q3 2006-Q1 2008 Of course, Google's visible in that Microsoft rearview mirror, too--especially now that it offers a product that is directly competitive with Office. And then there's the most depressing comparison (from Microsoft's perspective). After 13 years of heavy investment, frequent doubling down, and--until recently--a browser monopoly, here's how Microsoft's online business is doing relative to Google's search business. Remember: Google was founded four years after Microsoft launched its online business, and Microsoft's search business is just a tiny piece of Microsoft Online.
  • The "Windows monopoly+Office monopoly=Microsoft" story was absolutely true 10 years ago, but less so now. 1. It looks as if the "Office" revenue figures are coming from MSFT's reported revenues in the Business segment. That's not all Office. Based on what they've said at the last few Financial Analyst Meetings, Exchange is approaching $2B/year, SharePoint is about $1B/year, and Dynamics (formerly Microsoft Business Solutions) is more than $1B per year. I also know that Project has been a $1B/year business for a long time (believe it or not), and products such as Comms Server and Visio contribute around $500m/year. Margins on all these products are lower than on Office, but most (not Comms Server) are profitable. 2. In addition to all the non-Office products that compose its Business segment as mentioned above, the Server and Tools business (Windows Server, SQL Server) is profitable (30% margins) and growing revenues average of 15% for the last six years. Not monopoly, but a good business. Look at all these stats together, and seems like they should get out of search and advertising and sell off (or scale back to maintenance mode) most of the consumer online sites, focusing instead on hosted business apps--they're already doing it with Exchange and SharePoint, why not Office? If somebody's going to canniblize their "real" business, it might as well be them.
  •  
    The Henry Blodgett article comparing Google and Microsoft. Excellent source!
  •  
    Blodgett calls Windows a "natural monopoly," a term derived from the science of economics. But the view of Windows as a natural monopoly blinks past more than a few facts: [i] the monopoly at all times was firmly rooted in government-granted monopoly created by copyrights, patents, and trade secrets; [ii] even the 3.x versions depended mightily on antitrust violations involving DR DOS; and [iii] the dependence on antitrust violations to build, maintain, and extend the monopoly continue to this day. I see scant basis for labeling Windows as a "natural monopoly." Economic theory may blink past the antitrust issues on free market principles, but it may not blink past the government grants of monopolies in similar fashion..
Gary Edwards

Is HTML in a Race to the Bottom? A Large-Scale Survey of Open Web Formats - 0 views

  • The "race to the bottom" is a familiar phenomenon that occurs when multiple standards compete for acceptance. In this environment, the most lenient standard usually attracts the greatest support (acceptance, usage, and so on), leading to a competition among standards to be less stringent. This also tends to drive competing standards toward the minimum possible level of quality. One key prerequisite for a race to the bottom is an unregulated market because regulators mandate a minimum acceptable quality for standards and sanction those who don't comply.1,2 In examining current HTML standards, we've come to suspect that a race to the bottom could, in fact, be occurring because so many competing versions of HTML exist. At this time, some nine different versions of HTML (including its successor, XHTML) are supported as W3C standards, with the most up-to-date being XHTML 1.1. Although some versions are very old and lack some of the newer versions' capabilities, others are reasonably contemporaneous. In particular, HTML 4.01 and XHTML 1.0 both have "transitional" and "strict" versions. Clearly, the W3C's intent is to provide a pathway to move from HTML 4.01 to XHTML 1.1, and the transitional versions are steps on that path. It also aims to develop XHTML standards that support device independence (everything from desktops to cell phones), accessibility, and internationalization. As part of this effort, HTML 4.01's presentational elements (used to adjust the appearance of a page for older browsers that don't support style sheets) are eliminated in XHTML 1.1. Our concern is that Web site designers might decline to follow the newer versions' more stringent formatting requirements and will instead keep using transitional versions. To determine if this is likely, we surveyed the top 100,000 most popular Web sites to discover what versions of HTML are in widespread use.
  •  
    What makes the Internet so extraordinary is the interoperability of web ready data, content, media and the incredible sprawl of web applications servicing the volumes of information. The network of networks has become the information system connecting and converging all information systems. The Web is the universal platform of access, exchange and now, collaborative computing. This survey exammines the key issue of future interoperability; Web Document Formats.
  •  
    Excellent link from marbux.
Gary Edwards

XML-Empowered Documents Extend SOA's Connection to People and Processes | BriefingsDire... - 0 views

  • We're going to talk about dynamic documents. That is to say, documents that have form and structure and that are things end-users are very familiar with and have been using for generations, but with a twist. That's the ability to bring content and data, on a dynamic lifecycle basis, in and out of these documents in a managed way. That’s one area.The second area is service-oriented architecture (SOA), the means to automate and reuse assets across multiple application sets and data sets in a large complex organization.We're seeing these two areas come together. Structured documents and the lifecycle around structured authoring tools come together to provide an end-point for the assets and resources managed through an SOA, but also providing a two-way street, where the information and data that comes in through end-users can be reused back in the SOA to combine with other assets for business process benefits.
  • Thus far we’ve been talking about the notion of unstructured content as a target source to SOA-based applications, but you can also think about this from the perspective of the end application itself -- the document as the endpoint, providing a framework for bringing together structured data, transactional data, relational data, as well as unstructured content, into a single document that comes to life.Let me back up and give you a little context on this. You mentioned the various documents that line workers, for example, need to utilize and consume as the basis for their jobs. Documents have unique value. Documents are portable. You can download a document locally, attach it to an email, associate it with a workflow, and share it into a team room. Documents are persistent. They exist over a period of time, and they provide very rich context. They're how you bring together disparate pieces of information into a cohesive context that people can understand.
  •  
    There is a huge productivity jump to be had by sinking data management into the "system"!
  •  
    Dana Gardner transcript of podcast interview with JustSystems and Phil Wainwright. Covers the convergence of the portable XML document model with SOA. It's about time someone out there got it. You know the portable XML document has arrived when analyst finally get it.
Gary Edwards

The Acrobat.com Blog: Welcome to Acrobat.com - Work. Together. Anywhere. - 0 views

  • With Acrobat.com people will not have to sacrifice the quality of their documents or the quality of the user experience in order to work together more efficiently online. The documents look great. They are truly ‘what you see is what you get’ no matter who you are or what computer you are using, including the text, the graphics, and the pages. Finally, the user experience or design of the applications is beautiful, easy to use and getting better all the time. Acrobat.com takes the meaning of rich internet application to the next level by using the Adobe technology platform of Flash, PDF and AIR to create distinctive and compelling software. You can access Acrobat.com while online from almost any browser thanks to the Flash Player or from your desktop via Acrobat.com on AIR. And soon you will be able to access your work via the AIR version of Acrobat.com even while off-line.
  •  
    Adobe's Erik Larson introduces Acrobat.com. His blog comments echo his post in response to an article at ComputerWorld: http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9091678 In the CW article, Guy Creese of the Burton Group holds the line, defending, as expected, the Microsoft alighnment of MSOffice, Exchange and SharePoint.
Gary Edwards

BOOK Offered Or Kept: Digital reading without Epub? | TeleRead: Bring the E-Books Home - 0 views

    • Gary Edwards
       
      .wiki is the native wikiWORD language for MSOffice "editors". It's really AJAX for documents, with HTML+ handlign the "structure", and CSS+ handling the "presentation". We need javascript to perfect the full range of typographical options used by knowledge workers makign their way from MSOffice to the web. BOOK is a good place to start.
  • The structure of a BOOK would look like this: …BOOK/ ……index.html ……images/ ………cover.png ……css/ ………base.css ………skins/ …………modern.css …………classic.css …………nouveau.css ……scripts/ ………prototype.js ………base.js ………extensions.js
  • As for the Javascript, it’s based on the ECMAScript standard, which has evolved into a strongly-typed, object-oriented programming language and is one of the few web “standards” which really is a standard. BOOK authors will welcome the addition of a scripting language, as it is NOT currently supported in the IDPF specifications. In fact, it’s forbidden for .epub reading systems to execute scripts. It’s also forbidden for them to display a file called index.html without first loading and parsing several other files.
  • ...10 more annotations...
    • Gary Edwards
       
      Good point! The IDPF ePUB format does not support javascript! Which makes "BOOK" a better format to target.
  • EPub is an excellent, high-fidelity format for both direct rendering and for user-side conversion to other formats for particular platforms such as very limited resource handheld devices.
  • Jon Noring Says:
  • For BOOKs, it offers true pagination, typesetting, skinnable and collapsible layouts, footers and headers, footnotes as popups, inline text, true footer notes, or endnotes . . . the list goes on. YUI, JQuery, dojo, MooTools, and Prototype are just a few of the frameworks available, and they’ve been addressing these issues for some time now.
  • Javascript is useful mainly for rendering, not bells and whistles. Without Javascript, the non-normalized implementations of CSS out there become useless–you can’t rely on them to produce a consistent rendering of a document. Unfortunately, with CSS3 the rendering game is only going to get more complicated. I don’t advocate executing scripts from epubs, I advocate executing scripts in epub reading systems. Two very different things, as you’re aware.
  • Scripting is *essential* for many digital publishing projects and not understanding it is a major failure of IDPF. Saying that “we will reconsider scripting when adoption of epub grows” is also inadequate, because nobody will wait patiently, but will choose some another platform for their publishing needs, Adobe AIR for example.
  • My criticism of epub is not about details but about its fundamentals. It seems to me that while preparing the spec the most fundamental question was left out of view: what is the right model for digital publication: is it a physical book? Or is it something else? If something else, then what? From my point of view, not a physical book, but a website should be thought as the right model. Why website? - because of the well supported and ubiquitous mix of technologies (html, css, javascript) and because of the workflow (publishing early versions of the publication on the website for gathering feedback and then publishing as downloadable file). If a model for a digital publication is a website, then any format which does not allow to have everything which we have on websites and does not allow to take all website’s html, css and client-side scripts and publish them as downloadable file without much changing them, is doomed to failure in the long run. It seems that epub is now on this way to failure.
  • What I’d like to see is a sort of epub spinoff, another specification from the IDPF, if you will, with slightly different requirements. Instead of BOOK, we could call it epub-lite. The basis for this simplified, consumer-oriented version of .epub would be the same browser-centric building blocks under the IDPF specs. The difference would be in the file structure and in the way a browser deals with it.
    • Gary Edwards
       
      What we really need are "webDOCS". Laisvunas is absolutely right. The web is the target, with print and device "flow" an auxillary offshoot. I think we can have it all, and Aaron's "BOOK" is a good place to start. My thinking though is that javascript has to come from standardized libraries such as jQuery or Yahoo's "BrowserPLUS". Yahoo BrowserPLUS does have a security model and off-line capability built in. It's nowhere near as robust and sweepign as the jQuery javascript library, but i don't see why the two can't be combined. Good thinking on the part of Laisvunas!
  • What I wish for is this: a simple ebook format which allows me to use all technologies there are on the web with exactly the same freedom as on web and imposing no additional limitations. Secondly, some browser-based reader (browser add-on or some program based on some quality browser engine). Thirdly, some program (editor/compiler) for producing publications from preexisting web-pages.
    • Gary Edwards
       
      Once again Laisvunas nails it. I really like his "AIR" suggestion. It's also true that flowing content ready device browsers like the webKit "Safari" and SkyFire will be far more widespread than any ePUB reader!!!!! So why not write for both the web and the device at the same time?
  • The system I’m referring to is alive and well at bookglutton.com. It features an AJAX reader and Package Creation tool. The package tool is currently part of the upload feature which enables people to convert .doc, .rtf, and html documents to epub packages that can be viewed in the Reader. Once we have more epubs out there, direct epub upload will also be an option. We may also eventually enable epub download. Right now, we’re having some doubts about the value of that.
    • Gary Edwards
       
      How about "eWEB" as a format name? Is it better than "webBOOK" or webDOC"?
  •  
    Aaron Miller writes about the limitations and difficulties with ePUB. He suggests a new format, "BOOK" based on ePUB but web ready. BOOK is an AJAX format in that it includes (X)HTML, CSS and JavaScript! Excellent stuff! The discussion on this page is one of the best on the Web. ePUB gets thrashed, but with arguments very difficult to contest. The web is everything, and Aaron's friends fully understand this. Sadly, the ePUB crowd does not. I found this site looking to solve the problem of numbered lists in ePUB.
Gary Edwards

The Fall of Microsoft Office - 0 views

  • On the same day that the state of New York published a report supporting open formats for electronic documents, mighty Microsoft (Nasdaq: MSFT) said that it would support the open-source ODF format in Office 2007. Redmond's own Open Office XML specification may be heading for the great Recycle Bin in the sky, never to come back.
  • The company's biggest revenue generator may be a shadow of its former self in a few years. I just hope that Microsoft has some alternative business prospects on tap
  •  
    More confusion about the MS announcement of native support for ODF, with delayed support for whatever ISO finally determines to be ISO 29500; "OOXML". Damn but these guys are all twisted up about this. The truth is, ISO National Bodies traded their vote in favor of OOXML for MSOffice support for ODF and Microsoft's joining the OASIS ODF TC. It's not complicated. MS wants ISO approval of OOXML because it established MSOffice as a "standards" editor. The rest of this kurfufull is all about anti trust concerns and Microsoft's need to put htose concerns to bed before the world figures out that they are leveraging the MS desktop monopoly into an MS Web monopoly. ISO approval of OOXML is the final piece of very complex puzzle. The harmonization of OOXML-ODF is impossible. MS knows this. So why not join OASIS ODF TC if it means putting aside the anti trust claims from ISO NB's and getting that all important standardization of OOXML? Both ODF and OOXML are both XML encodings of entirely application specific binary formats. There is no possible to way to reconcile the file formats without also reconciling the applications! Incuding feature sets and layout engines!!!! Impossible!! The real game is the transition from client/server to the emerging client/Web-Stack/server model. MS is the "client" in client/server. No way were they about to give that up without a plan to control the transition of MSOffice documents to the emerging client/Web-Stack/server model. They sought to fully control the formats, protocols and API's of this new model. ISO handed it to them. The thing to watch is the MSOffice SDK where one can find a very cool OOXML <> XAML converter. XAML is totally proprietary, but "web ready". Meaning, MSOffice is a "web ready" application. It's just that the web readiness is 100% MS .NET-Silverlight. The great transition to client/Web-Stack/server is now on. Thanks to ISO. All this ODF stuff is just background noise designed to quiet the anti t
Paul Merrell

My take on why Microsoft finally decided to support ODF « Arnaud's Open blog - 0 views

  • Let’s just now hope that Microsoft won’t try to play games anymore. Besides their rather poor track record at delivering on the ongoing chain of announcements about becoming open and caring about interoperability (as opposed to intraoperability), there are other reasons one might want to take today’s announcement with caution. One trick they could try and pull for instance would be to put just enough support for ODF to claim that they support it but not enough for people to really use it systematically. They could then tell customers who complain something isn’t working that it’s because ODF isn’t powerful enough, and if they want the full power of Office they need to use OOXML.
  •  
    IBM's Arnaud La Hors on why Microsoft should be blamed for what is inevitable given that ODF is not designed for interoperability and is not application-neutral. One might rationally fault Microsoft for not having joined the ODF TC earlier, but the ODF TC studiously avoided enabling interoperability even among ODF implementations and ODF has almost no mandatory conformity requirements, with application-specific extensions classified as conformant. The real ODF standard is the OOo code base controlled by Sun Microsystems. IBM played along with that game and cloned the OOo code base instead of fighting on the TC to make the myth of ODF interoperability come true. I don't see a lot of moral high ground for IBM here.
Gary Edwards

Microsoft Says Yes With Mesh While Google Waits On Officenomics - 0 views

  • Imagine (not for long will it be ephemeral) an information bus that orchestrates the signaling of text, rich media, calendar, communications, transaction, and group location status under a social graph umbrella based in part on user-controlled behavior aggregation (gestures). Now imagine what Google needs to do to match this architecture and its overwhelming lead in connectors to existing hardware via Windows. Google’s answer for now is no. There’s no need to attack Mesh directly, but rather continue to iterate on Officenomics while retaining its dominant leads in user credibility and advertiser cloud. But Microsoft can efficiently hybridize Google and other microbig services with the Mesh layer added, creating information bus fail-over to multiple streams (virtual devices) to insure enterprise levels of reliability and security.
  •  
    Techcrunch review of a recent Gilmore Group interview with MS Live Mesh product manager
Gary Edwards

Meshing the desktop into the cloud | Software as Services | ZDNet.com - 0 views

  • Live Mesh brings that to life, as product director Mike Zintel explains on the brand new Live Mesh blog: “[It] blend[s] the web, Windows and other computing endpoints in a way that preserves the ‘it just works’ feel of the web with seamless integration into my common workflows. The coolest thing about Live Mesh is how it smashes the abrupt mental switch that I have to make today as I move between being ‘on the web’ and ‘in an application’.” At first glance, that may seem a perfectly reasonable and innocuous statement — and indeed it is, if you take a Web-centric view of the world — but coming out of Microsoft, it’s dynamite. Instead of seeing the Web as an extension of the desktop, it includes the desktop as part of the continuum of the Web. Where then does the application sit? Not on the desktop, or on any identifiable server machine, but simply in the mesh. In other words, it becomes a service, capable of running anywhere in the cloud, including on the desktop.
  • “The core philosophy is to make it easy to manage information in a world where people have multiple computing experiences (i.e. PCs and applications, web sites, phones, video games, music and video devices) that they use in the context of different communities (i.e. myself, family, work, organizations) …” “At the core of Mesh is [the] concept of a customer’s mesh, or collection of devices, applications and data that an individual owns or regularly uses.
Gary Edwards

Live Mesh: Microsoft hews to open standards rule | John Carroll | ZDNet.com - 0 views

  • Live Mesh is supposed to be a common framework to enable cross-device interoperability. It also includes a bunch of shared services that can be used from any Mesh-compatible device, such as network storage space and photo-sharing services, among others (others likely include many of the “Live” properties) . This makes sense given the direction that the world is moving in, with an ever-growing proliferation of computing devices both on one’s person and within the home that, currently, are too much like islands of processing power. A true mesh platform that standardized cross-device communication and synchronization in the same way HTML / CSS / Javascript has standardized user interfaces on the web would surely be a step forward from an IT evolutionary standpoint. Perhaps it was a Freudian slip, but I think the use of the term “standard” was the essential part of the previous sentence. Microsoft won’t get anywhere if they tried to peddle a closed-protocol environment to developers in 2008.
  •  
    I saw Live-Mesh today at the Web 2.0 Expo. It's still flashware, but very cool flashware. (Or is that "silverware" :) If they get this right the web will belong to Microsoft. I disagree with John that mesh will be standards base. Yes, mesh will work with HTML/CSS amd MAYBE JavaScript. But it will also work with the prorietary XAML, Silverlight, Smart Tags - LINQ. All of which are proprietary alternatives to what mesh won't support :: the advanced format standards from the W3C - XHTML, CSS3, SVG, XForms, CDF, RDF, RDFa and SPARQL. Live-Mesh will break the open web just s surely as the MSOffice SDK OOXML <> XAML conversion component will break the open web future into a Google consumer web, and a Microsoft business web.
Paul Merrell

Do new Web tools spell doom for the browser? | InfoWorld | Analysis | 2008-05-12 | By N... - 0 views

  • As these technologies mature, a new kind of browser is likely to emerge, one that combines the current Web experience with new capabilities based on emerging tools. The key to that evolution will be to integrate today's cutting-edge features with tomorrow's Web standards -- a process that Adobe and Google are both actively pursuing.
  • Adobe is similarly involved in the standardization process -- in particular, extending ECMAScript, the standard on which JavaScript is based,
  • Despite differences in approach between AIR and Gears, Adobe and Google actually share a common vision. Both companies aim to extend the current Web browsing experience with new features that allow developers to deliver RIAs more easily. And, because Web developers, too, have diverse goals and methods, the traditional browser is unlikely to disappear as an application-delivery platform, even as desktop-based Web apps proliferate.
  •  
    Tomorrow's Web Despite differences in approach between AIR and Gears, Adobe and Google actually share a common vision. Both companies aim to extend the current Web browsing experience with new features that allow developers to deliver RIAs more easily. And, because Web developers, too, have diverse goals and methods, the traditional browser is unlikely to disappear as an application-delivery platform, even as desktop-based Web apps proliferate.
Gary Edwards

Do new Web tools spell doom for the browser? | InfoWorld | Analysis | 2008-05-12 | By N... - 0 views

  • Today's Web sites are another matter, however. Gone are the static pages and limited graphics of 15 years ago. In their place are lush, highly interactive experiences, as visually rich as any desktop application. The Web has become the preferred platform for enterprise application delivery, to say nothing of online entertainment and social software. In response, new kinds of online experiences have begun to emerge, challenging old notions of what it means to browse the Web.
Paul Merrell

Power to the Patients - 0 views

  •  
    It might take Google and Microsoft-technology giants, but health-records neophytes-to give networked and interoperable electronic health records just the kick start they need to escape the siloed and proprietary model now prevalent. The new technologies, Google Health and Microsoft HealthVault, are classified as personal health records (PHRs), which are a subset of industry-recognized electronic health records (EHRs).
  •  
    What is the likelihood that the Microsoft and Google solutions will be interoperable? Will either company be able to resist the temptation to introduce incompatibilities? Methinks it far more likely based on the history in the software industry that the interoperability will be intra-company solution rather than between each company's solution. This is a potential issue for the same reason that the solutions are being developed; people in the U.S. have many health care providers. Records can't be consolidated and made portable absent interoperability. I haven't researched the issue, but I note it.
Gary Edwards

OOXML/ODF: Just One Battlefield in a Much Bigger War | Brian Proffitt Linux Today - 0 views

  • Once in a while, a confluence of random events (or not so random, depending on your belief system) can create the ideal aha! moment. The moment of clarity when all the pieces just fall into place and you realize "that's what's going on!" I believe I have had one of those moments. And if this thought has any basis in reality, it could mean that everything we have seen in IT is about to make a huge change.
  •  
    Brian figures out that the document wars are really about Cloud Computing. Big vendors IBM, Sun, Google and Microsoft are jockeyign for position in our cloud computing future. And this is why Microsoft MUSt get ISO approval of MSOffice-OOXML! What Brian misses is the key to a Microsoft Cloud that can be found int he MSOffice SDK; the OOXML<>XAML conversion component. XAML, Silverlight and Smart Tags replace W3C XHTML-CSS, SVG-Flash, and RDF. Makign the MS Cloud one where Microsoft owned protocols, formats and .NET components dominate all processes. ISO approval of MSOffice-OOXML establishes MSOffice as a standards "editor", thus masking the cloud computing shift to XAML. A shift that will lock out all other Web 2.0 - Cloud providers dependent on Open Web - W3C protocols and formats!
  •  
    Note that Brian posted this article in February, on the eve of the Geneva BRM. Since then ISO has gone on to approve MSOffice-OOXML. Note also that, a week prior to this publication, i had sent Brian a lengthy discussion entitled "Windows can't do Cloud Computing", where all of these issues were discussed except for the IBM motivations. Not wanting to interfere with the upcoming Geneva BRM and vote, I had declined Brian's request to publish.
Paul Merrell

Sun: Java ubiquity an advantage in RIA battle | InfoWorld | News | 2008-05-09 | By Paul... - 0 views

  •  
    A browser plug-in for JavaFX will be featured in the Java SE (Standard Edition) 6 Update 10 release due this fall. Both Adobe, with its Flash platform, and Microsoft, with Silverlight, are offering plug-in platforms for rich Internet applications. But Sun plans to provide the industry-leading rich client with JavaFX, said Param Singh, Sun senior director of Java marketing. The Java runtime helps make this possible, he stressed during an interview at the JavaOne conference on Thursday afternoon. "The Java runtime is on over 900 million desktops today," Singh said. Every month, there are 40 million downloads of updates to the Java runtime, he said. Additionally, there are more than 2.2 mobile phones with Java on them, not to mention Java's presence in 100 percent of Blu-ray devices, said Singh. "The notion is, we will take JavaFX where the Java runtime is available," Singh said. Sun's JavaFX plug-in will enable deployment of applications that can work either in or outside of the browser, Singh said. This ability to run applications inside or outside of a browser is similar to what Adobe is offering with its AIR (Adobe Integrated Runtime) software.
Paul Merrell

Sun defends JavaFX Script | InfoWorld | News | 2008-05-08 | By Paul Krill - 0 views

  •  
    But Sun CTO Bob Brewin emphasized in an interview that JavaFX Script features a new set of capabilities such as allowing development of applications that can be moved outside the browser. JavaFX Script also is designed for content authors, not necessarily developers alone. ... With JavaFX and the Java 6 Update 10 release, also called Consumer JRE (Java Runtime Environment), developers can deploy applications to browsers and have applets dragged out onto the desktop. Brewin also filled in details about Sun's cloud services effort, called Project Hydrazine. It is to feature an infrastructure enabling developers to run services on the Web such as mapping, location, calendaring, and e-mail services. Due next year, Hydrazine is to be part of Sun's network.com grid infrastructure. Also part of Hydrazine is Project Insight, which will measure who is visiting Web sites. Developers will be able to find who is using their service and perhaps could deliver targeted advertising. Hydrazine combines attributes offered in Microsoft's Live Mesh data folder-sharing service, the Amazon Elastic Compute Cloud Web-based service and Google Analytics, Brewin said.
1 - 20 of 26 Next ›
Showing 20 items per page