We should support the use of Structured Syntax Name Suffixes as a fallback for importers.
Currently we support rdf+xml and know that it's more specific than the generic text/xml so we should try the RDF importer before the XML importer, but if we encounter an unknown type with a syntax suffix, we don't prioritize the appropriate importer.
The idea would be that if we were to encounter application/3gpdash-qoe-report+xml or application/activity+json (to pick the first ones on the list), we would suggest the XML and JSON importers, respectively, as the first fallback options.
This is something we could implement directly in the importer framework, so perhaps it's orthogonal to the idea that @wetneb had for #2598.
Originally posted by @tfmorris in #2598 (comment)
We should support the use of Structured Syntax Name Suffixes as a fallback for importers.
Currently we support
rdf+xmland know that it's more specific than the generictext/xmlso we should try the RDF importer before the XML importer, but if we encounter an unknown type with a syntax suffix, we don't prioritize the appropriate importer.The idea would be that if we were to encounter
application/3gpdash-qoe-report+xmlorapplication/activity+json(to pick the first ones on the list), we would suggest the XML and JSON importers, respectively, as the first fallback options.This is something we could implement directly in the importer framework, so perhaps it's orthogonal to the idea that @wetneb had for #2598.
Originally posted by @tfmorris in #2598 (comment)