When the abstract were produced in plain text, it was necessary to identify what was testable and how in the ATS. Now the situations has changed with the modular spec. The req. classes are formalized in a language that is precise and almost testable. The ATS becomes a repetition of the same req. but with small "grammatical" changes. It still not defines completely how to test the req in practice, so, IMHO it does not add any value.
I would like to propose to remove the ATS from the standards that use formal requirements
And with standards that are APIs or JSON specialisations, the tests are the schema fragments from the full schema bundle, whether YAML, JSON Schema, etc. So I agree with @joanma747 .
When the abstract were produced in plain text, it was necessary to identify what was testable and how in the ATS. Now the situations has changed with the modular spec. The req. classes are formalized in a language that is precise and almost testable. The ATS becomes a repetition of the same req. but with small "grammatical" changes. It still not defines completely how to test the req in practice, so, IMHO it does not add any value.
I would like to propose to remove the ATS from the standards that use formal requirements