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

0007110

Part-2 TDL graphical syntax

[TDL] Editorial

public

21-07-2015 13:37

07-12-2015 16:06

Reporter

Philip Makedonski

Assigned To

Philip Makedonski

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

feedback

Resolution

open

Platform

OS Version

Product Version

[TDL] Part-2 V1.1.1

Target Version

[TDL] Part-2 V1.2.1

Fixed in Version

Summary

0007110: Ensure consistency between meta-model properties and graphical syntax labels

Description

Consistency may be helpful and should be generally encouraged unless there are good reasons not to go through with it. Someone looking at the meta-model first, may have hard time finding the corresponding property in the graphical notation at first. For example period vs duration, dataType vs interaction, etc.

I think there is a case to be made regarding ensuring consistency unless there are good reasons for not doing so and in the case of periods and durations (and possibly a few others - interaction vs dataType in GateType?), there aren’t any.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0013565) Gusztáv Adamis (manager) 07-12-2015 15:45 edited on: 07-12-2015 16:06	Interaction is changed to DataType in GR in GateType. But for the period in Time and Timer Operations - if the name consistency is required - the name in the MM shall be changed from 'period' to 'duration' since it is not actually a period, but a duration as the explanation of that property also shows in MM. E.g.: • period: DataUse [1] The 'period' defines the time duration of the 'TimeOperation'. I guess the name of a property shall be clean and self-explaining in the GR - which is used by the users - rather in MM - which is mainly only for tool developers. But since in the OCL definition in GR it is explained, I guess it cannot lead to misunderstanding even if the names are different. I also believe that it would be better if the names were the same in both documents, but here I believe that the term used in MM is worse than the term used in GR.

Issue History
Date Modified	Username	Field	Change
21-07-2015 13:37	Philip Makedonski	New Issue
21-07-2015 13:37	Philip Makedonski	Status	new => assigned
21-07-2015 13:37	Philip Makedonski	Assigned To	=> Gusztáv Adamis
07-12-2015 15:45	Gusztáv Adamis	Note Added: 0013565
07-12-2015 15:47	Gusztáv Adamis	Assigned To	Gusztáv Adamis => Philip Makedonski
07-12-2015 15:47	Gusztáv Adamis	Status	assigned => feedback
07-12-2015 16:06	Gusztáv Adamis	Note Edited: 0013565	View Revisions

MantisBT 1.2.14 [^]