[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
- To: <tribble>
- Subject: FromNess, ToNess
- From: Ravi Pandya <ravi>
- Date: Wed, 31 Jan 90 12:03:52 PST
- Cc: <mark>, <bobp>, <xanatech>
- In-reply-to: <Eric>,40 PST <9001311947.AA28872@xanadu>
Date: Wed, 31 Jan 90 11:47:40 PST
From: tribble (Eric Dean Tribble)
The following are questions and comments that came off the top of my
head. I'm pretty certain that we will want to provide B&O, but I'm
happy to resolve this *after* we ship.
Does Docs&Links support unification? inform? forwarding documents (for
partial data)? archiving? Unless D&L ends up being a superset of B&O,
achiving will require B&O. So will BeBe.
All of these are things that should eventually be in D&L, since users
will want to employ them in the context of the standard objects and
interfaces. Because of the standard D&L objects are built out of the
general D&L objects, they will then be able to do these things with
non-standard objects as well. Manana...