Versioning of VOEvent information
On the low-latency call today, there was discussion about what information should be used to build a VOEvent and whether we can do some sort of versioning of this information, presumably so that VOEvents can be built using "past" information. This issue attempts to track the discussion and come up with a list of solutions.
The problem at hand was framed as:
- How do we store the information about what content should be used in building a VOEvent?
- How do we populate that content when building a VOEvent?
- How do we access that content?
Another way of framing it is:
- All content from a superevent which is used to build a VOEvent should be versioned/tracked.