For each service declared in metadata in the previous step, Kevin must define an APS type as explained here.
In this document:
Currently, there are two ways of developing an APS type:
*.schema
extension.To use the first of the above-listed ways, Kevin must get familiar with the APS type structure and the rules to define resource properties, relationship, structures, and operations as explained in the Type Definition document. Typically, the process consists of the following steps:
apsVersion
, name
, id
, and implements
parameters.relations
section, define the relationship with other APS types.structures
section, define the structures to be used as types in properties and in operations.properties
section, define all properties.operations
section, define all custom operations.For every APS type, Kevin must have a schema definition either created in a source file with the .schema
extension
or in another source (for example, in a PHP script) to be later generated as a file with the .schema.gen
extension.
The schema files must be inside the schemas/
folder in the APS package.