Attributes come in two flavours. Some apply to systems and some apply to sysvers.
human readable license identifier ";" path to license textAn example is
Eclipse Public License - v 1.0; src/eclipse/epl-v10.htmlThe human readable license identifier will typically be the title text of the license or something similar that uniquely identifies the license. Ideally the path to license text will be a path relative to the installation of the sysver to the license text. This is preferred to (for example) a URL, since the URL can become stale, so a URL is only provided when no license text is distributed. Details as to the reliability of this information are available.
This value has to apply to types for which there is source code (otherwise LOC has no meaning) and it doesn't seem sensible to include types for which there is source code but no binary, hence the "both" designation.
This is one candidate for determining the number of types in the system. The reasoning for this choice is, types for which there is a compiled version are intended to be part of the system so must be counted, even if there is no source available (e.g. because it is generated). Note that LOC/NCLOC measurements may not exist for all types.
This is another means to measure the number of types in the system. The reasoning is, types for which there is source but no binary are probably infrastructural (e.g. testing) or examples or similar. Types for which there are binary but not source are probably generated.
This might not always match n_files if there are files with multiple top-level types declared (meaning some must be non-public).
This value has to apply to types for which there is source code (otherwise LOC has no meaning) and it doesn't seem sensible to include types for which there is source code but no binary, hence the "both" designation.
Records the decision we have made regarding what is in a system (and not, for example, third-party library types). This is a space-separated list of prefixes of packages of Java types. Any type (class, interface, enum, annotation) whose binary name has one of the listed package prefix as a prefix of it is considered a type that was developed for the system, and everything else is considered as being a library type.
So, for azureus-3.0.3.4, its sourcepackages value is "org.gudy. HTML. com.aelitis.", indicating that types such as com.aelitis.azureus.core.AzureusCore are considered part of that version of azureus, whereas java.lang.String would not.