[DDI-SRG] Tomorrow's meeting

[Wendy Thomas]

Two things on the agenda:

1 - Preparation for publication: the list of new bugs coming out of review 
need to be included in this revision if possible. See list below.

2 - URN call follow-up

Preparation for publication:

A number of corrections were identified during Chris's review of the model 
and review of the proposed 3.1 structure. We need to go over this list 
quickly to see what can be included and what are longer term issues. I've 
broken this into 3 types of bugs:

DOCUMENTATION - FIELD LEVEL [these should just be fixed, please review]

267	documentation on Relationship needs to be made generic to 
application in Note and OtherMaterial
269	VariableSchemeReference - not generic enough for usage
276	DataFileReference documentation is unclear
279	Label documenation throughout

NON-CONTROVERCIAL CHANGES [trying to get all minor fixes that are 
invalidating into 3.1 if possible]

260	add ResearcherID to Individual
261	UniverseReference defined twice not caught in earlier review
262	DDIProfile nees prefix mapping - looks like it should be 
straightforward but out of my field to suggest specific change
263	Addition of ElseIf option to simplify and clarify If Then ElseIf 
ElseIf...Else nesting patterns
264	Add name, label, description to ControlConstructType  [abstract] 
(missed this one in the original list)
265	Allow dynamic text in interview instructions
268	Change Name in SeriesStatement to standard format and make 
repeatable for language
270	Interative ConceptReference [is it an error if so can we fix now]
271	Format of Boolean attribute
272	Format of Boolean attribute
274	ExternalInformationReference is r:Reference and could reference 
non-DDI content
277	CodeRepresentation and CategoryRepresentation allow multiple 
references to Code/CategorySchemes within their structure. This is handled 
by StructuredMixedResponse in Questions and is not allowed in Varibles 
(composit code scheme should be created and used by Variable)
278	SpecificSequence requires AlternateSequenceType even when a valid 
sequence type is provide in QuestionSequence...also "QuestionSequence" is 
not generic in terms of uses for describing category sequences

HOLD FOR LATER VERSION

266	Temporal, Spatial, and Topical Coverage are all identifiable 
although Coverage is not. Can reside in multiple locations, is not 
referenced. Is this correct? logical?
273	ResponseUnit is inconsistant, internationalstring in 
QuestionConstruct and xs:string in other locations. ResponseUnit is slated 
for addtional review in future version for a variety of reasons.
275	CoordinateGroupStructure looks odd, needs review
280	Inability to create an IfThen construct within a MultipleQuestion

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