Skip to content

Commit 7b42bc3

Browse files
evanpevanp
committed
fix: indentation on ERRATA.md
1 parent 706f85f commit 7b42bc3

File tree

1 file changed

+137
-137
lines changed

1 file changed

+137
-137
lines changed

‎ERRATA.md‎

Lines changed: 137 additions & 137 deletions
Original file line numberDiff line numberDiff line change
@@ -4,159 +4,159 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a
44

55
## Activity Streams
66

7-
- None yet reported.
7+
- None yet reported.
88

99
## Activity Vocabulary
1010

11-
- Example 150 has `latitude` and `longitude` properties with string values.
12-
The range of these properties is `xsd:float`. A correct example would be:
13-
14-
```json
15-
{
16-
"@context": "https://www.w3.org/ns/activitystreams",
17-
"type": "Place",
18-
"name": "San Francisco, CA",
19-
"longitude": 122.4167,
20-
"latitude": 37.7833
21-
}
22-
```
23-
24-
- Example 80 has `Image` objects with `width` and `height` properties, which
25-
are only allowed on `Link` objects. One alternative is to use `Link` objects
26-
with the correct `height` and `width` as the `url` property for each `Image`
27-
object.
28-
29-
```json
30-
{
31-
"@context": "https://www.w3.org/ns/activitystreams",
32-
"summary": "A simple note",
33-
"type": "Note",
34-
"content": "A simple note",
35-
"icon": [
36-
{
37-
"type": "Image",
38-
"summary": "Note (16x16)",
39-
"url": {
40-
"type": "Link",
41-
"href": "http://example.org/note1.png",
42-
"width": 16,
43-
"height": 16
44-
}
45-
},
46-
{
47-
"type": "Image",
48-
"summary": "Note (32x32)",
49-
"url": {
50-
"type": "Link",
51-
"href": "http://example.org/note2.png",
52-
"width": 32,
53-
"height": 32
54-
}
11+
- Example 150 has `latitude` and `longitude` properties with string values.
12+
The range of these properties is `xsd:float`. A correct example would be:
13+
14+
```json
15+
{
16+
"@context": "https://www.w3.org/ns/activitystreams",
17+
"type": "Place",
18+
"name": "San Francisco, CA",
19+
"longitude": 122.4167,
20+
"latitude": 37.7833
21+
}
22+
```
23+
24+
- Example 80 has `Image` objects with `width` and `height` properties, which
25+
are only allowed on `Link` objects. One alternative is to use `Link` objects
26+
with the correct `height` and `width` as the `url` property for each `Image`
27+
object.
28+
29+
```json
30+
{
31+
"@context": "https://www.w3.org/ns/activitystreams",
32+
"summary": "A simple note",
33+
"type": "Note",
34+
"content": "A simple note",
35+
"icon": [
36+
{
37+
"type": "Image",
38+
"summary": "Note (16x16)",
39+
"url": {
40+
"type": "Link",
41+
"href": "http://example.org/note1.png",
42+
"width": 16,
43+
"height": 16
5544
}
56-
]
57-
}
58-
```
59-
60-
- The range of the `units` property is given as an enumerated set of values.
61-
Due to a formatting error, some of these values are shown with an incorrect
62-
leading space character. The correct range is:
63-
64-
```text
65-
"cm" | "feet" | "inches" | "km" | "m" | "miles" | xsd:anyURI
66-
```
67-
68-
- Example 58 includes a `summary` property on a `Mention` object, which is
69-
not allowed. A corrected example:
70-
71-
```json
72-
{
73-
"@context": "https://www.w3.org/ns/activitystreams",
74-
"type": "Mention",
75-
"href": "http://example.org/joe",
76-
"name": "Joe"
77-
}
78-
```
79-
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-
82-
- Example 60, for the `Tombstone` type, is missing the `@context` property. The correct example should be:
83-
84-
```json
85-
{
86-
"@context": "https://www.w3.org/ns/activitystreams",
87-
"type": "OrderedCollection",
88-
"totalItems": 3,
89-
"name": "Vacation photos 2016",
90-
"orderedItems": [
91-
{
92-
"type": "Image",
93-
"id": "http://image.example/1"
94-
},
95-
{
96-
"type": "Tombstone",
97-
"formerType": "Image",
98-
"id": "http://image.example/2",
99-
"deleted": "2016-03-17T00:00:00Z"
100-
},
101-
{
102-
"type": "Image",
103-
"id": "http://image.example/3"
45+
},
46+
{
47+
"type": "Image",
48+
"summary": "Note (32x32)",
49+
"url": {
50+
"type": "Link",
51+
"href": "http://example.org/note2.png",
52+
"width": 32,
53+
"height": 32
10454
}
105-
]
106-
}
107-
```
55+
}
56+
]
57+
}
58+
```
59+
60+
- The range of the `units` property is given as an enumerated set of values.
61+
Due to a formatting error, some of these values are shown with an incorrect
62+
leading space character. The correct range is:
63+
64+
```text
65+
"cm" | "feet" | "inches" | "km" | "m" | "miles" | xsd:anyURI
66+
```
67+
68+
- Example 58 includes a `summary` property on a `Mention` object, which is
69+
not allowed. A corrected example:
70+
71+
```json
72+
{
73+
"@context": "https://www.w3.org/ns/activitystreams",
74+
"type": "Mention",
75+
"href": "http://example.org/joe",
76+
"name": "Joe"
77+
}
78+
```
79+
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+
82+
- Example 60, for the `Tombstone` type, is missing the `@context` property. The correct example should be:
83+
84+
```json
85+
{
86+
"@context": "https://www.w3.org/ns/activitystreams",
87+
"type": "OrderedCollection",
88+
"totalItems": 3,
89+
"name": "Vacation photos 2016",
90+
"orderedItems": [
91+
{
92+
"type": "Image",
93+
"id": "http://image.example/1"
94+
},
95+
{
96+
"type": "Tombstone",
97+
"formerType": "Image",
98+
"id": "http://image.example/2",
99+
"deleted": "2016-03-17T00:00:00Z"
100+
},
101+
{
102+
"type": "Image",
103+
"id": "http://image.example/3"
104+
}
105+
]
106+
}
107+
```
108108

109-
- The domain of the `attributedTo` property is both `Link` and `Object`. `attributedTo` should be included in the list of properties of a `Link`.
109+
- The domain of the `attributedTo` property is both `Link` and `Object`. `attributedTo` should be included in the list of properties of a `Link`.
110110

111-
- The Notes for the `to` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the public primary audience of this Object."
111+
- The Notes for the `to` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the public primary audience of this Object."
112112

113-
- The Notes for the `bto` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the private primary audience of this Object."
113+
- The Notes for the `bto` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the private primary audience of this Object."
114114

115-
- The Notes for the `cc` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the public secondary audience of this Object."
115+
- The Notes for the `cc` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the public secondary audience of this Object."
116116

117-
- The Notes for the `bcc` property do not correctly define the range of the property, limiting it to only the `Object` type. The notes should read: "Identifies one or more entities that are part of the private secondary audience of this Object."
117+
- The Notes for the `bcc` property do not correctly define the range of the property, limiting it to only the `Object` type. The notes should read: "Identifies one or more entities that are part of the private secondary audience of this Object."
118118

119-
- 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."
119+
- 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."
120120

121-
- Example 157 is not valid JSON because the `content` property extends over multiple lines. The correct example is:
121+
- Example 157 is not valid JSON because the `content` property extends over multiple lines. The correct example is:
122122

123-
```json
124-
{
125-
"@context": "https://www.w3.org/ns/activitystreams",
126-
"name": "A thank-you note",
127-
"type": "Note",
128-
"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>",
129-
"to": {
130-
"name": "Sally",
131-
"type": "Person",
132-
"id": "http://sally.example.org"
133-
},
134-
"tag": {
135-
"id": "http://example.org/tags/givingthanks",
136-
"name": "#givingthanks"
137-
}
123+
```json
124+
{
125+
"@context": "https://www.w3.org/ns/activitystreams",
126+
"name": "A thank-you note",
127+
"type": "Note",
128+
"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>",
129+
"to": {
130+
"name": "Sally",
131+
"type": "Person",
132+
"id": "http://sally.example.org"
133+
},
134+
"tag": {
135+
"id": "http://example.org/tags/givingthanks",
136+
"name": "#givingthanks"
138137
}
139-
```
140-
141-
- Example 102 is missing a `type` property on the `Link` value of the `url` property. For clarity, the example should read:
142-
143-
```json
144-
{
145-
"@context": "https://www.w3.org/ns/activitystreams",
138+
}
139+
```
140+
141+
- Example 102 is missing a `type` property on the `Link` value of the `url` property. For clarity, the example should read:
142+
143+
```json
144+
{
145+
"@context": "https://www.w3.org/ns/activitystreams",
146+
"type": "Video",
147+
"name": "Cool New Movie",
148+
"duration": "PT2H30M",
149+
"preview": {
146150
"type": "Video",
147-
"name": "Cool New Movie",
148-
"duration": "PT2H30M",
149-
"preview": {
150-
"type": "Video",
151-
"name": "Trailer",
152-
"duration": "PT1M",
153-
"url": {
154-
"type": "Link",
155-
"href": "http://example.org/trailer.mkv",
156-
"mediaType": "video/mkv"
157-
}
151+
"name": "Trailer",
152+
"duration": "PT1M",
153+
"url": {
154+
"type": "Link",
155+
"href": "http://example.org/trailer.mkv",
156+
"mediaType": "video/mkv"
158157
}
159158
}
160-
```
159+
}
160+
```
161161

162162
- In Section 4, the range of the `formerType` property is given as `Object`. The property should have the same range as the `type` property for which it forms a replacement for deleted `Tombstone` objects.

0 commit comments

Comments
 (0)