Difference between revisions of "Talk:The nodal model"
From Organic Design wiki
(Parents-children) |
m |
||
(2 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
I can then do a Jack-reduction thingy. -- [[User:Jack|Jack]] 13:55, 20 Aug 2006 (NZST) | I can then do a Jack-reduction thingy. -- [[User:Jack|Jack]] 13:55, 20 Aug 2006 (NZST) | ||
+ | :Just doin' a bit of spring cleaning ;-) | ||
+ | :I've actually updated the parent-child stuff (there was a comment following it which warned that it may be removed). | ||
---- | ---- | ||
+ | *The following are two important principles | ||
+ | |||
+ | **the architecture | ||
+ | |||
+ | Nodal Network <--> Peer <--> Nodal Space <--> List Space | ||
+ | |_ _ reduction _-^ ^| Relative Traversal binary trei | ||
+ | |||
+ | **unifying principles that they all adhere to, ie a peer will behave in its own network environment in the same way that relative traversal will deal with the data structure. | ||
+ | |||
+ | *build a document that looks like this layout: | ||
+ | |||
+ | | | ||
+ | ||| | ||
+ | ||||| | ||
+ | details | ||
+ | ||||| | ||
+ | ||| | ||
+ | | | ||
+ | |||
+ | where the rows are the first principles, clearly articulated, "why you would want to do it", then towards the middle the different ramifications of those first principles working in concert are explored "what is being done", then toward the end they are brought together again now that the processes are understood, and it is then explained how this knowledge is used "how to use it". | ||
+ | |||
+ | **explain a systems view based on the principle of change, ie one based on harmonics, and changes in those harmonics not having to be gross to be evident, etc. | ||
+ | |||
+ | **including the within-without aspect and the essential (self-)similarity of each level of the process. |
Latest revision as of 19:21, 4 November 2006
These changes represent a real step forward.
Need to work on the parent-children relationship and perhaps try and describe it as orthogonal to the class-instance axis (or prototype-instance), or dimensionally or whatever.
I can then do a Jack-reduction thingy. -- Jack 13:55, 20 Aug 2006 (NZST)
- Just doin' a bit of spring cleaning ;-)
- I've actually updated the parent-child stuff (there was a comment following it which warned that it may be removed).
- The following are two important principles
- the architecture
Nodal Network <--> Peer <--> Nodal Space <--> List Space
|_ _ reduction _-^ ^| Relative Traversal binary trei
- unifying principles that they all adhere to, ie a peer will behave in its own network environment in the same way that relative traversal will deal with the data structure.
- build a document that looks like this layout:
| ||| |||||
details
||||| ||| |
where the rows are the first principles, clearly articulated, "why you would want to do it", then towards the middle the different ramifications of those first principles working in concert are explored "what is being done", then toward the end they are brought together again now that the processes are understood, and it is then explained how this knowledge is used "how to use it".
- explain a systems view based on the principle of change, ie one based on harmonics, and changes in those harmonics not having to be gross to be evident, etc.
- including the within-without aspect and the essential (self-)similarity of each level of the process.