From: Paul & Eleanor (goodhill_at_xmission.com)
Date: Wed Feb 14 2001 - 07:20:21 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id HAA03536 for cavexml-outgoing; Wed, 14 Feb 2001 07:16:45 +0100 Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id HAA03532 for <cavexml_at_cartography.ch>; Wed, 14 Feb 2001 07:16:44 +0100 Received: from slc35.modem.xmission.com ([166.70.9.35] helo=xmission.com) by mail.xmission.com with esmtp (Exim 3.12 #1) id 14SvF6-0006vj-00 for cavexml_at_cartography.ch; Tue, 13 Feb 2001 23:16:44 -0700 Message-ID: <3A8A23A5.32D924B0@xmission.com> Date: Tue, 13 Feb 2001 23:20:21 -0700 From: Paul & Eleanor <goodhill_at_xmission.com> X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en 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> <3A89A178.6060806_at_europa.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
Garry Petrie wrote:
> Why not assign the group names as
> attributes to the shots or stations, certainly an object can have
> several attributes of the same type?
Not as actual XML attributes, as in words before equal signs
that appear within the angle brackets.
Going back to my simple note tag.
<note name="Ceiling Tube near the end of the AAA Survey" type="lead">
Up above point AAA103 there is a small ceiling tube heading
to the southwest. Interestingly this is near the southern most edge of
the cave.
</note>
The words "name" and "type" in the above are not allowed
to repeat, these are the "attributes" in the official XML terminology.
Someone can correct me, if I'm out of touch on that no repeat rule.
On the other hand, within a <shot> block there certainly could
be room for one or more sub-elements that provides a list of names.
<shot ... >
...
<name>Entrance Pit</name> <!-- alternate syntax is possible -->
<name>Connection Pit</name>
...
</shot>
Elements can be defined to be allowed to repeat, but attributes on a
particular element can not repeat.
If each point that is in one or more named areas had a list, that sounds
like a lot of data to me compared to the occassional start of a name
followed lines later by a close of an element that says we are ending
a set of points that would be found all in an area with a particular
name.
Given the idea of putting attributes on all shots in a certain named
area,
think of the poor person trying to XML edit a basic cave with a few
names,
having to label every point in the "Entrance Room" and every point in
the
"Connection Pit", so that the set is properly defined.
Seems to me XML already has a way to mark a bunch of stuff with the same
value, put the stuff physically together in the file and surrond it with
a block element. The amount of clutter is greatly reduced. The amount
of overhead is greatly reduced. The hand editor has a chance.
XML does nested blocks realy well.
cheers,
-Paul
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:01 CET