Re: Lotus Notes -- Too much Hype !!!

Paul Everitt (
Thu, 8 Sep 1994 08:51:06 -0500 (CDT)

I'd like to address some of the below, as I think that the Notes vs. WWW
argument is getting more important. A caveat -- by business partner is a
Lotus Certified Notes Specialist and we are Lotus Business Partners.
However, I am a WWW person approaching Notes, so I can see through some
of its models, and appreciate some of its strengths.

Comments interspersed below.

On Thu, 8 Sep 1994, Ravi Kalakota wrote:
> i)Notes uses the compound document architecture (CDA) of DEC,
> which is probably the only implementation of Open Document
> Architecture (ODA). CDA attempts to capture the structure of document
> using a document application profile (DAP), similar to a template in Notes,
> and the layout information and tranform them into a binary bit stream for
> the purpose of document interchange between platforms. To do this it
> uses the notion of memory aggregates which are encoded bit streams of
> what the document contains and looks like. (See Byte 1992 -- Universal
> Content Access for more info.)

>From your below statement ("separation of logical structure from
rendering information"), that _is_ done by Notes, albeit on the server.
There can be multiple representations of the same data, using different
forms. Moreover, technologies such as Notes/FX, and tools such as ViP
and Notes API programs can pick out parts of the information and render
it in any way you choose.

It appears your point is that the client doesn't have choice like in
SGML. That is true -- the decision is made programatically beforehand by
the provider. However, as the great publishing debate on www-talk
several months ago showed, this might be greeted with applause.

> In other words, exchange NOTES is like exchanging binary files, whereas
> exchange HTML files is like passing source code around which can be
> customized or even personalized to the environment you are working in
> at that moment. This is a significant step forward that was never envisioned
> by the world in 1984-90 timeframe when NOTES was conceptualized and built.

See the comments above. Notes is not like passing around binary data.
You can use technologies other than today's standard Notes client (i.e.
ViP, VB/Link, Notes/FX, C API) to extract only the data. However, your
point about allowing run-time choices on the client stands.

> Another drawback of Notes is that CDA (according to a DEC Professional article)
> cannot handle Hypertext links as these would be dropped in the
> encoding process. Well, folks this is a major drawback of Notes that puts the
> HTML on a different plane altogether.

Notes has DocLinks that can connect to other documents on other databases
on other servers, in accordance with the Access Control List.

> 2. Search and Retrieval: Notes can only allow content searching using
> bit-pattern matching techniques. It is quite possible to use HTML
> markup to do more sophisticated searches such as sub-tree retrieval,
> because every HTML document is a tree, and even other sophisticated
> methods that were developed in compiler theory that we have not
> exploited in this environment.

You can comment on the esoterics of indexing theory. I can say that Notes
_today_ (based on Verity's engine -- Nick?? :^) gives full-text retrieval,
weighted hits, and internal highlights. Morevoer, it takes about three
mouse clicks to index a database. Finally, indices can be either
server-side or local (important for the disconected user).

In another vein, by using structured fields and categories, customized
views can be presented that organize content beforehand. Full-text
indexing is wrong, IMHO. Cataloging and classifying lend themselves to
browsing, and tools that simplify this are invaluable.

> My point is that unless Notes does a major rewrite of its software
> using SGML as the underlying document format, it is futile and pointless
> to even compare the two.

Which leads to my next point. It is futile to say that the WWW, as a
corporate solution, is equivalent to HTML. Where in the above have you
mentioned HTTP? So, some other comments:

1) Name one case of an HTTP server talking to another HTTP server

2) Name one case of a WWW user editing a document, and sending it back to
the server

3) Name one case of an active object going to the client, capable of
conditionally executing internal or external code, interacting with the
reader, and sending a result to the server

4) Explain how WWW addresses nomadic users, when all of the programmatic
intelligence is on the server (CGI) and there is no model for
client-server or server-server replication

5) *Today*, Notes has corporate ACL (very robust, point-and-click) with RSA
security, and the tools to administer it

6) Name one client or server that has implemented the Version attribute in
the HTTP spec, thus allowing revision control

7) Notes can be bought from a Fortune 500 company with a support staff,
maintenance agreements, a third-party catalog, and contracts with the
government (I disagree the true importance of any of that, but others
believe it)

I could name WWW technologies that are addressing all of the above,
namely Harvest:
However, asking an MIS to get twenty pieces written by twenty places,
that may or may not compile on your platform, and are an absolute *bitch*
to administer (oh, what even a _curses_ admin interface would do for a
WWW server administrator), might be asking too much.

Funny, I have come off sounding like a Notes zealot, when the opposite is
true -- I think that the popular press is beginning to view "Mosaic"
(snicker) as more than a toy, and a Notes competitor. Notes is too
monolithic, and I don't think the Notes 4 rewrite is going to change its

Well, that's the end of this spiel.

Paul Everitt V 703.785.7384 Email
Connecting Minds, Inc. F 703.785.7385 WWW