OASIS OpenEoX TC

Dear TC Members,

Create definitions.md by santosomar · Pull Request #13 · oasis-tcs/openeox

GitHub		remove preview
Create definitions.md by santosomar · Pull Request #13 · oasis-tcs/openeox This document draft aims to clearly define key terms related to the lifecycle of software and hardware products, providing a reference for understanding various phases from sales or creation to support termination. This is just a starting point and the TC will provide additional edits, inputs, etc. Fixes #11 View this on GitHub >

lifecycle schema proposal · Issue #15 · oasis-tcs/openeox

GitHub		remove preview
lifecycle schema proposal · Issue #15 · oasis-tcs/openeox Below is a lifecycle schema proposal. It's very flexible and the general conception is similar to the CSAF schema, where items defined in the product tree are mapped to the list if lifecycle phases. The main purpose of this is to allow v... View this on GitHub >

One Use Case w/ portable schema · Issue #14 · oasis-tcs/openeox

GitHub		remove preview
One Use Case w/ portable schema · Issue #14 · oasis-tcs/openeox Companies including our own may speak in terms of End of Sale, End of Standard Support, End of Security Support/Life, End of Life, End of Service Life. These terms might not match the use case of other vendors. Because of this, a flexibl... View this on GitHub >

 

Best regards,

Omar

------------------------------
Omar Santos
Distinguished Engineer, AI Security Research
Cisco Systems
Raleigh NC
919 412-8568
------------------------------

Dear TC members,

@Omar: thank you for the draft.

I commented on the Pull Request to provide some insights from my perspective. Please do the same. So this is a call to action for all members to review the PR and comment on it.

Best wishes,

Thomas

------------------------------
Thomas Schmidt
Federal Office for Information Security (BSI) Germany
------------------------------