semicolon usage in describing DID URL params

[jiyoontbd]

currently adding path to did url like did:example:123456789abcdefghi/path;foo=bar;baz=qux?foo=bar&baz=qux#keys-1 will break how the Did parser translates path and params. this fails for both web5-go, web5-kt, and web5-js in the same way.

relevant portion of the spec: https://www.w3.org/TR/did-core/#did-url-syntax

we should discuss the use of semicolons, as the spec seems to indicate that we should refrain from using them.

[jiyoontbd]

@mistermoe @frankhinek @decentralgabe

[mistermoe]

same behavior in web5-js as well:

it.only('hehe', () => {
  const didUri = Did.parse('did:example:123456789abcdefghi/path;foo=bar;baz=qux?foo=bar&baz=qux#keys-1');
  console.log(JSON.stringify(didUri, null, 2));
});

output:

{
  "uri": "did:example:123456789abcdefghi",
  "method": "example",
  "id": "123456789abcdefghi",
  "path": "/path;foo=bar;baz=qux",
  "query": "foo=bar&baz=qux",
  "fragment": "keys-1",
  "params": {
    "foo": "bar",
    "baz": "qux"
  }
}

[mistermoe]

i think it may make the most sense for us to just drop ; param delimiting. @decentralgabe what are your thoughts? only thing i can see about it in the spec is a note that suggests we ought not to use it

[decentralgabe]

I agree @mistermoe. What would the alternative look like?