The LDP specification mentions the recommended use of the Accept-Post response header (in cases where POST is supported). The header itself is defined in a draft IETF document.

In the examples from the LDP documentation, this header is shown to list the various RDF serializations that a server will accept, along with any specific non-RDF mime types. Yet if a Solid server supports ldp:NonRDFSource resources of arbitrary type, it is clearly not practicable to list every known data serialization.

Is it within the scope of the Solid specification to describe what to do in this case? Should the presence of a format in this list merely indicate that the server definitely supports that format? and that the absence of a given format has no significance? Or should a server indicate only the RDF serializations that are supported? E.g.:

Accept-Post: text/turtle, application/ld+json, application/n-triples

Alternatively, should that response header contain a wildcard mime type for all possible NonRDFSource types? E.g.:

Accept-Post: text/turtle, application/ld+json, application/n-triples, */*