-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicit null
to omit subject (powerline)
#11
Comments
null
to omit subject (powerline)
It seems consistent with |
I think we have discussed this in the past, but can't recall conclusions we came to so I apologize to bring this up again, but maybe we can capture decisions this time around. One alternative we could consider is to constraint Similarly we could use policy to restrict delegation channel e.g. using synthetic selector that gives you iterator of |
My understanding was that we were punting on delegations restricting things beyond the |
@Gozala at least looking at my implementation from around that time, I think that we had landed on "Require that you use an explicit
Can you give me a concrete example? |
I’m ok with punning and using |
I chatted with @matheus23 earlier today about the updated powerline syntax & changes from past iterations. [Philipp, feel free to correct me if I'm wrong on any of the below but wanted to capture here.]
TL;DR he's in favour, but raised that it's too easy to omit the
sub
field accidentally. Two suggestions:sub: null
if omittedsub: "did:*
The glob has the disadvantage that it looks like you can restrict DIDs by scheme (
did:dns:*
), when I'm pretty sure that's not the behaviour that we want.I am in favour of making the
Null
explicit. In most libraries you're already going to have to give have some variation onaudience: Option<DID>
, so let's just renderNone
tonull
as a default.Any objections?
The text was updated successfully, but these errors were encountered: