Confusing behavior of compaction with mandated context
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- json
- Domain
- authentication
Research direction
Start with the Solid OIDC context linked in the issue and the Client ID Document example in section 5.1, then reproduce the compaction in the JSON-LD Playground using the extra http://foo statement. Done means the context no longer produces the confusing alias while preserving the intended JSON-LD semantics.
Written by the indexing model from the issue text.
Description
While tryint to combine Solid-OIDC config with SAI app identity statements in the JSON-LD Playground, I stumbled upon the following practical annoyance, which I could only circumvent by diverting from the mandated JSON-LD context.
Starting from the example Client ID Document in 5.1, I expanded it with the context, and added some other statements, e.g. "http://foo": [{ "@id": "http:/bar" }]. However, when compacting the result again, such a statement becomes the "http://foo": [{ "client_id": "http:/bar" }]. While semantically correct (see below), this is of course extremely confusing to work with. It is due to the following part of the context:
"client_id": {
"@id": "@id",
"@type": "@id"
}
This creates an allias for @id, and was probably meant to remove the need of "redundantly" adding the Client Identifier twice (once as @id and once as client_id). While I am partial to the semantic elegance of this construct, the resulting behavior makes it all quite confusing. I would be in favor of changing that line of the context to "@id": "oidc:client_id".
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solid/solid-oidc
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
solid/solid-oidc#258 ·
-
doc: solid-oidc-primer editorial
Difficulty 1/5 Under an hour Newbie friendliness 75/100
solid/solid-oidc#144 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
solid/solid-oidc#238 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
solid/solid-oidc#237 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
solid/solid-oidc#231 · 1 comment ·
All issues in solid/solid-oidc
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#142 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
oblt-aw/detector/security
Difficulty 2/5 1-3 hours Newbie friendliness 70/100