Skip to content

Assertions terminology/naming is inconsistent and ambiguous #6

@kvakes

Description

@kvakes

Every assertion has three properties: claim, type and proof. Example (from the source code):

{
    "claim": "windingtree.com",
    "type": "dns",
    "proof": "TXT"
}

So, what is type here? Is it the claim type or the proof type? From this example, it seems like it's the type of the proof, a "TXT" DNS record in this case. Let's look at another example (from the source code again):

{
    "claim": "lif.windingtree.com",
    "type": "domain",
    "proof": "https://lif.windingtree.com/orgid.txt"
}

Well now it looks like the type belongs to the claim. This assertion tries to prove that a certain domain is controlled by the claimant. If it was a proof type, it would have been "file", I guess?

I suggest the following change:

{
    "claimType": "domain",
    "claim": "lif.windingtree.com",
    "proofType": "file",
    "proof": "https://lif.windingtree.com/orgid.txt"
}

or

{
    "claimType": "domain",
    "claim": "lif.windingtree.com",
    "proofType": "dns"
}

dns proof should be restricted to TXT records. There is no reason to allow further ambiguity.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions