By doing away with groups that focus on specific parts of a person’s identity, a company is doing away with a space in which people can feel truly comfortable expressing themselves. In turn, it may lose the collective voice of those ERG members and the opportunity to learn about their particular needs. Eliminating the groups may lead to the company losing these workers’ energy and talents, as well. https://goo.gl/ZA22jC #GlobalHR #HRTech
Reuse Driven by DataType
#ICYDK: Raml 1.0 introduces a new concept called DataType. This fragment is used to declare type in a separate yaml file. This is not just a simplification of JSON schema to conform raml/yaml. It also brings simple improvements and syntax sugar that allows to write types in more concise form, and therefore more readable. In this article, we will look at how to define our own data types and reuse them in the API and its implementation.
Custom Data Types
Anyone who has designed an API knows that it is probably always necessary to define custom data structures as simple data types are not meaningful enough. Below, you can see data types that are supported by Raml 1.0. We have a group of scalar types like integer, date-only, and so on. We have also compound structures like array and objects. XSD and JSON schema are a separate type as a developer can still share custom types using these schemas. https://goo.gl/e1NND4 #DataIntegration #ML
