isLinkedTo Property

[jorgearj]

Currently the isLinkedTo property has the domain: PriceComponent, and is used to link service features to determined PriceComponents.

Should we keep this property or link all the service features to the Service through the gr:qualitativeProductOrServiceProperty and gr:quantitativeProductOrServiceProperty?

This way we may not know to wich features is the PriceComponent linked.

[drleidig]

If we link to a ProductOrServiceProperty, this will be the target of a service property (via the hasProductOrServiceProperty). Theoratically it must be possible to find out which feature and which service this is.

[jorgearj]

After the discussion of the 28th March meeting it seems this issue is quite complex to address. Without the isLinkedTo property we have no way to relate a PriceComponent to a specific service feature. Saying for example in the the amazon EC2 example that the PriceComponent_EC2_Small_EU_OnDemand_Linux_General is related to a Unix operating system.

Some options discussed:

• Change the name of the property isLinkedTo and use it to link PriceComponents to URIs that could be domain specific concepts or gr:qualitativeServiceOrProductProperty. This would be similar to tagging.
• Maybe the hasMetrics property can be used. i.e. a PriceComponent price is measured based on service features. We still have the problem of defining these features.
• Use the price function to add these features as variables. However some are features that do not change the price but are included in the service. i.e. 24h support.

A simple way of dealing with this issue is yet to be found.

[jorgearj]

If the service features are defined in the Service and ServiceOffering levels through the ServiceProperty concept there may be no need for the isLinkedTo property at the PriceComponent level.

[jorgearj]

The conclusion was to leave aside the isLinkedToProperty. All the service features should be defined in the Service or ServiceModel.