[Ietf-not43] [Fwd: CRISP: Language/script-specific data sets?
]
Hollenbeck, Scott
shollenbeck@verisign.com
Thu, 26 Dec 2002 20:05:48 -0500
> -----Original Message-----
> From: Andrew Newton [mailto:anewton@ecotroph.net]
> Sent: Thursday, December 26, 2002 4:52 PM
> To: ietf-not43@lists.verisignlabs.com
> Subject: [Ietf-not43] [Fwd: CRISP: Language/script-specific
> data sets?]
>
>
> I received the following comment off-list. It sounds to me like a
> reasonable basis for a requirement.
>
> -------- Original Message --------
> Subject: CRISP: Language/script-specific data sets?
> Date: Wed, 25 Dec 2002 13:12:56 +0100
>
> Dear Andrew,
>
> I'm contacting you since you are the author of the
> crisp-requirements Internet-Draft.
>
> I notice that this draft, while it does talk about
> internationalization in relatively general terms, lacks what I
> believe to be a key requirement for an internationally useful WHOIS
> successor service.
>
> In Asian countries (but not only there), there may be ways to
> express the same physical contact data in scripts appropriate for
> different kinds of users: For instance, you'll have "Hotel
> Intercontinental, 777 Zhangyang Road, Shanghai" (don't expect the
> local taxi driver to be able to read this), and you'll have a
> Chinese name and address which I can't read (but the taxi driver
> understands). For CRISP, this means that there should be provisions
> for some language- or script-based polymorphism -- like a more
> advanced version of the "/EN" switch known from the .jp WHOIS
> service.
FWIW, in the provreg WG protocol we're providing the ability to provision
contact data in two character sets. It would probably be a good idea if
there were provisions to display one or both forms using the CRISP protocol.
-Scott-