raml-spec

> are there no existing languages comprehensive enough for this? In my experience, RAML[0] is worth adopting as an API specification language. It is superior to Swagger/OpenAPI in both being able to scale in complexity and by supporting modularity as a first class concept: RAML provides several mechanisms to help modularize the ecosystem of an API specification: Includes Libraries Overlays Extensions[1] 0 - https://github.com/raml-org/raml-spec/blob/master/versions/r... 1 - https://github.com/raml-org/raml-spec/blob/master/versions/r...

> The goal is to build a language and system model that allows us to reliably sandbox and support agents in constructing "Trustworthy-by-Construction AI Agents." 1 - Reliability implies predictable behavior. 2 - Predictable behavior implies determinism. 3 - LLM's are non-deterministic algorithms. In the link you kindly provided are phrases such as, "increases the likelihood of successful correct use" and "structure for the underlying LLM to key on", yet earlier state: In this world merely saying that a system is likely to behave correctly is not sufficient. Also, when describing "a suitable action language and specification system", what is detailed is largely, if not completely, available in RAML[0]. Are there API specification capabilities Bosque supports which RAML[0] does not? Probably, I don't know as I have no desire t

> How does one even write an API client against a REST API that only publishes the initial entry point? in particular, how should the client discover the resources that can be manipulated by the API or the request/response models? HAL[0] is very useful for this requirement IMHO. That in conjunction with defining contracts via RAML[1] I have found to be highly effective. 0 - https://datatracker.ietf.org/doc/html/draft-kelly-json-hal 1 - https://github.com/raml-org/raml-spec/blob/master/versions/r...