hey there, im working on a related spec - Common Lifecycle Enumeration (CLE)
The CLEs goal is to provide an enumeration of lifecycle events (including EOL states) for components.
We started brainstorming on the CLE a little before TEA was off the ground and imagined that we would need to support component aliasing in some way, for lifecycle events such as a component being renamed. Acme App renamed to Acme Awesome App for example would change the PURL identifier used to identify it. And a user would like to be able to use either identifier to find supply chain information about the app.
we'd love for TEA to support a way to add or remove aliases for component identifiers
hey there, im working on a related spec - Common Lifecycle Enumeration (CLE)
The CLEs goal is to provide an enumeration of lifecycle events (including EOL states) for components.
We started brainstorming on the CLE a little before TEA was off the ground and imagined that we would need to support component aliasing in some way, for lifecycle events such as a component being renamed. Acme App renamed to Acme Awesome App for example would change the PURL identifier used to identify it. And a user would like to be able to use either identifier to find supply chain information about the app.
we'd love for TEA to support a way to add or remove aliases for component identifiers