Scoped attributes available to other definitions?

[Baron Fujimoto]

On Mon, Jan 13, 2014 at 08:05:01PM +0000, Cantor, Scott wrote:
>On 1/13/14, 3:02 PM, "Baron Fujimoto" <baron at hawaii.edu> wrote:
>>
>>Hmmm, I must have some pretty basic flaw in my definition then.
>
>I don't have the schema in front of me, but a parsing error is simply
>invalid order or syntax, so that's all that's wrong.

I assume it must be syntax then, though I'm kind of at a loss since
the encoder bits were cut-paste from other working definitions.  AFAIK,
the order is pretty basic: dependencies, definition, encoder(s)

    <!-- aacli_kludge_principal_to_email -->
    <resolver:AttributeDefinition xsi:type="ad:Mapped"
            id="aacli_kludge_principal_to_email"
            sourceAttributeID="principal">

        <resolver:Dependency ref="principal" />

        <ad:ValueMap>
            <ad:ReturnValue>$1 at hawaii.edu</ad:ReturnValue>
            <ad:SourceValue>(.+)</ad:SourceValue>
        </ad:ValueMap>

        <resolver:AttributeEncoder xsi:type="enc:SAML2String"
                name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="kludge_mail" />

    </resolver:AttributeDefinition>
    <!-- /aacli_kludge_principal_to_email -->

-baron
-- 
Baron Fujimoto <baron at hawaii.edu> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum