From: Richard Knapp (gyp_caver_at_yahoo.com)
Date: Tue Jan 01 2002 - 19:30:04 CET
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 245599C1F for <cavexml-outgoing_at_ethz.ch>; Tue, 1 Jan 2002 19:38:14 +0100 (CET) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 37C0A9C1C; Tue, 1 Jan 2002 19:38:11 +0100 (CET) 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 5253B9C1F for <cavexml_at_cartography.ch>; Tue, 1 Jan 2002 19:38:10 +0100 (CET) Received: from smtp016.mail.yahoo.com (smtp016.mail.yahoo.com [216.136.174.113]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with SMTP id 90A059BAD for <cavexml_at_cartography.ch>; Tue, 1 Jan 2002 19:38:06 +0100 (CET) Received: from slip-12-64-108-145.mis.prserv.net (HELO Muphin) (12.64.108.145) by smtp.mail.vip.sc5.yahoo.com with SMTP; 1 Jan 2002 18:28:31 -0000 From: "Richard Knapp" <gyp_caver_at_yahoo.com> To: "cavexml_at_cartography.ch" <cavexml_at_cartography.ch> Date: Tue, 01 Jan 2002 13:30:04 -0500 (EST) X-Mailer: PMMail 2.20.2300 for OS/2 Warp 4.5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Attributes Message-Id: <20020101183806.90A059BAD@karmail.ethz.ch> Sender: owner-cavexml_at_karmail.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch X-Virus-Scanned: by AMaViS perl-11
One thing COMPASS (and probably other programs) allows is the use of attributes. COMPASS defines three
individual and one group shot attributes. They are:
Length Exclusion (L) - removes shot from total length calculations;
Plot Exclusion (P) - prevents shot from being plotted;
Closure Exclusion (C) - prevents this shot from being part of the loop closure calculations;
All Exclusions (X) - short-hand for all three (CLP).
In the DTD on which I'm working, I have these as part of a parent element called Exclusions.
<!ELEMENT Length EMPTY>
<!ELEMENT Plot EMPTY>
<!ELEMENT Closure EMPTY>
<!-- ELEMENT Exclusions
Definition - allow for the exclusion of small or large sections
of data to be removed from processing or drawing without removing
it from the data file. Multiple child elements can be included but
the presence of one will trigger the exclusion. -->
<!ELEMENT Exclusions (Length | Plot | Closure)*>
which is then an optional part of a shot
<!ELEMENT Shot (Distance | Azimuth | Inclination | Drop | InstrumentHeight | TargetHeight | Direction |
Exclusions | Walls)*>
I think this is a little restrictive.
What if the Exclusions were just Attributes defined at the top of a CaveXML file.
(in the DTD)
<!ELEMENT Attribute EMPTY>
<!ATTLIST Attribute
name CDATA #REQUIRED
shorthand NMTOKEN #REQUIRED
description CDATA #IMPLIED>
<!ELEMENT Attributes (Attribute)*>
(in the XML file)
<Attributes>
<Attribute name="LengthExclude" shorthand="L" description="Exclude from length calculations"/>
<Attribute name="PlotExclude" shorthand="P" description="Do not plot"/>
<Attribute name="ClosureExclude" shorthand="C" description="Exclude from closure calculations"/>
</Attributes>
Then the Shot element would only need to reference the shorthand instead of the entire attribute structure.
(in the DTD)
<!ELEMENT Shot (stuff...)>
<!ATTLIST Shot
(...)
attributes CDATA #IMPLIED>
(in the XML file)
<Shot attributes="LP">
<(other stuff)/>
</Shot>
A con is that some sort of key would have to be common to all programs using the references (almost like a
Processing Instruction but hopefully simpler).
A pro is users could define additional attributes that could be placed on Stations or Shots for their information
(almost like a GIS).
<Attributes>
<Attribute name="Resurvey" shorthand="R" description="Resurveyed shot"/>
<Attribute name="Water" shorthand="W" description="Potable water location"/>
</Attributes>
This introduces quite a bit of flexibility and complexity. However, one of the things that seems to be missing
from a lot of cave programs is the ability for users to define more parameters they can either search for or
show graphically. Yes, they could do this with a GIS addition. But for simple things, this would be helpful.
- Richard Knapp
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Thu Jan 31 2002 - 23:00:01 CET