csarven on trust-between-owners-same-origin-multiple-storages
Trust between owners on same or… (compare)
I'd presume that the primary case to do a HEAD on a resource to check if it is available in RDF or not is because the resource URI was discovered in a containment listing.
Since the container description is not expected to include information about the contained resources (re RDF or not) client will need to go through the resources one by one.
Yes exactly. But then that info does need to be available on those Resources, so if it doesn't state that it's an RDFSource (or something equivalent), then that doesn't work either.
The Content-Type header (combined with an Accept header in the request) is probably your best bet
But at that point we're looking at actual representations right? Or should I just request
text/turtle, and if that doesn't result in a 406, I know that it's RDF?
in Solid, it is possible to have containers with HTML(+RDFa) representations
In Trellis, all Resources can be represented using RDFa (if content-negotiation requires such), and that includes containers, binaries and non-container RDF resources
text/turtleis the default format for RDF, and not e.g. JSON-LD?
Acceptheader is for