Skip to main content

Home/ OpenDocument/ Group items tagged Machine

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

Asia Times Online :: Operation Tomahawk The Caliph - 0 views

www.atimes.com/...MID-01-240914.html

war & peace Syria ISIL al-Nusra Israel U.S.-foreign-policy Khorasan

shared by Paul Merrell on 24 Sep 14 - No Cached
  • The Tomahawks are finally flying again - propelled by newspeak. 42 Tomahawks fired from a Sixth Fleet destroyer parked in Mare Nostrum, plus F-22s raising hell and Hellfires spouted by drones, that's a neat mini-Shock and Awe to honor Caliph Ibrahim, aka Abu Bakr al -Baghdadi, self-declared leader of Islamic State. It's all so surgical. All targets - from "suspected" weapons depots to the mayor's mansion in Raqqah (the HQ of The Caliph's goons) and assorted checkpoints - were duly obliterated, along with "dozens of", perhaps 120, jihadis. And praise those "over 40" (Samantha Power) or "over 50" (John Kerry) international allies in the coalition of the unwilling; America is never alone, although in this case mightily escorted, de facto, only by the usual Gulf petrodollar dictatorships and the realm of <a href='http://asianmedia.com/GAAN/www/delivery/ck.php?n=a9473bc7&cb=%n' target='_blank'><img src='http://asianmedia.com/GAAN/www/delivery/avw.php?zoneid=36&cb=%n&n=a9473bc7&ct0=%c' border='0' alt='' ></a> King Playstation, Jordan, all none too keen to engage in "kinetic activities".
  • Aseptic newspeak aside, no one has seen or heard a mighty Gulf Cooperation Council air force deployed to bomb Syria. After all the vassals are scared as hell to tell their own populations they are - once again - bombing a fellow Arab nation. As for Damascus, it meekly said it was "notified" by the Pentagon its own territory would be bombed. Nobody really knows what the Pentagon is exactly telling Damascus. The Pentagon calls it just the beginning of a "sustained campaign" - code for Long War, which is one of the original denominations of the Global War on Terror (GWOT) anyway. And yes, for all practical purposes this is a coalition of one. Let's call it Operation Tomahawk The Caliph.
  • Hold your F-22s. Not really. The tomahawking had barely begun when an Israeli, made in USA Patriot missile shot a Syrian Su-24 which had allegedly "violated" Israeli air space over the Golan Heights. How about that in terms of sending a graphic message in close coordination with the Pentagon? So this is not only about bombing The Caliph. It is a back-door preamble to bombing Bashar al-Assad and his forces. And also about bombing - with eight strikes west of Aleppo - a ghost; an al-Qaeda cell of the mysterious Khorasan group. No wonder global fans of the Marvel Comics school of geopolitics are puzzled. Two simultaneous villains? Yep. And the other bad guy is even more evil than The Caliph.
  • ...5 more annotations...
  • Astonishing mediocrity Ben Rhodes, Obama's deputy national security adviser, has defined Khorasan as "a group of extremists that is comprised of a number of individuals who we've been tracking for a long time." The Obama administration's unison newspeak is that Khorasan includes former al-Qaeda assets not only from across the Middle East - including al-Qaeda in Iraq and Jabhat al-Nusra - but also Pakistan, as in an ultra-hardcore extension of the Pakistani Taliban.
  • What a mess. Al-Qaeda in Iraq is the embryo of ISIS, which turned into IS. Jabhat al-Nusra is the al-Qaeda franchise in Syria, approved by CEO Ayman al-Zawahiri. Both despise each other, and yet Khorasan holds the merit of bundling Caliph's goons and al-Qaeda goons together. Additionally, for Washington Jabhat al-Nusra tend to qualify as "moderate" jihadis - almost like "our bastards". Too messy? No problem; when in doubt, bomb everybody. The Caliph, then, is old news. Those ghostly Khorasan goons are the real deal - so evil that the Pentagon is convinced their "plotting was imminent" leading to a new 9/11.
  • Khorasan is the perfect ghost in the GWOT machine; the target of a war within a war. Because Obama in fact launched two wars - as he sent two different notifications to Congress under the War Powers Resolution to cover both The Caliph and Khorasan. And what's in a name? Well, a thinly disguised extra demonization of Iran, why not - as historic Khorasan, the previous Parthia, stretched from mainly Iran towards Afghanistan. Khorasan is theoretically led by The Joker, sorry, al-Qaeda honcho Muhsin al-Fadhli, born in Kuwait in 1981, a "senior facilitator and financier" to Abu Musab al-Zarqawi in Iraq, in the priceless assessment of the State Department. Although Ayman al-Zawahiri, ever PR-conscious, has not claimed the credit, the Pentagon is convinced he sent al-Fadhli to the Syrian part of the Caliphate to attract Western jihadis with EU passports capable of evading airport security and plant bombs on commercial jets.
  • The Treasury Department is convinced al-Fadhli even led an al-Qaeda cell in Iran - demonization habits die hard -, "facilitating" jihadi travel to Afghanistan or Iraq. And what a neat contrast to the Society of the Spectacle-addicted Caliph. Khorasan is pure darkness. Nobody knows how many; how long they've existed; what do they really want. By contrast, there are about 190,000 live human beings left in bombed out Raqqa. Nobody is talking about collateral damage - although the body count is already on, and The Caliph's slick PR operation will be certainly advertising them on YouTube. As for The Caliph's goons, they will predictably use Mao tactics and dissolve like fish in the sea. The Pentagon will soon be bombing vast tracts of desert for nothing - if that's not the case already. There is no "Free Syrian Army" - that Qatari myth - anymore. There are no "moderate" jihadis left in Syria. They are all fighting for The Caliph or for al-Zawahiri. And still the Obama administration extracted a Congressional OK to train and weaponize "moderate rebels".
  • US ambassador to the UN Samantha Power - Undisputed Queen of Batshit Craziness - at least got one thing right. Their "training" will "service these troops in the same struggle that they've been in since the beginning of this conflict against the Assad regime." So yes - this "sustained campaign" is the back door to "Assad must go" remixed. People who are really capable of defeating The Caliph's goons don't tomahawk. They are the Syrian Arab Army (roughly 35,000 dead so far killed in action against ISIS/ISIL/IS and/or al-Qaeda); Hezbollah; Iranian Revolutionary Guards advisers/operatives; and Kurdish militias. It won't happen. This season's blockbuster is the Empire of Chaos bombing The Caliph and the ghost in the GWOT machine. Two tickets for the price of one. Because we protect you even from "unknown unknown" evil.
  • Paul Merrell on 24 Sep 14
     
    Pepe Escobar at his finest. 
Gary Edwards

Microsoft Watch Finally Gets it - It's the Business Applications!- Obla De OBA Da - 1 views

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

odef odf officeopenxml ooxml opendocument vista-stack

shared by Gary Edwards on 13 Jul 07 - Cached
  • To be fair, Microsoft seeks to solve real world problems with respect to helping customers glean more value from their information. But the approach depends on enterprises adopting an end-to-end Microsoft stack—vertically from desktop to server and horizontally across desktop and server products. The development glue is .NET Framework, while the informational glue is OOXML.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      OOXML is the transport - a portable XML document model where the "document" is the interface into content/data/ and media streaming.

      The binding model for OOXML is "Smart Documents", and it is proprietary!

      Smart Documents is how data, streaming media, scripting-routing-workflow intelligence and metadata is added to any document object.

      Think of the ODF binding model using XForms, XML/RDF and RDFA metadata. One could even use Jabber XMP as a binding model, which is how we did the Comcast SOA based Sales and Inventory Management System prototype.

      Interestingly, Smart Documents is based on pre written widgets that can simply be dragged, dropped and bound to any document object. The Infopath applicaiton provides a highly visual means for end users to build intelligent self routing forms. But Visual Studio .NET, which was released with MSOffice 2007 in December of 2006. makes it very easy for application and line of business integration developers to implement very advanced data binding using the Smart Document widgets.

      I would also go as far to say that what separates MSOOXML from Ecma 376 is going to be primarily Smart Documents.

       Yes, there are .NET Framework Libraries and Vista Stack dependencies like XAML that will also provide a proprietary "Vista Stack" only barrier to interoperability, but Smart Documents is a killer.

      One company that will be particularly hurt by Smart Documents is Google. The reason is that the business value of Google Search is based on using advanced and closely held proprietary algorithms to provide metadata structure for unstrucutred documents.

      This was great for a world awash in unstructured documents. By moving the "XML" structuring of documents down to the author - workgroup - workflow application level though, the world will soon enough be awash in highly structured documents that have end user metadata defining document objects and
  • Microsoft seeks to create sales pull along the vertical stack between the desktop and server.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      The vertical stack is actually desktop - server - device - web based.  The idea of a portable XML document is that it must be able to transition across the converged application space of this sweeping stack model.

      Note that ODF is intentionally limited to the desktop by it's OASIS Charter statement.  One of the primary failings of ODF is that it is not able to be fully implemented in this converged space.  OOXML on the other hand was created exactly for this purpose!

      So ODF is limited to the desktop, and remains tightly bound to OpenOffice feature sets.  OOXML differs in that it is tightly bound to the Vista Stack.

      So where is an Open Stack model to turn to?

      Good question, and one that will come to haunt us for years to come.  Because ODF cannot move into the converged space of desktop to server to device to the web information systems connected through portable docuemnt/data transport, it is unfit as a candidate for Universal File Format.

      OOXML is unfi as a UFF becuase it is application - platform and vendor bound.

      For those of us who believe in an open and unencumbered universal file format, it's back to the drawing board.

      XHTML (XHTML CSS3 RDF) is looking very good.  The challenge is proving that we can build plugins for MSOffice and OpenOffice that can fully implement XHTML .  Can we conver the billions of binary legacy documents and existing MSOffice bound business processes to XHTML ?

      I think so.  But we can't be sure until the da Vinci proves this conclusively.

      One thign to keep in mind though.  The internal plugins have already shown that it is possible to do multiple file formats.  OOXML, ODF, and XML encoded RTF all have been shown to work, and do so with a level of two way conversion fidelity demanded by existing business processes.

      So why not try it with XHTML , or ODEF (the eXtended version of ODF en
  • Microsoft's major XML-based format development priority was backward compatibility with its proprietary Office binary file formats.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      This backwards compatibility with the existing binary file formats isn't the big deal Micrsoft makes it out to be.  ODF 1.0 includes a "Conformance Clause", (Section 1.5) that was designed and included in the specification exactly so that the billions of binary legacy documents could be converted into ODF XML.

      The problem with the ODF Conformance Clause is that the leading ODF application, OpenOffice,  does not fully support and implement the Conformance Clause. 

      The only foreign elements supported by OpenOffice are paragraphs and text spans.  Critically important structural document characteristics such as lists, fields, tables, sections and page breaks are not supported!

      This leads to a serious drop in conversion fidelity wherever MS binaries are converted to OpenOffice ODF.

      Note that OpenOffice ODF is very different from MSOffice ODF, as implemented by internal conversion plugins like da Vinci.  KOffice ODF and Googel Docs ODF are all different ODF implementations.  Because there are so many different ways to implement ODF, and still have "conforming" ODF documents, there is much truth to the statement that ODF has zero interoperabiltiy.

      It's also true that OOXML has optional implementation areas.  With ODF we call these "optional" implementation areas "interoperabiltiy break points" because this is exactly where the document exchange  presentation fidelity breaks down, leaving the dominant market ODF applicaiton as the only means of sustaining interoperabiltiy.

      With OOXML, the entire Vista Stack - Win32 dependency layer is "optional".  No doubt, all MSOffice - Exchange/SharePoint Hub applications will implement the full sweep of proprietary dependencies.    This includes the legacy Win32 API dependencies (like VML, EMF, EMF ), and the emerging Vista Stack dependencies that include Smart Documents, XAML, .NET 3.0 Libraries, and DrawingML.

      MSOffice 2007 i
  • ...6 more annotations...
  • Microsoft's backwards compatibility priority means the company made XML-based format decisions that compromise the open objectives of XML. Open Office XML is neither open nor XML.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      True, but a tricky statement given that the proprietary OOXML implementation is "optional".  It is theoretically possible to implement Ecma 376 without the prorpietary dependencies of MSOffice - Exchange/SharePoint Hub - Vista Stack "OOXML".

      In fact, this was first demonstrated by the legendary document processing - plugin architecture expert, Florian Reuter.

      Florian has the unique distinction of being the primary architect for two major plugins: the da Vinci ODF plugin for MSOffice, and, the Novell OOXML Translator plugin for OpenOffice!

      It is the Novell OOXML Translator Plugin for OpenOffice that first demonstrated that Ecma 376 could be cleanly implemented without the MSOffice application-platform-vendor specific dependencies we find in every MSOffice OOXML document.

      So while Joe is technically correct here, that OOXML is neither open nor XML, there is a caveat.  For 95% of all desktops and near 100% of all desktops in a workgroup, Joe's statment holds true.  For all practical concerns, that's enough.  For Microsoft's vaunted marketing spin machine though, they will make it sound as though OOXML is actually open and application-platform-vendor independent.


  • Microsoft got there first to protect Office.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      No. I disagree. Microsoft needs to move to XML structured documents regardless of what others are doing. The binary document model is simply unable to be useful to any desktop- to server- to device- to the web- transport!

      Many wonder what Microsoft's SOA strategy is. Well, it's this: the Vista Stack based on OOXML-Smart Documents-.NET.

      The thing is, Microsoft could not afford to market a SOA solution until all the proprietary solutions of the Vista Stack were in place.

      The Vista Stack looks like this:

      ..... The core :: MSOffice <> OOXML <> IE <> The Exchange/SharePoint Hub

      ..... The services :: E/S HUb <> MS SQL Server <> MS Dynamics <> MS Live <> MS Active Directory Server <> MSOffice RC Front End

      The key to the stack is the OOXML-Smart Documents capture of EXISTING MSOffice bound business processes and documents.

      The trick for Microsoft is to migrate these existing business processes and documents to the E/S Hub where line of business developers can re engineer aging desktop LOB apps.

      The productivity gains that can be had through this migration to the E/S Hub are extraordinary.

      A little over a year ago an E/S Hub verticle market application called "Agent Achieve" came out for the real estate industry. AA competed against a legacy of twenty years of contact management based - MLS data connected desktop shrinkware applications. (MLS-Multiple Listing Service)

      These traditional desktop client/server productivity apps defined the real estate business process as far as it could be said to be "digital".  For the most part, the real estate transaction industry remains a paper driven process. The desktop stuff was only useful for managing clients and lead prospecting. No one could crack the electronic documents - electonic business transaction model.  This will no doubt change with the emer
  • By adapting XML
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      The requirements of these E/S Hub systems are XP, XP MSOffice 2003 Professional, Exchange Server with OWL (Outlook on the Web) , SharePoint Server, Active Directory Server, and at least four MS SQL Servers!

      In Arpil of 2006, Microsoft issued a harsh and sudden End-of-Life for all Windows 2000 - MSOffice 2000 systems in the real estate industry (although many industries were similarly impacted). What happened is that on a Friday afternoon, just prior to a big open house weekend, Microsoft issued a security patch for all Exchange systems. Once the patch was installed, end users needed IE 7.0 to connect to the Exchange Server Systems.

      Since there is no IE 7.0 made for Windows 2000, those users relying on E/S Hub applications, which was the entire industry, suddenly found themselves disconnected and near out of business.

      Amazingly, not a single user complained! Rather than getting pissed at Microsoft for the sudden and very disruptive EOL, the real estate users simply ran out to buy new XP-MSOffice 2003 systems. It was all done under the rational that to be competitive, you have to keep up with technology systems.

      Amazing. But it also goes to show how powerfully productive the E/S Hub applications can be. This wouldn't have happened if the E/S Hub applications didn't have a very high productivity value.

      When we visited Massachusetts in June of 2006, to demonstrate and test the da Vinci ODF plugin for MSOffice, we found them purchasing en mass E/S Hubs! These are ODF killers! Yet Microsoft sales people had convinced Massachusetts ITD that Exchange/SahrePoint was a simple to use eMail-calendar-portal system. Not a threat to anyone!

      The truth is that in the E/S Hub ecosystem, OOXML is THE TRANSPORT. ODF is a poor, second class attachment of no use at the application - document processing chain level.

      Even if Massachusetts had mandated ODF, they were only one E/S Hub Court Doc
  • Microsoft can offer businesses many of the informational sharing and mining benefits associated with the markup language while leveraging Office and supporting desktop and server products as the primary consumption conduit.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      Okay, now Joe has the Micrsoft SOA bull by the horns.  Why doesn't he wrestle the monster down?
  • Microsoft will vie for the whole business software stack, a strategy that I believe will be indisputable by early 2009 at the latest.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      Finally, someone who understands the grand strategy of levergaing the desktop monopoly into the converged space of server, device and web information systems.

      What Joe isn't watching is the way the Exchange/SharePoint Server connects to MS SQL Server, Active Directory Server, MS LIve and MS Dynamics.

      Also, Joe does not see the connection between OOXML as the portable XML document/data transport, and the insidiously proprietary Smart Documents metadata - data binding system that totally separates MSOOXML from Ecma 376 OOXML!
  • I'm convinced that Office as a platform is an eventual dead end. But Microsoft is going to lead lots of customers and partners down that platform path.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      Yes, but the new platform for busines process development is that of MSOffice <> Exchange/SharePoint Hub.

      The OOXML-Smart Docs transport replaces the old binary document with OLE and VBA Scripts and Macros functionality.  Which, for the sake of brevity we can call the lead Win32 API dependencies.

      One substantial difference is that OOXML-Smart Docs is Vista Stack ready, while the Win32 API dependencies were desktop bound.

      Another way of looking at this is to see that the old MSOffice platform was great for desktop application integration.  As long as the complete Win32 API was available (Windows MSOffice VBA run times), this platform was great for workgroups.  The Line of Business integrated apps were among the most brittle of all client/server efforts, bu they were the best for that generation.

      The Internet offers everyone a new way of integrating data, content and streaming media.  Web applications are capable of loosly coupled serving and consuming of other application services.  Back end systems can serve up data in a number of ways: web services as SOAP, web services as AJAX/REST, or XML data streams as in HTTPXMLRequest or Jabber P2P model.

      On the web services consumption side, it looks like AJAX/REST will be the block buster choice, if the governance and security issues can be managed.

      Into this SOA mash Microsoft will push with a sweeping integrated stack model.  Since the Smart Docs part of the OOXML-Samrt Docs transport equation is totally proprietary, but used throughout the Vista Stack, it will provide Microsoft with an effective customer lockin - OSS lockout point.

  • Gary Edwards on 15 Jul 07
     
    Great article series from eWeek.  A must read.  But it all comes down to interoperability across two stack models:  The Microsoft Vista Stack, and an alternative Open Stack model that does not yet exist!

    Incompatible formats become a nightmare for the kind of integration any kind of SOA implementation depends on, let alone the Web 2.0 AJAX MashUps this article focuses on.

    I wonder why eWEEK didn't include the Joe Wilcox Micrsoft Watch Article, "Obla De OBA Da".  Joe hit hard on the connection between OOXML and the Vista Stack.  He missed the implications this will have on MS SOA solutions.  Open Source SOA solutions will be locked out of the Vista Stack.  And with 98% or more of existing desktop business processes bound to MSOffice, the transition of these business processes to the Vista Stack will no doubt have a dramatic impact on the marketplace.  Before the year is out, we'll see Redmond let loose with a torrent of MS SOA solutions.  The only reason they've held back is that they need to first have all the Vista Stack pieces in place.

    I don't think Microsoft is being held back by OOXML approval at ISO either.  ISO approval might have made a difference in Europe in 2006, but even there, the EU IDABC has dropped the ISO requirement.  For sure ISO approval means nothing in the US, as California and Massachusetts have demonstrated. 

    All that matters to State CIO's is that they can migrate exisiting docuemnts and business processes to XML.  The only question is, "Which XML?  OOXML, ODF or XHTML+".

    The high fidelity conversion ratio and non disruptive OOXML plugin for MSOffice has certainly provided OOXML with the edge in this process. <br
Gary Edwards

The future of XML - 0 views

www.ibm.com/...x-xml2008prevw.html

odf ooxml xhtml xml

shared by Gary Edwards on 07 Mar 08 - Cached
  • Of course, the most important conversion isn't from OpenDoc to OOXML or vice versa: it's a down conversion from either OpenDoc or OOXML to XHTML. The HTML exporters in OpenOffice and Microsoft Office are uniformly atrocious. Look for third-party developers to pick up the slack. Most important, look for individual corporate developers and webmasters to begin publishing custom templates for their sites. This will enable regular folks to write in Microsoft Word as they're accustomed to doing and then upload their musings straight into the local content-management system. Editing and reviewing tools can be built right in. Because machines generate all the markup (the humans see the GUI interface they're used to), well-formedness will be a freebie. The majority of the Web won't be well-formed by the end of 2008, but a larger percentage will be than today.
Gary Edwards

Q&A: Nicholas Carr on the big switch to utility computing - 0 views

www.computerworld.com/...article.do

carr cloud switch utility web-platform

shared by Gary Edwards on 25 Jan 08 - Cached
  • I think we’re at the early stages of a fundamental shift in the nature of computing, which is going from something that people and businesses had to supply locally, through their own machines and their own installed software, to much more of a utility model where a lot of the computer functions we depend on are supplied from big, central stations, big central utilities over the Internet.
liza cainz

Comprehensive Help and Support for Computer Beginners - 1 views

I am a beginner when it comes to computer stuff. I really had a difficulty of mastering a digital machine like computers partly because there is no one who can teach me. I am really eager to know h...

support service Desktop computer technical services PC tech

started by liza cainz on 08 Feb 11 no follow-up yet
1 - 7 of 7
Showing 20▼ items per page