Tim Anderson wrote:
We really need to harden the URI spec a little and the "/" is a good start.
I missed that the "jars" or type dir was required. what about,
I suppose this is the version named Alpha of the alpha/alpha project.
Or is it the alpha release of the version named alpha of the project named alpha or..
These are silly examples, but lets try to prevent at least some of them.
Yes that is the start, make org and product un ambigous is a really good start.The above a legal for the URI Syntax proposal , but illegal according to the common build version  and java artifact specifiers . Tools based on  &  should ignore them.
Is it simply a matter of restricting organisation back to a single
path segment? This would allow product-specifier to be determined
Note that this was the original approach, but some people expressed aI still think reverse-FQDN is a good idea but for parsability I would use . not /
desire to be able to break down the hierarchy using reverse-FQDNs.