దామోదర

@sgodwincs , In this, all structs that use `Cow`. With this, in most cases, owned uri is as cheap as borrowed one, and can be passed around, and included in...

Yes, but dealing with lifetimes may be difficult in some involved cases. If owned invariant is available without much allocations, it would be great. Thanks for your work

And it also may helps where normalization is necessary. It seems, currently segment normalization allocates, if it is not already normal. `KStringCow` invariant from kstring may co-operate well with existing...

@sgodwincs, Currently, to get a owned `URI`, that is not static, one have to allocate for each segment in path. Getting owned version may be required when certain traits require...

@sgodwincs , if open to idea, i can make a PR, that doesn't introduce any breaking change, and changes only little code regarding `Segment` struct

@sgodwincs , We will follow just same pattern as existing segment implementation, that is to use a cow'd invariant. that is if it is not owned, it can be just...

Yes, though in draft stage, it is fairly used in production. Auth0 [supports it](https://auth0.com/resources/podcasts/S1E001IDUnlocked). And [SOLID-OIDC](https://solid.github.io/solid-oidc/)mandates it, as it supports decentralised identity.

@ramosbugs , _/\_ you can see dPoP being listed in **[OAuth Working Group Specifications](https://oauth.net/specs/)** too.

With regarding permissions, As per docs, Inrupt's ESS seems taking approach of controlling QPF/GraphQl query-endpoint at the level of pod itself. Otherwise evaluating sparql along with consideration of external acl-system...

There is usefulness in `abstraction` instead of `extension`. If we abstract away protocol layer, then there will be only one protocol agnostic test-case needed for `FileDataAccessor`. And every other object...