From: Richard Knapp (gyp_caver_at_yahoo.com)
Date: Wed Feb 07 2001 - 22:39:36 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id XAA22752 for cavexml-outgoing; Wed, 7 Feb 2001 23:36:36 +0100 Received: from smtp1b.mail.yahoo.com (smtp3.mail.yahoo.com [128.11.68.135]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id XAA22745 for <cavexml_at_cartography.ch>; Wed, 7 Feb 2001 23:36:34 +0100 Message-Id: <200102072236.XAA22745@karto.ethz.ch> Received: from slip166-72-184-40.nc.us.prserv.net (HELO Muphin) (166.72.184.40) by smtp.mail.vip.suc.yahoo.com with SMTP; 7 Feb 2001 23:43:46 -0000 X-Apparently-From: <gyp?caver_at_yahoo.com> From: "Richard Knapp" <gyp_caver_at_yahoo.com> To: "cavexml_at_cartography.ch" <cavexml_at_cartography.ch> Date: Wed, 07 Feb 2001 16:39:36 -0500 (EST) X-Mailer: PMMail 2.10.1999 for OS/2 Warp 4.00 In-Reply-To: <3A818D56.45C0B540_at_earthlink.net> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: re:Groupings Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
>I submit that we've been using an incorrect term. What we seem to mean
>by Groupings is in reality referred to as a "view" in data modeling
>vernacular. I.e. Groupings are "logical" views of data, that is stored
>in some "physical" model.
Excellent! I think you (and Garry) are correct.
>>What we do not want is to embed the actual
>>measurements of length, bearing, inclination, whatever, in more than
>>one place.
>Here, here...
Second..
>>For the
>>gourpings advocates, show me a method that does not repeat data, but
>>allows the objects to be members of more than one group.
>And this is what a view should provide for you, no repetition of data,
>but it lets you see your data the way you want to look at it. Remember,...
So would a view of the data be done via a separate file (ick!), an XSL (?) transform (unlikely), or ? I
would say that information would still have to be stored in the main data file. Maybe it could be
broken into sections; one for the data, one for views, another for ?.
>done with such things like XSLT, a method of translating one physical
>model into another (yuch), or in the application layer where a
>cave-survey display-tool draws the line plots you want to see (e.g.
>morphologic view, time sequential view, cave cricket view, etc.)
XSLT is great for turning one format into another. Granted, that is nothing more than a view into
the data. However, it seems kind of an ugly way to handle things.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:00 CET