-
Notifications
You must be signed in to change notification settings - Fork 171
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
Register content-type? #79
Comments
It should probably be "application/openmetrics". |
@satterly The format is intended to be human readable text, not a binary format. But application might make sense. |
IMO Media types should be registered at iana.org. How to register a media type is explained in this RFC, where section 4.2.1 also says that a So A registration template can be found in section 5.6 |
IMHO, it should be "application" not "text" because (emphasis added) ...
That it is utf-8 encoded (and mostly human readable) is neither here nor there. It is designed to be consumed by an application, though it can be understood by humans just as JSON or XML can. XML is an good comparison because the XML mime type RFC defines three mime types ("application/xml", "application/xml-external-parsed-entity", and "application/xml-dtd") and they explicitly state in the introduction that "text/xml" is only an alias to the "application/xml" mime type. |
I am sure the rfc editors will give guidance on this once we are that far.
I don't care too much what we get as long as it makes sense.
Sent by mobile; please excuse my brevity.
… |
Fair points, @satterly. |
@satterly Thanks, What about |
Per prometheus/OpenMetrics#79 Signed-off-by: Brian Brazil <[email protected]>
Do we need to register openmetrics/text or text/openmetrics somewhere? https://github.com/RichiH/OpenMetrics/issues/8
The text was updated successfully, but these errors were encountered: