Syntax highlighting for JSON-LD examples in federation docs

This commit is contained in:
fr33domlover 2019-05-27 11:17:56 +00:00
parent e86a2970ba
commit 3bf7dbea7d

View file

@ -115,18 +115,20 @@ Allow an actor's signing key to be a separate document, rather than embedded in
the actor document. In Vervis, the use of that is for server-scope keys (see the actor document. In Vervis, the use of that is for server-scope keys (see
proposal below), but otherwise, an embedded key is just as good. proposal below), but otherwise, an embedded key is just as good.
``` `GET /users/aviva/keys/key1`
GET /users/aviva/keys/key1
```json
{ "@context": "https://w3id.org/security/v1" { "@context": "https://w3id.org/security/v1"
, "@id": "https://example.dev/users/aviva/keys/key1" , "@id": "https://example.dev/users/aviva/keys/key1"
, "@type": "Key" , "@type": "Key"
, "owner": "https://example.dev/users/aviva" , "owner": "https://example.dev/users/aviva"
, "publicKeyPem": "-----BEGIN PUBLIC KEY----- ..." , "publicKeyPem": "-----BEGIN PUBLIC KEY----- ..."
} }
```
GET /users/aviva `GET /users/aviva`
```json
{ "@context": { "@context":
[ "https://www.w3.org/ns/activitystreams" [ "https://www.w3.org/ns/activitystreams"
, "https://w3id.org/security/v1" , "https://w3id.org/security/v1"
@ -165,9 +167,9 @@ document, or a URI specifying the ID of a key defined in a separate document.
Actors that never need to post activities can simply not specify any keys at Actors that never need to post activities can simply not specify any keys at
all. all.
``` `GET /users/aviva`
GET /users/aviva
```json
{ "@context": { "@context":
[ "https://www.w3.org/ns/activitystreams" [ "https://www.w3.org/ns/activitystreams"
, "https://w3id.org/security/v1" , "https://w3id.org/security/v1"