From: Richard Knapp (richfk_at_attglobal.net)
Date: Sat Sep 28 2002 - 13:25:37 CEST
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 7B31415970 for <cavexml-outgoing_at_ethz.ch>; Sat, 28 Sep 2002 13:52:39 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id EA25B1594C; Sat, 28 Sep 2002 13:52:35 +0200 (CEST) Delivered-To: cavexml-loopcheck_at_ethz.ch Received: from localhost (localhost [127.0.0.1]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id D40E215970 for <cavexml-loopcheck_at_ethz.ch>; Sat, 28 Sep 2002 13:52:34 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 6667515878; Sat, 28 Sep 2002 13:52:31 +0200 (CEST) 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 1CC1215977 for <cavexml_at_cartography.ch>; Sat, 28 Sep 2002 13:52:31 +0200 (CEST) Received: from prserv.net (out4.prserv.net [32.97.166.34]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 3D09915878 for <cavexml_at_cartography.ch>; Sat, 28 Sep 2002 13:52:27 +0200 (CEST) Received: from Muphin (slip-12-65-6-153.mis.prserv.net[12.65.6.153]) by prserv.net (out4) with SMTP id <2002092811272920403qau96e>; Sat, 28 Sep 2002 11:27:30 +0000 From: "Richard Knapp" <richfk_at_attglobal.net> To: "CaveXML" <cavexml_at_cartography.ch> Date: Sat, 28 Sep 2002 07:25:37 -0400 (EDT) X-Mailer: PMMail 2.20.2380 for OS/2 Warp 4.5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Data format/visualization? Message-Id: <20020928115227.3D09915878@karmail.ethz.ch> X-Loop: cavexml Sender: owner-cavexml_at_karmail.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch X-Virus-Scanned: by AMaViS perl-11
I've been thinking (look out!) about the book format in the data file. Is
this data or a format? If it's data, then it should be placed in the XML
file. If it's a format, should it not be XSL based?
What may be an issue in separating things like that (using an XSL for
display the book) would be the change from book to book, trip to trip, or
sketcher to sketcher. XSLs would have to be generated "on the fly" which
seems too complex.
Granted, the XML file could always be reformatted later to appear
differently (for different viewers tastes/preferences) but what about the
main, original data?
The items I'm addressing are things like element order and format (Is the
format two line or one line; is it Dist, Azi, Incl or Azi, Incl, Dist? is
is LRUD or UDLR?). I used to think this information would be stored in an
Order element and would also contain default units for each item.
Something like:
<Order>
<Item name="Station" units="null"/>
<Item name="Distance" units="Feet"/>
<Item name="Azimuth" units="Degrees"/>
<Item name="Inclination" units="Mills"/>
</Order>
This is similar to the Measurement element Peter proposed but only
contains information, not data. Should more information be gathered at the
same time?
<Item name="FrontAzimuth" units="Degrees"
instrument="Suunto" ID="02939103" correction="0"/>
<Item name="ReverseAzimuth" units="Degrees"
instrument="Suunto" ID="93810485" correction="-0.5"/>
Or would it be better to keep instrument data separate from order/units?
<Order>
<Item name="FrontAzimuth" units="Degrees"/>
<Item name="ReverseAzimuth" units="Degrees"/>
</Order>
<Instruments>
<Instrument name="Suunto" ID="02939103" correction="0"
position="FrontAzimuth"/>
<Instrument name="Suunto" ID="93810485" correction="-0.5"
position="ReverseAzimuth"/>
</Instruments>
Seems like there is some redundancy (and some linkage to be done) but it
is clearer.
Comments?
This archive was generated by hypermail 2b30 : Mon Sep 30 2002 - 23:00:00 CEST