Background : Meeting Notes for 16th January 2018 Tiger Team Meeting : Parser As A Service (16th January 2018)
Points Discussed :
SO is using SDC as a baseline, usecase UI (SDC Java Parser) --- APP-C TOSCa Parser --- Can we have capability for components to still write extensions while retaining a central Par As A ser implementation
CSAR and Service Templates (is there a need / use case ?) to pass them to PaaS
If the call is fro service templates, how would service template reference
(import section to refer file within a repository pointn to central repository)
Circulate a note to this effect to see the impact and challenges or resolution ?
First call into PaaS, earnings or errors, some components can work around (SDC example, upper case or lower case, hence need to segregate warnings and error codes) Error should be an aggregation of all parsing functions rather than one bu one line
PaaS has to have segregation on what issues should it fail and where it should have a warning (in general this behavious should be configurable, - we do not want the component to having to respond to non relevent exceptions to its call)
Different languages, common API
What is the output of each parser