[DDI-SRG] rehashing old discussions

[Wendy Thomas]

However, we need to provide some guidelines if this is something you want 
to have interoperable. Does name behave differently in different place? If 
you expect name to behave in a certain way and I use it diferently...what 
then?


On Wed, 28 Jan 2009, Pascal Heus wrote:

> Achim:
> I think I remember discussing this during the DExT development and the
> variable name goes in the identifier r:Name element (at least in DExT).
> We can optionaly use the Label to provide alternate versions of the name
> (like short name or long name using the maxLength attribute). It seem
> intuitive to me to store the name in Name and label in Label and I would
> expect most implementers to do this (not everyone will read the docs).
> *P
>
> Joachim Wackerow wrote:
>> Probably you are right to provide a choice. r:Name or r:Label, this is
>> very much dependent from how the user of DDI 2 defined the semantics for
>> @ID and @name (often it is only an implicit assumption). I think in many
>> cases @name should go to r:Name, but the person who is responsible for
>> the mapping process should think about. So it makes sense to offer a choice.
>>
>> Furthermore it raises the question where the variable name should go in
>> DD 3.0. When it is in r:Label with @type="VariableName", what is then in
>> r:Name? The documentation doesn't seem to be clear with that. I think we
>> have to describe the preferred way. r:Name seems to be the right place
>> at least for variable. But r:Label offers more flexibility with the type
>> attribute. Do we have a preferred location for variable name?
>>
>> Achim
>>
>>
>> Wendy Thomas wrote:
>>
>>> In doing the translation for 2 to 3 I did the following in terms of
>>> handling the @name for var (required), varGrp (optional), nCubeGrp
>>> (optional) and ncube (optional). I used a standard option of the Name
>>> elemnt in the identification standard content or Label. See example below
>>> from var.
>>>
>>> s:StudyUnit/l:LogicalProduct/l:VariableScheme/l:Variable/r:Label OR r:Name
>>> r:Label OR r:Name	r:internationalStringType,  r:Label is extended to
>>> include @type and @maxLength if appropriate	May also use the Name in
>>> the Identification base elements
>>>
>>> Is it wrong to provide this option? I have a slew of NHGIS where the name
>>> content is simply a replication of the ID content because its required.
>>> Personally when I tranlate these that's going right out the window. In the
>>> NCubes we used it for the table number which may make more sense as a
>>> label.
>>>
>>> Thoughts? Sanda wants them all to go to Name rather than providing an
>>> option.
>>>
>>> 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
>>>
>>
>>
>>
>
>

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