updates go architecture doc based on what was found in implementation

[nellshamrell]

I found that original proposed structure for coordinates wasn't going to work well with the vanity import paths/urls that Go allows for. This updates the architecture to better accommodate those paths.

Signed-off-by: Nell Shamrell [email protected]

[jeffmendoza]

Should be go/golang.org/x/net/v0.0.0-20210226172049-e18ecbb05110 i think

[nellshamrell]

ah- typo!

[jeffmendoza]

Just a note: This isn't a result of vanity import paths. A Go module can live anywhere on the web, a module of mydomain.com/package could very well be the literal git repo url, and not a redirect.

Modules can still have multiple directories in the path between the host and final name of the package. ex: domain.com/long/path/go-package. The slash in "long/path" will need to be encoded to be a valid ClearlyDefined "namespace".

Also, periods are valid in url's as well domain.com/project.xyz/v2/package. "project.xyz/v2" will need to encoded in a way that can be deterministically un-encoded.

[nellshamrell]

@jeffmendoza- ty so much for your input on this! I can definitely see your point, there - we may have no choice but to do some url encoding in the case of go components - I don't currently see any other way around it.