stevenc-stb

hasSecurityContactPoint can include a location(digital or physical) too...

Regulation class topic: Mandatory with a regulation is unclear: Products may have a mandatory regulation based on external factors A common part used in multiple industries will have different implementation...

discuses at the hardware meeting 20250516 approved for Hardware. This might be need for the other profiles. @kestewart @goneall To be reviewed at tech meeting

@kestewart or @goneall for review and approve.

discuses at the hardware meeting 20250516 approved for Hardware. This might be need for the other profiles. @kestewart @goneall To be reviewed at tech meeting

> Should reviews infer that the deletions of `DefinedHazard`, `HBOMDimensions`, and `HBOMMass` mean some or all of that data would end up "refactored" in `additionalInformationSpecifed` or removed altogether? @aj-stein No......

> am pretty sure in the case of `hasConcludedLicense` we should have only one -- if there a multiple licenses, there should be a single expression combining them. There made...

> @stevenc-stb So the general suggestion is to keep the Licensing profile conformance separated from the type constraints as describe in the relationship type description - right? > > i.e....

> I am firmly of the opinion that a `hasConcludedLicense` relationship should never have more than one `to` licenses. Therefore we should never talk about "each of the `to`", since...

What about for this Profile conformance? 1. for every `/Software/SoftwareArtifact` there is a `/Core/Relationship` of type `hasConcludedLicense` having that element as its `from` property and there shall exist exactly one...