How to express End Of Life?
See original GitHub issueHello codemeta.
Many software products have an end of life calendar. I was wondering what the best way to express this might be. I’m thinking perhaps temporalCoverage
? But the EOL applies to specific versions.
Any ideas?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Communicating End-of-Life Care Wishes With Clinicians and ...
Five Ways to Officially Communicate End-of-Life Wishes With Family and Clinicians ... This can be placed in an advance directive and states that ......
Read more >What is End of Life (EOL) vs. End of Service/Support (EOSL)?
End of Service Life (EOSL) (or End of Support Life) meaning: Phrases OEMs use to indicate the ending of services and updates for...
Read more >'Letter Project' Makes End-of-Life Wishes Clear - Next Avenue
... Letter Project, developed by researchers at Stanford University to give people a simple way to express their end-of-life preferences.
Read more >Must-Know Words and Phrases Related to End-of-Life Care
Navigating any stressful and significant situation requires effective communication and clear understanding. All the more so when that scenario involves ...
Read more >Cisco Unity Express - End-of-Life and End-of-Sale Notices
Taliored to your team's skills and goals, this intensive training program gets your team the skills they need to help your organization realize...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@brucellino Ah, right, there’s two separate things here. While I think
developmentStatus
is the appropriate property for this, that doesn’t mean you are bound to the repostatus.org vocabulary. The field takes free text, and you can provide whatever you want. There’s quite a lot of other badge-oriented status vocabularies available as well.For instance, the
codemetar
R generator for codemeta also recognizes https://www.tidyverse.org/lifecycle vocabularies, which I like for the very reason you describe: it has more nuance instead of “active” vs “inactive” for more mature software. There are quite a number of other commonly used vocabularies as well.I guess this could be expressed via
developmentStatus
…