Question:
Is every StructureNode embedded in a StructureLink??
Arguments for/against:
<ul>
<li>Engineering arguments</li>
<ul>
<li>Yes: When programming, all node references can be
treated the same.</li>
<li>Yes: As a result, the programming is simpler.</li>
<li>No: The programming may be simpler, but the data
structures are more complex.</li>
</ul>
<li>Functional arguments</li>
<ul>
<li>Yes: Author can apply relationship categories to
newly written nodes, as well as to references.</li>
<li>No: The functionality isn't needed and isn't worth
the performance/space cost.</li>
</ul>
</ul>
Background:
StrucureNodes that are referenced in another hierarchy
are embedded in a StructureLink. The existence of
that link serves several purposes:
* Set a flag when nodes are traversed, so
the outer system can easily identify cycles.
* Adding categories to the link defines relationships
(whereas adding categories to the node defines
intrinsic properties of the node.)
* Relationships like "comment" or "reply" can be used
to hide the referenced material when the user
doesn't want to see it.
-------------------------- eGroups Sponsor -------------------------~-~>
eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9699/2/_/444287/_/973388287/
---------------------------------------------------------------------_->
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 - 17:48:12 PST