<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><div class=""><div><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">There's this idea that you can cross-walk attributes, but you can't. Attributes are always "just like each other" except for all the edge cases where they're not. Nothing is really interchangeable when you're operating with the precision of software.</span></div></blockquote></div><br class=""></div></div></div><div class="">I don’t think they need to be interchangeable or identical for there to be value here. I want a sufficient schematic and semantic definition, and I want a set of operations to execute on those definitions to massage my data to a point where I can interoperate with the service provider.<div class=""><br class=""></div><div class="">If someone has already written an attribute resolver template that can be used with a particularly ornery SP, I want a copy of it to work from. If that has already been done by an IdaaS vendor, I’m a new customer. If that were distributed by the federation...<br class=""><div class=""><br class=""></div><div class="">I’ve seen software do that all day, under the names of attribute resolution and attribute mapping. Same story, different locus of definition.</div></div></div></body></html>