Monthly Archives: November 2008

How do you say CMIS?

While I’ve been saying “see em eye ess” for CMIS up to this point, I’ve discovered that others are pronouncing CMIS “see miss” instead.

  • One’s pronunciation of SQL has been offered in support of pronouncing CMIS (i.e. “see qul” versus “ess queue el”). (I say “see qul;” so perhaps I should be saying “see miss.”)
  • Using the shortest pronunciation possible as measured by number of syllables has been offered in support of “see miss” (i.e. two versus four syllables).
  • Conjunctives like CMIS-enabled, CMIS-ready, etc. has been offered in consideration of “see miss.” On other hand, “see em eye ess” may be better in conversation with someone not yet familiar with the standards effort.
  • One’s locale and native language has also been offered in support of “see em eye ess” (e.g. easier to understand in conversation with non-native speakers by avoiding use of two common English words, which can be hard to parse in the middle of a sentence for someone not already used to the meaning).
  • Pop culture features shows like CSI, SVU and NCIS. Initialism applies to these shows (e.g. you don’t hear “see sci” or “en sis”). Therefore, …

So, how do you say CMIS? :-)

P.S. Yes, this is completely unimportant in every technical aspect where the standards effort around CMIS is concerned. Nevertheless, consistent identity, including pronunciation matters, and the standards effort is just getting started…

P.P.S. Happy Thanksgiving!

Intelligent capture

Today, EMC announced new releases of EMC Captiva products (i.e. EMC Captiva InputAccel 6.0 and EMC Captiva Dispatcher 6.0). I want to address the benefits of service-oriented infrastructure related to capture as embodied by these new releases.

The big deal with SOA and InputAccel 6.0 (IA6) is the connectivity it enables with other enterprise applications.

Capture depends heavily on validation of the captured data so access to systems that can supply information based on an extracted value or can perform the validation of extracted values is necessary. Service-orientation in IA6 lets capture be part of a company’s composite TCM applications.

Prior to the release of IA6, capture systems “connectivity” was restricted to ODBC, dropping files on file shares, and/or duplicating validation rules in software.

Another potentially big deal is the exposure of Captiva’s capture functionality to other applications (e.g. a web service for importing data into Captiva).

Today Captiva takes (captures) data from scanners, email, fax machines and legacy systems using specialty importers and file shares. Using web services will reduce complexity by allowing for a single method to be used to take in data from all kinds of systems.

Capture processing tends to occur in large batches; so, the “queue” behavior of a file share is useful. However, it lacks a handshake when the data has been picked up.

A web service would be more likely to be used by an interactive process or could be used as a call-back with the file share method to give a handshake.

It will be interesting to see how service-orientation within capture takes hold.

I want to thank my colleague, Clay Mayers, Captiva CTO, for contributing to this post. (Ah, another potential CMA blogger target… :-) )

Hello donr7n

My colleague, Don Robertson, has finally succumbed to my constant encouragement (er, barrage) to blog publicly. Even better, Don’s put several of his previously behind-a-firewall posts into the public domain. If you want to know about business objects, aspects, smart containers, etc. in the EMC Documentum ECM platform, you’ll definitely want to subscribe to Don. I have. :-)


On Monday EMC announced Atmos. While I was in flight, returning from a short vacation, a number of my EMC colleagues blogged about this new offering. I’d like to draw your attention to their posts as follows:

  • Steve Todd first offers, among other things, a concise definition of Cloud Optimized Storage (COS): “global storage with a policy focus.” He continues in a follow-up post by delving into more details concerning the “special sauce” of Atmos (i.e. its use of global policies). I have the strong sense that more posts will come from Steve regarding Atmos in the not too distant future, too.
  • Barry Burke: “Atmos seeks to blaze a new approach to “cloud” storage (oh how I hate that term), to create a global storage platform that is not only cost-effective to install and grow, but extremely efficient to operate as well…set-it-and-forget-it cloud storage. And trust me, if your business thinks in petabytes or even exabytes of unstructured data, you’re already looking for a totally new storage paradigm, because nothing – and I mean NOTHING – built on current commercial file systems or databases will handle that kind of storage.”
  • After some humorous precursor posts, Mark Twomey dives into Atmos by relaying his conversation with one of the Atmos architects, Dr. Patrick Eaton, who was also involved in OceanStore.
  • Dave Graham talks about what Atmos is and is not and then covers the underlying architecture of Atmos.
  • Last but not least, Chuck Hollis provides his perspective on Atmos, drawing in other commentary from the web in the process.