Mimetype not registered #5

New Issue

Open

opened 2020-11-13 11:23:51 +00:00 by vanrein · 1 comment

vanrein commented

2020-11-13 11:23:51 +00:00

(Migrated from github.com)

You are producing a MIME-type without having registered it properly,

  "mimetype": "application\/searsia+json",

Please don't hijack names like that, especially not if you ignore the commonly provided x- registration-free prefixes. It's unpolite and leads to a chaos of undocumented names if standards are ignored or overruled. The interference is minimised and interoperability maximised with a simple registration of the name and a specification. In this case, it's a web form and you may get some email interaction.

You are producing a MIME-type without having [registered](https://www.iana.org/assignments/media-types/media-types.txt) it properly, ``` "mimetype": "application\/searsia+json", ``` Please don't hijack names like that, especially not if you ignore the commonly provided `x-` registration-free prefixes. It's unpolite and leads to a chaos of undocumented names if standards are ignored or overruled. The interference is minimised and interoperability maximised with a simple registration of the name and a specification. In this case, it's a [web form](https://www.iana.org/form/media-types) and you may get some email interaction.

searsia commented

2020-11-13 11:49:31 +00:00

(Migrated from github.com)

Thanks, good point, we will take this up as a possible enhancement for future versions. When producing results, the standard application/json may actually be fine for Searsia. However -- you may find this even more inpolite -- mimetypes are also used internally to decide on strategies to parse results from disparate, federated sources, see the searsiaserver code: It has totally nonsensical mimetype application/html+json, because one of our clients returned html code inside json strings, because, why not?

Thanks, good point, we will take this up as a possible enhancement for future versions. When producing results, the standard `application/json` may actually be fine for Searsia. However -- you may find this even more inpolite -- mimetypes are also used internally to decide on strategies to parse results from disparate, federated sources, see [the searsiaserver code](/searsia/searsiaserver/blob/master/src/main/java/org/searsia/engine/Resource.java#L530): It has totally nonsensical mimetype `application/html+json`, because one of our clients returned html code inside json strings, because, why not?