From: Richard Knapp (richfk_at_attglobal.net)
Date: Fri Jul 12 2002 - 22:11:38 CEST
Return-Path: <owner-cavexml-outgoing_at_ethz.ch> Delivered-To: cavexml-archive_at_cartography.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 36E3214A3E for <cavexml-outgoing_at_ethz.ch>; Fri, 12 Jul 2002 22:30:41 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 1325613BCE; Fri, 12 Jul 2002 22:30:39 +0200 (CEST) Delivered-To: cavexml-loopcheck_at_ethz.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id BD6EE14A3E for <cavexml-loopcheck_at_ethz.ch>; Fri, 12 Jul 2002 22:30:37 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 9248A8A98; Fri, 12 Jul 2002 22:30:35 +0200 (CEST) Delivered-To: cavexml_at_cartography.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 15D6C14A3E for <cavexml_at_cartography.ch>; Fri, 12 Jul 2002 22:30:35 +0200 (CEST) Received: from prserv.net (out2.prserv.net [32.97.166.32]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 33EBF7D8C for <cavexml_at_cartography.ch>; Fri, 12 Jul 2002 22:30:30 +0200 (CEST) Received: from Muphin (slip-12-65-12-114.mis.prserv.net[12.65.12.114]) by prserv.net (out2) with SMTP id <2002071220194520204gm660e>; Fri, 12 Jul 2002 20:19:45 +0000 From: "Richard Knapp" <richfk_at_attglobal.net> To: "cavexml_at_cartography.ch" <cavexml_at_cartography.ch> Date: Fri, 12 Jul 2002 16:11:38 -0400 (EDT) X-Mailer: PMMail 2.20.2380 for OS/2 Warp 4.5 In-Reply-To: <3D2F06FE.7090606_at_xmission.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: comments on the data model Message-Id: <20020712203030.33EBF7D8C@karmail.ethz.ch> X-Loop: cavexml Sender: owner-cavexml_at_karmail.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch X-Virus-Scanned: by AMaViS perl-11
On Fri, 12 Jul 2002 10:42:38 -0600, P A Hill & E V Goodall wrote:
> Richard Knapp wrote:
>
> > <Closure using="LeastSquares" azimuth="92.5"
>
>
> Two problems with this particular notation.
> (1) very verbose
> and
> (2) doesn't provide complete information
> [snip]
This was not meant to be the final result, just an example.
> > This would allow multiple closing methods to be applied to a
> > cave/system and not overwrite each other. All necessary spherical
> > coordinate data would be part of that element (as children or
> > attributes).
> Seems like a good idea, but keep in mind that if we talk about
> what things are needed before talking format we might have a better
> chance of collecting up a longer list of what we want in the format
> before trying to work out compactness or organization. That is at least
> the approach the list is in at this time.
The issue I was trying to raise - apparently unsuccessfully - was
with the duplication of Measurements and trying to store "Corrected"
data. A previous point had discussed adding another attribute to the
Measurement Element. However, with multiple Measurements of the same
type/item, how would that work?
> >>>Measurements
> >>>already have a cvalue (or at least did for a while) to store the
> >>>canonical value of the measurement. Why not have a similar attribute
> >>>for corrected values?
>
>
> Hmm, whose is more correct: my value or yours? At first glance picking
> from a list of multiple XYZ seems to be a different problem than
> having a dataset that has multiple calculated XYZs. But maybe there
> is something to the analogy.
Which value? The "cvalue"?
The attempt to have names on the Closure Element was so you could
pick from a list which you wanted to view.
Whatever is chosen, it would be nice to still have the capability to
merge files without really merging them. For instance, if I wanted to
specify where the entrance was for a project you were working and
compare how close it was to my project, I wouldn't have to copy and
alter either file; I could just create a new CaveXML file (like a
Make file) to hold URLS to both datasets. The results could then be
compiled (or linked or whatever) so the data could be viewed at one
time.
Hmmmm... How would coordinates be stored for this situation?
This archive was generated by hypermail 2b30 : Wed Jul 31 2002 - 23:00:00 CEST