Provide existing component libraries

[adrpo]

• Update API spec to handle hierarchical component library
• load MSL
• use a list of nodes that contains other nodes. Each node has its own SVG
• put the information about the libraries (in JSON format) inside a MongoDB
• setup MongoDB server that can be accessed from OMWebService instances
• provision server infrastructure for hosting OMWebService
• create deployment procedure for OMWebService

Libraries

• assume the MSL is loaded

Data for the library

• hierarchical class structure
• svg at the leafs
• currently we have [components] (https://omwebservice-api-docs-dev-docsbucket-63c7h6kaz6lp.s3.eu-central-1.amazonaws.com/index.html) but we need a hierarchy

Data as json in a database