Risks and Technical Debts

Each of the subsections discusses a risk and technical debt aspect.

PyRAML/ramlifications Adoption

As mentioned before, pyraml nor ramlifications weren’t adopted to develop raml2agl. This leaves an important technical debt since the compliance with the RAML standard isn’t verified in the implemented RAML parser. Meaning, that some modeling language syntax error in an input RAML model wouldn’t be caught.

Moreover, the by the time of writing this document, the RAML parser doesn’t support all RAML 1.0 features but are being increasingly supported. Thus, creating a gap between the RAML 1.0 modeling features and the raml2agl features. Nevertheless, the most important RAML 1.0 modeling features are supported in raml2agl. Please review [22] for an updated list of RAML 1.0 supported features.

RPC Limitations

The use of an RPC communication model on top of Web Socket represents a risk and technical debt since some applications might work better on top of the raw Web Socket communication. Nevertheless, raml2agl can still be used for the client side automatically code generation as mentioned in RPC over Web Socket Communication.

[22]	Pedro Cuadra. Raml to agl. URL: https://github.com/pjcuadra/raml2agl.