<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I have posted a question to today’s Adobe Connect session, just to
signal the question, and not to get an answer there. <br>
The question is: <b><i>Does anyone in the working group have
knowledge of octree data management techniques?</i></b> <br>
The technique holds promise for how the end product of this rds-pdp
working group might be implemented. <br>
Octree data management techniques are already used in Internet
infrastructures (to reduce collisions etc.).<br>
<br>
I am doing some tiny work with <i>non-destructive archaeology</i>
(think of opening up a tomb or crypt, installing a “Mars Rover”
type facility, sealing up the tomb and collecting data remotely).<br>
Octree database techniques are increasingly being considered in
archaeology as a way of archiving data for wider access and allow
levels of gated access.<br>
Most archaeologists cannot physically access a site (certainly not
all at once) and the approach both protects the integrity of the
site, and opens a more level playing field for archaeology research.
<br>
<br>
One additional advantage of using an octree technique, rather than
common database management techniques, is that users can further tag
data as it relates to their individual uses.<br>
Those tags are simply a extension further down the octree tree,
where the tags are integral to the subsets of the data assembled by
the users, and tied to the work they are engaged in. <br>
My impression is that at the Registrar/Registry level this is no
more difficult to implement than a relatively flat standard
database, but is rich in the range of applications it supports. <br>
<br>
Sam L. <br>
<br>
<br>
</body>
</html>