Re: Finding groupings

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

From: Garry Petrie (gp_at_europa.com)
Date: Tue Feb 13 2001 - 22:04:56 CET 

Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id WAA01488 for cavexml-outgoing; Tue, 13 Feb 2001 22:14:57 +0100
Received: from io.europa.com (IDENT:root_at_io.europa.com [216.65.131.2]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id WAA01484 for <cavexml_at_cartography.ch>; Tue, 13 Feb 2001 22:14:56 +0100
Received: from europa.com (ip85.gte15.rb1.bel.nwlink.com [209.20.244.85]) by io.europa.com (8.11.1/8.11.1) with ESMTP id f1DLEsE16575 for <cavexml_at_cartography.ch>; Tue, 13 Feb 2001 13:14:54 -0800 (PST)
Message-ID: <3A89A178.6060806@europa.com>
Date: Tue, 13 Feb 2001 13:04:56 -0800
From: Garry Petrie <gp_at_europa.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20001108 Netscape6/6.0
X-Accept-Language: en,pdf
To: cavexml_at_cartography.ch
Subject: Re: Finding groupings
References: <200102081326.OAA29149_at_karto.ethz.ch> <3A85A949.1DCBD783_at_xmission.com> <3A8617A3.1050504_at_europa.com> <3A879934.44D4C90D_at_xmission.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

Paul & Eleanor wrote:

>
> I will continue to demonstrate that I think you must be making some extra
> assumptions. May I suggest when you do think of one, you ask if I was assuming
> such a thing, instead of accusing me and thus putting me on the defensive.

Do not allow for assumptions, be concise.

> The only thing I am assuming is that when any processing software
> sees <group name=" " type=" " > it means that all of whatever is within
> the group, i.e. before the closing </group> tag, can be referred to by
> the type/name pair defined as the attributes of that group.
> Nested groups? That introduces an additional name, now all points
> could be referred to by either type/name pair that is now in scope.
> A group within a group is a convenience of the markup language, not an
> implied hierarchy of names. For example:
>
> <group name="Entrance Room>
> ...
> <group name="Connection Pit"
> ...
> </group>
> ...
> </group>
> ....
> <group name="Lower Level">
> ...
> <group name="Connection Pit">
> ...
> </group>
> ...
> </group>

I must admit I assumed groups were hierachical. Why not assign the group names as
attributes to the shots or stations, certainly an object can have several attributes of
the same type?

Garry Petrie

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:01 CET