Changing the "directionBound" attribute name

Submitted by Loïc Blaive on Thursday, 22 January, 2015 - 11:18
Issue ID
187
Component
UML General
Category
Feature request
Priority
Normal
Assigned
Status
Fixed
Source
CEN
Description

Comment raised by UK during TC approval of CEN/TS 16157-2
There are various uses of "directionBound" – this term implies a boundary or even a binding, not a heading.

A better term should be used e.g. "flowDirection".
 

{"changeLogs":[{"date":1527781687099,"componentOLD":"- Select a value -","component":"UML General","categoryOLD":"- Select a value -","category":"Feature request","priorityOLD":"- None -","priority":"Normal","assignedOLD":"","assigned":"iancornwell (42)","statusOLD":"- None -","status":"Fixed"},{"date":1537268228613}]}

Posted by iancornwell on July 23, 2022 Permalink

Implemented TG resolution documented by Loic - dropping "bound" from attribute names. At Oporto there was a suggestion to use "absoluteDirection" but on reflection that has the wrong implication since the possible direction values would not all be considered absolute. It is surely clear enough that "direction" is different from "relativeDirection" without adding "absolute".