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 formulating the standard as Milestones #49
For clarity, this is not about the existing definitions and naming.
The goal of this issue is to document that a customer will want to know what they need to take action upon in the next 3-6-9-12 months and which events will happen from the vendor in those next quarters.
This issue documents the ask to formulate the data in the standard so that it can be interpreted as:
AT WHAT DATE
WHAT CHANGES HOW
WHICH ACTIONS ARE NEEDED
So for instance:
17-Jan-2025
ProductX can no longer be ordered
Consider replacement ProductY
For clarity, this is not about the existing definitions and naming.
The goal of this issue is to document that a customer will want to know what they need to take action upon in the next 3-6-9-12 months and which events will happen from the vendor in those next quarters.
This issue documents the ask to formulate the data in the standard so that it can be interpreted as:
So for instance:
17-Jan-2025 ProductX can no longer be ordered Consider replacement ProductY