Issue 4692: 6.8.1.9 String on page 6-34 (ocl2-ftf) Source: Fujitsu (Mr. Hiroshi Miyazaki, miyazaki.hir-02@jp.fujitsu.com RHD02651@nifty.ne.jp) Nature: Uncategorized Issue Severity: Summary: In the String explanation, There is a descrition that "The OCL type String represents ASCII strings." I think this cannot apply to multi-byte code. Could you change this sentence to "The OCL type String represents strings consisting of ASCII characters and/or multi-byte characters. Resolution: Revised Text: No text change needed. Actions taken: November 9, 2001: received issue December 2, 2004: Transferred to OCL 2.0 FTF November 1, 2005: closed issue Discussion: Resolution: This is an OCL 1 issue transferred to the OCL 2 FTF. Already resolved in OCL2: In 11.4.3 it is written: "The standard type String represents strings, which can be both ASCII or Unicode." End of Annotations:===== From: "Hiroshi Miyazaki" To: , Subject: Internationalization issues with UML 1.4 Date: Fri, 9 Nov 2001 11:57:03 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0247_01C16915.A5593080" X-UIDL: >hJe9,YWd9VOP!!ZKHe9 Dear UML-RTFer and UML2er As Kobryn-san mentioned, I send a issue list about UML1.4/OCL. Could you see an attached file? Best Regards, ================================ Hiroshi Miyazaki Fujitsu e-mail)miyazaki.hir-02@jp.fujitsu.com TEL)+81-43-299-3531 FAX)+81-43-299-3633 1-9-3 Nakase, Mihama-ku Chiba-city Chiba, Japan 261-8588 ================================= [] oclcommentsfor118.txt 2. 6.8.1.9 String on page 6-34 In the String explanation, There is a descrition that "The OCL type String represents ASCII strings." I think this cannot apply to multi-byte code. Could you change this sentence to "The OCL type String represents strings consisting of ASCII characters and/or multi-byte characters. X-Sender: klas0@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 03 Jun 2002 09:27:22 +0200 To: From: Jos Warmer Subject: Re: UML RTF: Poll to correct internationalization issues Cc: "UML RTF" Cris, I reviewed the changed in detail. All chnages are ok, except for the second ond. This is simply a misunderstanding. The '~' character in the String grammar rule simply means all characters except the ones mentioned. In this case: (( ~[ it means all characters except the ones mentined bnetween the sauare brachets. The '~' symbol belongs to the grammar formalism, not to OCL. I propose to add a sentence explaining the meaning of '~' in the second paragraph of 6.9 Jos] At 11:59 PM 6/2/2002 -0700, Cris Kobryn wrote: ISSUES & PROPOSED RESOLUTIONS -------------------------------------------------------------- > This is issue # 4691 Hiroshi Miyazaki" > > 1. 6.2.1 "legend" on page 6-3, Internationalization issue > > 1. 6.2.1 "legend" on page 6-3, > There is a following description. > "OCL expression are written using ASCII characters only" > This sentence can be interpreted in this context as > a) OCL expressions are written using only > ASCII characters as examples in this document, > b) the OCL expression must be written by only > ASCII characters in general usage? > > Could you change this to > "OCL expressions in this document are > written using ASCII character only." RESOLUTION: In Section 6.2.1 change the sentence "OCL expression are written using ASCII characters only" to "OCL expressions in this document are written using ASCII characters only." > ------------------------------ > > This is issue # 4692 Hiroshi Miyazaki" > > > 6.8.1.9 String on page 6-34 > > In the String explanation, > There is a descrition that > "The OCL type String represents ASCII strings." > I think this cannot apply to multi-byte code. > > Could you change this sentence to > "The OCL type String represents strings consisting > of ASCII characters and/or multi-byte characters. RESOLUTION: In Section 6.8.1.9 change the sentence "The OCL type String represents ASCII strings." to "The OCL type String represents strings consisting of ASCII characters or multi-byte characters." > --------------------------------- > > This is issue # 4693 Hiroshi Miyazaki" > > > EBNF of the String on page6-48. > > Relating this, in the EBNF of the String on page6-48. > There is a "~" symbol after double brackets. > Does this means negation? > If it is negation, there is no modification of String > definition on the EBNF even though the body of string > explanation is changed. > But, I cannot find a "~" definition in the EBNF. > In the unaryOperater definition of the EBNF on page6-48 > There is a "-". > I think this is a "~" symbol. RESOLUTION: p. 6-48 change "unaryOperator := "-" | "not" " to "unaryOperator := "~" | "not" " > > -------------------------------- > > This is issue # 4694 Hiroshi Miyazaki" > > inhibtedChar on page6-48, > > 4.Regarding inhibtedChar on page6-48, > its definition is following. > > inhibitedChar := > "|"\"|"#"|"\'"|"("|")"|"*"|"+"|","| > "|"."|"/"|":"|";"|"<"|"="|">"|"@"| > ["|"\\"|"]"|"{"|"|"|"}" > > But, this definition is slightly different from one which we > have provided previously. > (Top two characters of each line are dropped) > > > inhibitedChar := " " | "\"" | "#" | "\'" | "(" | ")" | > "*" | "+" | "," | "-" | "." | "/" | > ":" | ";" | "<" | "=" | ">" | "@" | > "[" | "\\" | "]" | "{" | "|" | "}" RESOLUTION: p. 6-48 replace the current inhibitedChar set with the corrected version provided above. _____________________________________________________ Klasse Objecten tel : +31 (0)35 6037646 Chalonhof 153 fax : +31 (0)35 6037647 3762 CT Soest email : J.Warmer@klasse.nl The Netherlands internet: http://www.klasse.nl "