New name(s) for iBO

Is it just me, or are all the "business object" named things starting to become confusing? Here's the ones I can count:

  • The original COM-based iBO
  • iBO for .NET
  • The core Business Objects which make up iMIS
  • Business Object Builder, Business Object Architect, Business Object Designer, or whatever else it becomes
  • Stephen Moseley's iBO Wrapper
  • The Active Matter iBO Wrapper
  • Any business objects which we create in the future for interacting with iMIS. When you have some for iMIS and some not, it's natural to describe the ones for iMIS as "the iMIS business objects".
  • Business Objects, the company who bought Crystal Reports. (Now themselves owned by SAP)
  • Sony's robotic dog

I know COM iBO is on its way to a well-deserved oblivion, but it will still be around to talk about for quite a while. Some of the others aren't serious problems. It mostly comes down to distinguishing COM iBO from iBO-for-.NET from the core business objects. These are at least manageable in print if you're consistent (COM iBO, iBO for .NET, Core BOs), but try talking about them over the phone -- you have to over-specify every time, which gets old for both the speaker and the listeners.

Has anyone thought about a better naming convention? I recognize that they are all to varying degrees "business objects", and that legal and marketing won't be happy unless the brand name is in there. No perfect solution, I'm sure. The confusion seems to come up every time any two iBO-like components are mentioned in the same breath.

How about calling one or the other part the "iMIS API"? I know one of the help files for COM-iBO is named iBO_API.chm, so maybe that's a natural name to use. It may also help to refer to the core business objects as simply "iMIS Core", with the optional subtext for the geeks that the core consists of business objects (little b, little o).

Any other suggestions? Does ASI marketing have any ideas in the works? I'd like to start training my tongue as soon as possible. How many years have I been an Authorized iMIS Solution Provider, yet "iMIS Reseller" is still more natural to say.

I'll wrap up with some lovely haiku written a couple of years ago by my good friend Jeff Spring. It is perhaps less accurate than before, but still speaks to the very essence of what COM-iBO has meant to so many of us...

iBO will be dead
replaced by iMIS 15
in death it is fixed

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Who knew?

Bruce,

Nice haiku - who knew you had it in you?

I agree that the iMIS API is probably the way to go - I often call it that now.

-Sig

Sig VanDamme
VanDamme Associates
AiSP

Pretty good post there good

Pretty good post there good buddy and I totally agree with you. There is just too many components names that people get confused.

We should just refer to it as as iBO or as it was mentioned iMIS API.

Business Object Builder, Business Object Architect, Business Object Designer is simply a mess mostly because one in iMIS 10.6 the Bob was built not to build iBO objects but rather a totally seperate set of code which i refer to as IQA business objects which depended on the 1.1 .NET framework. This is before iBO for .NET even existed right?

What is the new version of the eCM suppose to be called? you know the one 100% built on .NET. If it is called eCM for .NET my head will spin. First off ASI please show me a content manager system that is not electronic or web based and I will show you what I call a 3 drawer file cabinet . So lets just drop their "e" and ".net" on all the components since it is already implied. Naming something based on the technology behind it is soooooo 90's

This goes for all the "Wrapper" products that are out there... Isn't it implied? Isn't iBO for .NET nothing more then a Wrapper of .NET is some respects everything is inherited by the 'object' class. One of the pillars and important aspects of OO is the fact you and inheritance and Encapsulation, we get it people ;)