handling hierarchical sectioning

[HansBKK]

I'm using @shadow, but should also apply to @thin
I would prefer to use method 2 ("cascading rollup"?) below, but I'm getting the feeling method 1 ("flat rollup"?) is more robust from the POV of data security. I'm hoping this is only because I've been playing around with bad multi-source cloning practices in the past.

Yes there is a question in there. . .

8-)

Method 1:

header: @ <file> a.xyz
  body:
    blah-blah-top
      <<section 1>>
    blah-blah-top
    <<section 2>>
    blah-blah-top

header: <<section 1>>
  body:
    blah-blah-1
    <<section 1a>>
    blah-blah-1
    <<section 1b>>
    blah-blah-1

--------------------

Method 2:

header: @ <file> a.xyz
  body:
    blah-blah-top
      blah-blah-1
      <<section 1a>>
      blah-blah-1
      <<section 1b>>
      blah-blah-1
    blah-blah-top
    <<section 2>>
    blah-blah-top

[Edward K. Ream]

On Thu, Dec 15, 2011 at 8:55 PM, HansBKK <han...@gmail.com> wrote:

> Yes there is a question in there. . .

Not sure what your question is, but please note that sections must be
defined in some descendant of the node containing the reference.
That's the one and only constraint.

EKR

[HansBKK]

To clarify, my question was

"Is it possible that my use of method B contributed to my data loss problems?"

and you have answered with a "no".