![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm looking for any references, discussion or theory about hierarchical models for situations such as residential addresses, geopolitical subdivisions, corporate structures, military ranks, file systems, type systems, etc. |
|
I'm specifically interested in models that can recognize partial correlations between subtrees, e.g. most/all countries have cities, [...] |
#3
| |||
| |||
|
|
Nilone wrote: I'm looking for any references, discussion or theory about hierarchical models for situations such as residential addresses, geopolitical subdivisions, corporate structures, military ranks, file systems, type systems, etc. Do you mean something like this? ftp://ftp.software.ibm.com/software/...sted_rdbms.pdf |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Nilone wrote: I'm looking for any references, discussion or theory about hierarchical models for situations such as residential addresses, geopolitical subdivisions, corporate structures, military ranks, file systems, type systems, etc. Do you mean something like this? *ftp://ftp.software.ibm.com/software/...apers/nested_r.... |
|
I'm specifically interested in models that can recognize partial correlations between subtrees, e.g. most/all countries have cities, [...] What does that mean? *Should the data model itself express such quantitative correlations, or only the query language? -- Reinier |
#6
| |||
| |||
|
|
It seems to me that these organizational structures can be modeled as trees where every node is typed and every node can have children, but the parent/child relationship is not an attribute of the type of the parent. *The entire tree forms a domain such that valid values of the domain are paths from the root of the tree to any leaf. If you take the types and values of the nodes through which such a path passes / is constructed, you get something that looks like a tuple, except that the presence of certain attributes depends on the values of other attributes. I see some resemblance to parsing regular expressions. |
#7
| |||
| |||
|
|
On Aug 16, 3:09*am, Nilone <rea... (AT) gmail (DOT) com> wrote: It seems to me that these organizational structures can be modeled as trees where every node is typed and every node can have children, but the parent/child relationship is not an attribute of the type of the parent. *The entire tree forms a domain such that valid values of the domain are paths from the root of the tree to any leaf. If you take the types and values of the nodes through which such a path passes / is constructed, you get something that looks like a tuple, except that the presence of certain attributes depends on the values of other attributes. I see some resemblance to parsing regular expressions. That would be XML -- a robust and well established data model applied universally to any problem. |
|
So are you looking into theory of parsing? This one has been developed in little to none database context, of course. Or is it transitive- like query of binary relation in database context (http:// en.wikipedia.org/wiki/Hierarchical_model)? |
#8
| |||
| |||
|
|
On Aug 16, 7:16*pm, Tegiri Nenashi <tegirinena... (AT) gmail (DOT) com> wrote: That would be XML -- a robust and well established data model applied universally to any problem. XML can represent it, yes. *I'll investigate further in this direction. |
#9
| |||
| |||
|
|
On Aug 16, 1:21*pm, Nilone <rea... (AT) gmail (DOT) com> wrote: On Aug 16, 7:16*pm, Tegiri Nenashi <tegirinena... (AT) gmail (DOT) com> wrote: That would be XML -- a robust and well established data model applied universally to any problem. XML can represent it, yes. *I'll investigate further in this direction. Well, you missed two subtle points. First, I borrowed the word "robust" from some computer climate modeler who used it dozen times in his last paper. Second, XML is far from being a just a data model, let alone "well established" one. To make it crystal clear, I was kidding in the XML part of my message; the other part was serious. |
![]() |
| Thread Tools | |
| Display Modes | |
| |