Skip to main content

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

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Philipp Arytsok

REST - Der bessere Web Service? || IT-Republik - JAXenter - Artikel - 0 views

it-republik.de/...-bessere-Web-Service-2158.html

jaxenter REST Web Service

shared by Philipp Arytsok on 23 Feb 09 - Cached
  • REST - Der bessere Web Service?
  • Philipp Arytsok on 23 Feb 09
     
    Vor nicht all zu langer Zeit schien es völlig klar, dass der Weg für eine interoperable Kommunikation zwischen Anwendungen mit unterschiedlichen Entwicklungszyklen über Web Services führen muss. In letzter Zeit jedoch ist immer häufiger die Rede von einer leichtgewichtigen, einfacheren Alternative: Web Services auf Basis von REST (REpresentational State Transfer).
Gary Edwards

Independent study advises IT planners to go OOXML: The Bill Gates MSOffice "formats and... - 0 views

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

anti-trust browser-wars comes gates iowa msoffice netscape ooxml w3c

shared by Gary Edwards on 30 May 08 - Cached
  • 3.2.2.2. A pox on both your houses! gary.edwards - 01/22/08 Hi Robert, What you've posted are examples of MSOffice ”compatibility settings” used to establish backwards compatibility with older documents, and, for the conversion of alien file formats (such as various versions of WordPerfect .wpd). These compatibility settings are unspecified in that we know the syntax but have no idea of the semantics. And without the semantic description there is no way other developers can understand implementation. This of course guarantees an unacceptable breakdown of interoperability. But i would be hesitant to make my stand of rejecting OOXML based on this issue. It turns out that there are upwards of 150 unspecified compatibility settings used by OpenOffice/StarOffice. These settings are not specified in ODF, but will nevertheless show up in OpenOffice ODF documents – similarly defying interoperability efforts! Since the compatibility settings are not specified or even mentioned in the ODF 1.0 – ISO 26300 specification, we have to go to the OOo source code to discover where this stuff comes from. Check out lines 169-211. Here you will find interesting settings such as, “UseFormerLineSpacing, UseFormerObjectPositioning, and UseFormerTextWrapping”. So what's going on here?
  • From: Bill Gates Sent: Saturday, December 5 1998 To: Bob Muglia, Jon DeVann, Steven Sinofsky Subject : Office rendering "One thing we have got to change in our strategy - allowing Office documents to be rendered very well by other peoples browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities. Anything else is suicide for our platform. This is a case where Office has to avoid doing something to destroy Windows. I would be glad to explain at a greater length. Likewise this love of DAV in Office/Exchange is a huge problem. I would also like to make sure people understand this as well." Tuesday, August 28, 2007
  • Gary Edwards on 30 May 08
     
    The IOWA Comes vs. Microsoft antitrust suit evidence is now publicly available. This ZDNet Talkback posts an extraordinary eMail from Bill Gates concerning the need to control MSOffice formats and protocols as Microsoft pushes onto the Web. The key point is that Chairman Bill understands that the real threat to Microsoft is that of Open Web formats and protocols outside of Microsoft's control. It's 1998, and the effort to "embrace and eXtend" W3C HTML, XHTML, SVG and CSS isn't working well. The good Chairman notifies the troops that MSOffice must come up with another plan. Interestingly, it's not until 2001, when OpenOffice releases an XML encoding of the OpenOffice/StarOffice imbr that Microsoft finally sees a solution! (imbr = in-memory-binary-representation) The MSOffice crew immediately sets to work creating a similar XML encoding of the MSOffice binary (imbr) dump. The first result is released in the MSOffice 2003 beta as "WordprocessingML and SpreadsheetML". XML was designed as a structured language for creating specific structured languages. OpenOffice saw the potential of using XML to create an OpenOffice specific XML language. MSOffice seized the innovation and the rest is history. Problem solved! So what was the "problem" the good Chairman identified in this secret eMail? It's that the Web is the future, and Microsoft needed to find a way of leveraging their existing desktop document "editor" monopoly share into owning and controlling the Web formats produced by Microsoft applications. MSOffice OOXML is the result. ISO approval of MSOffice OOXML is beyond important to Microsoft. It establishes MSOffice "editors" as standards compliant. It also establishes the application, platform and vendor specific MSOffice OOXML as an international "open" standard. Many will ask why this isn't a case of Microsoft actually opening up the MSOffice formats in compliance with government antitrust demands. It is "compliance", but not in the sense of what
Gary Edwards

The Fall of Microsoft Office - 0 views

www.fool.com/...-fall-of-microsoft-office.aspx

iso odf ooxml xaml

shared by Gary Edwards on 29 May 08 - Cached
  • 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
  • Gary Edwards on 29 May 08
     
    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
Gary Edwards

Live Mesh: Windows Becomes the Web | Microsoft Watch - Web Services & Browser - - 0 views

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

hubs mesh msoffice silverlight snart soa tags web-stack woa xaml

shared by Gary Edwards on 29 Apr 08 - Cached
  • simply: Microsoft is launching a synchronization platform that the company claims is technology-agnostic. That absolutely is not true. Live Mesh is Microsoft's attempt to turn operating system and proprietary services platforms into hubs that replace the Web. It's the most anti-Web 2.0 technology yet released by any company. Microsoft is building a services-based operating system that transcends and extends Windows and also the function of Web browsers. It's bold, brilliant and downright scary. Microsoft has identified the right problem, synchronization, but applied a self-serving solution.
  • The services platform doesn't seek to keep the Web as the hub, but replace it with something else. The white paper is wonderfully misleading, by implying that Microsoft supports the Web as the hub. Live Mesh is the hub.
  • Live Mesh is competitively important to Microsoft because of companies like Google, whose services shift computational and informational relevancy from desktop software to the Web. But there is something missing as data spreads out across the Web platform to millions of devices: simple synchronization.
  • ...3 more annotations...
  • This mesh of services compromises the overlaying platform, which is supported by proprietary Microsoft APIs.
  • APIs, desktop software and Mesh run-time take on real importance. Users must install Live Mesh software on their PC, which includes the synchronization run-time and makes extension changes to Windows Explorer.
  • Microsoft's broader Mesh vision extends the operating system to cloud services. Microsoft's PR information refers to the "Mesh Operating Environment," which would presumably grant end users access to applications anytime, anywhere and on anything. Access includes the Web browser, provided it's from Live Desktop. End users would designate devices in their Mesh that would be permitted to run applications. And, yes, it does foreshadow hosted applications as well as those accessed from a Mesh-designated PC.
  • Gary Edwards on 29 Apr 08
     
    Joe Wilcox takes on MS "Live Mesh" in a series of articles. Clearly he gets it but one has to wonder about the rest of the techno crowd.
Gary Edwards

'Enough with WOA, stick to SOA,' say IT architects - I say drop WOA and SOA | Dana Gard... - 0 views

blogs.zdnet.com/Gardner

cloud-computing ria soa woa

shared by Gary Edwards on 22 Apr 08 - Cached
  • So, true, WOA, isn’t an architecture, it’s a webby style of apps and integration, of mashups and open APIs, of using REST and RIA clients, all from a variety of Internet sources. It’s integration as a service, too. These can all be composited, accessed and managed by an enterprise’s internal SOA, or not. The services can come from a cloud, public or private. Forrester says the growth curve for Enterprise 2.0 is steep, but I think it will be even steeper. These webby assets could just as well come together as portals, standalone Web apps, SaaS, or RIA front ends for composited ecology services that support extended enterprise processes. The point is there’s no need to wait.
  • rapid ramp-up of services hybrids — of public/private clouds, services ecologies, internal and external hosting, social enterprise media tools, mashups in myriad forms, integration of services regardless of origins or types of aggregation. You can today begin a business online and scale it without an IT department, or an on-premises datacenter. You just can.
  • The fact is that the definitions of and distinctions between applications, platforms, services, tools, clouds, portals, integration, middleware are — all up for grabs. IT as a concept is up for grabs. The shifts in the software arena at that disruptive. It’s why Microsoft is seeking to buy Yahoo, and not Oracle.
1 - 6 of 6
Showing 20▼ items per page