You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been labelled as potentially needing a FEP, and contributors are welcome to [submit a FEP](https://codeberg.org/fediverse/fep/src/branch/main#submitting-a-fep) on the topic.
22
+
23
+
Note that issues may be closed without the FEP being created; that does not mean that the FEP is no longer needed.
Copy file name to clipboardExpand all lines: ERRATA.md
+68Lines changed: 68 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,6 +79,74 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a
79
79
80
80
- Unlike `latitude` and `longitude`, the domain of the `altitude` term is the `Object` type. The `altitude` term should be included in the list of properties of an `Object`. Because `altitude` is primarily documented as a property of a `Place`, publishers should not include `altitude` on objects that are not of type `Place`, and consumers should accept objects with this property that aren't of type `Place`.
81
81
82
+
- Example 60, for the `Tombstone` type, is missing the `@context` property. The correct example should be:
- The domain of the `attributedTo` property is both `Link` and `Object`. `attributedTo` should be included in the list of properties of a `Link`.
83
110
84
111
- The description of the `audience` property should read "Identifies one or more entities that represent the total population of entities for which the object can be considered to be relevant."
112
+
113
+
- Example 157 is not valid JSON because the `content` property extends over multiple lines. The correct example is:
"content": "Thank you <a href='http://sally.example.org'>@sally</a> for all your hard work! <a href='http://example.org/tags/givingthanks'>#givingthanks</a>",
121
+
"to": {
122
+
"name": "Sally",
123
+
"type": "Person",
124
+
"id": "http://sally.example.org"
125
+
},
126
+
"tag": {
127
+
"id": "http://example.org/tags/givingthanks",
128
+
"name": "#givingthanks"
129
+
}
130
+
}
131
+
```
132
+
133
+
- Example 102 is missing a `type` property on the `Link` value of the `url` property. For clarity, the example should read:
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,6 +83,8 @@ Extensions are documented on the [Extensions registry](https://www.w3.org/wiki/A
83
83
84
84
The [Fediverse Enhancement Proposals](https://codeberg.org/fediverse/fep) process is a lightweight collaboration process for creating and documenting Activity Streams 2.0 extensions (and other changes to the Fediverse). It's a good place to start if you're considering a backwards-compatible change.
85
85
86
+
There are many ideas for backwards-compatible changes to ActivityPub that have not yet been written up as a FEP or other document. These are marked [Needs FEP](https://github.com/w3c/activitystreams/issues?q=is%3Aissue+label%3A%22needs-fep%22) in the ActivityPub GitHub issue repository, and contributors are welcome to [submit a FEP](https://codeberg.org/fediverse/fep/src/branch/main#submitting-a-fep) on the topic. Note that issues may be closed without the FEP being created; that does not mean that the FEP is no longer needed.
87
+
86
88
Extensions that become popular can be integrated into the AS2 vocabulary document, making them practically part of the spec. The [Extensions Policy](https://swicg.github.io/extensions-policy/) describes how to propose extensions for inclusion in AS2.
87
89
88
90
Future versions of the AS2 specification(s) may include popular extensions as part of the core specs; see below.
"content": "Thank you <a href='http://sally.example.org'>@sally</agt for all your hard work! <a href='http://example.org/tags/givingthanks'>#givingthanks</a>",
0 commit comments