[Scstudio-devel] [ scstudio-Bugs-3346100 ] Spaces in condition nodes

[SourceForge.net <no...@so...>]

Bugs item #3346100, was opened at 2011-06-30 01:14
Message generated for change (Comment added) made by xrehak
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3346100&group_id=219467

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Visio Interface
Group: None
>Status: Closed
Resolution: None
Priority: 7
Private: No
Submitted By: Radek Sedláček (rsedlac)
Assigned to: Martin Bezděka (mbezdeka)
Summary: Spaces in condition nodes

Initial Comment:
SCStudio reports an error if the text in condition nodes contains spaces.

----------------------------------------------------------------------

>Comment By: Vojtech Rehak (xrehak)
Date: 2012-07-10 06:39

Message:
Solved in Visio interface. It remains to add into internal data structure
and subsequently repair import and export.

----------------------------------------------------------------------

Comment By: Ondřej Bouda (obouda)
Date: 2011-11-25 19:02

Message:
Regarding the last comment, a condition name should really only consist of
alphanumeric characters and underlines and dots, as it is syntactically the
same as <name> ::= {<letter> | <decimal digit> | <underline> | <full
stop>}+

However, it would be useful for users to specify a free text in the
condition, just for documentation purposes - then, the condition might be
always evaluated to true.

Therefore, the following should be done:
1) BMSC conditions should forbid any characters other than {<letter> |
<decimal digit> | <underline> | <full stop>}+
2) For both BMSC and HMSC, a more explaining error should be generated,
something like "condition name can only contain letters, digits, underlines
or full stops".
3) An extension to the standard should be implemented: a string enclosed in
double quotes should be allowed as an additional value type of the
condition text. Such a string may contain anything except double quotes.
Semantics: a condition containing such a string should always be evaluated
to true.

----------------------------------------------------------------------

Comment By: Ondřej Bouda (obouda)
Date: 2011-11-25 18:42

Message:
The behavior is different in BMSC and in HMSC.

In BMSC, even a condition node containing spaces is verified OK.

In HMSC, an error is reported on a condition node containing spaces,
although quite confusing. For example, an HMSC containing just start symbol
connected to a condition containing spaces, connected to a reference node,
connected to an end symbol, the following errors are reported:
1) Bad condition: expecting next state name
2) Wrongly attached connector.
3) Wrongly attached connector.
4) Verification failed. Graphical errors in the drawing.
The reason for such a set of errors is that the parser probably does not
connect the condition node containing spaces with other elements.

The problems are the following:
1) The behavior should be the same for BMSC and HMSC.
2) According to the ITU-T Z.120, section Condition, the condition text
should (among others) contain a condition name list, which may consist of
one or more condition names. A condition name is not defined anywhere,
though, so basically there is no reason for forbidding spaces. Thus, spaces
should be allowed in condition names.
3) Should spaces be forbidden in the condition names, a more explaining
error message should be reported, at least.

----------------------------------------------------------------------

Comment By: Martin Bezděka (mbezdeka)
Date: 2011-07-08 04:06

Message:
Ok, according to previous comment, this isn't error, but feature. If not,
please specifiy the problem again.

----------------------------------------------------------------------

Comment By: Vojtech Rehak (xrehak)
Date: 2011-06-30 02:38

Message:
According to the ITU Z.120 specification, the text is specified as depicted
in the attached picture. Therefore, it is a condition expression or
condition name rather than a long text description. The reported error says
that spaces are not supported in condition names. The underline and dot is
allowed. 

For more info how to use conditions see, e.g.,
www.itu.int/ITU-T/2005-2008/com17/languages/Z120.pdf pages 42-44 (44-46 in
the PDF).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3346100&group_id=219467