Skip to main content

Home/ In-the-Clouds-with-SOA-XML-and-the-Open-Web/ Group items matching "woa" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

The Enterprise- Cloud Duo: SOA plus WOA | Dana Gardner - 0 views

  • Cloud providers and mainstay enterprise software vendors could make sweeter WOA plus SOA music together. They may not have a choice. If Microsoft acquires Yahoo!, there will be a huge push for Microsoft Oriented Architecture that will double-down on “software plus services.” And MSFT combined with Yahoo would have an awful lot in place to work from — from the device and PC client, to the server farm, business applications, developer tools and communities, and ramp-up of global cloud/content/user metadata resources. I think Microsoft already understands the power of WOA plus SOA.
  • The cloud that can manage data in way that allows both user-level and process-level access, with granular permissioning — and allows CXOs to feel good about it all — gets the gold ring. The cloud business is a 50-year business.
  •  
    Review of Dion Hinchcliffe's article, "Web 2.0 driving Web Oriented Architecture and SOA".
Gary Edwards

'Enough with WOA, stick to SOA,' say IT architects - I say drop WOA and SOA | Dana Gardner's BriefingsDirect | ZDNet.com - 0 views

  • 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.
Gary Edwards

Web 2.0 success stories driving WOA and informing SOA | Enterprise Web 2.0 | ZDNet.com - 0 views

  • Organizations clearly want to leverage high levels of interoperability to seize new business opportunities, innovate on top of existing assets, and properly leverage the extensive landscape of software, data, and infrastructure that most organizations have accumulated in large quantities over the years. But we are still having a great deal of difficulty doing so and SOA investments are just not reaping the types of return on investments that most businesses would like to have.
Gary Edwards

The Mesh lives but the cloud Office is vaporous | Outside the Lines - CNET News.com - 0 views

  • Office Live will bring Office to the web, and the web to Office. We will deliver new and expanded productivity experiences that build upon the device mesh vision to extend productivity scenarios seamlessly across the PC, the web, and mobile devices. Individuals will seamlessly enjoy the benefits of each - the rich, dynamic editing of the PC, the mobility of the phone, and the work-anywhere ubiquity of the web. Office Live will also extend the PC-based Office into the social mesh, expanding the classic notion of "personal productivity" into the realm of the "inter-personal" through the linking, sharing and tagging of documents. Individuals will have a productivity centric web presence where they can work and productively interact with others. This broadly extended vision of Office is being realized today through Office Mobile and Office Live Workspace on the web, augmented by SharePoint, Exchange, and OCS for the connected enterprise.
  •  
    I don't think Dan Farber gets it. ISO approval of MSOffice-OOXML establishes MSOffice as a standards compliant web/cloud/WOA "editor" for client/Web-Stack/server systems. No need to try to squeeze all tha tcomplexity into a browser. Just use the MSOffice SDK OOXML <> XAML conversion component to convert rich, business process loaded, documents to a web ready format. OH my, XAML is proprietary and IE-8 does not support XHTML2, CSS3, SVG, XForms, RDF, SPARQL, SWF, PDF or JavaScript. Bummer. ISO has done the unthinkable and Microsoft can now break the web without worry of anti trust retribution. They are after all, simply implementing an open standard.
Gary Edwards

Open source SOA infrastructure project CXF elevated to full Apache status | Dana Gardner's BriefingsDirect | ZDNet.com - 0 views

  • CXF is really designed for high performance, kind of like a request-response style of interaction for one way, asynchronous messaging, and things like that. But it’s really designed for taking data in from a variety of transports and message formats, such as SOAP or just raw XML. If you bring in the Apache Yoko project, we have CORBA objects coming in off the wire. It basically processes them through the system as quickly as possible with very little memory and processing overhead. We can get it to the final destination of where that data is supposed to be, whether it’s off to another service or a user-developed code, whether it’s in JavaScript or JAX-WS/JAXB code. That’s the goal of what the CXF runtime is — just get that data into the form that the service needs, no matter where it came from and what format it came from in, and do that as quickly as possible.
  • the fascinating intersection of SOA and WOA — with on-premises services and cloud-based resources (including data) supporting ecologies of extended enterprises business processes
  • Creating federated relationships between private and public clouds and their services and resources requires more than just industry standards. It requires visibility and access, the type that comes from open source communities and open use licenses.
  •  
    The Apache CFX "Interoperability Framework" for SOA Project is ready. We really could have used CFX in the 2003 Comcast project where a Tomcat/MYSQL Web-Stack connected to many disparate blackboxes. The blackboxes were standalone "Inventory and Billing" transaction processing data centers aquired by Comcast during a five year burst of acquisitions. Of course, none of these blackboxes could talk to any other! Enter SOA with XMLHTTPRequest streams. 2002-2003. We needed CFX to scale!
Gary Edwards

XML-Empowered Documents Extend SOA's Connection to People and Processes | BriefingsDirect Transcripts - 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

Web 2.0 Stovepipe System: Sir Tim Berners-Lee: Semantic Web is open for business | The Semantic Web | ZDNet.com - 0 views

  • “Web 2.0 is a stovepipe system. It’s a set of stovepipes where each site has got its data and it’s not sharing it. What people are sometimes calling a Web 3.0 vision where you’ve got lots of different data out there on the Web and you’ve got lots of different applications, but they’re independent. A given application can use different data. An application can run on a desktop or in my browser, it’s my agent. It can access all the data, which I can use and everything’s much more seamless and much more powerful because you get this integration. The same application has access to data from all over the place.”
  •  
    podcast with Sir Tim discusses the "linked Data Project" and the Semantic Web contrast to Web 2.0 Social Stovepipe Systems
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

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

  • 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.
  •  
    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

Web 2.0 Silos! Sir Tim Berners-Lee addresses WWW2008 in Beijing | The Semantic Web | ZDNet.com - 0 views

  •  
    Perpetuating current data silos by continuing to "give your data to a site" was, Berners-Lee asserted, "not ideal." He argued instead for wider adoption of new or existing Web specifications such as OAuth and RDFAuth, enabling the individual to store data relevant to themselves wherever they felt fit, and assemble it at will within one or more Web and local applications of their choosing at the point of need. "Acquaintance-based social networks," Berners-Lee suggested, were "the tip of the iceberg," with his notion of the emerging Giant Global Graph "exist[ing] above the Web" and creating opportunities for far richer functional and role-based interconnections. Turning to consideration of the Web itself, Berners-Lee remarked that "Openness tends to be an inexorable movement through time" He juxtaposed the 'Web Application Platform' with proprietary solutions to parts of the problem such as Flash, AIR and Silverlight. This Web Application Platform, he argued, relies upon W3C specifications and other open standards, and it is increasingly moving toward specifications that are small, modular, and interoperable. Moving toward his conclusion, Berners-Lee reiterated the importance of Linked Data again saying "Linked Open Data is the Web done as it should be." Returning to his earlier discussion of modularity, he suggested that existing specifications such as those for JavaScript be reworked, carving JavaScript's functionality up into a series of modular packages. Each of those packages should then be assigned a URI, and the Semantic Web should be used to describe the packages, their dependencies, and their interrelationships. Used in conjunction with the resulting applications, Linked Data would provide, "elements of an ability to do things [with data] that cross application boundaries." Turning to Q&A, Berners-Lee was first asked to comment on the concept of 'Web 2.0′, which he did; "Web 2.0 sites a
  •  
    And of course it is the incredible variety in data formats used by Web 2.0 apps that forces the creation of new data silos on the Web. Web 2.0 is bringing us the same kinds of incompatible data format issues forced on software users since the beginning of the proprietary software industry.
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

The problem with Forrester's $4.6 billion prediction | Irregular Enterprise | ZDNet.com - 0 views

  • Collaboration is about problem solving in the flow of business processes - or at least it should be. That’s where cost sits and where all the automation in the world will not rescue the business manager. Enterprise 2.0 doesn’t solve problems per se but it may serve to expose them. The question then comes, how does business go about solving the problems it has discovered? In many cases, this comes down to one of several things.
  • Forrester has missed a trick. It has fallen into the evolutionary trap of assuming that existing processes will accommodate the new world of socially networked operations. If anything, the adoption of these technology solutions will raise the specter of how business process designed to release value is articulated through software. That alone could kill off many an otherwise worthy project as business managers stop to rethink what they need to build in order to solve the real problems of the day. Collaboration will go some distance, but without a fast track way of implementing BRP, it will represent a lot of wasted effort.
Gary Edwards

The end of the web as we know it | Adobe - Developer Center : Duane Nickull - 0 views

  • The web as we knew it in 1995 has already largely died. Out of the ashes has arisen a second incarnation and we are currently on the verge of a new reality, Web 2.0. While there is no one definition, Web 2.0 is perhaps best described as the migration to the web as a platform spanning all connected devices, coupled with a specific set of patterns. Web 2.0 has many components, but it is generally associated with a class of web applications that harness the intelligence, data, and actions of their users to create value (iconic Web 2.0 applications include Flickr, YouTube, and Amazon). While many are looking to Web 2.0 to solve the problems of yesteryear, the mass migration is creating a new set of problems that must be addressed. This article is divided into three parts: an analysis of the web today, an analysis of what has already died or is dying, and a look forward at aspects of Web 2.0 that are creating problems and will likely die in the next five years.
  •  
    Humm. Good idea Duane! I'm thinking why it is that i don't have a Wikipedia resource center for my personal information. Instead i have Diigo, Facebook and Flickr.
  •  
    Excellent whitepaper from Duane.
Gary Edwards

Component Content Management in Practice - Meeting the Demands of the Most Complex Content Applications | Gilbane Group White Papers - 0 views

  • Executive Summary As the market for content management technology continues to grow, so too do the ways in which organizations seek to use content management. What began as a market focused on web content management has grown to include document management, digital asset management, and records management. What has emerged along with this growth is a desire by vendors to provide a broad, enterprise-class platform of content management technology that can handle all kinds of content.
  •  
    Gilbane white paper on Content Management Systems. Covers evolution of CMS from paper to digital to web.
  •  
    Notice that most of the concepts discussed in the Gilbane white paper are implemented in the open source Daisy wiki/content management system, which is a new wave document assembly/management system specifically designed for producing large technical documents. http://cocoondev.org/daisy/features.html
1 - 14 of 14
Showing 20 items per page