Skip to content

Commit

Permalink
requirements directly linked to GitHub
Browse files Browse the repository at this point in the history
  • Loading branch information
Nicholas Car committed Sep 23, 2018
1 parent ca8f41b commit 26fd374
Showing 1 changed file with 38 additions and 152 deletions.
190 changes: 38 additions & 152 deletions conneg-by-ap/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -209,249 +209,135 @@ <h2>List of Requirements</h2>
This section lists, and then addresses, individual requirements that the Dataset Exchange Working Group
considered important to address content negotiation by profile.
</p>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-1">
Entailment of schema.org [RES]
<a href="https://github.com/w3c/dxwg/issues/65">65</a>
</p>
</div>
<div class="issue" data-number="65"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-1">Req. 1</a></p>
<p class="respTitle">RESPONSE FOR Req. 65</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-2">
Profile definition [RPFDF]
<a href="https://github.com/w3c/dxwg/issues/72">72</a>
</p>
</div>
<div class="issue" data-number="72"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-2">Req. 2</a></p>
<p class="respTitle">RESPONSE FOR Req. 72</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-3">
Profiles listing [RPFL]
<a href="https://github.com/w3c/dxwg/issues/73">73</a>
</p>
</div>
<div class="issue" data-number="73"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-3">Req. 3</a></p>
<p class="respTitle">RESPONSE FOR Req. 73</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-4">
Profile negotiation [RPFN]
<a href="https://github.com/w3c/dxwg/issues/74">74</a>
</p>
</div>
<div class="issue" data-number="74"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-4">Req. 4</a></p>
<p class="respTitle">RESPONSE FOR Req. 74</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-5">
Usage notes [RUN]
<a href="https://github.com/w3c/dxwg/issues/86">86</a>
</p>
</div>
<div class="issue" data-number="86"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-5">Req. 5</a></p>
<p class="respTitle">RESPONSE FOR Req. 86</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-6">
Responses can conform to multiple, modular profiles (UC 5.3)
<a href="https://github.com/w3c/dxwg/issues/217">217</a>
</p>
</div>
<div class="issue" data-number="217"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-6">Req. 6</a></p>
<p class="respTitle">RESPONSE FOR Req. 217</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-7">
Define conneg interaction with media types that have a profile param
<a href="https://github.com/w3c/dxwg/issues/261">261</a>
</p>
</div>
<div class="issue" data-number="261"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-7">Req. 7</a></p>
<p class="respTitle">RESPONSE FOR Req. 261</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-8">
IETF submission must not include query param pattern requirements
<a href="https://github.com/w3c/dxwg/issues/263">263</a>
</p>
</div>
<div class="issue" data-number="263"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-8">Req. 8</a></p>
<p class="respTitle">RESPONSE FOR Req. 263</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-9">
Metadata about server profile support can be used for discovery and mediated traversal via content negotiation. [ID5] (5.5)
<a href="https://github.com/w3c/dxwg/issues/264">264</a>
</p>
</div>
<div class="issue" data-number="264"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-9">Req. 9</a></p>
<p class="respTitle">RESPONSE FOR Req. 264</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-10">
Enable the ability to negotiate the metadata profile via http, similar to the negotiation of metadata formats today. [ID30] (5.30)
<a href="https://github.com/w3c/dxwg/issues/265">265</a>
</p>
</div>
<div class="issue" data-number="265"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-10">Req. 10</a></p>
<p class="respTitle">RESPONSE FOR Req. 265</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-11">
Return http link headers using the following relationship types... [ID30] (5.30)
<a href="https://github.com/w3c/dxwg/issues/266">266</a>
</p>
</div>
<div class="issue" data-number="266"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-11">Req. 11</a></p>
<p class="respTitle">RESPONSE FOR Req. 266</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-12">
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)
<a href="https://github.com/w3c/dxwg/issues/267">267</a>
</p>
</div>
<div class="issue" data-number="267"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-12">Req. 12</a></p>
<p class="respTitle">RESPONSE FOR Req. 267</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-13">
A profile must have an identifier that can be served with a response to an API or http request. [ID2] (5.2)
<a href="https://github.com/w3c/dxwg/issues/284">284</a>
</p>
</div>
<div class="issue" data-number="284"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-13">Req. 13</a></p>
<p class="respTitle">RESPONSE FOR Req. 284</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-14">
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.
<a href="https://github.com/w3c/dxwg/issues/285">285</a>
</p>
</div>
<div class="issue" data-number="285"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-14">Req. 14</a></p>
<p class="respTitle">RESPONSE FOR Req. 285</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-15">
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)
<a href="https://github.com/w3c/dxwg/issues/286">286</a>
</p>
</div>
<div class="issue" data-number="286"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-15">Req. 15</a></p>
<p class="respTitle">RESPONSE FOR Req. 286</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-16">
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)
<a href="https://github.com/w3c/dxwg/issues/287">287</a>
</p>
</div>
<div class="issue" data-number="287"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-16">Req. 16</a></p>
<p class="respTitle">RESPONSE FOR Req. 287</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-17">
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)
<a href="https://github.com/w3c/dxwg/issues/288">288</a>
</p>
</div>
<div class="issue" data-number="288"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-17">Req. 17</a></p>
<p class="respTitle">RESPONSE FOR Req. 288</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-18">
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)
<a href="https://github.com/w3c/dxwg/issues/289">289</a>
</p>
</div>
<div class="issue" data-number="289"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-18">Req. 18</a></p>
<p class="respTitle">RESPONSE FOR Req. 289</p>
<p>

</p>
</div>
<div class="requirement">
<p class="reqTitle">Requirement</p>
<p class="req" id="req-19">
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)
<a href="https://github.com/w3c/dxwg/issues/290">290</a>
</p>
</div>
<div class="issue" data-number="290"></div>
<div class="req-response">
<p class="respTitle">RESPONSE FOR <a href="#req-19">Req. 19</a></p>
<p class="respTitle">RESPONSE FOR Req. 290</p>
<p>

</p>
Expand Down

0 comments on commit 26fd374

Please sign in to comment.