oasis-tcs / openeox

OASIS OpenEoX TC: The purpose of this repository is to support version control for Work Product artifacts developed by members of the OASIS OpenEoX TC, including prose specification editing and secondary artifacts like meeting minutes, productivity code, etc.
Other
13 stars 6 forks source link

Consider adding "geography" or "jurisdiction" to end of sales, end of life and probably other definitions #47

Open ddillard opened 1 month ago

ddillard commented 1 month ago

At times end of sales and possibly other terms used here may be geography/jurisdiction dependent. A vendor may choose to end sales in one geography before another one for a variety of reasons, e.g. regulations.

The one example I have in mind here is regulations enacted within a particular geography that cause a vendor to decide it's no longer going to sell the product within that geography in order to not have to comply with the regulations. For example, the CRA requires vendors to "make security updates available without delay" and "publicly disclose information about fixed vulnerabilities." A vendor may decide that they do not want to/are not able to comply with such regulations and therefore stop selling a product within the EU prior to the CRA going into effect, while continuing to sell the product in other geographies/jurisdictions where such requirements are not imposed.

I can think of other possible reasons this kind of thing would be useful as well, but I've been thinking about this one for a while now.