Repository navigation
An assumption of the UI being the consumer of the returned data #25
Description
Activity
Using the data for an UI was my primary use-case. But I wanted to be open about other use-cases, therefore yes the data can be used in other ways, absolutely. Apparently, there is room for improvement to phrase this better.
But I think it is important to note that the data returned is not signed.
Makes sense. Although the similar ui_ convention is used in other specs, I think we need to be mindful of say AI agents using it too.
I agree that we shouldn't include the "ui_" prefix in the identifier names. Yes, the returned values may be used in UIs but those are not the only potential uses.
@zachmann What would you say about changing ui info to entity info to make it more generous?
I'm fine with changing the claim. I think
entity_infosis reasonable. I can prepare a PR for it.- linked a pull request that will close this issuerename ui_infos to entity_infos and ui_claims to info_claims #58
on May 29, 2026
Is it necessary to prescribe the use of the returned data? I understand that there's a use case where the UI needs it, but we do not know whether this is going to be the UI that is going to use it. It is just data that can be used in various ways.