Skip to main content

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

Rss Feed Group items tagged

Paul Merrell

Decentralizing the cloud in urban areas -- CellNode M100 - 0 views

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

8 SOA mistakes architects should avoid - 0 views

  • 8 SOA mistakes architects should avoid
  •  
    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.
Gary Edwards

Yahoo BrowserPlus™: Web 3.0 - 0 views

  • BrowserPlus™ is a technology for web browsers that allows developers to create rich web applications with desktop capabilities.
  •  
    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.
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.
Paul Merrell

IBM Press room - 2008-04-30 IBM to Create Alliance With Industry Leaders Supporting Sta... - 0 views

  •  
    IBM) today announced it is creating an alliance program for independent hardware and software vendors to support industry standards for new enterprise data centers, which are dramatically more energy efficient, virtualized, and resilient. The new alliance with top IT companies around the world will enable clients to evolve to new enterprise data centers while offering the widest possible choice of open technologies. The importance of interoperability and open standards for new enterprise data centers -- including those for energy management, virtualization, networking, security, and service management, among others -- is a focal point of this program.
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

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
Xpandion Ltd

Xpandion expand solutions for SAP applications - 0 views

  •  
    Xpandion expand solutions for SAP applications ProfileTailor Suite now available as CLOUD/SAAS as well as classic enterprise software
1 - 8 of 8
Showing 20 items per page