[DDI-SRG] InstrumentType ControlConstructReference JEREMY DAN READ THIS

[Wendy Thomas]

Hi Dan,

As I understand it since my Instrument points to one control construct 
(the head one) everything within the that needs to be nested within or 
have a singular planned exit and reentrance route in order to show up in 
the instrument. So I can have everything nexted within a single <Sequence> 
</Sequence> bracket set (aka DTD approach) or identified subroutines that 
can be called (aka schema approach). I'd have to check and see if the 
loops, repeats, and IfThenElse acutally allowed for a consistant reentry 
if these referenced outside hierarchies but I believe they do. So in fact 
the ControlConstructs are ordered within the schema as there is nowhere 
else to provide them with order. Its simply that being outside of the 
Instrument both Blaise and CSPro could use the same set of 
controlconstructs.

But you answer leads me to believe that it is structured as intended and 
that we need to get the documentation updated and expanded.

Wendy


On Fri, 22 Feb 2008, Dan Smith wrote:

> Hi Wendy,
>
> I believe that ControlConstructScheme was meant to be unordered, simply
> a collection of the ControlConstructs that are used to create the
> instrument.  The ControlConstructReference in the InstrumentType was
> intended to point to the initiating/top ControlConstruct, which can then
> continue to reference the rest of the instrument.
>
> If you feel there is a better way, we can discuss it over a drink at
> Town Hall.
>
> Cheers,
> Dan
>
> Wendy Thomas wrote:
>> Before entering a bug I want to know if it really is a bug or the
>> structure was intended.
>>
>> InstrumentType currently contains a ControlConstructReference 0..1
>> (allowing for reference to an instrument that has not had its contents
>> described in DDI)
>>
>> ControlConstructScheme contains ControlConstruct 1..n implying that
>> multiple independent control sequences can be stored in a single
>> ControlConstructScheme and the Instrument is referencing the top construct
>> of its initiating sequence.
>>
>> If this is how its supposed to be, fine, I'll make sure it is documented
>> in this way.
>>
>> However, if a ControlConstructScheme was intended to contain a single
>> master seqence then InstrumentType should change ControlConstructReference
>> to ControlConstructSchemeReference and ControlConstructScheme should
>> change its ControlConstruct to 1..1 forcing a single starting point for
>> the control sequence.
>>
>> Which is correct? You may have discussed this while I was at the Doctor's.
>> I hope Jeremy and Dan are paying attention to this email ;)
>>
>> Wendy
>>
>> Wendy L. Thomas                          Phone: +1 612.624.4389
>> Data Access Core Director		 Fax:   +1 612.626.8375
>> Minnesota Population Center              Email: wlt at pop.umn.edu
>> University of Minnesota
>> 50 Willey Hall
>> 225 19th Avenue South
>> Minneapolis, MN 55455
>> _______________________________________________
>> DDI-SRG mailing list
>> DDI-SRG at icpsr.umich.edu
>> http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg
>
>
> -- 
> Dan Smith
> +1 608-213-2867
> Algenta Technologies, LLC
> http://www.algenta.com
> _______________________________________________
> DDI-SRG mailing list
> DDI-SRG at icpsr.umich.edu
> http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg
>

Wendy L. Thomas                          Phone: +1 612.624.4389
Data Access Core Director		 Fax:   +1 612.626.8375
Minnesota Population Center              Email: wlt at pop.umn.edu
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455