Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BaSyx / Documentation / API / Registry"
(Added page) |
|||
Line 80: | Line 80: | ||
* 400: Bad Request | * 400: Bad Request | ||
* 502: Bad Gateway | * 502: Bad Gateway | ||
+ | |} | ||
+ | |||
+ | |||
+ | {| class="wikitable" | ||
+ | | BaSyx project links: [[BaSyx | Project BaSyx main wiki page]] <nowiki>|</nowiki> [[BaSyx.WhatIsBasyx | What is BaSyx?]] <nowiki>|</nowiki> [[BaSyx.Documentation | BaSyx Developer Documentation]] | ||
|} | |} |
Revision as of 12:28, 20 November 2018
The BaSyx discovery API is implemented by BaSyx discovery services. Discovery services enable the discovery of conforming production entities, which are production entities that export an Asset Administration Shell (AAS). The Asset Administration Shell is a data structure that describes the production entity. It provides basic data and a directory of sub models that describe specific aspects of production entities. Production entities may be any entity that is relevant to production. This includes products under production, devices, workers, but also non-physical entites such as placed orders, and as well products that have been sold. The discrovery service enables discovery and management of Asset Administration Shells via a defined HTTP REST interface.
GET | /api/v1/registry | Description
|
POST | /api/v1/registry | Description
|
GET | /api/v1/registry/{aasId} | Description
|
PUT | /api/v1/registry/{aasId} | Description
|
DELETE | /api/v1/registry/{aasId} | Description
|
BaSyx project links: Project BaSyx main wiki page | What is BaSyx? | BaSyx Developer Documentation |