- From: <ishida@w3.org>
- Date: Thu, 26 May 2016 18:14:05 +0100
- To: www International <www-international@w3.org>
https://www.w3.org/2016/05/26-i18n-minutes.html
text version follows:
Internationalization Working Group Teleconference
26 May 2016
See also: [2]IRC log
[2] http://www.w3.org/2016/05/26-i18n-irc
Attendees
Present
JcK, Rob_Sanderson, Tim_Cole, r12a, Steve_Atkin,
Ivan_Herman, Benjamin, Takeshi
Regrets
Felix_Sasaki
Chair
r12a
Scribe
r12a
Contents
* [3]Topics
* [4]Summary of Action Items
* [5]Summary of Resolutions
__________________________________________________________
<ivan>
[6]https://github.com/w3c/web-annotation/issues?utf8=%E2%9C%93&
q=is%3Aissue+is%3Aopen+label%3Ai18n-review+-label%3Aeditor_acti
on
[6]
https://github.com/w3c/web-annotation/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Ai18n-review+-label%3Aeditor_action
<azaroth> Link:
[7]http://w3c.github.io/web-annotation/model/wd2/#external-web-
resources
[7]
http://w3c.github.io/web-annotation/model/wd2/#external-web-resources
[8]https://github.com/w3c/web-annotation/issues/224
[8] https://github.com/w3c/web-annotation/issues/224
<ivan> -> WG decision
[9]https://github.com/w3c/web-annotation/issues/224#issuecommen
t-219953153
[9]
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
[10]https://github.com/w3c/web-annotation/issues/224#issuecomme
nt-219953153 sticks.
[10]
https://github.com/w3c/web-annotation/issues/224#issuecomment-219953153
<azaroth> +1
+1
<ivan> +1
<takeshi> +1
<TimCole> +1
scribenick r12a
<scribe> scribenick: r12a
<azaroth> proposal:
[11]https://github.com/w3c/web-annotation/issues/213#issuecomme
nt-221098949
[11]
https://github.com/w3c/web-annotation/issues/213#issuecomment-221098949
[12]https://github.com/w3c/web-annotation/issues/213
[12] https://github.com/w3c/web-annotation/issues/213
<ivan> Comment of Hugo:
[13]https://github.com/w3c/web-annotation/issues/213#issuecomme
nt-221530850
[13]
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> [14]https://github.com/w3c/web-annotation/issues/206
[14] https://github.com/w3c/web-annotation/issues/206
[15]https://github.com/w3c/web-annotation/issues/206
[15] https://github.com/w3c/web-annotation/issues/206
<azaroth> code units:
[16]https://github.com/w3c/web-annotation/issues/206#issuecomme
nt-219893634
[16]
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
[17]https://github.com/w3c/web-annotation/issues/221
[17] 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
[18]http://www.w3.org/2016/05/26-i18n-minutes.html#action01]
[18] 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
[19]https://github.com/w3c/web-annotation/issues/227
[19] https://github.com/w3c/web-annotation/issues/227
<azaroth> Link:
[20]http://w3c.github.io/web-annotation/model/wd2/#text-quote-s
elector
[20]
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
[21]http://www.w3.org/2016/05/26-i18n-minutes.html#action02]
[21] 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 :)
Summary of Action Items
[NEW] ACTION: Addison to review Web Annotation #227 and reply
asap with advice on Unicode normalization [recorded in
[22]http://www.w3.org/2016/05/26-i18n-minutes.html#action02]
[NEW] ACTION: Richard to provide note text to indicate that
selection tools should take care in selecting boundaries
[recorded in
[23]http://www.w3.org/2016/05/26-i18n-minutes.html#action01]
[22] http://www.w3.org/2016/05/26-i18n-minutes.html#action02
[23] http://www.w3.org/2016/05/26-i18n-minutes.html#action01
Summary of Resolutions
[End of minutes]
Received on Thursday, 26 May 2016 17:14:16 UTC