Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve service-http-resp-content-type assertion #341

Closed
mmccool opened this issue Jun 13, 2022 · 1 comment · Fixed by #400
Closed

Improve service-http-resp-content-type assertion #341

mmccool opened this issue Jun 13, 2022 · 1 comment · Fixed by #400
Assignees
Labels
Resolve by CR Issues that need to be resolved by CR

Comments

@mmccool
Copy link
Contributor

mmccool commented Jun 13, 2022

  • The use of "specifically" is a little confusing. What we want to say is to allow either application/json or application/td+json, but that td+json is more specific (and implies/includes application/json).
  • We also need to do the corresponding thing in CoAP, simply allowing two numeric content codes for either application/json or application/td+json
@farshidtz
Copy link
Member

farshidtz commented Jun 13, 2022

This wording currently appears in three places:

wot-discovery/index.html

Lines 1052 to 1054 in 2356eb5

<span class="rfc2119-assertion" id="exploration-server-http-resp-content-type">
A successful response with JSON serialization MUST contain `application/json`
or more specifically, `application/td+json` in the Content-Type header.</span>

wot-discovery/index.html

Lines 1622 to 1624 in 898f607

<span class="rfc2119-assertion" id="tdd-things-retrieve-resp-content-type">
A successful response with JSON serialization MUST contain `application/json`
or more specifically, `application/td+json` in the Content-Type header.</span>

wot-discovery/index.html

Lines 1851 to 1853 in 2356eb5

<span class="rfc2119-assertion" id="tdd-things-list-resp-content-type">
A successful response with JSON serialization MUST contain `application/json`
or more specifically, `application/ld+json` in the Content-Type header.</span>

@mmccool mmccool self-assigned this Jun 27, 2022
@mmccool mmccool added the Resolve by CR Issues that need to be resolved by CR label Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolve by CR Issues that need to be resolved by CR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants