Closed nathanshammah closed 1 year ago
I agree, I think something a bit more rigid would be useful.
Another related thing that might be worthwhile is to borrow from the "submission" page of PWC: https://paperswithcode.com/contribute/dataset/new
(note, you'll need to be logged into PWC to see the above).
Issues are also related to that:
https://github.com/unitaryfund/metriq-app/issues/153 https://github.com/unitaryfund/metriq-app/issues/265
I discouraged the suggestion, originally, but I think a method hierarchy might also help, akin to tasks. For one thing, it would help restrict an endless scroll in the methods index view, if we restricted to top level of the hierarchy, as we now do with tasks.
We do have a method hierarchy, now. If there's more to be said on this issue, please reopen it.
Currently, going to the "A Verified Optimizer for Quantum Circuits"page, one finds the following as Methods:
I see a couple of issues with the current list, as it is inhomogeneous. Moderators can act to tidy that up, I just think that this may happen again in the future so my question tries to abstract this a bit and ask: how can we enable a tidier taxonomy in general? To begin with, I propose to add more contextual information on a good nomenclature and examples for "methods" and "tasks" in the methods and task root pages, possibly with (a link to) more information also in the FAQ page.