From 26fd3740ee2b4f7567432878dc64fa92deffa307 Mon Sep 17 00:00:00 2001 From: Nicholas Car Date: Sun, 23 Sep 2018 15:02:42 +1000 Subject: [PATCH] requirements directly linked to GitHub --- conneg-by-ap/index.html | 190 ++++++++-------------------------------- 1 file changed, 38 insertions(+), 152 deletions(-) diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html index d6c17b9ab..761ec5e06 100644 --- a/conneg-by-ap/index.html +++ b/conneg-by-ap/index.html @@ -209,249 +209,135 @@

List of Requirements

This section lists, and then addresses, individual requirements that the Dataset Exchange Working Group considered important to address content negotiation by profile.

-
-

Requirement

-

- Entailment of schema.org [RES] - 65 -

-
+
-

RESPONSE FOR Req. 1

+

RESPONSE FOR Req. 65

-
-

Requirement

-

- Profile definition [RPFDF] - 72 -

-
+
-

RESPONSE FOR Req. 2

+

RESPONSE FOR Req. 72

-
-

Requirement

-

- Profiles listing [RPFL] - 73 -

-
+
-

RESPONSE FOR Req. 3

+

RESPONSE FOR Req. 73

-
-

Requirement

-

- Profile negotiation [RPFN] - 74 -

-
+
-

RESPONSE FOR Req. 4

+

RESPONSE FOR Req. 74

-
-

Requirement

-

- Usage notes [RUN] - 86 -

-
+
-

RESPONSE FOR Req. 5

+

RESPONSE FOR Req. 86

-
-

Requirement

-

- Responses can conform to multiple, modular profiles (UC 5.3) - 217 -

-
+
-

RESPONSE FOR Req. 6

+

RESPONSE FOR Req. 217

-
-

Requirement

-

- Define conneg interaction with media types that have a profile param - 261 -

-
+
-

RESPONSE FOR Req. 7

+

RESPONSE FOR Req. 261

-
-

Requirement

-

- IETF submission must not include query param pattern requirements - 263 -

-
+
-

RESPONSE FOR Req. 8

+

RESPONSE FOR Req. 263

-
-

Requirement

-

- Metadata about server profile support can be used for discovery and mediated traversal via content negotiation. [ID5] (5.5) - 264 -

-
+
-

RESPONSE FOR Req. 9

+

RESPONSE FOR Req. 264

-
-

Requirement

-

- Enable the ability to negotiate the metadata profile via http, similar to the negotiation of metadata formats today. [ID30] (5.30) - 265 -

-
+
-

RESPONSE FOR Req. 10

+

RESPONSE FOR Req. 265

-
-

Requirement

-

- Return http link headers using the following relationship types... [ID30] (5.30) - 266 -

-
+
-

RESPONSE FOR Req. 11

+

RESPONSE FOR Req. 266

-
-

Requirement

-

- There is a need to distinguish between distributions that package the entire dataset and those that support access to specific items, queries, and packaged downloads of data. [ID51] (5.51) - 267 -

-
+
-

RESPONSE FOR Req. 12

+

RESPONSE FOR Req. 267

-
-

Requirement

-

- A profile must have an identifier that can be served with a response to an API or http request. [ID2] (5.2) - 284 -

-
+
-

RESPONSE FOR Req. 13

+

RESPONSE FOR Req. 284

-
-

Requirement

-

- A client should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. - 285 -

-
+
-

RESPONSE FOR Req. 14

+

RESPONSE FOR Req. 285

-
-

Requirement

-

- There should be a way for a client to look up additional information about a profile. (What kinds of information? Can we clarify this?) [ID2] (5.2) - 286 -

-
+
-

RESPONSE FOR Req. 15

+

RESPONSE FOR Req. 286

-
-

Requirement

-

- A profile can be modular, with a given response made up of more than one module. A server can indicate that a response conforms to multiple, modular profiles. [ID3] (5.3) - 287 -

-
+
-

RESPONSE FOR Req. 16

+

RESPONSE FOR Req. 287

-
-

Requirement

-

- Profiles offered by a service must be discoverable through a machine-readable graph of metadata that describes what is offered and how to invoke the offered profiles. [ID5] (5.5) - 288 -

-
+
-

RESPONSE FOR Req. 17

+

RESPONSE FOR Req. 288

-
-

Requirement

-

- Invocation of a profile may be by profile name, a schema choice, an encoding, and/or a language. (schema? And assume that encoding is type as in type="application/xml".) [ID5] (5.5) - 289 -

-
+
-

RESPONSE FOR Req. 18

+

RESPONSE FOR Req. 289

-
-

Requirement

-

- There needs to be metadata about the views provided by profiles (“named collections of properties”) that can included in a http header [ID5] (5.5) - 290 -

-
+
-

RESPONSE FOR Req. 19

+

RESPONSE FOR Req. 290