w3c
Avoid ambiguous use of 'match' in specification
"match" is a yellow flag in specifications. Does this mean that it must be the same string, or does it use some other matching algorithm?
See https://w3c.github.io/did-resolution/#resolving
We mean string equivalence
This was discussed during the #did meeting on 11 November 2025.
View the transcript
w3c/did-resolution#233
Wip: moving on - we have a yellow flag - we use term "match" and what does this term mean?
Wip: I linked to wrong thing section 4 - must match...what does it mean? we should be more clear. I think we state string equivalent.
Wip: I will take this...
csarven: question of whatever spec you are already covering this - is there a place URI comparisions are described - to get to the point of determining base. for example upper-case = lower case equivalent?
csarven: need to refer to place.
manu: we have ABNF for did syntax - we do not have normalization rules for url if quiry parameters on in different orders - is this the same URL
JoeAndrieu: query about DID not DID URL (has parameters)
JoeAndrieu: method could create this problem for us
JoeAndrieu: Did method specific component can have upper and lower case.
manu: after we get into identifier - it is up to did method
