Versioning will finally boil down to whether content, or an attribute of
some content, is added or changed. An attribute of an element may be
content to another, and so on... The workflow issues are: Do I have the
latest version? What is the history of the content? How do my changes
and comments get published and reported to collaborators?
Is a system that is built around or emerges from the kernal an
Application? Maybe a piece of it is a subsystem. Some of the naming I
may have seen in Augment used a descriptive name followed by the word
subsystem to categorize a functionality. I like it when there is a real
descriptive name for the thing. What does it do? How can you help the
user exploit its features by choosing the name(s)?,)
Looking forward to seeing node descriptions;
Thank You,
Joe
Alternative Interface Devices.
Improve Accessibility and Utility of the WWW...
-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/2/_/444287/_/973348331/
---------------------------------------------------------------------_->
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 : Sat Nov 04 2000 - 06:42:18 PST