<div dir="ltr"><div>Hi Sam,</div><div><br></div><div>Sorry for not getting back to you sooner but I wanted to check this out before replying off the top of my head. My son informs me that I should take nothing from the top of my head as it will only make me shorter :-)</div><div><br></div><div>Ok. Represented Variable and Variable/VariableRepresentation use a choice of ValueRepresentation or ValueRepresentationReference. A ValueRepresentation is an inline description of any of the following substitutions:</div><div><br></div><div>TextRepresentation</div><div>DateTimeRepresentation</div><div>NumericRepresentation</div><div>ExternalCategoryRepresenation</div><div>CodeRepresentation</div><div>ScaleRepresentation</div><div>GeographicStructureCodeRepresentation</div><div>GeographicLocationCodeRepresentation</div><div><br></div><div>The following can also be included by reference as they are managed objects:</div><div><br></div><div><div>TextRepresentation</div><div>DateTimeRepresentation</div><div>NumericRepresentation</div><div>ScaleRepresentation</div><div><br></div><div><br></div><div>Why, you may ask, just these four? Good question, it was part of a compromise solution to requiring people to manage ALL of their representation types and yet allowing them to manage some of them. We agreed to drop those that were already maintained and referenced by their representation type. So CodeList is maintained and CodeRepresentation is not. We realize that it means you have to replicate aanyCodeList subsetting you do when defining a CodeRepresentation, but there it is.</div><div><br></div><div>CategorySchemeReference was added as an additional choice in RepresentedVariable to allow for defining a categorization without an associated CodeList (this is not an allowed use in a Variable).</div><div><br></div><div>Given the modeling base of DDI 4 all representations will be identified objects and therefore this dichotomy will go away.</div><div><br></div><div>Hope this clarifies things.</div><div><br></div><div>Wendy</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 20, 2015 at 11:54 PM, Samuel Spencer <span dir="ltr"><<a href="mailto:theodore.therone@gmail.com" target="_blank">theodore.therone@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<div><br></div><div>I'm looking at ways to represent 11179 objects in DDI, specifically Value Domains.<div><br></div><div>I was pointed towards the ValueRepresentation class and think I have found a bug.</div></div><div><br></div><div>ValueRepresentationReference[1] doesn't define a CodeValueRepresentationReference, which I think makes pointing to a CodeValueRepresentation[2] not semantically possible? <br></div><div><br></div><div>But additional to this, neither the CodeValueRepresentation or the abstract ValueRepresentation[3] are identifiable which makes referring to them impossible. Meaning the only way to include them is inline within a RepresentedVariable or a VariableRepresentation[5] (which itself is non-identifiable and can only exist within a Variable[6].</div><div><br></div><div>Cheers,</div><div>Sam.</div><div> </div><div>1. <a href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/ValueRepresentationReference.html" target="_blank">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/ValueRepresentationReference.html</a><br>2. <a href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/CodeRepresentation.html" target="_blank">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/CodeRepresentation.html</a><br>3. <a href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/ValueRepresentation.html" target="_blank">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/ValueRepresentation.html</a></div><div>4. <a href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/RepresentedVariable.html" target="_blank">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/RepresentedVariable.html</a><br></div><div><div>5. <a href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/VariableRepresentation.html" target="_blank">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/VariableRepresentation.html</a></div></div><div>6. <a href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/Variable.html" target="_blank">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/Variable.html</a></div>
<br>_______________________________________________<br>
DDI-users mailing list<br>
<a href="mailto:DDI-users@icpsr.umich.edu">DDI-users@icpsr.umich.edu</a><br>
<a href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-users" target="_blank">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div>Wendy L. Thomas Phone: +1 612.624.4389</div><div>Data Access Core Director Fax: +1 612.626.8375</div><div>Minnesota Population Center Email: <a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a></div><div>University of Minnesota</div><div>50 Willey Hall</div><div>225 19th Avenue South</div><div>Minneapolis, MN 55455</div></div>
</div>