The AAS-connect GraphQL reference schema for the Asset Administration Shell introduces a clear separation between data and its metadata. The complexity of implementing and using the AAS is greatly reduced and performance is increased.
The GraphQL AAS-connect Reference Schema is developed for the application together with Neo4j. The schema is according to the IDTA specification IDTA-01001 - Metamodel of the Asset Administration Shell and is part of the AAS-connect Repository & DataHub OTS Installation Kit.
AAS-connect Repository & DataHub OTS Installation Kit on GitHub: xxx
Design of the AAS-connect GraphQL Reference Schema:
- The AAS-connect GraphQL reference schema is divided into two schemas: the user data schema (user data model level) and the metadata schema (metadata model level). In principle, both schemas can be used independently of each other and implemented via different endpoints.
- The reference to metadata is realized with the relations hasMetadata and metadataFor or for Submodel Templates with hasTemplate and templateFor.
- The user data schema contains the object types of the Asset Administration Shell (e.g. AssetAdministrationShell, AssetInformation or SpecificAssetId) as well as the data of the model elements. The designation of the data objects always begins with the abbreviation from the AAS specification, e.g. SmcData or PropData.
Not all model elements are available in the model. This is an excerpt from the leading GraphQL schema.
Example of an GraphQL-Query (Neo4j GraphQL Library):