Dear all, concerning the mismatch between CPF and XTC format, I can only say that this is no longer an issue: CPF 3 has just been released and it will no longer support XTC itself, but a cleaned up variant. So competition organisers have to write a converter from their TRS-format to the CPF-input format, which should be an easy task. Such a converter is already available for the new ARI-format, a format that will be used in CoCo starting in 2024. For more information regarding the changes in CPF (in particular for running competitions), cf. http://cl-informatik.uibk.ac.at/isafor/cpf3.html (overview) or http://cl-informatik.uibk.ac.at/isafor/cpf3.tgz (specification + converter) Best, René
Am 13.11.2023 um 09:37 schrieb Raúl Gutiérrez <raguti@upv.es>:
Dear Florian,
On 11/8/2023 5:39 PM, Florian Frohn wrote:
So if you compete, or are interested in, the TRS categories at TermComp, please let us know what you think. I'm also particularly interested in the following questions:
- If you participate, can your tool still parse the old format?
MU-TERM can deal with the original TPDB format.
- Do you recall more details about the reasons for the switch from the old format to the current one?
From a programming perspective, utilizing standard formats like XML or JSON to define TRSs is a good idea, given the availability of libraries that facilitate the transformation of these files into data structures (not in Haskell, where we use Parsec, but in Python, for example, there are libraries to do this automatically) and also to interact between different tools. However, from a user standpoint, it is crucial that TRSs can be easy to write.
Best,
Raúl.
_______________________________________________ Termtools mailing list -- termtools@lists.rwth-aachen.de To unsubscribe send an email to termtools-leave@lists.rwth-aachen.de