-
Right now, for a configURL of `https://accounts.idp.example/config.json` it requires the IdP host a file at `https://idp.example/.well-known/web-identity`. As mentioned in other discussions, this can …
-
Using HATEOS ideas, this:
When the FAIR Data Point Service root URL receives an HTTP GET request (e.g., http://mydomain.com/fdp/)
would typically be implemented using the Well-Known URI approach…
-
Type Metadata introduced new well-known URI /.well-known/vct/ in "6.3.1. From a URL in the vct" , but this is not reflected in appendix-A.3 Well-Known URI Registry.
Additionally, using in sentence…
-
If `/.well-known/did.json` usage is to be kept (contrary to #50, but following https://github.com/w3c-ccg/did-method-web/pull/50#pullrequestreview-834762306), shall we register it with IANA/IETF?
- …
-
**Describe the problem**
I get an `Error: Unauthenticated` message upon opening the dashboard homepage. Checking the browser's development console, it is attempting to fetch the OIDC configuration …
-
I would expect that one may still uses URI template to declare how the URI looks like even if there are currently no parameters that require configuration just to make it aligned with the other extend…
-
[RFC 5785](https://tools.ietf.org/html/rfc5785) provides a registry from "well-known URIs".
Well known URIs "are designed to facilitate discovery of information on a site when it isn't practical to…
-
Code currently assumes all URIs in an Annex (-annex True) are "Wellknown", if not in an Annex then they're Examples.
This does not hold true as a generalization (see Core resources). Probably need…
-
https://en.wikipedia.org/wiki/Well-known_URI
Описание, которое помогает понять суть:
> They are URL path prefixes that start with `/.well-known/`. This implementation is in response to the commo…
-
RFC5785 is internet standard for defining well known machine discoverable URIs
https://tools.ietf.org/html/rfc5785
We should do something like
https://bp.org/.well-known/eos/chain-id/bp.json