Thanks to Kim's explanation finally I have a clear understanding of how the InfoCard selection mechanism (GUI) will work.
In my blog here I was saying that what is displayed in wireframe GUI that comes with Indigo BETA SDK is an attribute card and not Infocard. My understanding was wrong. He corrects me here
“Well, the question is, does the user have to know about the metadata connecting the InfoCard to the Identity Provider? I don't think so. Therefore we "dereference" the metadata and show the underlying identity information. Developers might find this confusing at first, but what do developers like better than a level of indirection????
Here's our thinking. The InfoCards contain "metadata" just as Kapil says. But when a user looks at an InfoCard, we don't show her the metadata (which would be meaningless to her). Instead, we use the metadata to procure a token, and show the information the identity provider is capable of releasing (in other words the set of claims that go along with that identity). “
So, what is displayed is a portion of InfoCard i.e set of claims supported by STS (whose representive this InfoCard is).
But in wirefram GUI I am able to see the attributes (data) which I can also edit, it goes against the notion that InfoCard is just a metadata.
Trevor Lawrence throws a light on this as a comment in Kim's blog.
“It looks at the moment as if the InfoCard UI has a special case built in to allow you to edit your claims in the self-asserted IP that is included. In general, as I understand it, out-of-band mechanisms are likely to be needed to change the claim data that an external IP asserts for a user. (In an authoritive IP I can't just change my passport number without by some other means proving to this IP that that indeed is the number of a new passport issued to me.) “
Now this makes everything clear. What is displayed are supported claims in InfoCard (minus the geekey part) and if these claims reside on user's machine (PC as a local identity provider) then you can edit and see the claims else you need an out of band mechanism to do that. Mostly knowing that these are claims [not data] (displayed in wireframe GUI) which will be transmitted by my IDP to relying party should be enough.
Many thanks to Kim and Trevor for insight.