Currently an HTTP-backed resolver can't communicate the MIME type of the
resource. (It can only communicate the charset parameter of the
Content-Type header.)
When an NVDL subschema is in the Compact Syntax and the schema comes with
the appropriate MIME type, the parser dispatch should probably happen on
the HTTP content type, but currently that can't be done, because the
content type doesn't travel that far.
Original issue reported on code.google.com by hsivonen@iki.fi on 14 Nov 2008 at 2:52
Original issue reported on code.google.com by
hsivonen@iki.fi
on 14 Nov 2008 at 2:52