దామోదర

@kjetilk , @elf-pavlik > I believe we should address this in the future. I am not sure if gravity of this issue is clearly understood. **Solid doesn't specify whether to...

> contd from above... > > There seems two straight-forward behaviours possible to address this case. > > 1. Solid should specify, it only supports uris for information resources it...

@kjetilk , thanks for response > On the backend, I suspect that IRIs would be prevalent, as RDF is defined in those terms. In the case of NSS, I found...

@elf-pavlik auxilliary resources can only be LDP-RS(s) at present. Which have same issues of non-auxiliary rdf resources in preserving comments, whitespace etc. If they are to be saved as `text/plain`...

`oxigraph::io` seems can be used as layer over `oxrdf` and `rio`. Though `rio` provides specialized parsers, ability to specify syntx at runtime, and parsing/serializing into run-time specified syntax, which can...

This type `http::Uri` is actually http-request-target (#523 ), is it correct to say that @seanmonstar ?

`Accept-Patch`: `text/n3`, should better be supported, if not to force any spec compliant solid server to wade through solidos code, to figure out why it is returning random `update: Error:...

iiif is de-facto standard for image collection, presentation, annotation, usage purposes, and is ubiquitious in GLAM(Galleries, libraries, archives and museums) ecosystems. Almost every professional library like loc, cambridge, oxford-boldien, etc...

Are there any architectural blockers for this?

[Next Cloud](https://github.com/nextcloud/server) support in some random future may be worthwhile.