Update did:solidus specification link to v0.2.0

[fatih-koc]

Updates the specification URL for did:solidus from the v0.1.0 tag to v0.2.0.

v0.1.0 — the version this registry currently points at — contains errors in the identifier
grammar and in every one of its examples. They were found while checking our own documentation
against the chain and are corrected in v0.2.0:

• The ABNF admitted characters the method cannot mint. base58char was ALPHA / DIGIT, which
  includes 0, O, I and l, with the exclusions noted only in a comment. A parser generated
  from that grammar accepts identifiers did:solidus can never produce. The alphabet is now
  enumerated as six explicit ranges.
• All three example identifiers in §4.3 were unproducible by the derivation in §4.2. One
  decoded to 23 bytes rather than the specified 20; the other two were not Base58 at all (both
  contained 0).
• The stated length range was impossible. "Typically 27–33 characters for a 20-byte payload" —
  a 20-byte payload encodes to 20–28 characters. That upper bound is what allowed the invalid
  32-character examples to look acceptable. Over-28 is now a MUST reject, and the bound is in the
  grammar (20*28base58char).
• The DID Document example was internally inconsistent — its publicKeyMultibase did not derive
  to its own id, so the single worked example of §4.2 contradicted it. It now uses a verified pair,
  and the identifier resolves on the public testnet.

No normative change to the method. The identifier construction, DID Document shape and operation
semantics are unchanged, and every identifier valid under v0.1.0 remains valid — this is a minor
revision under the spec's own versioning rule. SPEC.md carries a "Changes in version 0.2.0" section
for implementers who generated a parser from v0.1.0.

Registered via #713. Contact details in the entry are unchanged; only the specification field moves.

[github-actions]

🤖 AI Preliminary Specification Review

This is an advisory, automated review of the DID Method specification(s) referenced in this pull request, checked against the registration checklist. It does not replace review by the registry editors.

✅ All reviewed submissions passed the preliminary checklist review. A registry editor will still perform the final review.

methods/solidus.json — method did:solidus

Specification: https://github.com/solidusnetwork/did-solidus-spec/blob/v0.2.0/SPEC.md

Preliminary verdict: ✅ PASS

The did:solidus specification is a recognizable, substantive DID Method spec with defined syntax (ABNF), CRUD operations, and combined Security & Privacy Considerations. All MUST criteria are satisfied; a few advisory items are noted as warnings.

	Item	Level	Status	Notes
✅	M1. Specification is reachable and is a DID Method specification	MUST	pass
✅	M2. DID Method Syntax is defined	MUST	pass
✅	M3. CRUD operations are defined	MUST	pass
✅	M4. Security Considerations section is present and substantive	MUST	pass
✅	M5. Privacy Considerations section is present and substantive	MUST	pass
✅	M6. Method name is indicative and non-generic	MUST	pass
✅	M7. No unreasonable legal, security, moral, or privacy harms	MUST	pass
✅	M8. Human-readable description of the addition	MUST	pass
✅	S1. contactEmail present	OPTIONAL	pass
✅	S2. verifiableDataRegistry present	OPTIONAL	pass
⚠️	S3. Intellectual-property posture is clear	SHOULD	warn	No explicit IP/copyright/license statement is visible in the fetched (truncated) text. This is advisory only; the Status section clarifies it is not a W3C endorsement but does not state licensing.