Dave Longley

I think the fact that some DID methods like `web` happen to run on HTTP is totally orthogonal to the `FileService` (or whatever name we prefer to give this) feature....

Hmm, this seems to only allow for a single `UrlResolver` service (without any additional changes here)? Or is there a mechanism I'm just missing to allow for more than one?...

@msporny, > Multiple base URLs MAY be provided for the purposes of redundancy. Yeah, but this only seemingly covers the redundancy case. What if I want the base path of...

Hmm, perhaps the "StaticUrlResolver" could handle the `DynamicUrlResolver` case too, though, by making the URL it resolves to itself a live service at the other end. If we're able to...

> Seems like a big price to pay for a single UrlResolver type. Agreed, so if that would be the consequence of relying solely on a single type and existing...

There are several ways to introduce a service to enable this feature (better `relativeRef` "sugar") that is backwards compatible with existing DID URLs. For example, the service could express a...

> For a dynamic resolver: > > ``` > "service": [{ > "type": "DynamicDidUrlResolver", > "serviceEndpoint": "https://resolver.example/service/" > }] > ``` You could still map a `DynamicDidUrlResolver` to a `basePath`...

Having good protections against malware in the software users might install is a separate consideration from relying on issuers or verifiers to enforce such protections. The latter can cause significant...

@davidlehn, Could you look into this? We should get a test case up based on the description -- and see if we have the same problem with jsonld.js. I'll note...

The JavaScript JSON-LD processor, jsonld.js, has a "safe mode" feature for this that hasn't yet been implemented in pyld that would do this in an optimized way. However, in the...