13 Production Readiness

13.1 Input Validation

All Cloud Library REST calls shall be validated, and appropriate HTTP error codes returned, according to the OpenAPI specification. Additionally, the uploaded NameSpaces (especially the ones not standardized and released through the OPC Foundation that have already gone through validation) shall be semantically validated using a new nodeset validator (that can be optionally built), where possible. For non-standardized NameSpaces, a subset of the OPC Foundation’s CTT test tool may be used for additional validation.

13.2 Ratings

The Cloud Library shall have a rating system built in (for example “stars”) giving users a quick overview about high quality NameSpaces, similar to what GitHub uses for repositories today.

13.3 Content Owner Insights

Content owners (i.e., the data model uploader persona) shall have access to basic metadata which helps to understand how popular their NameSpace is. This can be a great source of customer data that can flow into product management decisions regarding the assets being described by the uploaded NameSpace from a particular source.

13.4 Logging

The Cloud Library shall have operations logging built-in, without capturing personal identifiable information or credentials.

13.5 Query Performance Insights (Operations)

Operators of the Cloud Library shall have access to performance data specifying how many NameSpaces were returned for a particular query and the time it took to execute it. This will give the operator an indication of how the database scales and if adjustments to its resources must be made.