How is an asset defined? A Resource is the metadata representing a technical asset (Data or Software/Service). It includes a Resource Representation [3.2] a technical section for PDC machine interpretation [2.1]. The PDC [2.1] uses this representation from the contract [4.0] at runtime to communicate with the resource.
A resource is the technical representation of a data file or a software/service within the data space. It is defined as a data resource or software (API, service..) proposed by the provider to the marketplace that constitutes the metadata of an asset belonging to the provider and that, by itself, it is not displayed if it is not in an offer.
A resource acts as the operative description of an asset that will be used in the data exchange processes, contract negotiation and data flow processing. In this sense, a resource can represent both a data resource and a software (service) resource. The definition and configuration of a resource includes two key components: on one hand, a descriptive metadata that allows to identify, categorize and understand the purpose of a resource (such as name, type, description and geographical localization when appropriate); but, on the other hand, the technical information needed for the components of the data space to communicate with the resource during an exchange (Resource Configuration [3.2]).
During the exchange process, for a resource to be interpreted and used by the PDC, it is mandatory to complete its resource representation. This matches the access and operational technical requirements of a resource (aligned with the technical details that are defined in the PDC documentation. This includes protocol details, endpoints and parameters that allow the PDC to establish communication with the application or service exposed by the resource. This can include mechanisms to manage dynamic routes or performance variables.
A service resource is a special type of resource focused on describing a service, API/service or data process that a provider may offer and consists of technical and descriptive metadata that later, is gathered in an offer, ready to be published and discovered in the catalog [6.1].
Resources are not individually displayed in the marketplace catalog, but they are part of an offer that groups and contextualizes them for exposure to other data space participants. Once defined and configured (including the technical presentation that allows its implementation) these resources are used in the negotiation and execution of contractual processes done by the PDC [2.1] to carry out the data exchange and service execution according to defined agreements.
