Add more description to hasDataFile relationship type

[bact]

• Add description to hasDataFile
  • Add list of cases that an author should consider using a more specific relationship type
  • This is to resolve hasDataFile would benefit from a better description #690
• Also remove double "is" from hasAddedFile

[bennetkl]

It might be a good idea to open 3.1 PR to make the name change (if the anser to Arit's querstion, is yes we can make a name change in that On Tuesday, July 30, 2024 at 03:03:38 p.m. EDT, Gopi Krishnan Rajbahadur ***@***.***> wrote: @rgopikrishnan91 commented on this pull request. In model/Core/Vocabularies/RelationshipType.md:

- hasAssessmentFor: (Security) Relates a `from` Vulnerability and each `to` Element(s) with a security assessment. To be used with `VulnAssessmentRelationship` types

- hasAssociatedVulnerability: (Security) Used to associate a `from` Artifact with each `to` Vulnerability - hasConcludedLicense: The `from` Software Artifact is concluded by the SPDX data creator to be governed by each `to` license -- hasDataFile: The `from` Element treats each `to` Element as a data file +- hasDataFile: The `from` Element treats each `to` Element as a data file. A data file is a data resource that the `from` Element can use to fulfil its expected functinality or behavior. It can be a generic database fie, a log file, an AI model file, a calibration data file, a temporary file, etc. For AI training data, test data, other test artifacts, configuration data, Build input data, and Build output data, please consider using `trainedOn`, `testedOn`, `hasTest`, `configures`, `hasInputs`, and `hasOutputs` types, respectively. Okay. I am okay with it and maybe we can note down somewhere it should be hasArtificat as the name. But otherwise, I approve — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[bact]

From AI Team Meeting 2024-07-31:

• Name change/Type addition is not possible for 3.0.x
  • Can add hasArtifact in 3.x (like 3.1)
  • Can remove hasDataFile in 4.0
• @rgopikrishnan91 proposed to clarify on dependency, also incorporate @goneall suggestion on using the term "Artifact" #690 (comment) . The meeting agreed to add "A data file is an artifact that stores data ... This relationship does not imply dependency" statement.
• Approved to merge this PR as it is now for 3.0.1 -- @bennetkl

[gopirajbahadur]

LGTM, I approve