|
1950 | 1950 | <figure> |
1951 | 1951 | <artwork> |
1952 | 1952 | <![CDATA[ |
1953 | | - Content-Type: application/json; |
| 1953 | + Content-Type: application/schema-instance+json; |
1954 | 1954 | schema="https://example.com/my-hyper-schema#" |
1955 | 1955 | ]]> |
1956 | 1956 | </artwork> |
|
1964 | 1964 | <figure> |
1965 | 1965 | <artwork> |
1966 | 1966 | <![CDATA[ |
1967 | | - Content-Type: application/json; |
| 1967 | + Content-Type: application/schema-instance+json; |
1968 | 1968 | schema="https://example.com/alice https://example.com/bob" |
1969 | 1969 | ]]> |
1970 | 1970 | </artwork> |
|
1977 | 1977 | <figure> |
1978 | 1978 | <artwork> |
1979 | 1979 | <![CDATA[ |
1980 | | - Accept: application/json; |
| 1980 | + Accept: application/schema-instance+json; |
1981 | 1981 | schema="https://example.com/qiang https://example.com/li", |
1982 | | - application/json; |
| 1982 | + application/schema-instance+json; |
1983 | 1983 | schema="https://example.com/kumar" |
1984 | 1984 | ]]> |
1985 | 1985 | </artwork> |
|
1995 | 1995 | indicate that the client can accept several media types. |
1996 | 1996 | In the above example, note that the two media types differ |
1997 | 1997 | only by their schema parameter values. This requests an |
1998 | | - application/json representation that conforms to at least one |
| 1998 | + application/schema-instance+json representation that conforms to at least one |
1999 | 1999 | of the identified schemas. |
2000 | 2000 | </t> |
2001 | 2001 |
|
|
0 commit comments