Re: Splitting SHOT into constituent members

New Message Reply About this list Date view Thread view Subject view Author view

From: Paul & Eleanor (goodhill_at_xmission.com)
Date: Sat Jan 27 2001 - 06:33:00 CET 

Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id GAA24593 for cavexml-outgoing; Sat, 27 Jan 2001 06:29:40 +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 GAA24589 for <cavexml_at_cartography.ch>; Sat, 27 Jan 2001 06:29:39 +0100
Received: from slc523.modem.xmission.com ([166.70.7.15] helo=xmission.com) by mail.xmission.com with esmtp (Exim 3.12 #1) id 14MNvn-0001Nc-00 for cavexml_at_cartography.ch; Fri, 26 Jan 2001 22:29:47 -0700
Message-ID: <3A725D8C.2507A3BB@xmission.com>
Date: Fri, 26 Jan 2001 22:33:00 -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
Subject: Re: Splitting SHOT into constituent members
References: <200101241027.LAA07438_at_karto.ethz.ch>
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

Richard Knapp wrote:
> To me, without the implied structure given by having shots, the data becomes > unstructured. What
> would be the advantage with using XML if there is no structure to the data?

Agreed.

I don't see why <shot name=abc id=1234567><azi/><inc/><dist/><shot>
where
azi inc and dist are all optional doesn't support the each is
possibly a seperate event idea. Certainly the standard isn't
going to impose a rule the names have to be unique.

-Paul

New Message Reply About this list Date view Thread view Subject view Author view

This archive was generated by hypermail 2b30 : Wed Feb 14 2001 - 00:03:53 CET