Skip to content

Commit 72a16b8

Browse files
janinajjaninaj
committed
Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into gh-pages
2 parents df8fa43 + 04d3461 commit 72a16b8

21 files changed

+7482
-5892
lines changed

‎annotation-model/README.md

+23-10
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,35 @@
1-
Annotation Model Test Results
1+
Annotation Model test results
22
=============================
33

4-
Placeholder for annotation-model test results. Once some results are available, the
5-
implementation report will be available at
4+
Up-to-date result reports are available at:
65

7-
* http://w3c.github.io/test-results/annotation-model/all.html
6+
* https://w3c.github.io/test-results/annotation-model/all.html
7+
* https://w3c.github.io/test-results/annotation-model/less-than-2.html
8+
* https://w3c.github.io/test-results/annotation-model/complete-fails.html
9+
10+
Index of implementations in reports
11+
===================================
12+
13+
* EM - ???
14+
* IC - ???
15+
* MO - ???
16+
17+
18+
Adding new results
19+
==================
820

921
To add new tests results:
1022

11-
1. Select a two letter abbreviation for your implementation under test (e.g., AB)
12-
2. Produce a JSON test result files using http://w3c-test.org/tools/runner/index.html (or a local copy); naming that file using the two letter abbreviation and a two digit representation of the version number under test.
23+
1. Fork the test-results repo if you haven't already (https://github.com/w3c/test-results)
24+
2. Select a two letter abbreviation for your implementation under test (e.g., AB) and add it to the list above
25+
3. Produce a JSON test result files using http://w3c-test.org/tools/runner/index.html (or a local copy); naming that file using the two letter abbreviation and a two digit representation of the version number under test.
1326
* Use `/annotation-model` as the path for which tests to run.
14-
* Click start and there will be three pages, each of which will prompt for the JSON serialization of the annotation.
27+
* Click start and there will be several pages, each of which will prompt for a JSON serialization of an annotation from your implementation.
1528
* Note that failures in the test results can be caused by the annotation not using that particular feature, and for the optional tests should not be cause for alarm.
16-
3. Fork the test-results repo if you haven't already (https://github.com/w3c/test-results)
1729
4. Place your new _AA00_.json results in the annotation-model directory
18-
5. Create a pull request with your updated file
19-
6. When it is merged the maintainers will update the overall results report automatically (https://w3c.github.io/test-results/annotation-model/all.html)
30+
5. Create a pull request with your updated files
31+
6. When it is merged the maintainers will update the overall results reports automatically
2032

2133
If you want to see what the report would look like locally, use the wptreport tool (https://github.com/spec-ops/wptreport) to build a
2234
report with a command line like `wptreport -f -m -s "Annotation Model"`
35+

‎annotation-model/all.html

+330-252
Large diffs are not rendered by default.

‎annotation-model/complete-fails.html

+230-181
Large diffs are not rendered by default.

‎annotation-model/consolidated.json

+628-389
Large diffs are not rendered by default.

‎annotation-model/less-than-2.html

+246-178
Large diffs are not rendered by default.

‎annotation-protocol/CC01.json

+236
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,236 @@
1+
{
2+
"results": [
3+
{
4+
"test": "/annotation-protocol/server/server-manual.html",
5+
"subtests": [
6+
{
7+
"name": "Container MUST end in a \"/\" character",
8+
"status": "PASS",
9+
"message": null
10+
},
11+
{
12+
"name": "Containers MUST support GET (check Allow on GET)",
13+
"status": "PASS",
14+
"message": null
15+
},
16+
{
17+
"name": "Containers MUST support HEAD (check Allow on GET)",
18+
"status": "PASS",
19+
"message": null
20+
},
21+
{
22+
"name": "Containers MUST support OPTIONS (check Allow on GET)",
23+
"status": "PASS",
24+
"message": null
25+
},
26+
{
27+
"name": "Containers MUST have a Content-Type header with the application/ld+json media type",
28+
"status": "PASS",
29+
"message": null
30+
},
31+
{
32+
"name": "Containers MUST response with the JSON-LD representation (by default)",
33+
"status": "PASS",
34+
"message": null
35+
},
36+
{
37+
"name": "Containers MUST return a description of the container with BasicContainer",
38+
"status": "PASS",
39+
"message": null
40+
},
41+
{
42+
"name": "Containers MUST return a description of the container with AnnotationCollection",
43+
"status": "PASS",
44+
"message": null
45+
},
46+
{
47+
"name": "Containers MUST return a Link header (rfc5988) on all responses",
48+
"status": "PASS",
49+
"message": null
50+
},
51+
{
52+
"name": "Containers MUST have an ETag header",
53+
"status": "PASS",
54+
"message": null
55+
},
56+
{
57+
"name": "Containers MUST have a Vary header with Accept in the value",
58+
"status": "PASS",
59+
"message": null
60+
},
61+
{
62+
"name": "Containers MUST advertise its type by including a link where the rel parameter value is type and the target IRI is the appropriate Container Type",
63+
"status": "PASS",
64+
"message": null
65+
},
66+
{
67+
"name": "Containers MUST advertise that it imposes Annotation protocol specific constraints by including a link where the target IRI is http://www.w3.org/TR/annotation-protocol/, and the rel parameter value is the IRI http://www.w3.org/ns/ldp#constrainedBy",
68+
"status": "PASS",
69+
"message": null
70+
},
71+
{
72+
"name": "Containers MUST support HEAD method",
73+
"status": "PASS",
74+
"message": null
75+
},
76+
{
77+
"name": "Containers MUST support OPTIONS method",
78+
"status": "PASS",
79+
"message": null
80+
},
81+
{
82+
"name": "Containers MUST include a Content-Location header with the IRI as its value",
83+
"status": "PASS",
84+
"message": null
85+
},
86+
{
87+
"name": "Container's Content-Location and `id` MUST match",
88+
"status": "FAIL",
89+
"message": "assert_true: expected true got false"
90+
},
91+
{
92+
"name": "Annotation Pages must have a link to the container they are part of, using the partOf property",
93+
"status": "PASS",
94+
"message": null
95+
},
96+
{
97+
"name": "Annotation Pages MUST have a link to the previous page in the sequence, using the prev property (if not the first page)",
98+
"status": "PASS",
99+
"message": null
100+
},
101+
{
102+
"name": "Annotation Pages MUST have a link to the next page in the sequence, using the next property (if not the last page)",
103+
"status": "PASS",
104+
"message": null
105+
},
106+
{
107+
"name": "Annotations MUST support GET (check Allow on GET)",
108+
"status": "PASS",
109+
"message": null
110+
},
111+
{
112+
"name": "Annotations MUST support HEAD (check Allow on GET)",
113+
"status": "PASS",
114+
"message": null
115+
},
116+
{
117+
"name": "Annotations MUST support OPTIONS (check Allow on GET)",
118+
"status": "PASS",
119+
"message": null
120+
},
121+
{
122+
"name": "Annotations MUST have a Content-Type header with the application/ld+json media type",
123+
"status": "PASS",
124+
"message": null
125+
},
126+
{
127+
"name": "Annotations MUST have a Link header entry where the target IRI is http://www.w3.org/ns/ldp#Resource and the rel parameter value is type",
128+
"status": "FAIL",
129+
"message": "assert_equals: <http://www.w3.org/ns/ldp#Resource>; rel=\"type\" not found in Link expected \"<http://www.w3.org/ns/ldp#Resource>; rel=\\\"type\\\"\" but got \"<http://www.w3.org/ns/ldp#Resource>;rel=\\\"type\\\"\""
130+
},
131+
{
132+
"name": "Annotations MUST have an ETag header",
133+
"status": "PASS",
134+
"message": null
135+
},
136+
{
137+
"name": "Annotations MUST have a Vary header with Accept in the value",
138+
"status": "PASS",
139+
"message": null
140+
},
141+
{
142+
"name": "Annotations MUST support HEAD method",
143+
"status": "PASS",
144+
"message": null
145+
},
146+
{
147+
"name": "Annotations MUST support OPTIONS method",
148+
"status": "PASS",
149+
"message": null
150+
},
151+
{
152+
"name": "Created Annotation MUST have an id property",
153+
"status": "PASS",
154+
"message": null
155+
},
156+
{
157+
"name": "Created Annotation MUST have an id that starts with the Container IRI",
158+
"status": "PASS",
159+
"message": null
160+
},
161+
{
162+
"name": "Created Annotation MUST preserve any canonical IRI",
163+
"status": "PASS",
164+
"message": null
165+
},
166+
{
167+
"name": "Annotation Server MUST respond with a 201 Created code if the creation is successful",
168+
"status": "PASS",
169+
"message": null
170+
},
171+
{
172+
"name": "Location header SHOULD match the id of the new Annotation",
173+
"status": "PASS",
174+
"message": null
175+
},
176+
{
177+
"name": "Annotation update must be done with the PUT method",
178+
"status": "PASS",
179+
"message": null
180+
},
181+
{
182+
"name": "Annotation deletion with DELETE method MUST return a 204 status",
183+
"status": "PASS",
184+
"message": null
185+
},
186+
{
187+
"name": "Annotation server SHOULD use HTTPS rather than HTTP",
188+
"status": "FAIL",
189+
"message": "assert_equals: Server is not using HTTPS expected \"http:\" but got \"https\""
190+
},
191+
{
192+
"name": "SHOULD return the full annotation descriptions",
193+
"status": "PASS",
194+
"message": null
195+
},
196+
{
197+
"name": "SHOULD include the total property with the total number of annotations in the container",
198+
"status": "PASS",
199+
"message": null
200+
},
201+
{
202+
"name": "SHOULD have a link to the first page of its contents using `first`",
203+
"status": "PASS",
204+
"message": null
205+
},
206+
{
207+
"name": "SHOULD have a link to the last page of its contents using `last`",
208+
"status": "FAIL",
209+
"message": "assert_true: expected true got false"
210+
},
211+
{
212+
"name": "Response contains annotations via `items` when it SHOULD NOT",
213+
"status": "PASS",
214+
"message": null
215+
},
216+
{
217+
"name": "Response contains annotations via `ldp:contains` when it SHOULD NOT",
218+
"status": "PASS",
219+
"message": null
220+
},
221+
{
222+
"name": "SHOULD include Prefer in the Vary header",
223+
"status": "PASS",
224+
"message": null
225+
},
226+
{
227+
"name": "SHOULD NOT [receive] the Prefer header when requesting the page",
228+
"status": "PASS",
229+
"message": null
230+
}
231+
],
232+
"status": "OK",
233+
"message": null
234+
}
235+
]
236+
}

‎annotation-protocol/README.md

+24-9
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,32 @@
1-
Annotation Protocol Test Results
2-
=============================
1+
Annotation Protocol test results
2+
================================
33

4-
Placeholder for annotation-protocol test results. Once some results are available, the
5-
implementation report will be available at
4+
Up-to-date result reports are available at:
65

7-
* `http://w3c.github.io/test-results/annotation-protocol/all.html`
6+
* https://w3c.github.io/test-results/annotation-protocol/all.html
7+
* https://w3c.github.io/test-results/annotation-protocol/less-than-2.html
8+
* https://w3c.github.io/test-results/annotation-protocol/complete-fails.html
9+
10+
Index of implementations tested
11+
===============================
12+
13+
* RI - Reference Implementation
14+
* CC - Conquering Corsairs
15+
16+
Adding new results
17+
==================
818

919
To add new tests results:
1020

11-
1. Select a two letter abbreviation for your implementation under test (e.g., AB)
12-
2. Produce a JSON test result files using http://w3c-test.org/tools/runner/index.html (or a local copy); naming that file using the two letter abbreviation and a two digit representation of the version number under test.
13-
3. For the test-results repo if you haven't already (https://github.com/w3c/test-results)
21+
1. Fork the test-results repo if you haven't already (https://github.com/w3c/test-results)
22+
2. Select a two letter abbreviation for your implementation under test (e.g., AB) and add it to the list above
23+
2. Produce a JSON test result files using http://w3c-test.org/tools/runner/index.html?path=/annotation-protocol (or a local copy); naming that file using the two letter abbreviation and a two digit representation of the version number under test.
24+
* Use `/annotation-protocol` as the path for which tests to run.
25+
* Note that failures in the test results can be caused by the server not using that particular feature, and for the optional tests should not be cause for alarm.
1426
4. Place your new .json results in the annotation-protocol directory
1527
5. Create a pull request with your updated file
16-
6. When it is merged the maintainers will update the overall results report automatically (https://w3c.github.io/test-results/annotation-model/all.html)
28+
6. When it is merged the maintainers will update the overall results reports automatically
29+
30+
If you want to see what the report would look like locally, use the wptreport tool (https://github.com/spec-ops/wptreport) to build a
31+
report with a command line like `wptreport -f -m -s "Annotation Procotol"`
1732

0 commit comments

Comments
 (0)