From: Ralph Hartley (hartley_at_aic.nrl.navy.mil)
Date: Fri Feb 16 2001 - 20:48:51 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id UAA21629 for cavexml-outgoing; Fri, 16 Feb 2001 20:45:26 +0100 Received: from sun0.aic.nrl.navy.mil (sun0.aic.nrl.navy.mil [132.250.84.10]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id UAA21625 for <cavexml_at_cartography.ch>; Fri, 16 Feb 2001 20:45:25 +0100 Received: from aic.nrl.navy.mil (pc31.aic.nrl.navy.mil [132.250.84.181]) by sun0.aic.nrl.navy.mil (8.9.3+Sun/8.9.3) with ESMTP id OAA05467 for <cavexml_at_cartography.ch>; Fri, 16 Feb 2001 14:45:33 -0500 (EST) Message-ID: <3A8D8423.2040001@aic.nrl.navy.mil> Date: Fri, 16 Feb 2001 14:48:51 -0500 From: Ralph Hartley <hartley_at_aic.nrl.navy.mil> User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; m18) Gecko/20010124 X-Accept-Language: en To: cavexml_at_cartography.ch Subject: Re: Spanning trees (again) References: <Pine.GSO.4.05.10102131128030.21309-100000_at_cor.oz.cc.utah.edu> <3A899EB4.1090509_at_europa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
Garry Petrie wrote:
> John Halleck wrote:
>
>> Ralph Hartley, in private off list mail, has made a good case for
>> justifying having more than one kind of spanning tree around.
>>
>> Although I feel (and believe that Ralph feels) that having spanning
>> trees around is useful.
>
>
> So a CaveXML file could have multiple spanning trees, which I probably
> would ignore, but I would have to faithfully maintain as meta data
> when I use the file. There is a problem with including calculated
> information from the base elements that has limited appeal, are end
> users forced to propagate the results as meta data? If not, how do you
> decide which elements to discard for which your software does not
> recognize? Do you give the end user the option to filter out elements
> of CaveXML?
Yes, it is perfectly OK to give the user the option to discard (or even
change) data according to any criterion whatsoever.
The user could be allowed to delete (or filer) all XYZ data, all data
produced by program foo, all data this program (or even program foobar)
doesn't use, or all data older than 1972.
Programs don't NEED to have such options, but they may. Trouble only
starts when when the user is given no option, and the default is to
remove something. The asymmetry is because removing data is
irreversible, but preserving it is not.
Ralph Hartley
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:01 CET