From 3bf7dbea7d024f84987032e8e97842a16fe73de0 Mon Sep 17 00:00:00 2001 From: fr33domlover Date: Mon, 27 May 2019 11:17:56 +0000 Subject: [PATCH] Syntax highlighting for JSON-LD examples in federation docs --- FEDERATION.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/FEDERATION.md b/FEDERATION.md index 1637ba8..38405b4 100644 --- a/FEDERATION.md +++ b/FEDERATION.md @@ -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 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" , "@id": "https://example.dev/users/aviva/keys/key1" , "@type": "Key" , "owner": "https://example.dev/users/aviva" , "publicKeyPem": "-----BEGIN PUBLIC KEY----- ..." } +``` -GET /users/aviva +`GET /users/aviva` +```json { "@context": [ "https://www.w3.org/ns/activitystreams" , "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 all. -``` -GET /users/aviva +`GET /users/aviva` +```json { "@context": [ "https://www.w3.org/ns/activitystreams" , "https://w3id.org/security/v1"