Using attributes directly exported from data connectors in other attribute definitions

[Wessel, Keith]

Hi, all,

In my continuing work to adopt the attribute registry, I've got another question.

If I have an attribute definition that currently uses a simpleAttribute type and all of its interesting bits have moved to the registry, I know I can get rid of that definition and simply add it to the exportedAttributes attribute on the data connector. Beautiful; I like a shorter attribute-resolver.xml. But if I then want to use that attribute in another attribute definition, can I pull it in with an <InputAttributeDefinition> element, or do I have to use a <InputDataConnector> element? For instance, I currently have several attribute definitions using the attribute definition of uid as an input. If I get rid of the literal <AttributeDefinition> of uid and simply add it as an exported attribute in my data connectors, do I need to change anything that's using that definition as an input to pull in the attribute from the data connector instead? Or does exporting the attribute from a data connector create a pseudo attribute definition for that attribute?

Thanks,
Keith