Major, breaking change. Major justification is simplication.
In addition to basic change have also addressed a security concern by
introducing limitations on path (no / or ../).
Logic for this spelled out in detail in the github issue thread. Summary:
At the moment we have path and url. I originally had this to make it super easy
for tool implementors (no lists of web protocols to match against `http://,
https://, ftp://, etc).
At the same time it adds cognitive complexity to the spec and for publishers
and confusion about whether one could use both e.g. #223#232.
Whilst change increases demand on consumers to parse out urls from simple paths
this is relatively straightforward and consumer could not rely on url vs path
being used correctly anyway