From: Devin Kouts (devinkouts_at_earthlink.net)
Date: Mon Jan 29 2001 - 05:50:36 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id FAA31247 for cavexml-outgoing; Mon, 29 Jan 2001 05:44:55 +0100 Received: from falcon.prod.itd.earthlink.net (falcon.prod.itd.earthlink.net [207.217.120.74]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id FAA31243 for <cavexml_at_cartography.ch>; Mon, 29 Jan 2001 05:44:54 +0100 Received: from earthlink.net (sdn-ar-001varestP305.dialsprint.net [168.191.217.43]) by falcon.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id UAA19512 for <cavexml_at_cartography.ch>; Sun, 28 Jan 2001 20:45:04 -0800 (PST) Message-ID: <3A74F69C.1010105@earthlink.net> Date: Sun, 28 Jan 2001 23:50:36 -0500 From: Devin Kouts <devinkouts_at_earthlink.net> User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20001108 Netscape6/6.0 X-Accept-Language: ko,en To: cavexml_at_cartography.ch Subject: Re: defaulting units References: <3A6DD46C.5C6B291E_at_earthlink.net> <3A6EA342.628CEB2D_at_speleonics.com.au> <3A723FA2.F1D861DC_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
Touche Paul... I think you nailed it squarely.
Maybe global is an ugly word to some, and I shouldn't have used it as I
did. But in the interest of saving time that was what I came up with.
To be more specific, The CaveXML data model will, to some degree, be an
hierarchically structured data model of cave survey data. A lot of the
data in a given <Survey> will be the same from shot to shot, e.g. the
Units the length each shot was measured in. Making that declaration
known up front, "possibly" in the <Intsruments> section of the <Survey>
seems a valid way of stating the standard length units for the "entire"
survey. Doing so will save you from restating it for each individual
shot (and certainly save space in the file). But in the event a
particular shot was not recorded in the declared "standard" Units, you
want the ability to override the standard with a "local" Units
declaration. This would apply just once, to the <Shot> or <Leg> within
which it occurs.
Best of both worlds, brevity with felixibility.
Devin
Paul & Eleanor wrote:
>
> Michael Lake wrote:
>
>>> In reality it is more likely that various UNITS would have been
>>> specified at a global level, i.e. before the first SHOT, in something
>>> like a SURVEY header area.
>>
>> Global eeeeekkkkkkk !!!!!!
>
>
> As I see it, this almost has to provided.
> This certainly makes it easier to generate more readable datasets
> of consistent data.
>
> Makes for much shorter data sets if the whole dataset is consistent.
>
>>> need be. For instance, if your survey suddenly switches from
>>> decimal-feet to feet and inches (not an infrequent blunder in some U.S.
>>> surveys), you'll need to indicate this at each SHOT where it occurs.
>>
>> Once declared in INSTRUMENTS it would be read by a parser into an applications
>> memory/variable and can be in effect until another INSTRUMENT element chnages it.
>> We don't want to indicate it for every shot. We dont want eg. survex files when turned
>> into XML files to be as big as M$ Word files :-)
>
>
> What? You don't go for global declarations, but you admit specify on
> every
> shot would be bad. What is the middle ground? Specification on a
> "survey" or some other group of survey traverses?
> Actually this sounds like a good idea to me.
>
> This discussion is getting interesting.
>
> -Paul
>
>
>
This archive was generated by hypermail 2b30 : Wed Feb 14 2001 - 00:03:54 CET