Issue 16899: Attribute CodingRule::coding should be typed by ValueSpecification (uml-testing-profile-rtf)
Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de)
Nature: Revision
Severity: Minor
Summary: The specification states that coding rules should be defined outside of the utp model and just being referred from the utp model.


In some situations, it can might be required to include a precise coding and decoding of values already in the model. 

Therefore, the coding attribute should be typed by ValueSpecification, which would allow both merely naming the coding rule that should be used by an external test execution environment (LiteralString) and a formal representation of the coding/decoding mechanism itself (Expression/InstanceValue/OpaqueExpression)
Resolution: 
Revised Text: 
Actions taken:
December 14, 2011: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 14 Dec 2011 01:54:38 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Marc-Florian Wendland
Employer:        Fraunhofer FOKUS
mailFrom:        marc-florian.wendland@fokus.fraunhofer.de
Terms_Agreement: I agree
Specification:   UML Testing Profile
Section:         7.3.2.1
FormalNumber:    ptc/2011-07-19
Version:         1.1 - beta 1
Doc_Year:        2011
Doc_Month:       July
Doc_Day:         19
Page:            27f.
Title:           Attribute CodingRule::coding should be typed by ValueSpecification
Nature:          Revision
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


The specification states that coding rules should be defined outside of the utp model and just being referred from the utp model.


In some situations, it can might be required to include a precise coding and decoding of values already in the model. 

Therefore, the coding attribute should be typed by ValueSpecification, which would allow both merely naming the coding rule that should be used by an external test execution environment (LiteralString) and a formal representation of the coding/decoding mechanism itself (Expression/InstanceValue/OpaqueExpression)