From: Richard Knapp (richfk_at_attglobal.net)
Date: Sat Sep 28 2002 - 13:10:42 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 ACCAE15970 for <cavexml-outgoing_at_ethz.ch>; Sat, 28 Sep 2002 13:52:37 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 28) id 470FA15983; Sat, 28 Sep 2002 13:52:34 +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 1457915977 for <cavexml-loopcheck_at_ethz.ch>; Sat, 28 Sep 2002 13:52:33 +0200 (CEST) Received: by karmail.ethz.ch (Postfix on SuSE eMail Server 2.0, from userid 96) id 930261594C; Sat, 28 Sep 2002 13:52:29 +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 581B015977 for <cavexml_at_cartography.ch>; Sat, 28 Sep 2002 13:52:29 +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 9EC2E1583D for <cavexml_at_cartography.ch>; Sat, 28 Sep 2002 13:52:25 +0200 (CEST) Received: from Muphin (slip-12-65-6-153.mis.prserv.net[12.65.6.153]) by prserv.net (out4) with SMTP id <2002092811272820403qau95e>; Sat, 28 Sep 2002 11:27:28 +0000 From: "Richard Knapp" <richfk_at_attglobal.net> To: "CaveXML" <cavexml_at_cartography.ch> Date: Sat, 28 Sep 2002 07:10:42 -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: Measurement Element? Message-Id: <20020928115225.9EC2E1583D@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
In Peter's document, he uses an Measurement element to record measured
data. In my old model, I was using separate elements for each type of
measurement. Some of that was to allow for unit validation, some to allow
for more general data validation. However, I find I like the generalized
Measurement more useful. But it leaves a question:
- What, if any, validation should be done via the DTD/Schema? Units?
Parent/Child elements? Attributes?
I'm beginning to agree validating units may be too much - and become too
inflexible - if it is incorportated into the DTD/Schema.
Comments?
This archive was generated by hypermail 2b30 : Mon Sep 30 2002 - 23:00:00 CEST