- All Superinterfaces:
org.gcube.informationsystem.base.reference.Element, org.gcube.informationsystem.model.reference.entities.Entity, org.gcube.informationsystem.base.reference.entities.EntityElement, org.gcube.informationsystem.model.reference.ERElement, GCubeResource, org.gcube.informationsystem.base.reference.IdentifiableElement, org.gcube.informationsystem.model.reference.ModelElement, org.gcube.informationsystem.model.reference.entities.Resource, Serializable
- All Known Subinterfaces:
ComputingInfrastructure, EService, HostingNode, RunningPlugin, VirtualMachine, VirtualService
- All Known Implementing Classes:
ComputingInfrastructureImpl, EServiceImpl, HostingNodeImpl, RunningPluginImpl, ServiceImpl, VirtualMachineImpl, VirtualServiceImpl
@ResourceSchema(facets={@ResourceSchemaEntry(facet=DescriptiveMetadataFacet.class,description="Any descriptive information associated with the service, e.g. for discovery purposes."),,},resources={,,,,,})
@TypeMetadata(name="Service",
description="Service (Abstract) represents any typology of service worth registering in the infrastructure. Service has relations with quite all other resources. If on one side, a Hybrid Data Infrastructure (HDI) is created to manage datasets, on the other side the HDI is born to manage such datasets digitally. We could affirm that datasets and services are the two pillar resources around which revolves the entire infrastructure. It is important to highlight that Service has a general meaning and must not be intended as a network-callable service which is represented instead by one of its specialisations called [EService](type:EService). Given that Service is abstract no [IsIdentifiedBy](type:IsIdentifiedBy) association with a facet is provided which in turn is the responsibility of the specialisation.",
version="1.0.0")
@Change(version="1.0.0",
description="First Version")
public interface Service
extends GCubeResource
Service (Abstract) represents any typology of service worth registering in
the infrastructure.
Service has relations with quite all other resources.
If on one side, a Hybrid Data Infrastructure (HDI) is created to manage
datasets,
on the other side the HDI is born to manage such datasets digitally.
We could affirm that datasets and services are the two pillar resources
around which revolves the entire infrastructure.
It is important to highlight that Service has a general meaning and must
not be intended as a network-callable service which is represented instead
by one of its specialisations called
EService.
Given that Service is abstract no
IsIdentifiedBy association with a
facet is provided
which in turn is the responsibility of the specialisation.
Service could be intended as a specialisation of
the entity PE1_Service defined in PARTHENOS Entities Model (PE Model)
and the entity D1_Digital_Object defined in CRMdig.
- Author:
- Luca Frosini (ISTI - CNR)