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...

Taking this concept further one could model in RAML [0] to define both the types (flat or nested) and api definitions. It's based on YAML 1.2 with enough maturity to provide capabilities such as union types, extensions, includes, user-defined facets, etc. The AMF project [1] can be used to parse and transform to/from RAML, OpenAPI, GraphQL, and json schema. Code generation to languages of choice can be bolted on from there. I'm using this approach to define canonical data models. Subsequent code generation scaffolds internal application integration apis, master data management (MDM) entities, and SQL/OLAP artifacts for ETL / BI purposes. This approach keeps overall end-to-end data architecture consistent, in sync, and versioned under source control. Additionally, flat types as required by relational systems are re-used and composed into n

> Do you use JSON Schema? At one point I did, but then discovered RAML[0] and it subsumed the value of what JSON Schema provides as well as being easier to work with than OpenAPI[1]. Also, generating JSON Schema from RAML definitions has proven to be a fairly straightforward process. The usual caveats apply... Your mileage may vary, my experiences do not speak for any others, my opinion does not detract from the value of JSON Schema, etc. 0 - https://github.com/raml-org/raml-spec/blob/master/versions/r... 1 - https://swagger.io/specification/

Check out RAML: https://github.com/raml-org/raml-spec Maybe it will fit the bill? It can even encode sum types. But I'm not sure if that's what you're looking for. I'll ping you when I put my mini-ml in Python on Github.

Hi HN, As the title suggests, what RESTFul API modelling language are you using? We thought about using RAML[1].Your thoughts will be really great to us. Thanks. [1]: https://github.com/raml-org/raml-spec