Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Emit CID service[] with lws:OpenIdProvider in WebID profiles (#320) #321
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
Uh oh!
There was an error while loading. Please reload this page.
Emit CID service[] with lws:OpenIdProvider in WebID profiles (#320) #321
Changes from all commits
cccd0816bb12c8cd17be6f7cce336943238File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — my issue-body example was inconsistent with the code. I've updated #320's Before/After to use
@id/@type(matching what this PR actually emits) and added a short rationale:On the naive-plain-JSON-lookup concern specifically: a verifier that reads this doc as plain JSON would also see
"@type": "lws:OpenIdProvider"— which is a CURIE that only expands tohttps://www.w3.org/ns/lws#OpenIdProvidervia the context. So any verifier that doesn't run JSON-LD expansion is already broken regardless ofidvs@id. Running a JSON-LD processor is the minimum bar for reading CID-conformant documents, and once that's in play both key shapes are equivalent.Could you re-review now that the PR description / issue examples match the code?