Internationalization Working Group Teleconference

<ivan> https://github.com/w3c/web-annotation/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Ai18n-review+-label%3Aeditor_action

<azaroth> Link: http://w3c.github.io/web-annotation/model/wd2/#external-web-resources

https://github.com/w3c/web-annotation/issues/224

<ivan> -> WG decision https://github.com/w3c/web-annotation/issues/224#issuecomment-219953153

agreed: use direction property as currently described

<ivan> Proposal comment: On the meeting with the I18N WG (2016-05-26) the Anno WG reiterated that it intends to follow the direction as advised by the I18N WG. The decision in https://github.com/w3c/web-annotation/issues/224#issuecomment-219953153 sticks.

<azaroth> +1

+1

<ivan> +1

<takeshi> +1

<TimCole> +1

scribenick r12a

<scribe> scribenick: r12a

<azaroth> proposal: https://github.com/w3c/web-annotation/issues/213#issuecomment-221098949

https://github.com/w3c/web-annotation/issues/213

<ivan> Comment of Hugo: https://github.com/w3c/web-annotation/issues/213#issuecomment-221530850

<azaroth> +1 to my proposal :)

<ivan> +1

+1

<Steve_Atkin> +1

<TimCole> +1

<takeshi> +1

<ivan> https://github.com/w3c/web-annotation/issues/206

https://github.com/w3c/web-annotation/issues/206

<azaroth> code units: https://github.com/w3c/web-annotation/issues/206#issuecomment-219893634

<azaroth> proposal is to continue to use code points (still)

<ivan> +1

<Steve_Atkin> +1

+1

<takeshi> +1

<TimCole> +1

https://github.com/w3c/web-annotation/issues/221

<JcK> On 206, I continue to be concerned that using code points without further qualification will create opportunities for serious user confusion, introduce normalization issues, etc., But I'm not expert enough in this particular area to feel comfortable blocking a decision.

<azaroth> Proposal for 221 is to remove the recommendation to normalize whitespace

<TimCole> +1

+1

<ivan> +1

<Steve_Atkin> +1

<takeshi> +1

<JcK> +1

<azaroth> And that if the client cannot find the unnormalized text, it can easily normalize the whitespace internally and then search again

<scribe> ACTION: Richard to provide note text to indicate that selection tools should take care in selecting boundaries [recorded in http://www.w3.org/2016/05/26-i18n-minutes.html#action01]

<trackbot> Created ACTION-526 - Provide note text to indicate that selection tools should take care in selecting boundaries [on Richard Ishida - due 2016-06-02].

<azaroth> Proposal is to record, in a note, that clients may use the value of the Content-Location header to record the target of the annotation, to ensure that server specific content negotiation is taken into account (e.g. IP address geo-location, rather than Accept-Language header)

<ivan> +1

+1

<Steve_Atkin> +1

<TimCole> +1

<takeshi> +0

https://github.com/w3c/web-annotation/issues/227

<azaroth> Link: http://w3c.github.io/web-annotation/model/wd2/#text-quote-selector

<azaroth> And then scroll to the paragraph following the table in model

<azaroth> Micro proposal to change should to SHOULD

<ivan> +1

<scribe> ACTION: Addison to review Web Annotation #227 and reply asap with advice on Unicode normalization [recorded in http://www.w3.org/2016/05/26-i18n-minutes.html#action02]

<trackbot> Created ACTION-527 - Review web annotation #227 and reply asap with advice on unicode normalization [on Addison Phillips - due 2016-06-02].

<azaroth> i18n++ :)

<azaroth> +1 to r12a :)

<azaroth> Thank you i18n folks :)