Clarify that the keys in the run.files dictionary must be distinct when normalized

[ghost]

Section 3.2 says:

3.2. URI-valued properties
Certain properties in this specification specify the URI of a file. The value of every such property, if present, SHALL be a valid URI as described in RFC 3986.

So, for properties whose value is a URI, the spec says that the property value must conform to RFC 3986, which requires percent-encoding. (see RFC 3986 Appendix A).

But here’s what the spec says about the run.files dictionary:

3.12.9. files property
Each property name in the files object SHALL be the URI of a file examined by the tool.

They keys in the files dictionary aren’t properties, so 3.2 doesn’t strictly apply. On the other hand, the spec does say that those keys are URIs.

So I propose to make 3.12.9 explicit by changing it to: “Each property name in the files object SHALL be the URI (as described in RFC 3986) of a file examined by the tool.”

[michaelcfanning]

The files object can have relative URLs as a key and so there could be collisions. A physical location might have a relative URL with or without a base URL that differs. I don't think we describe how to populate colliding files object instances in this case. This sounds like a separate issue but it relates here because one way to resolve the collision is for the files dictionary keys not to be required to be URLs, they could be a constructed thing, for example, the uriBaseId + relative URL (the combination of which resolves a possible key collision).

[ghost]

I'll file a separate issue for this. Even if you allowed the key to be constructed from uriBaseId + relative URL, we would still want to require that the "relative URL" part be URL-encoded.

[ghost]

@michaelcfanning I filed #64, "run.files keys can collide if specified by relative URLs"

[ghost]

@michaelcfanning I changed the name of this issue to accord with the solution I'm actually proposing. What's important is not that the URL-valued key names be URL encoded. What's important is that, when normalized (See Section 3.2), they all be distinct.