Skip to content

Add example that does not contain @context. #124

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Nov 23, 2024
Merged

Add example that does not contain @context. #124

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8058ef8
Add example that does not contain `@context`.
msporny Nov 16, 2024
8b6e4f4
Fix typo in no `@context` example.
msporny Nov 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2747,6 +2747,26 @@ <h4>Context Injection</h4>
(`https://www.w3.org/ns/did/v1`).
</p>

<pre class="example nohighlight" title="A controller document without an @context property">
Copy link
Collaborator

@selfissued selfissued Nov 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<pre class="example nohighlight" title="A controller document without an @context property">
<pre class="example nohighlight" title="A controller document without a @context property">

Copy link
Member

@TallTed TallTed Nov 22, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I generally read @context as "at-context", not as "context", partly because it is distinct from context. That reading makes an @context ("an at-context") appropriate, not a @context ("a at-context"). Perhaps others should weigh in, so we can decide which indefinite article to use throughout.

Copy link
Contributor

@jandrieu jandrieu Nov 22, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tend toward TallTed's perspective. I have a similar inner voice that pronounces the @: "at-context".

But I think it's more important to figure out one way and be consistent.

A bit of sleuthing shows @selfissued's take shows up once in the JSON-LD spec, but the spec also uses "an @context" six times.

Copy link
Member

@TallTed TallTed Nov 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jandrieu — Thanks for that sleuthing. w3c/json-ld-syntax#448 created to make that errant a match the other six an.

Copy link
Contributor

@David-Chadwick David-Chadwick Nov 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also read it as "an at-context"

Copy link
Member Author

@msporny msporny Nov 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the Editors have attempted to consistently read @context as at context and therefore try to keep a consistent rule of us an vs. a.

{
"id": "https://controller.example/101",
"verificationMethod": [{
"id": "https://controller.example/101#key-203947",
"type": "JsonWebKey",
"controller": "https://controller.example/101",
"publicKeyJwk": {
"kid": "key-203947",
"kty": "EC",
"crv": "P-256",
"alg": "ES256",
"x": "f83OJ3D2xF1Bg8vub9tLe1gHMzV76e8Tus9uPHvRVEU",
"y": "x_FEzRu9m36HLN_tue659LNpXW6pCyStikYjKIWI5a0"
}
}],
"authentication": ["#key-20240828"]
}
</pre>

<p>
Implementations that do not intend to use JSON-LD MAY choose to not include an
`@context` declaration at the top-level of the document. Whether or not the
Expand All @@ -2755,6 +2775,7 @@ <h4>Context Injection</h4>
processors=] are the same. Any differences in semantics between documents
processed in either mode are either implementation or specification bugs.
</p>

</section>
</section>

Expand Down