In the context of information technology, interoperability refers to the ability of different systems and devices to exhange information. See also https://en.wikipedia.org/wiki/Interoperability
First published in 2015 and best known as the IIRA, this standards-based architectural template and methodology enables Industrial Internet of Things (IIoT) system architects to design their own systems based on a common framework and concepts. (See https://www.iiconsortium.org/IIRA.htm and in particular https://hub.iiconsortium.org/iira)
The International data spaces (IDS) Reference Architecture Model (IDS-RAM) sets the standard for building data-driven ecosystems, products and services. (see https://internationaldataspaces.org/use/reference-architecture/ - in particular https://internationaldataspaces.org/wp-content/uploads/IDS-Reference-Architecture-Model-3.0-2019.pdf )
The Asset Administration Shell (AAS) is the digital representation of an asset. The AAS consists of a number of submodels in which all the information and functionalities of a given asset – including its features, characteristics, properties, statuses, parameters, measurement data and capabilities – can be described. It allows for the use of different communication channels and applications and serves as the link between objects and the connected, digital and distributed world. (From 'Asset Administration Shell Reading Guide (As Of April 2021)')
This item is under development
The overall concept is the use of the Admnistrative Asset Shell (AAS). It is requesting access to an object. In the context of an AAS an object typically is a submodel or a property or any other submodel element connected to the asset. The implemented access control mechanism of the AAS evaluates the access permission rules (2a) that include constraints that need to be fulfilled w.r.t. the subject attributes (2b), the object attributes and the environment conditions (2d). The focus is on access control. An object in the context of ABAC corresponds typically to a submodel or to a submodel element. The object attributes again are modelled as submodel elements. Subject Attributes need to be accessed either via an external policy information point or they are defined as properties within a special submodel of the AAS. A typical subject attribute is its role. The role is the only subject attribute defined in case of role based access control. Optionally, environment conditions can be defined. In role based access control no environment conditions are defined. Environment conditions can be expressed via formula constraints. To be able to do so the values needed should be defined as property or reference to data within a submodel of the AAS.