On Fri, 16 May 2003, Tim McGrath wrote:
>>...
>>So, given this all happens, what end up with is UBLNames that have no
>>punctuation (only boring a-Z) BUT Dictionary Entry Names (and their
>>composite parts) that may have things like "-". Hopefully, this is good
>>enough for Java and Perl ;-)
Yes, boring UBLNames are good enough. The important thing is
for developers feel safe about mapping UBLNames directly
into programming language's variable or type name spaces in
a consistent manner without exception treatments of particular
UBLNames (such as those with punctuations).
Given that, is there another NDR ruling on the casing of
the word segment that comes after the hyphen? For instance,
CountrySub-Entity will, in 0p80 and after, become
CountrySubEntity or CountrySubentity?
Will E-mail and E-Mail become Email or EMail?
Is there a casing rule for that given that UBLNames shall
have no punctuations in 0p80 and further?
Best Regards,
Chin Chee-Kai
SoftML
Tel: +65-6820-2979
Fax: +65-6743-7875
Email: cheekai@SoftML.Net
http://SoftML.Net/