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.

Sign up for GitHub

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

Jump to bottom

Fix content type specifically #400

Merged
merged 7 commits into from Aug 29, 2022
Merged

Fix content type specifically #400

merged 7 commits into from Aug 29, 2022

Conversation

mmccool
Copy link
Contributor

@mmccool mmccool commented Aug 29, 2022 •
edited by pr-preview bot

Resolves #341

  • Remove "specifically" from assertion itself
  • Add informative text saying application/td+json (with one case of application/ld+json in listing affordance) is preferred as it is more specific and implies application/json
  • Add equivalent statements for CoAP content-format 50 and 432

Preview | Diff

@mmccool mmccool requested a review from farshidtz August 29, 2022 13:27
@mmccool mmccool merged commit 75dfad8 into w3c:main Aug 29, 2022
JKRhb pushed a commit to JKRhb/wot-discovery that referenced this pull request Mar 28, 2023
@mmccool @JKRhb
Fix content type specifically (w3c#400)
61f8b04 
* updates

* include VIAMEE results

* reword specifically phrasing

* using ld+json instead of td+json in one place
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@farshidtz farshidtz Awaiting requested review from farshidtz

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Improve service-http-resp-content-type assertion
1 participant
@mmccool