csarven on main
Add server-auxiliary-resources-… Apply suggestions from code rev… Clarify server-auxiliary-resour… and 2 more (compare)
csarven on server-link-auxiliary-type
Make server-auxiliary-resources… (compare)
Folks on the authorization panel might want to check out the discussion about auth from command line apps at https://forum.solidproject.org/t/authorisation-for-a-mobile-app/3692/9
validates fine on http://ttl.summerofcode.be/ and also using Jena's
@base <http://base1> . <a> <b> <c> . @base <http://base2> . <d> <e> <f> . <g> <h> <i> .
<http://base1/a> <http://base1/b> <http://base1/c> . <http://base2/d> <http://base2/e> <http://base2/f> . <http://base2/g> <http://base2/h> <http://base2/i> .
Acceptheader, and check whether the returned Content-Type included either
application/ld+json, which is what we ended up doing: inrupt/solid-client-js#214. If it did not include those, then we treat it as a NonRDFSource.
/, so you don't need the
typeLink header for that. Unfortunately I'm not sure what are and are not it's use cases, I'm mostly just regurgitating what I got as answers when I asked the same question a while ago :)