[Openid-specs-risc] openid/sharedsignals: Comment created on issue 85

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 85
Issue Title: Simple & Complex Subject Identifiers: why not use "aliases" construct defined in secevents draft spec?
https://github.com/openid/sharedsignals/issues/85

Comment: I think that once we realized that the Aliases format does not carry the same semantic information as the Complex format, the issue was dropped. That is, you _could_ put all of the Simple subjects that make up a Complex subject into an Aliases format instead, but you would no longer know whether each Simple subject referred to a user, a group, a tenant, etc. What about @independentid 's original comment that sparked this thread? Should we consider changing `complex` format to `ssf-complex` to make it less likely to conflict with something else?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20240426/61115aa7/attachment.html>