Don't allow leading / in relative artifact location URIs.

[ghost]

The rationale for requiring artifactLocation.uri to be a relative reference when uriBaseId is present is that we should be able to combine uri with any file-based URI to form an absolute path. /dir/file.c is technically a relative URI reference, but it is an absolute file path. That means you cannot combine it with a base value such as file:///C:/dev/myProject.

The spec should prohibit leading /s on artifactLocation.uri. It doesn't even matter whether or not artifactLocation.uriBaseId is present: if artifactLocation.uri is not absolute, it can't start with a /.

@michaelcfanning FYI

[michaelcfanning]

Approved TC session 43.

[dmk42]

Now that the Errata document has been published, this has been fixed in the official version of the standard.