Alexios Zavras (zvr)

Yes, @mlinksva interpretation accurately describes the common understanding, I think. If you are concern whether `file1` requires `B`, you should be checking the licensing info for `file1`, not the one...

Nice data, @juliusmusseau, although you have to define what the "release date" actually mean. For example, I can think of: - when the source was last modified - when the...

@swinslow you are correct, and what you think should be there also matches my understanding. @davaya: - the RDF/XML tags may obviously repeat, so if you had two files excluded,...

You are correct that this part of the spec is not great... We should have written different section for each sub-field: `packageVerificationCodeValue` and `packageVerificationCodeExcludedFile` saying that the first has cardinality...

Any nested type is a pain because it has to be translated to flat tag-value pairs. So I assume you mean something like: ``` AnnotationDate: "2011-03-13T00:00:00Z" AnnotationType: "REVIEW" AnnotatorType: "PERSON"...

:+1: for the ideas of the two methods. However, since I am not a Java person, I have to ask: as I think we don't anticipate any use of hierarchies,...

If we're considering breaking changes, I would go all the way and propose no restrictions on which algorithms have to be there: > Cardinality: Mandatory, one or many.

Please note that SPDX already provides IRIs for all the _resources_ it publishes. For example, you can use `http://spdx.org/licenses/MIT` to refer to a specific license. I am not sure of...

I beg to differ. Do you really think that all repositories named "foo" by different users on github are the same or equivalent? Even with the name in your example...

Well, I understand the need to sometimes use the last part of the whole namespace+name string. It is similar to a database keeping filenames and wanting to separate directory and...