multiple AttributeEncoders of the same type in an AttributeDefinition?

[Cantor, Scott]

On 9/11/13 4:33 PM, "Liam Hoekenga" <liamr at umich.edu> wrote:
>
>I was trying to figure out what would less ugly... adding a different
>attribute specifically for the service provider who doesn't want to use a
>standard encoding, or just extending our normal attribute definition.
>
>Potato, Po-tah-to, I suppose.

I've done both, but usually I do a separate attribute, it's just pointless
to bloat everybody else's assertions.

-- Scott