UML14 — OCL: String literals

If, as I was told before, they are supposed to be similar to Java
strings, the correct rule for string constants will be:

string := "'" (
(~["'","\\","\n","\r"] )

Allowing octal escapes only in the ASCII range is not really a part
of syntax ­ it is a part of OCL semantics, and this is where it
belongs.

As a matter of fact, even that is not 100% right ­ because it doesn't
allow for hexadecimal escape sequences ­ and allows to specify
only ASCII characters (decimal codes 0..255), while in Java strings
the hexadecimal escapes can be used to specify any UNICODE
character.

I am also wondering, why OCL insists that all strings should be
ASCII strings? Is there a compelling reason for disallowing
UNICODE strings (and thus having no support for international
applications)?

No Data Available