Re: Nested Groupings

New Message Reply About this list Date view Thread view Subject view Author view

From: John Halleck (John.Halleck_at_utah.edu)
Date: Thu Feb 08 2001 - 17:45:18 CET 

Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id RAA31080 for cavexml-outgoing; Thu, 8 Feb 2001 17:44:40 +0100
Received: from cor.oz.cc.utah.edu (nahaj_at_cor.oz.cc.utah.edu [155.99.2.2]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA31076 for <cavexml_at_cartography.ch>; Thu, 8 Feb 2001 17:44:39 +0100
Received: from localhost (nahaj_at_localhost) by cor.oz.cc.utah.edu (8.9.2/8.9.2) with ESMTP id JAA17316 for <cavexml_at_cartography.ch>; Thu, 8 Feb 2001 09:45:18 -0700 (MST)
Date: Thu, 8 Feb 2001 09:45:18 -0700 (MST)
From: John Halleck <John.Halleck_at_utah.edu>
To: cavexml_at_cartography.ch
Subject: Re: Nested Groupings
In-Reply-To: <3A823C42.1040405_at_europa.com>
Message-ID: <Pine.GSO.4.05.10102080941200.15462-100000@cor.oz.cc.utah.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-cavexml_at_karto.baug.ethz.ch
Precedence: bulk
Reply-To: cavexml_at_cartography.ch

On Wed, 7 Feb 2001, Garry Petrie wrote:

> Date: Wed, 07 Feb 2001 22:27:14 -0800
> From: Garry Petrie <gp_at_europa.com>
> Reply-To: cavexml_at_cartography.ch
> To: cavexml_at_cartography.ch
> Subject: Re: Nested Groupings
>
> Paul & Eleanor wrote:
>
> > Garry Petrie wrote:
> >
> >> 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.
> >
> > In the following assume all shots listed as "..." are unique measurements
> > with no repeats. Any interesting additional attributes on
> > the group tag (i.e type) I have left for clarity.
> >
> > I. Nested groupings
> >
> > <group name="Upper Cave">
> > <group name="Entrance Room">
> > ... <!-- in Upper cave and in the Entrance --!>
> > </group>
> > ... <!-- in Upper cave but not in the Entrance --!>
> > </group>
> > ... <!-- somewhere else --!>
> >
> > I hope the above examples make it obvious enough that data doesn't
> > have to be repeated to allow the ability to slap some simple
> > categorization over the shots.
>
> What Paul is suggest is optionally allowing for "horizontal" or "vertial" representations
> of the data. In all of the shots in the "Upper cave and in the Entrance" group, the shots
> would have to have additional information as to who recorded the shots, what were the
> instraments, etc. Personally, I find this sorting un-natural, as it assumes you already
> know the physical relationships of the the data before it is recorded.

  I didn't take Paul's suggestion as that at all.
  All he seems to be doing is taking and existing survey and
  adding markings for name. Places with two names have two markings,
  not repeated data.

  The only difference between the file as it stood before,
  and as it stands now, is the specific group markings that
  Paul added... Nothing else need be changed.

> Again, the example Paul gives is for mutually exclusive groupings, sorted by physical
> location. Now, show me how to group by time in the same file.

  I may have missed the point of the question.

  Existing file:

    linea
    lineb
    linec
    lined
    linee

  Marked file:
   <group time="...">
    linea
    lineb
   </group>
    linec
   <group time="...">
    lined
    linee
   </group>

New Message Reply About this list Date view Thread view Subject view Author view

This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:00 CET