Hi, Why is "item" field of Item_tree of type List<Item>? I feel that it is causing a litle bit of overlap betwen Item_tree and item_table. Item_table has a rows property with type List<Cluster>, which is nice for representing multi column tables, but when it comes to a single column table, item_tree also seem to allow it, by using a List<Element> given that items property is List<Item> Would not it be better to enforce semantics of a tree structure by making item property of Item_tree a single Cluster ? Then the meaning of the elements of the cluster would be enforced by the container class, item_tree, where each member of cluster (whether cluster or element) would mean a new row in a tree. This would also force a tree with a single parent node, but it would still allow expression of a tree. Not a big deal, but I think it would be better to force the semantics of a type to make its use as clear as possible. Care to show me if I'm missing something? :)
Kind regards Seref -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090401/0f110511/attachment.html>
