Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0007159

Part-1 Metamodel

[TDL] Technical

public

03-09-2015 09:00

14-12-2015 17:13

Reporter

Philip Makedonski

Assigned To

Philip Makedonski

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

[TDL] Part-1 V1.2.1

Target Version

[TDL] Part-1 V1.3.1

Fixed in Version

[TDL] Part-1 V1.3.1

Summary

0007159: Change dataType multiplicity for SpecialValueUse

Description

Currently, SpecialValueUse has a mandatory dataType property (multiplicity=1). In the graphical syntax there is no way to modify access the data type, as it is assumed to be automatically derived. If it is automatically derived, it does not need to be specified in the meta-model. This would suggest that the property is removed altogether.

However, there is a case where it may be impossible to derive it automatically. In the case where AnyValue is used as the argument of an interaction between two gate instances that support multiple data types (e.g. string and integer), it is impossible to determine a single data type. While there may be a valid case where either one is acceptable, it is also useful to allow the user to optionally specify a data type in case the interaction argument needs to be refined to "any integer" in one case and "any string" in another, while still having the ability to express "any integer or string" (technically any data type supported by both the source and target gates when there is no data type specified). Corresponding CR will be filed for the GR as well.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0013607) Gusztáv Adamis (manager) 11-12-2015 16:33	Apart from changes related AnyValue, in MM either the multiplicity of dataType of AnyValueOrOmit and OmitValue shall to be set to [0] or a constraint must be added in these classes, if the multiplicity is specified as [0..1] in SpecialValueUse.

(0013626) Philip Makedonski (manager) 14-12-2015 17:13	Fixed by moving the dataType property to AnyValue and changing its multiplicity to [0..1]. Corresponding semantics description has been adapted to explain the role of the dataType property.

Issue History
Date Modified	Username	Field	Change
03-09-2015 09:00	Philip Makedonski	New Issue
03-09-2015 09:00	Philip Makedonski	Status	new => assigned
03-09-2015 09:00	Philip Makedonski	Assigned To	=> Philip Makedonski
11-12-2015 16:33	Gusztáv Adamis	Note Added: 0013607
14-12-2015 17:13	Philip Makedonski	Note Added: 0013626
14-12-2015 17:13	Philip Makedonski	Status	assigned => resolved
14-12-2015 17:13	Philip Makedonski	Fixed in Version	=> [TDL] Part-1 V1.3.1
14-12-2015 17:13	Philip Makedonski	Resolution	open => fixed

MantisBT 1.2.14 [^]