[DDI-SRG] [DDI 3.0 0000006]: LogicalRecordReference in PhysicalDataProduct should be optional

[Wendy Thomas]

response to specific section below...

On Sat, 29 Sep 2007, Pascal Heus wrote:

> Wendy and all:
> What if in RecordLayout I point to a
> Variable or a VariableScheme that is not in the LogicalRecord? What if I
> point to a VariableScheme not in the LogicalProduct? etc. We basically
> have three variable containers: LogicalProduct, LogicalRecord and
> DefaultVariableScheme, how can we ensure integrity of the metadata?
> *P

LogicalProductReference is 0..n
   This was requested in order to quickly identify which logicalProducts 
would be addressed by this PhysicalDataStructure in order to avoid having 
to parse all the references and derive it from the URN structures

VariableSchemeReference
   Currently occurs only twice. The first time Line 57 is highlighted in 
blue with a note of Needs further Discussion. You had asked that this be 
moved up to the RecordLayout level to avoid repeating it in each 
VariableReference. However, if references are to be URNs then it will be 
explicitly stated in the URN as the containing maintainable. Hence the 
need for further discussion of its need. The second occurance (line 85)is 
highlighted in black with the note KILL THIS SUGGESTION...its essentially 
non-existant at this point of the discussion.

In terms of container. Your physical segment can be part of only one 
logical record. If we "rectangularize" a file then we should be creating a 
new logical record description that incorporates both logical records into 
a single one. This is nessesary as I can create the rectangularized file 
based on either part as the case (one householdrecord with person 1, 
person 2 etc strung out behind OR one person record with its household 
information attached thereby repeating household information for each 
household by the number of persons in the household).


>
> noreply at opendatafoundation.org wrote:
>> The following issue has been RESOLVED.
>> ======================================================================
>> http://mantis.ddialliance.org/view.php?id=6
>> ======================================================================
>> Reported By:                pheus
>> Assigned To:                wthomas
>> ======================================================================
>> Project:                    DDI 3.0
>> Issue ID:                   6
>> Category:                   !Schema
>> Reproducibility:            N/A
>> Severity:                   minor
>> Priority:                   normal
>> Status:                     resolved
>> Related Module:             PhysicalData
>> XPath:                      /GrossRecordStructure/LogicalRecordReference
>> Related use case:           DExT
>> Implemented Solution:
>> Resolution:                 open
>> Fixed in Version:
>> ======================================================================
>> Date Submitted:             07-12-2007 14:46 PDT
>> Last Modified:              09-27-2007 16:22 PDT
>> ======================================================================
>> Summary:                    LogicalRecordReference in PhysicalDataProduct should
>> be optional
>> Description:
>> The mandatory aspect of this element located in the GrossRecordStructure or
>> the create several issues
>>
>> (1a) The LogicalRecord located in the LogicalProduct/DataRelationship
>> comes with a mandatory CaseIdentification. Such unique key may not exist
>> for all files and therefore makes it currently impossible to define a
>> PhysicalDataInstance for such file (nfor the same reason, I will suggest
>> shortly to make CaseIdentification optional).
>>
>> (1b) A LogicalRecord has a mandatory VariablesInRecord element that may
>> conflict with RecordLayout/DataItem
>>
>> (2) In most case, a PhysicalDataInstance will simply mirror a
>> VariableScheme which means we could instead point to a VariableScheme.
>>
>> (3) Note that even if this element is optional, it makes it possible to
>> point to a LogicalRecord located in different LogicalProduct than the one
>> specified for this PhysicalDataInstance. This therefore requires
>> validation outside the schema.
>>
>> (4) Overall, this ability to point to a set of variables outside the
>> RecordLayout/DataItem open the door to inconsistencies as it become
>> possible to point to difference variables that may reside in completely
>> different spaces
>>
>>
>> ======================================================================
>> Relationships       ID      Summary
>> ----------------------------------------------------------------------
>> related to          0000036 DataSet no longer in PhyiscalDataProduc...
>> related to          0000009 Extra DataType under PhysicalDataInstance
>> related to          0000021 LogicalRecord overkill for simple files
>> related to          0000022 PhysicalDataSegment type choice
>> related to          0000023 GrossRecordStructure confusion
>> related to          0000010 Move NamesOnFirstRow to GrossRecordStru...
>> related to          0000008 Format vs FormatScheme under PhysicalDa...
>> related to          0000037 Mispelling of SeparateFile in PhysicalD...
>> related to          0000011 Introduce default tVariableSchemeRefere...
>> ======================================================================
>>
>> ----------------------------------------------------------------------
>>  wthomas - 09-27-07 16:22
>> ----------------------------------------------------------------------
>> ACTION:
>> The problem is being addressed by simplification of the DataRelationship
>> description for simple files and continued requirement of the reference
>> from PhysicalDataProduct. Note that LogicalDataProduct/DataRelationship
>> remains optional because a LogicalDataProduct may contain just a
>> CategoryScheme early in the lifecycle.
>>
>> In LogicalDataProduct/DataRelationship
>>
>> CHANGE: Description from 1..n to 0..n
>> CHANGE: LogicalRecord from 0..1 to 1..n
>>
>> NO CHANGE TO REQUIRED REFERENCE FROM
>> PhysicalDataProduct/GrossRecordStructure/LogicalRecordReference
>>
>>
>> Issue History
>> Date Modified   Username       Field                    Change
>> ======================================================================
>> 07-12-07 14:46  pheus          New Issue
>> 07-12-07 14:46  pheus          Related Module            => PhysicalData
>> 07-12-07 14:46  pheus          XPath                     =>
>> /PhysicalDataProduct/GrossRecordStructure
>> 07-12-07 14:46  pheus          Related use case          => DExT
>> 07-12-07 14:48  pheus          Description Updated
>> 07-12-07 14:50  pheus          XPath
>> /PhysicalDataProduct/GrossRecordStructure =>
>> /GrossRecordStructure/LogicalRecordReference
>> 07-12-07 15:10  pheus          Relationship added       related to 0000011
>> 07-12-07 16:25  pheus          Status                   new => assigned
>> 07-12-07 16:25  pheus          Assigned To               => wthomas
>> 07-12-07 16:29  pheus          Assigned To              wthomas =>
>> 07-12-07 16:29  pheus          Status                   assigned => new
>> 07-21-07 10:17  wthomas        Status                   new => assigned
>> 07-21-07 10:17  wthomas        Assigned To               => wthomas
>> 08-19-07 05:07  wthomas        Relationship added       related to 0000036
>> 08-19-07 05:08  wthomas        Relationship added       related to 0000009
>> 08-19-07 05:08  wthomas        Relationship added       related to 0000021
>> 08-19-07 05:08  wthomas        Relationship added       related to 0000022
>> 08-19-07 05:09  wthomas        File Added: schemaLayoutsForEdit.xls
>>
>> 08-19-07 05:10  wthomas        Relationship added       related to 0000023
>> 08-19-07 05:10  wthomas        Relationship added       related to 0000010
>> 08-19-07 05:10  wthomas        Relationship added       related to 0000008
>> 08-19-07 05:10  wthomas        Relationship added       related to 0000037
>> 09-27-07 16:22  wthomas        Note Added: 0000057
>> 09-27-07 16:22  wthomas        Status                   assigned => resolved
>> ======================================================================
>>
>>
>>
>
> _______________________________________________
> 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