sql.json
Add SQL DID method
"id": "did:web:stellarquantalabs.org" https://stellarquantalabs.org/.well-known/did-configuration.json https://stellarquantalabs.github.io/.well-known/did-configuration.json
DID Method Registration
As a DID method registrant, I have ensured that my DID method registration complies with the following statements:
- [ X ] The DID Method specification defines the DID Method Syntax.
- [ X ] The DID Method specification defines the Create, Read, Update, and Deactivate DID Method Operations.
- [ X ] The DID Method specification contains a Security Considerations section.
- [ X ] The DID Method specification contains a Privacy Considerations section.
- [ X ] The JSON file I am submitting has passed all automated validation tests below.
- [ X ] The JSON file contains a
contactEmailaddress [OPTIONAL]. - [ X ] The JSON file contains a
verifiableDataRegistryentry [OPTIONAL].
Are you trying to register a method or just make a did:web DID?
Hi, I had already made a did:web (did:web:stellarquantalabs.org), but I am now trying to validate it in order to resolve the following when attempting to validate my DID document: "Notes on JSON-LD Context: '{"@base"=>"did:web:stellarquantalabs.org"}' is not yet listed as Verification Method Type in the DID Specification Registries".
I am hosting the .json files here: https://github.com/StellarQuantaLabs/.well-known
https://github.com/StellarQuantaLabs/.well-known/blob/main/did-configuration.json https://github.com/StellarQuantaLabs/.well-known/blob/main/did.json
I had to setup a redirect using my domain and github, due to the website domain being hosted by squarespace and it not allowing me to host the json file on my actual website. This link redirects: https://stellarquantalabs.org/.well-known/did-configuration.json
let me know if this is the correct way to complete this process :)
The files in https://github.com/w3c/did-extensions/tree/main/methods are used to register methods themselves. Those have details on the method spec and so on. For instance, details for did:web are in web.json, did:key is in key.json, etc. DID Web documents don't have a centralized registry. It looks like you already setup the DID document for did:web:stellarquantalabs.org. For people to help, some more details are needed on what kind of validation you are trying to do. It looks like this PR is not part of the solution you are looking for and can be closed.
The files in https://github.com/w3c/did-extensions/tree/main/methods are used to register methods themselves. Those have details on the method spec and so on. For instance, details for
did:webare inweb.json,did:keyis inkey.json, etc. DID Web documents don't have a centralized registry. It looks like you already setup the DID document fordid:web:stellarquantalabs.org. For people to help, some more details are needed on what kind of validation you are trying to do. It looks like this PR is not part of the solution you are looking for and can be closed.
I have corrected the specification, it is an app in development: (https://github.com/StellarQuantaLabs/sqlverify/blob/main/README.md)
Appreciate the review and the candid feedback. I’ve been heads-down on related patent/IP work and an enterprise implementation, which is why this lingered and the repo drifted from what I originally intended. I’m not proposing a new DID Method here—the earlier PR mixed that up with an app-specific setup—so I’ve cleaned things up: the DID is now correctly hosted at https://stellarquantalabs.org/.well-known/did.json, legacy redirects are removed, and the prototype repo has been archived to avoid further confusion. I’ll also add a domain-linkage VC covering both the apex and www origins for stricter verifiers. Thanks for the pointer—closing this PR so it doesn’t distract from the work in progress.