In-the-Clouds-with-SOA-XML-and-the-Open-Web

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.

Version 0.01 of the Universally Accessible and Interoperable Specification has been released. The draft sets for criteria derived from competition law for evaluating the suitability of data formats and communications protocols in the ICT sector.

While proponents of ICT modernization might hope that other candidates would embrace and extend the relevant Obama pledges, thus far none have done so. But what is still missing from the Obama campaign's to-do list is specific criteria for evaluation of file formats and communications protocols to achieve the goals announced. This document is intended to suggest such criteria and to provide a set of principles useful for other governments concerned with revamping their information infrastructure to foster greater interoperability, accessibility, and competition in the software market in a manner consistent with antitrust law in the U.S. and the European Union as well as with international law applicable to all Member nations of the Agreement on Technical Barriers to Trade and the Agreement on Government Procurement. Consistency with the laws of other nations is an ultimate goal.

Epilog Like many of us, I'm a kind of addicted to Twitter. But a few weeks ago, the admins of my client cuts the connection to Twitter and all of the known anonymanizers like "agentanon". My hands began to tremble, my work became poorer and poorer (just a joke!). Two lucky circumstances: * first free weekend since many month * my SAP PRD server is already up and connected to the internet, because I have a presentation on Monday Why don't turn a problem into a challenge and develop my own "ABAP twitter client" ?

Nice to find my blog here ;)

Bonus points to Paul!

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.

A pessimistic approach towards SOA seems to prevail in some blogs. But these opinions strike me by surprise. In the industries I am working for - public sector, healthcare and Defense/ public security - SOA is predominant and you will find only rare examples of tenders where SOA is not highlighted as the guiding principle for the whole architecture. SAP's CTO Vishal Sikka has already provided the community with some very helpful insights concerning these discussions. I just want to add some points from an architect's point of view: From my point of view it is not the SOA approach itself which should be questioned but the way how we architects sometimes work on SOA. Some of the mistakes that are listed below I have encountered during my SOA projects. Others are based on discussions with other architects and decision makers inside and outside SAP, from customers and from partners. My intention is simple: I want to help to avoid these mistakes in the future and to strengthen the SOA approach which is for me without an alternative.

SOA ist nicht tot - SOA ist Mainstream

uh oh. JavaScript - SVG rendering engine relacing HTML - CSS with SVG drawn from a transform library.

Don't forget that SVG Tiny allows vendor-specific extensions, with some conditions.

What is SAP Solution Manager?

More review of the Gilmopre Gang interview

The Wikipedia "OpenDocument Foundation" page is continually re edited, changing the factual truth to portray the Foundation in the worst light possible. Every time we try to repair the page to reflect the truth, the liars jump right back in. Is there a Wikipedia resolution for liies? Our facts can be verified by the five year history of the OASIS membership and ODF TC records that are public information. This anonymous post to Joe Barr's Linux.com article is perhaps the best explanation on the Web of why the Foundation choose CDF, and could not use ODF.Good explanation of MSOffice-OOXML and the MS Web-Stack :: MS Cloud.No mention of the December 2007 MSOffice SDK beta that provided us with that first all important glimpse of the MSOffice-OOXML <> XAML converter component. I take it the article comment was written before that most important discovery. XAML "fixed/flow" is an alternative to W3C/ISO XHTML-CSS and ISO PDF.

Microsoft faces down threats from Google, IBM and SalesForce.com with it's threat to enterprise IT - MSOffice as the ultimate browser.

Google Office productivity alternatives are "trapped inside the browser". MSOffice, Silverlight, Live Mesh and Adobe Flex "RIA" browser alternatives are comparatively feature rich and powerfull.

Once again it's the business processes bound to MSOffice that bind users to MS products. The Massachusetts ODF Pilot Study first uncovered the business processes bound to MSOffice issue tha tmade implementation of ODF impossible. The IBM "rip out and replace" approach simply does nto work anywhere there are these bound business processes. Massachusetts CIO Louis Gutierrez correctly identified the problem and the solution: coem up with an ODF plug-in for MSOffice. Replace the docuemnt format - not the application and bound business processes.

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

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

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.

CellNode M100 is a unique WiFi device which enables providers to securely deploy wireless mesh networks. Every CellNode features two radio transceivers that support the 802.11a/g/b standards. The first radio usually serves local wireless subscribers (downlink) at 2.4Ghz, while the second radio is used to connect to the infrastructure backbone (uplink) at 5Ghz.

"CellNode M100 is designed for deployment in wireless mesh infrastructure. In such infrastructure, each CellNode M100 communicates with an uplink relay (bridge) or access controller and with other wireless clients within its reach. If one CellNode device becomes temporarily unavailable, traffic is transparently redirected to other CellNodes located within physical proximity." I'm not a hardware expert by any means, but the sniff here is sprinkling these things around town, managing centrally including firmware update rollouts, built in UPS for keeping the network up during power outages, automagic switching to other nodes if one goes down, on and on and on. Could I cope with a mere 54 Mbs 802.11/n connection instead of Comcast's ~ 11 Mpbs just to save $50 a month? Gee, that's a hard one. I'll have to think about that. No wonder the cable and telco providers are fighting municipal networks hair, tooth, and nail.

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

Another JavaSript library concept, but this time secure. Not as robust as jQuery, but Yahoo is off to a great start. wikiWORD could use this for dynamic page generation.