You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current specification doesn't say that in order to block or remove a registration that a /registered/ trademark is required. The language around copyright is also problematic (granting a copyright holder the broad ability to block a registration). The text needs to be updated to remove much of the evaluation burden from the maintainers (by requiring that the trademark owner has the burden of proof). The purpose of this issue is to track this desired clarification.
The text was updated successfully, but these errors were encountered:
ready for pr
...
The purpose of this issue is to track this desired clarification.
This is a contradiction. @manu please remove the "ready for pr" label until there is more concensus on what the eventual solution is ..i.e. let's avoid dueling PRs. ...perhaps tag your idea as a proposal.
We can't rely or restrict the uniqueness of a DID Method name based solely on trademarking due to some DID Method names not being trademarkable.
Read #597 for a super/meta proposal,
The current specification doesn't say that in order to block or remove a registration that a /registered/ trademark is required. The language around copyright is also problematic (granting a copyright holder the broad ability to block a registration). The text needs to be updated to remove much of the evaluation burden from the maintainers (by requiring that the trademark owner has the burden of proof). The purpose of this issue is to track this desired clarification.
The text was updated successfully, but these errors were encountered: