Standardize RData delimiter

[mistermoe]

Is there a specific reason as to why the root record's RData delimits fields using ; but _kN and _sN uses ,? i think we should use ; to delimit fields so that we can use , for multiple values for a given field.

If not, there are typos here:

• _s0._did.'s RData value should be t=LinkedDomains,uri=foo.com,… not t=LinkedDomains;uri=foo.com;…
• _s1._did has the same issue

[decentralgabe]

; separates distinct entities (like different verification relationships) whereas , delineates multiple values for a given field

there is indeed a typo below, which I will address.

[mistermoe]

yeah in that case i think _sN._did. should absolutely use ; to separate entities vs. , as you have right now because values like uri can have multiple values as noted here.

On that note, did did:dht make an explicit decision to not support serviceEndpoint being an object? DWNs require this which you can see here

[decentralgabe]

@mistermoe the spec here creates a profile (method) of DID core. so even though you're correct that DID core supports multiple values, the spec as written does not.

I think we should close this issue (after #84 is merged) and open a new issue to discuss services with multiple values.

[decentralgabe]

fixed in #84

[mistermoe]

sounds good!