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

Mime type name inconsistent in http problem section 9 #2

Closed
pezra opened this issue Jun 29, 2012 · 5 comments
Closed

Mime type name inconsistent in http problem section 9 #2

pezra opened this issue Jun 29, 2012 · 5 comments

Comments

@pezra
Copy link

pezra commented Jun 29, 2012

listed as application/json-problem but then the sub-type is declared as problem+json

@pezra
Copy link
Author

pezra commented Jun 29, 2012

Fwiw, i very much prefer application/problem+json.

@mnot
Copy link
Owner

mnot commented Jul 3, 2012

Fixed, thanks. +json doesn't quite yet exist.

@mnot mnot closed this as completed Jul 3, 2012
@pezra
Copy link
Author

pezra commented Jul 3, 2012

By what definition does '+json' not exist? Its meaning is convention rather than normative, but there is absolutely no confusion about its meaning. In what sense does 'json-' exist if '+json' doesn't?

@mnot
Copy link
Owner

mnot commented Jul 3, 2012

See:
http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-01

This registers the convention; it's not final yet.

@pezra
Copy link
Author

pezra commented Jul 3, 2012

In that case i'd say jump on board the rough consensus.

On Tuesday, July 3, 2012, Mark Nottingham wrote:

See:

http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-01

This registers the convention; it's not final yet.


Reply to this email directly or view it on GitHub:
#2 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants