Dictionary for task types

[Zarquan]

A suggestion from a reviewer reading the document:

https://github.com/ivoa-std/ExecutionPlanner/blob/7f9722546b165c5c950d1c0d834b98183a9c8de1/ExecutionPlanner.tex#L799-L800

In an ideal world, we have a dictionary for resources, identifying them with unique IDs ... Could we provide users with a way to register types of resources in a service?

[Zarquan]

I need to clarify that the next couple of paragraphs were intended to demonstrate how easy it is to add a new type for the Xilinx FPGA, but I didn't explicitly state that in the text.

https://github.com/ivoa-std/ExecutionPlanner/blob/7f9722546b165c5c950d1c0d834b98183a9c8de1/ExecutionPlanner.tex#L841-L843

Missing text is something like:

For example if a project wanted to use Xilinx FPGAs to accelerate their algorithm (available in Amazon F1 instances(, all they would need to do is choose a URL that describes this type of resource and add it to their service implementation. When one of their users wanted to run a notebook that required a Xilinx FPGA to accelerate the algorithm, they can simply add this as a requirement to their request. 99.9% of the ExecutionPlanner services would say NO, but again, the carbon footprint would be minimal. The only services that would say YES would be their own project services that had this hardware available.

[Zarquan]

If people want a 'registry' of types, we (the IVOA) could curate a simple list of types that people can subscribe to. It could be as simple as a wiki page, or a md file in the ExecutionPlanner source code. Getting technical, we could have a machine-readable YAML file and a make target that transforms it into a human readable md file.

Simple options:

• An appendix to the document
• A human readable md file in the same repository
• A page on the IVOA wiki.

Important to emphasise that being on this list is not a requirement for a type, it is just a nice way to get your modification noticed.