Skip to content

Commit 8737a5c

Browse files
committed
Specify type-specific rule as an advisement.
1 parent 4c3a158 commit 8737a5c

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

index.html

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4586,18 +4586,18 @@ <h2>Type-Specific Credential Processing</h2>
45864586

45874587
<p>
45884588
That is, [=type-specific credential processing=] is allowed as long as the
4589-
document being consumed or produced is a [=conforming document=]. If this
4590-
type of processing is desired, an implementer is advised to follow this rule:
4589+
document being consumed or produced is a [=conforming document=].
45914590
</p>
45924591

4593-
<ul>
4594-
<li>
4595-
Ensure that all values associated with a `@context` property are in the
4596-
expected order, the contents of the context files match known good
4597-
cryptographic hashes for each file, and domain experts have deemed that the
4598-
contents are appropriate for the intended use case.
4599-
</li>
4600-
</ul>
4592+
<p class="advisement">
4593+
If [=type-specific credential processing=] is desired, an implementer is advised
4594+
to follow this rule:
4595+
<br><br>
4596+
Ensure that all values associated with a `@context` property are in the expected
4597+
order, the contents of the context files match known good cryptographic hashes
4598+
for each file, and domain experts have deemed that the contents are appropriate
4599+
for the intended use case.
4600+
</p>
46014601

46024602
<p>
46034603
Using static context files with a JSON Schema is one acceptable approach to

0 commit comments

Comments
 (0)