దామోదర

For now making `FileDataAccessor` methods non-private, and refactoring of fs access methods just works. There seems no better comprehensive storage abstraction layers in node, unlike golang where `afero`(https://github.com/spf13/afero), `@viant/afs` etc...

@joachimvh `FileDataAccessor` seems dealing with concepts like containers, data, meta-data, extensions, and many interactions b/w these concepts, which are not so obvious. Though one can indeed extend, it seems much...

There are also certain use cases where we want to use different stores for different mime-types. For example, when want to persist TEI conformant xml file for an encoded text...

As there can be multiple files in which different components with same `@id` can be defined as alternatives, And effective one depends upon which are imported, one cannot decide name...

Along with batch-put, there may also will be issue with `POST` to `a/` container along with slug, that can add other race permutations to all other cases. ==EDIT==: sorry, i...

Along with above contention axes, there seems many other contention axes plausible. Following is one. Any method on a container + `PUT`/`DELETE` on it's dessendents. Particularly `DELETE` on container +...

That seems indeed the case, if we have to "layer" the locking functionality as outer layer of `DataAccessorBasedStore`. But we may can `intersperse` locking in implementation of `DataAccessorBasedStore`, which takes...

Indeed _/\\\_. We just has programming language level constants for requirements. So that we can attach them to violation errors. They are generated from rdfa query. And thus the uri...

> However, it is easy to identify a quad in this scheme too: The fourth component is the request URI identifying each resource. This seems to one of the not-very-outspoken...

Is there any prior discussion, that resolved to allow only rdf-documents as auxiliary resources? If so can some one help in pointing it out, so that i can be better...