Re: [calsify] [Last-Call] Artart last call review of draft-ietf-calext-jscontact-07

[Robert Stepanek <[e-mail]>]

All,

thanks for your input. I have now published a new draft which includes a section about internationalization. I think this addresses our discussion. I copy the section contents verbatim here:

---
1.6. Internationalization

JSContact aims to be used for international contacts and addressbook data. Notably text values such as names and addresses are likely to cover a wide range of languages and cultures. This section describes internationalization for free-form text values, as well as for Uniform Resource Identifiers (URIs).

1.6.1. Free-form text

Properties having free-form text values MAY contain any valid sequence of Unicode characters encoded as a JSON string. Such values can contain unidirectional left-to-right and right-to-left text, as well as bidirectional text using Unicode Directional Formatting Characters described in Section 2 of [UBiDi]. Implementations setting bidirectional text MUST make sure that each property value complies with the requirements of the Unicode Bidirectional Algorithm. Implementations MUST NOT assume that text values of adjacent properties are processed or displayed as a combined string, for example the values of a given name component and a surname component may or may not to be rendered together.

1.6.2. URIs

Several properties require their string value to be a URI as defined in [RFC3986]. Implementations MUST make sure to use proper percent-encoding for URIs that can not be represented using unreserved URI characters. JSContact makes no recommendation how to display such URIs, but section "4.8.3 Internationalization and special characters" of the W3C URL Standard [W3C-URL] provides guidance for URLs found in context of a web browser.

---

Regards,
Robert

On Wed, Aug 30, 2023, at 7:50 PM, Rob Sayre wrote:
> On Wed, Aug 30, 2023 at 8:37 AM Robert Stepanek <[e-mail]> wrote:
>> 
>> I do plan to look at Rob's suggested example on Wikipedia tomorrow. Should I find something there that currently isn't supported in JSContact and is relevant for addressbook data, I'll be happy to try coming up with a way to support it.
> 
> To be clear, the case I wondered about was the URL itself (try selection on that one in a web browser).
> 
> thanks,
> Rob
>