I don't believe there's currently a rule that covers this.
My guess is that the rule should state something like "The case
of the word segment that comes after the (deleted) hypen
remains" (that is, E-mail becomes Email, whereas E-Mail
becomes EMail); Lisa, we should put this in the agenda, I
believe.
Chin Chee-Kai wrote:
> 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:
> http://SoftML.Net/
>
>
>
--
Eduardo Gutentag
|
e-mail:
Web Technologies and Standards |
Phone: +1 510 550 4616 x31442
Sun Microsystems Inc.
|
1800 Harrison St.
Oakland, CA 94612
W3C AC Rep / OASIS TAB Chair
