From: Devin Kouts (devinkouts_at_earthlink.net)
Date: Tue Feb 20 2001 - 01:38:21 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id BAA07220 for cavexml-outgoing; Tue, 20 Feb 2001 01:31:26 +0100 Received: from swan.prod.itd.earthlink.net (swan.prod.itd.earthlink.net [207.217.120.123]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id BAA07216 for <cavexml_at_cartography.ch>; Tue, 20 Feb 2001 01:31:24 +0100 Received: from earthlink.net (sdn-ar-004varestP172.dialsprint.net [168.191.219.212]) by swan.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id QAA02586 for <cavexml_at_cartography.ch>; Mon, 19 Feb 2001 16:31:04 -0800 (PST) Message-ID: <3A91BC7D.7060804@earthlink.net> Date: Mon, 19 Feb 2001 19:38:21 -0500 From: Devin Kouts <devinkouts_at_earthlink.net> User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20001108 Netscape6/6.0 X-Accept-Language: ko,en To: cavexml_at_cartography.ch Subject: Re: <DataFileVersion> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
Yes, namespaces could be used to fulfill this role, but at the time I
put <DataFileVersion> into the mix it wasn't clear to me how the
developers might/or might not use namespaces.
I'm still digging into namespaces and I'm not quite convinced yet that
they'll do what we need. But I confess that the need (read requirement)
is still pretty poorly defined at this stage. When I look at namespaces
I see that (among other things):
"An XML namespace is a collection of names that can be used as element
or attribute names in an XML document. The namespace qualifies element
names uniquely on the Web in order to avoid conflicts between elements
with the same name. The namespace is identified by some URI (Universal
Resource Identifier), either an URL (Uniform Resource Locator), or an
URN (Uniform Resource Number), but it doesn't matter what, if anything,
it points to."
That doesn't really tell me that the namespace is used to "qualify" the
elements of a given version of CaveXML for example. It seems like it
could be used that way, I just haven't put much effort into this area.
Development work such as this is best done top-down and iteratively.
What you've hit upon is an early solution to a high-level requirement.
In true evolutionary-development fashion this subject will need to be
addressed again, and in greater detail. Thanks for your perspective
though. It's could be the right answer in the end.
DSK
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:01 CET