From: Richard Knapp (gyp_caver_at_yahoo.com)
Date: Wed Sep 05 2001 - 02:44:51 CEST
Received: (from mdom_at_localhost) by karto.ethz.ch (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) id f850rQc09769 for cavexml-outgoing; Wed, 5 Sep 2001 02:53:26 +0200 Received: from smtp016.mail.yahoo.com (smtp016.mail.yahoo.com [216.136.174.113]) by karto.ethz.ch (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with SMTP id f850rOQ09765 for <cavexml_at_cartography.ch>; Wed, 5 Sep 2001 02:53:25 +0200 Message-Id: <200109050053.f850rOQ09765@karto.ethz.ch> Received: from slip166-72-184-114.nc.us.prserv.net (HELO Muphin) (166.72.184.114) by smtp.mail.vip.sc5.yahoo.com with SMTP; 5 Sep 2001 00:56:06 -0000 X-Apparently-From: <gyp?caver_at_yahoo.com> From: "Richard Knapp" <gyp_caver_at_yahoo.com> To: "cavexml_at_cartography.ch" <cavexml_at_cartography.ch> Date: Tue, 04 Sep 2001 20:44:51 -0400 (EDT) X-Mailer: PMMail 2.20.2300 for OS/2 Warp 4.0 In-Reply-To: <881CC7991757D51196CF00508BCFE591016B638A_at_mcl-its-exs03.mail.saic.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: RE: Nested Surveys Sender: owner-cavexml_at_karto.baug.ethz.ch Precedence: bulk Reply-To: cavexml_at_cartography.ch
>This goes directly to the heart of the point I was arguing several months
>ago. The ability to nest surveys is absolutely necessary as you illustrate...
Yep. I've still got you message on this topic (dated 2-7-2001).
>Richard's example of <SurveyGroup> illustrates how clumsy it can become to....
Thanks... I think. <g>
>As an option to grouping surveys you might consider a structure that uses
>Xpointer to give access to surveys in a predertermined order. For instance,...
That is another option: to keep each survey separate and put grouping into a display or tree section. The link could be
make either with XLink or an (ick!) ID.
<Survey name="A" ID="1">
</Survey>
<Survey name="A continuation" ID="2">
</Survey>
<Survey name="A still continued" ID="3">
</Survey>
<Survey name="B" ID="4">
</Survey>
<Tree name="Partially nested structure">
<Branch XLink to "1">
<Branch XLink to "2"/>
<Branch XLink to "3"/>
</Branch>
<Branch XLink to "4"/>
</Tree>
A disadvantage is the added complexity in representing data. However, it does allow multiple views of the data without
replication.
<Tree name="Fully nested structure">
<Branch XLink to "1">
<Branch XLink to "2">
<Branch XLink to "3"/>
</Branch>
</Branch>
<Branch XLink to "4"/>
</Tree>
or
<Tree name="Plain structure">
<Branch XLink to "1"/>
<Branch XLink to "2"/>
<Branch XLink to "3"/>
<Branch XLink to "4"/>
</Tree>
This might be a feature that would be nice to have in the future - or to still allow in addition to the data enter's default view.
- Richard Knapp
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Wed Jan 23 2002 - 17:06:45 CET