Open TabrizPlv opened 1 year ago
We believe that the user has mistaken the entity class Character
as a valid CLASSIFICATION
field.
In fact, our UG has several examples using char
, not Character
as a command term in our app.
Team chose [response.Rejected
]
Reason for disagreement: It is precisely that I have mistaken the entity class Character
as a valid CLASSIFICATION field that I feel that the UG is misleading.
This is because under the description of Entity classifications
, the dev team has described the entity class for characters to either be Character
or char
. That is why I mistook Character
as a valid CLASSIFICATION field.
Under entity classifications, the
Character
classification is described asCharacter
orchar
. However, when executing commands that expect aCLASSIFICATION
field likemake
command,Character
is not recognised as aCLASSIFICATION
field. For example,make Character Bob
does not work.