దామోదర

Thanks @bourgeoa , @kjetilk , @csarven for replies and insights. @csarven , > The example with the thumbnail doesn't come across meaningful or easily workable to me. How about thumbnails...

@kjetilk , @csarven Indeed, it is clearly expressed in dimensions issue. These use-cases primarily depends on dimensions of `discovery`, `binded-acls`, `binded-lifecycles`, and `server-management`.

Issue is not just about iiif. For example tei-publisher is a tool that take tei-xml file and embedded directives, and outputs htmls of tei-document parts . Those html resources are...

@csarven , If not as auxilliary resources, then can we have something like auxilliary-api? So that, on top of solid-defined base CRUD api, we can interact with given resource, through...

Hello @csarven , @kjetilk request you to show torch on how can we achieve following requirements in solid-compilant-way. 1. Just like there are discussions on having shape files as auxiliary...

@kjetilk , indeed, hierarrchies will be bad for knowledge organization. But, this case doesn't actually comes under "knowledge organization", instead comes under "document organization". Though there may not be clear...

In other words, there may not be much issue in organizing documents in hierarchies, until free form linking also supported (As is natural on web. And already recommonded by solid...

> Right, but I feel that document organization should just be a subcase of knowledge organization. Indeed.. But there is subtle difference. If resources are used for representing description of...

In spec, it mentions that slash semantics only applies to `/` char in `URL path`. Thus a `/` in query-params of an uri in origin-form may not cause issue as...

Allowing origin-form for normal resources arises lot of unspecified behaviour as described in previous comment. Even not taking security perspective, that will leave so many ambiguities, un-understood behaviours as solid...