Software: Add sizeInBytes in field

[JPEWdev]

Adds a property to software Artifact that indicates the size, in bytes

[bact]

Two things:

1. Does it possible for a SoftwareArtifact to have a size of 0 ?

   • If yes, then we may need to have this as a xsd:nonNegativeInteger type to allows zero

2. If we eventually have this, we may like to deprecate Dataset/datasetSize and let Dataset/DatasetPackage use this Core/sizeInBytes instead.

   • Good news: DatasetPackage is a SoftwareArtifact, and the datasetSize is in bytes
   • @rgopikrishnan91 @bennetkl what do you think?

[JPEWdev]

Ya, 0 bytes makes sense, so we should change that.

[zvr]

Why not simply call it size, or at most artifactSize ? We can have the description say that the number is in bytes.

[kestewart]

LGTM

[bennetkl]

I'm in agreement to add this field in software profile and remove from datasets. I like the new name of field, better than with bytes in the field name. You might want to put in examples of how to fill in this field. I approve the change and for 3.1 we add a PR to remove similar field from dataset profile.

[bact]

I'm in agreement to add this field in software profile and remove from datasets. I like the new name of field, better than with bytes in the field name. You might want to put in examples of how to fill in this field. I approve the change and for 3.1 we add a PR to remove similar field from dataset profile.

@bennetkl for backward compatibility with 3.0.x, I don't think we can remove datasetSize from the spec.

We can however deprecate it, put some description encouraging people to use the new artifactSize, also maybe considering putting a owl:sameAs to tell that the two are similar.

A 3.0 to 3.1 migration tool can also help users convert this.