<Comments>

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

From: Paul & Eleanor (goodhill_at_xmission.com)
Date: Fri Jan 19 2001 - 09:24:39 CET 

Received: (from mdom_at_localhost) by karto.ethz.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id JAA14324 for cavexml-outgoing; Fri, 19 Jan 2001 09:21:35 +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 JAA14320 for <cavexml_at_cartography.ch>; Fri, 19 Jan 2001 09:21:34 +0100
Received: from slc88.modem.xmission.com ([166.70.9.88] helo=xmission.com) by mail.xmission.com with esmtp (Exim 3.12 #1) id 14JWni-0008N1-00 for cavexml_at_cartography.ch; Fri, 19 Jan 2001 01:21:38 -0700
Message-ID: <3A67F9C7.B1368DBD@xmission.com>
Date: Fri, 19 Jan 2001 01:24:39 -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" <cavexml_at_cartography.ch>
Subject: <Comments>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-cavexml_at_karto.baug.ethz.ch
Precedence: bulk

Here is a typical example of XML hierarchy. I only show it to
discuss and ask about comments.

<Instruments>
  <Comment/>
    <Compass>
      <Correction units= .../>
      <SerialNumber/>
      <Owner/>
    </Compass>
    <Clinometer>
      <Correction units= .../>
      <SerialNumber/>
      <Owner/>
    </Clinometer>
    <Tape>
      <Correction units= .../>
      <SerialNumber/>
      <Owner/>
    </Tape>
</Instruments>

Looks like great XML and I think it is a great start. I just wish
to discuss one aspect at this time: comment blocks.

To place text inside a <Comment></Comment> block, can be
useful, but is it necessary? Isn't it possible in XML to specify
that you may have text (PCDATA) inside the <Instrument> block, but
outside of the any other blocks, such that untagged text is
just assumed to be text that goes with structure the text is in?
Example:

What are the pros and cons of actually defining the interpretation
of this text? Is it any more or less complex to deal with a series of
<Comment> blocks? In my limited processing of XML, I didn't think it
was.
Is there some attribute that would be useful to place on the Comment
block
that would make them more useful and thus prefered over just plain text?

I'm not saying place free text everywhere, just where you currrently
allow one (or more?) comment blocks.

<Instruments>
    <Comment>
    The compass was refurbished by the manufacture on 1/1/2000
    </Comment>
    <Compass>
      <Correction units= .../>
      <SerialNumber/>

Is that really any different than:

<Instruments>
    The compass was refurbished by the manufacture on 1/1/2000
    <Compass>
      <Correction units= .../>
      <SerialNumber/>
...

What role does the Comment tag serve? What role could it serve?

  <Comment Language=English>
  </Comment>

That is the only thing I can think of, but is that desired? That seems
like a weak reason, but maybe I'm not international enough. :-)

Comments anyone?

-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:52 CET