diff options
-rw-r--r-- | specification/forgefed-vocabulary.md | 48 |
1 files changed, 1 insertions, 47 deletions
diff --git a/specification/forgefed-vocabulary.md b/specification/forgefed-vocabulary.md index cc4a456..022f56e 100644 --- a/specification/forgefed-vocabulary.md +++ b/specification/forgefed-vocabulary.md @@ -53,27 +53,6 @@ A typical `@context` of a ForgeFed object may look like this: ## Activity Types -### Follow - -**URI:** `https://www.w3.org/ns/activitystreams#Follow` - -**Notes:** used by a user who wants to follow a repository. -This activity doesn't define a new type (the `Follow` Activity is defined in -ActivityPub) but it's here for reference. - -**Example:** - - { - "@context": [ - "https://www.w3.org/ns/activitystreams", - "https://forgefed.peers.community/ns" - ], - "summary": "Alice started following ForgeFed", - "type": "Follow", - "actor": "https://localhost/alice", - "object": "https://remotehost/bob/forgefed" - } - ### Push **URI:** `https://forgefed.peers.community/ns#Push` @@ -104,31 +83,6 @@ A Repository actor can use this Activity to notify followers of new changes. ## Actor Types -### Person - -**URI:** `https://www.w3.org/ns/activitystreams#Person` - -**Notes:** Represents forge user. For this purpose ForgeFed reuses the Person -type defined by ActivityPub. - -**Example:** - - { - "@context": [ - "https://www.w3.org/ns/activitystreams", - "https://forgefed.peers.community/ns" - ], - "type": "Person", - "id": "https://localhost/alice", - "name": "Alice Smith", - "preferredUsername": "alice", - "summary": "", - "inbox": "", - "outbox": "", - "followers": "", - "following": "" - } - ### Repository **URI:** `https://forgefed.peers.community/ns#Repository` @@ -173,7 +127,7 @@ type defined by ActivityPub. "message": "Fix #89" } -#### Ticket +### Ticket **URI:** `https://forgefed.peers.community/ns#Ticket` |