{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 兄弟一词,经得起流年. 的问题《Using plus sign in custom internet media types (MI》','https://www.manongdao.com/q-613230.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm building a RESTful web service, and I'm creating some custom media types. It seems like in media types the subtype becomes more specific as you go right to left using '+'. So for example:
application/json is more general than application/hal+json, since HAL adds more restrictions on top of json.
My question is whether this is standard, or just a convention (I've poked through some of the RFCs on MIME types and I couldn't find anything, but I may not have looked hard enough).
If it is standard, does it generalize so I can add even more specific subtypes like application/vnd.custom.mime+hal+json or is it limited to one "+"?
The procedure for registering new suffixes is now defined in http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-regs-14#section-6.
"+json" will be defined in a separate document; right now: http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-02#section-3.1
And no, you are not supposed to have multiple subtypes there.