A single praragraph contains a design note,
a business model, and a feature requirement.
It was originally offered in a single
category, or with none at all.
It must be possible to assign the categories
retroactively. The node must either be broken up
into pieces to do that, or a node must have the
ability to belong to multiple categories.
That tends to imply that categories are *lists*
rather than attributes of a node. (It is either
a list of attributes in the node, or an external
list which has the node as a member.)
When I recategorize (additionally categorize) a
node, the revisions I made to the category list
don't necessarily exist as a separate "document",
yet the changes I make need to be transmitted
to others (assuming a distributed email model or
a client-copy/server-copy model).
------------------------------------------------------------------------
1.6 Million Digital Images!
Download one Today from Corbis.com
http://click.egroups.com/1/3353/3/_/444287/_/955600052/
------------------------------------------------------------------------
Community email addresses:
Post message: unrev-II@onelist.com
Subscribe: unrev-II-subscribe@onelist.com
Unsubscribe: unrev-II-unsubscribe@onelist.com
List owner: unrev-II-owner@onelist.com
Shortcut URL to this page:
http://www.onelist.com/community/unrev-II
This archive was generated by hypermail 2b29 : Wed Apr 12 2000 - 21:34:58 PDT