Skip to main content
Jump to: navigation, search

Difference between revisions of "BaSyx / Documentation / API"

 
Line 1: Line 1:
BaSyx defines for each component an API through which it can be accessed.
+
This section documents the API of major BaSyx components. The API enables developers and users to access BaSyx components, and will be kept stable between versions of the BaSyx platform. They are mostly relevant for developers that want to develop substitutes or extensions to BaSyx components. Most application developers will want to develop their applications with the BaSyx SDK that provides higher-level access to these APIs.
Currently, for the following components the API is defined:
+
 
 +
Currently, for the following components have a defined API:
 
* [[BaSyx.AssetAdministrationShell | Asset Administration Shell]]
 
* [[BaSyx.AssetAdministrationShell | Asset Administration Shell]]
 
* [[BaSyx_/_Documentation_/_API_/_Submodel | SubModel ]]
 
* [[BaSyx_/_Documentation_/_API_/_Submodel | SubModel ]]
 
* [[BaSyx_/_Documentation_/_API_/_Registry | Registry]]
 
* [[BaSyx_/_Documentation_/_API_/_Registry | Registry]]
 
* [[BaSyx_/_Documentation_/_API_/_ControlComponent | Control Components]]
 
* [[BaSyx_/_Documentation_/_API_/_ControlComponent | Control Components]]

Latest revision as of 14:36, 9 March 2020

This section documents the API of major BaSyx components. The API enables developers and users to access BaSyx components, and will be kept stable between versions of the BaSyx platform. They are mostly relevant for developers that want to develop substitutes or extensions to BaSyx components. Most application developers will want to develop their applications with the BaSyx SDK that provides higher-level access to these APIs.

Currently, for the following components have a defined API:

Back to the top