Andrew Stewart Gibson

Agreed. I was not proposing an exact interface here. I also think that we should allow that #66 and #65 might be implemented in either order since we are evolving...

Proposed design here: https://github.com/linked-data-dotnet/json-ld.net/issues/59#issuecomment-653392194

Proposed design here: https://github.com/linked-data-dotnet/json-ld.net/issues/59#issuecomment-653392194

I think the best way to proceed with this might be to extract a namespace (either as a project within this repository, or as a distinct repository + nuget package)...

I agree with all of your sentiments, but I was trying to stick to the principle of evolving the package forward, rather than doing rewrites (which to me implies breaking...

thanks @sblom i'm very much looking forward to us achieving this (via your idea or any other). I've been chomping at the bit to do this myself but stopped when...

For my part I think we should use a simple `Dictionary` and `List` as the internal representation, and provide `string`, `Json.Net` and `System.Text.Json` as external representations that the library can...

I think your design idea and mine are heading in two rather different directions @sblom . I suggest that I stop my work if you are going ahead. FWIW, I...

As far as I am aware, the prototcol for this is simply: Expose an invalidation() method which returns: 1. If the Method is one of "GET", "HEAD", "OPTIONS", "TRACE", return...

Spitballing: A. CachePolicy would expose a method validation() which returns: 1. If the cached response can not be revalidated, return null [stop] 2. Return an object with props indicating i....