From: Paul & Eleanor (goodhill_at_xmission.com)
Date: Tue Feb 13 2001 - 18:44:31 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id SAA17450 for cavexml-outgoing; Tue, 13 Feb 2001 18:40:51 +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 SAA17446 for <cavexml_at_cartography.ch>; Tue, 13 Feb 2001 18:40:50 +0100 Received: from slc688.modem.xmission.com ([166.70.7.180] helo=xmission.com) by mail.xmission.com with esmtp (Exim 3.12 #1) id 14SjRe-0001P3-00 for cavexml_at_cartography.ch; Tue, 13 Feb 2001 10:40:54 -0700 Message-ID: <3A89727F.65576F47@xmission.com> Date: Tue, 13 Feb 2001 10:44:31 -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" <cavexml_at_cartography.ch> Subject: Unique Station names 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
ichard Knapp wrote:
> If so, wouldn't I be pretty much required to use a special program
> to handle that? Or could I just use any XML editor? How much can be
> specified in the DTD/Schema to make this work?
Assuming you are refering to the idea of originating (i.e. typing
in the notes) by using caveXML, I believe you have just stated
a very good reason to define caveXML such that
'basic' information could be defined without the use of
IDs.
If you defined as 'basic' the following:
shots,
basic-cross section info
(think LRCF with some other odds and ends yet to be worked out),
station names,
instrument info (include all the historical info like who, with what
etc.)
and as most people would guess from my discussion of the <group name="
"> tag,
names of stuff.
I'd say all of these have to grouped and need the
ability to reference each by their position relative
to each other, so as not to require any more repeats of anything
than is absolutely necessary (which is probably nothing repeated).
I'd also suggest that typing in 'by hand' could be supported
by allowing that anywhere an ID could be used, a name should be
allowable.
As to requiring that the Ids be the same everytime the
cave is generated which I got the impression someone suggested
in caveXML, that would be impossible and outside the scope of
caveXML, because someone could have typed the same data into two
systems, or feed non-ID labeled information into two systems.
Both systems might provide perfectly good unique IDs, but one
might assign them in connectity order at time of caveXML
generation, another might assign them as the data is read in
(historical order), another might have it own internal ID
(like Garry already has) and just us what he knows is unique.
By the way, if there is an ID, I'd suggest a unique integer,
anything else becomes another name.
-Paul
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:01 CET