<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 1, 2016 at 10:13 AM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">By definition if the definition is an aggregate of others, it shouldn't be of a type that intrinsically can only operate on one.</blockquote></div><br>Are there definitions that don't require a source attribute?</div><div class="gmail_extra"><br></div><div class="gmail_extra">One of our examples is our construction of eduPersonScopedAffiliation</div><div class="gmail_extra">We have multiple campuses, and we wanted to be able to represent them in ePSA.</div><div class="gmail_extra">Rather than have one giant mapped attribute that could calculate ePSA, we currently have campus specific mapped attributes that are aggregated under ePSA:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">    <resolver:AttributeDefinition id="eduPersonScopedAffiliation" xsi:type="ad:Prescoped"></div><div class="gmail_extra">        <resolver:Dependency ref="umichPersonScopedAffiliation"/></div><div class="gmail_extra">        <resolver:Dependency ref="umichPersonScopedAffiliationAA"/></div><div class="gmail_extra">        <resolver:Dependency ref="umichPersonScopedAffiliationDBRN"/></div><div class="gmail_extra">        <resolver:Dependency ref="umichPersonScopedAffiliationFLNT"/></div><div class="gmail_extra">...</div><div class="gmail_extra">    </resolver:AttributeDefinition><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">It made sense at the time we did it.</div><div class="gmail_extra">Do we live with the warning? Are there more appropriate attribute types?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Liam</div></div></div>