|
395 | 395 | hint may be added in a future draft (see issue #73 in the GitHub repository). |
396 | 396 | </cref> |
397 | 397 | </t> |
398 | | - <t> |
399 | | - Link Description Objects do not directly indicate what operations, such |
400 | | - as HTTP methods, are supported by the target resource. Instead, operations |
401 | | - should be inferred primarily from link <xref target="rel">relation types</xref> |
402 | | - and URI schemes. Note, however, that a resource may always decline an operation at |
403 | | - runtime, for instance due to application state that controls the operation's |
404 | | - availability. |
405 | | - </t> |
406 | 398 | <t> |
407 | 399 | There are several ways that a client can use data can with a link: |
408 | 400 | <list> |
|
416 | 408 | schema keyword within the link description object. Link operations |
417 | 409 | ignore schemas that are not relevant to their semantics. |
418 | 410 | </t> |
| 411 | + <t> |
| 412 | + Link Description Objects do not directly indicate what operations, such |
| 413 | + as HTTP methods, are supported by the target resource. Instead, operations |
| 414 | + should be inferred primarily from link <xref target="rel">relation types</xref> |
| 415 | + and URI schemes. Note, however, that a resource may always decline an operation at |
| 416 | + runtime, for instance due to application state that controls the operation's |
| 417 | + availability. |
| 418 | + </t> |
419 | 419 | <section title="Resolving templated URIs"> |
420 | 420 | <t> |
421 | 421 | URI Template variables in <xref target="href">"href"</xref> resolve from |
|
0 commit comments