Hi Omar,
On Sun, Apr 20, 2025, at 07:25, Omar Santos via OASIS wrote:
> Dear OpenEoX TC Members,
>
> I was able to copy the contents of the OpenEoX White Paper to the official OASIS paper template. This is exactly the same as the document we write during the OpenEoX gathering in Raleigh, NC. The following is the link to the current draft:
>
> docs.google.com/document/d/... <https: docs.google.com document d 19rguxezviv62abozq9dpgqmau_36ozsrowm7z4y2r7a edit?usp=sharing>
>
> We will be opening a ballot for official approval this week and the goal is to announce the paper during the RSA conference this year. Please review. You should receive an email with the ballot information within the next few days.
>
> ------------------------------
> Best regards,
>
> Omar Santos [...]
this is exciting news. Thank you for providing a head start to all of us.
I started my review and want to provide my initial albeit incomplete
feedback early on, so that we do not lose time I spent on completing
my review.
1. Abstract
- - - - - -
I suggest to rewrite the abstract to better describe the context
of the problem and our proposed solution.
Instead of the current abstract:
The accelerating evolution of technology underscores the critical
need for clear, consistent communication regarding product life
cycles. Currently, information about End-of-Life (EoL),
End-of-Security-Support (EoSSec), and other states for software,
hardware, services and specifications is often fragmented and
inconsistently defined across the industry. OpenEoX is a very
important initiative designed to address this challenge by
standardizing the exchange of this information. Encompassing both
commercial vendors and open-source maintainers, OpenEoX provides a
transparent, efficient, and unified framework. OpenEoX can also apply
to AI models. This white paper provides a detailed explanation of
OpenEoX core concepts and taxonomy, based on its foundational
definitions.
Proposed rewrite of abstract as:
Clear and consistent communication of the end of product life cycle
states is crucial in coping with the accelerating degree of coupling
between products. Currently, information about end of life (EoL), end
of support for security (EoSSec), and other states for hardware,
services, software, and specifications is often fragmented and
inconsistently defined across the industry. The OpenEoX initiative
addresses this challenge by standardizing the exchange of end of
anything information. Encompassing both commercial vendors and
open-source maintainers, OpenEoX seeks to provides an effective and
efficient unified framework. The OpenEoX core concepts and taxonomy
also apply to artificial intelligence (AI) models. Starting from
foundational definitions, this position paper explains the OpenEoX
core concepts and taxonomy.
Revision Notes:
. . . . . . . .
- Replaced "white" with "position "paper, because that is what it is.
It communicates our position on what is wrong and how to
fix or mitigate problems we observe. I never understood what
a "white" paper actually mneans ...
- Tried to formulate the importance of our initiative by focussing
on the need.
- Removed some soft expressions like "underscores" or "very
important" to let the severe need for our initiative do that work.
- Reordered some statements to emphasize cause, consequence, and cure.
Not sure, if I succeeded, as I am a German and not an English Native.
2. Keywords
- - - - - -
We have to identify some (at most six).
In the current IEEE taxonomy document, I found the following
hierarchies cointaining (kind of relevant to life cycles) mentions:
Engineering management:
Product development:
Product lifecycle management:
Life cycle assessment:
Industrial electronics:
Testing:
Remaining life assessment:
Instrumentation and measurement:
Measurement:
Lifetime estimation:
Testing:
Remaining life assessment:
Social implications of technology:
Environmental factors:
Life cycle assessment:
As keywords we might also want to consider the ACM Computing
Classification System at e.g.
https://dl.acm.org/ccsI still find the display on CRAN usefull:
https://cran.r-project.org/web/classifications/ACM.htmlI consider from an ACM classification perspective the following
taxonomy as intrerestring for ouir keyword finding endeavor:
Computing Milieux:
Legal Aspects Of Computing:
Hardware/Software Protection:
Management Of Computing And Information Systems:
Installation Management:
Software Management:
System Management:
Security and Protection:
I hope this helps and I will continue my review of the
rest of the draft.
Cheers,
Stefan.
Original Message:
Sent: 4/20/2025 1:25:00 AM
From: Omar Santos
Subject: OpenEoX White Paper in New Template
Dear OpenEoX TC Members,
I was able to copy the contents of the OpenEoX White Paper to the official OASIS paper template. This is exactly the same as the document we write during the OpenEoX gathering in Raleigh, NC. The following is the link to the current draft:
https://docs.google.com/document/d/19rGuxEzviV62aBoZQ9DpGqMau_36OzSrOWm7Z4Y2r7A/edit?usp=sharing
We will be opening a ballot for official approval this week and the goal is to announce the paper during the RSA conference this year. Please review. You should receive an email with the ballot information within the next few days.
------------------------------
Best regards,
Omar Santos
------------------------------
</https:>