Create tr.json

[burcinbozkurtgunay]

Instructions for Pull Requests

Please read these instructions thoroughly in order to ensure that your pull request is processed in a timely manner. This document contains detailed instructions for registering a DID Method. If your pull request concerns some other change to the repository, you may delete all of the text in this text box and write up a more relevant description.

There is a DID Method Registration form below that MUST be included in a DID Method Registration Request. The form includes check boxes that you are expected to fill out when you submit your request.

Once you submit your request, your pull request will be reviewed by the registry editors. Changes regarding the required criteria may be requested. If there are no objections or changes requested, your DID method will be registered after a minimum of 7 days.

DID Method Registration Process

In order to register a new DID method, you must add a JSON file to the ./methods directory.

Here is an example registration entry:

{
  // These fields are required
  "name": "example",
  "status": "registered",
  "specification": "https://w3c-ccg.github.io/did-spec/",
  // These fields are optional
  "contactName": "W3C Credentials Community Group",
  "contactEmail": "",
  "contactWebsite": "",
  "verifiableDataRegistry": "DID Specification"
}

Your Pull Request will be automatically validated, please ensure that all of the automated tests pass (no errors reported) or your submission will not be reviewed. Common reasons for failed validation includes invalidly formatted JSON files and missing mandatory fields.

----- DID METHOD REGISTRATION FORM: DELETE EVERYTHING ABOVE THIS LINE ------

DID Method Registration

As a DID method registrant, I have ensured that my DID method registration complies with the following statements:

• [ ] The DID Method specification defines the DID Method Syntax.
• [ ] The DID Method specification defines the Create, Read, Update, and Deactivate DID Method Operations.
• [ ] The DID Method specification contains a Security Considerations section.
• [ ] The DID Method specification contains a Privacy Considerations section.
• [ ] The JSON file I am submitting has passed all automated validation tests below.
• [ ] The JSON file contains a contactEmail address [OPTIONAL].
• [ ] The JSON file contains a verifiableDataRegistry entry [OPTIONAL].

[burcinbozkurtgunay]

When will the review take place, 7 days time period for review have already completed?

[swcurran]

Meets minimum requirements for registration.

Comments from my brief review:

Having been deeply involved in the use of did:sov, and the definition of did:indy, I'm not sure how did:tr is different from those methods and so is needed? Does did:tr just reference a specific instance of a Hyperledger Indy network? The use of a uuid for the method specific identifier is quite a departure from the did:indy/did:sov methods.