See also: IRC log
https://www.w3.org/International/track/actions/open
action-511?
<trackbot> action-511 -- Richard Ishida to Check if discource for wicg can add notifier for an i18n label -- due 2016-05-05 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/511
sent email, no reply yet
action-512?
<trackbot> action-512 -- Richard Ishida to Send www-international an email about removing topic index and prepare new home page and other page mods as needed to support that -- due 2016-05-05 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/512
close action-512
<trackbot> Closed action-512.
action-513?
<trackbot> action-513 -- Richard Ishida to Raise an issue against html about default q-styling -- due 2016-05-05 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/513
close action-513
<trackbot> Closed action-513.
<r12a> https://github.com/w3c/i18n-activity/issues/124
richard: new version of unicode-xml with disclaimer published
http://w3c.github.io/i18n-activity/radar/
richard: one issue raised
http://w3c.github.io/i18n-activity/projects/
<r12a> https://github.com/w3c/browser-payment-api/issues/53#issuecomment-215709951
richard: info share
... have found a way to put i18n tags on other peoples
repos
... and make it so that when the label is applied to an issue
we get notified
... and also when closed
<scribe> ... done for html wg
<scribe> ... done for some other wg
UNKNOWN_SPEAKER: might be payments
<scribe> ... in process of doing for annotation people
UNKNOWN_SPEAKER: negotiated with
ivan an hour or so ago
... have a way for all groups going forward
requirements dev
richard: some talk with
swaran
... trying to get more content/community involvement
... should watch summary of issues
... quite a lot of html issues now
... a lot from chaals
... also looked through issue list
<r12a> http://w3c.github.io/i18n-activity/reviews/
richard: vote on publishing ruby markup?
addison: any comments?
richard: a couple of very small
things, easily fixed
... none from fantasai and koji
... ping before publising?
addison: all in favor of publishing "ruby markup" (link below)?
<r12a> http://w3c.github.io/i18n-drafts/articles/ruby/markup.en.html
<David> +1
+1
<r12a> +1
<JcK> +1
addison: so approved
<scribe> ACTION: richard: publish ruby markup article after pinging fantasai and koji [recorded in http://www.w3.org/2016/05/05-i18n-minutes.html#action01]
<trackbot> Created ACTION-514 - Publish ruby markup article after pinging fantasai and koji [on Richard Ishida - due 2016-05-12].
richard: spent time trying diff
strategies for keeping by more efficient
... like putting keywords in meta
... but search is much more useful
... finds stuff I can't keyword
... and stays up to date
... propose to replace with a big search box
addison: just searches International/
richard: yes
<scribe> ACTION: richard: replace topic index with a giant search box [recorded in http://www.w3.org/2016/05/05-i18n-minutes.html#action02]
<trackbot> Created ACTION-515 - Replace topic index with a giant search box [on Richard Ishida - due 2016-05-12].
richard: sent note to steven p asking what he intended to do with it
https://lists.w3.org/Archives/Member/member-i18n-core/2016Apr/0027.html
talk about this next week
addison: triage wontfixed bugzilla items in case any action is needed?
<scribe> ACTION: addison: triage wontfixed bugzilla items in case any action is needed? [recorded in http://www.w3.org/2016/05/05-i18n-minutes.html#action03]
<trackbot> Created ACTION-516 - Triage wontfixed bugzilla items in case any action is needed? [on Addison Phillips - due 2016-05-12].
<scribe> ACTION: addison: remind working group to review HTML items in http://w3c.github.io/i18n-activity/reviews/ for next call [recorded in http://www.w3.org/2016/05/05-i18n-minutes.html#action04]
<trackbot> Created ACTION-517 - Remind working group to review html items in http://w3c.github.io/i18n-activity/reviews/ for next call [on Addison Phillips - due 2016-05-12].
<r12a> http://w3c.github.io/i18n-activity/reviews/#html
<r12a> https://lists.w3.org/Archives/Member/member-i18n-core/2016Apr/0045.html
richard: first one is about
reference to IRI
... they refer to URL or IRI
... what should be calling these? URL?
addison: and which spec
richard: no harm done?
investigate whether they spec needs to dirty its hands with serializing to the wire
am-2) Reference to BCP47 See https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bodies-and-targets <https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bodies-and-targets> "The Body or Target SHOULD have exactly 1 language associated with it, but MAY have 0 or more. The value of the property SHOULD be a language code following the [rfc5646 <https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bib-rfc5646>] specifiction.“ Shouldn’t this [CUT]
yes, BCP47
potentially raise issue about 0 or more
0 or 1 unless they mean to have a language priority list
am-3) Definition of character See https://www.w3.org/TR/2016/WD-annotation-model-20160331/#embedded-textual-body <https://www.w3.org/TR/2016/WD-annotation-model-20160331/#embedded-textual-body> "The character sequence of the content of the Textual Body.“: this text and the whole document is missing a definition of a character.
richard: word character used a
lot
... charmod says to define
... one their issues
define character probably as code point
am-4) Counting of characters See https://www.w3.org/TR/2016/WD-annotation-model-20160331/#fragment-selector <https://www.w3.org/TR/2016/WD-annotation-model-20160331/#fragment-selector> A question is whether Is it possible for the plain text selector to specify the normalization form, to understand what is being counted. One resolution may be to say in reference to comment 3) that a character is always a unicode character in NFC. The same comment applies t[CUT]
want to count the code points in the *not* normalized file
probably related to our work with find text
want grapheme boundaries (for some def of grapheme??)
richard: want normalization for some other operations possibly
addison: for matching and such
am-5) Text quote selectors and mixed scripts See https://www.w3.org/TR/2016/WD-annotation-model-20160331/#text-quote-selector <https://www.w3.org/TR/2016/WD-annotation-model-20160331/#text-quote-selector> Is there a need to specific what happens with mixed scripts, or at least require testing of text quote with mixed scripts?
not sure what this is
ap-1) General comment on annotation retrieval https://www.w3.org/TR/2016/WD-annotation-protocol-20160331/#annotation-retrieval The section says „If more than one representation of the Annotation is available, then the server SHOULD support content negotiation." Creators of annotations are missing guidance whether annotations in different languages should be provided via content negotiation or whether it is recommended to have variation in language speci[CUT]
needs further study
richard: one other think about
normalization
... when they say it, they mean stripping html and other such
stuff
... we need to be careful to be explicit about what we
mean
... when we use the "normalization" word
<scribe> ACTION: felix: submit approved issues to web-annotations after speaking to richard about the discussion [recorded in http://www.w3.org/2016/05/05-i18n-minutes.html#action05]
<trackbot> Created ACTION-518 - Submit approved issues to web-annotations after speaking to richard about the discussion [on Felix Sasaki - due 2016-05-12].