From: Peter MATTHEWS (matthews_at_melbpc.org.au)
Date: Sat Oct 12 2002 - 09:47:11 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 7446F159CE for <cavexml-outgoing_at_ethz.ch>; Sat, 12 Oct 2002 10:18:49 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 59F1715995; Sat, 12 Oct 2002 10:18:46 +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 3E421159CE for <cavexml-loopcheck_at_ethz.ch>; Sat, 12 Oct 2002 10:18:45 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 234EB15942; Sat, 12 Oct 2002 10:18:42 +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 C2DC6159CE for <cavexml_at_cartography.ch>; Sat, 12 Oct 2002 10:18:41 +0200 (CEST) Received: from relay1.melbpc.org.au (newglider.melbpc.org.au [203.12.152.9]) by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0) with ESMTP id 714EA8C00 for <cavexml_at_cartography.ch>; Sat, 12 Oct 2002 10:18:37 +0200 (CEST) Received: from peter.melbpc.org.au (a2-42.melbpc.org.au [203.12.157.42]) by relay1.melbpc.org.au (8.12.6/8.12.6) with ESMTP id g9C88CoP008343 for <cavexml_at_cartography.ch>; Sat, 12 Oct 2002 18:08:14 +1000 (EST) (envelope-from matthews_at_melbpc.org.au) Message-Id: <5.1.0.14.1.20021011055526.01d5f200@popa.melbpc.org.au> X-Sender: matthews_at_popa.melbpc.org.au X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 12 Oct 2002 17:47:11 +1000 To: cavexml_at_cartography.ch From: Peter MATTHEWS <matthews_at_melbpc.org.au> Subject: Other Definitions Content-Type: text/plain; charset="us-ascii"; format=flowed X-RAVMilter-Version: 8.3.4(snapshot 20020706) (relay1) 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
Coming out of previous discussion, here are some extra terms we should add
to "Other Definitions" which would be helpful for us to agree on prior to
our discussion to set up a list of what entities and fields we will need to
cover in our CaveXML spec. These definitions will end up on our current
'Task progress' web page, and later, in a more formal list.
(The following is based on extract from Peter Matthews post of 17-Jul-02
11:41 "Types of data sets". Draft definitions resulting from previous
discussions. Refer to this thread in archive for further background and
development detail.)
Field data Data and sketches recorded in the field, i.e. paper-based
or images thereof.
Raw data Field data when converted unchanged into character-based
form, or
downloaded from an instrument.
Edited data Raw data which has had any kind of mistakes edited out of
it, but no
systematic instrument corrections yet applied.
Final data The input data which is currently the accepted final version of
unconsolidated Shot or other measured data, but has no
systematic
instrument corrections yet applied.
Leg data The final single set of data ready for reduction processing.
It may be
the result of consolidation of several sets of final Shot
data, and may
or may not have its instrument corrections already applied.
It may also
be synthesised data generated from co-ordinates after loop
adjustments.
Reduced data The co-ordinate set resulting from leg data which has been
reduced to
co-ordinate form, but has no loop adjustments yet applied.
Adjusted data The co-ordinate set resulting from leg data which has been
reduced to
co-ordinate form and includes loop adjustments.
(The following is based on extract from Peter Matthews post of 8-Jul-02
17:43 "Entities and fields". Draft definitions resulting from previous
discussions. Refer to this thread in archive for further background and
development detail.)
Entity
A real-world thing, event or concept that we want to record data about.
(These are
represented by the squares in the diagram. Examples are Cave,
Instrument, Trip.)
Field
A property of an Entity. (In a database table, for example, the fields
are normally
represented by the columns in the table. For example, "start date" is a
field of
the entity "trip", so in a table which listed trips, "Start Date" would
be one of
the columns. Fields are not being shown in the E-R diagram, but will be
listed out
when we come to discuss them in detail in Task 6.3. In an XML file, any
particular
field would be represented either as an XML "element" or "sub-element"
in its own
right, or as an XML "attribute" of another element, depending on
considerations
about that field.)
We'll now go through these suggested terms, one by one. So, starting with
the first one, is the definition for "Field data" acceptable, in relation
to the other types of survey data listed?
=========================================================================
"Field data Data and sketches recorded in the field, i.e. paper-based
or images thereof."
=========================================================================
Please respond, saying whether you accept it, or if not, offering an
improved version. Even if you accept it, please be sure to respond, or else
we won't know for sure that it's acceptable.
Peter
This archive was generated by hypermail 2b30 : Thu Oct 31 2002 - 23:00:00 CET