From: Richard Knapp (gyp_caver_at_yahoo.com)
Date: Wed Jan 24 2001 - 23:13:43 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id AAA11408 for cavexml-outgoing; Thu, 25 Jan 2001 00:03:11 +0100 Received: from smtp4.mail.yahoo.com (smtp4.mail.yahoo.com [128.11.69.101]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id AAA11404 for <cavexml_at_cartography.ch>; Thu, 25 Jan 2001 00:03:06 +0100 Message-Id: <200101242303.AAA11404@karto.ethz.ch> Received: from slip166-72-184-146.nc.us.prserv.net (HELO Muphin) (166.72.184.146) by smtp.mail.vip.suc.yahoo.com with SMTP; 24 Jan 2001 23:03:06 -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, 24 Jan 2001 17:13:43 -0500 (EST) X-Mailer: PMMail 2.20.2030 for OS/2 Warp 4.00 In-Reply-To: <00bf01c0863d$ace66040$0a3c10ac_at_gordon> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Splitting SHOT into constituent members Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
>Possibly, the <shot> could contain "station1" and
>"station2" attributes rather than the misleading
>"from" and "to" ones because some of the measurements
>might be backward sights.
Are you addressing backsights or backshots? A back shot is nothing more than a shot done in
reverse; a back sight is from the to station to the from station. (say that three times fast)
>Ultimately, the general caveXML parser could be a very slim object indeed.
>All it would need to know is the full parameter list for each
>different type of measurement (distance, depthguage, GPS...
>there's about half a dozen), and the names of the commands which
>it should interpret as being an attribute over-ride type.
>It would not need to distinguish between them in order to
>expand everything into a big database. You'd only later bother with
>rules like: <surveytrip> can't have a "from" attribute.
That is what a DTD or Schema are used for. I'm not sure if the exceptions generated (anyone
know) are specific like that but it would be helpful if they were.
>Anyways, with this organization, it suggests that we should
>first agree on a complete set of attributes for each commonly
>used type of measurement.
Disagree. We haven't really agreed on the scope of things to be considered. Without any
defined boundaries, things could easily get out of control.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Wed Feb 14 2001 - 00:03:53 CET