From: Michael Lake (mikel_at_speleonics.com.au)
Date: Sun Feb 04 2001 - 04:28:28 CET
Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id EAA00692 for cavexml-outgoing; Sun, 4 Feb 2001 04:31:12 +0100 Received: from iggy.triode.net.au (IDENT:root_at_iggy.triode.net.au [203.63.235.1]) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id EAA00688 for <cavexml_at_cartography.ch>; Sun, 4 Feb 2001 04:31:09 +0100 Received: from speleonics.com.au (dm1-55.triode.net.au [203.63.34.56]) by iggy.triode.net.au (8.11.1/8.10.1) with ESMTP id f143VvP30399 for <cavexml_at_cartography.ch>; Sun, 4 Feb 2001 14:32:01 +1100 Message-ID: <3A7CCC5C.1E113DA@speleonics.com.au> Date: Sun, 04 Feb 2001 14:28:28 +1100 From: Michael Lake <mikel_at_speleonics.com.au> X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en To: cavexml_at_cartography.ch Subject: Re: <text> vs. <comment> and data format References: <3A72562B.6D8596E2_at_xmission.com> <3A74FA79.8000705_at_earthlink.net> 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
Hi All,
<text> vs <comment>
-------------------
With the discussion Re <text> as a markup tag to represent comments my wife, Jill, suggested <note>.
The reason is that note is a latin derived word and its meaning may be better undertsood by more countries throughout Europe. Just an idea.
Date Format
-----------
Paul & Eleanor wrote:
> So I would suggest that what was suggested as <comment/> would become
> <text> or <narrative> or something.
A narrative suggests an epistle :-) something rather long.....
> It would also allow me to comment out, some weird CaveXML+ extension
> that included something that others would find un-readable.
> <text>
> <roomModel >
> <poly id=1>1.234,3.456,34.5678</poly>
> ....
> <roomModel>
> </text>
I think that is improper use of the tag. If it's for encosing text then it should not be used for 'commenting' out elements. One should use <!-- --> for that. Also the application should read the XML CaveSurvey version at the top of the doc, find and parse the XSchema/DTD and that tells it what tags are defined. If it does not know how to handle a particular tag it should have code to handle that.
> 3. I believe there is already a date standard and what you show is NOT
> it. I would suggest sticking with that. The one that comes to mind is ISO 8601
> form 2001-01-26 (sortable, not any use of slashes to be be confused with
Excellent.
> > Just to play with text blocks a bit, I might suggest an optional
> > title/name attribute for the main text block. So in summary,
> > <text xml:lang="es" author="Jose" date="2001-01-27">
> > que significa?
> > </text>
I had a read of this standard at the URL supplied but what do you write if you know the year but not the month or day? or if you know just year and month?
Mike
-- -------------------------------------------------------------------- Michael Lake Active caver, Linux enthusiast and interested in anything technical. Safety Convenor, Australian Speleological Federation Owner, Speleonics (Australia) --------------------------------------------------------------------
This archive was generated by hypermail 2b30 : Thu Mar 01 2001 - 18:00:00 CET