See also: IRC log
felix: should publish something now.. the last publication was in dec
publication by next week
Pablo: finish by next Monday
Jirka: issues 106 & 107
issue 116 safely closed
issue 117 need feedback to close
issue 118 still clarifying with HTML wg
issue 119: waiting to be incorporated by Dave..
felix: issues pending review, which ones need to be closed
Dave: looked at pending issues first..
<fsasaki> jirka: my action needs one more week, to look at pending review issues
issue 70 did a follow-up with commentors.. just need to put it back in document (will close by next week)
<trackbot> ISSUE-70 -- Defined order of precedence missing inherited local values -- pending review
issue 76: ready to close
David: did some edits..
DaveL: safely closed: issue 79 82 84
marking it as a substantive or informative change
Felix: let's close it for now, see what w3c mgmt later thinks..
we currently have directionality, Yves & dF making tests
<fsasaki> "Directionality, non-normative" > "Directionality"
change the dashboard
daveL: issue 80 (global rules referring to examples) closed
dF: hear back from..
daveL: sent an email did not hear back
<fsasaki> "Please let us know wether you are ok with the resolution. If we don't hear back from you within two weeks we assume this as closed."
fsasaki: email sen to Richard dated 31 March
dF: what to do when commentator do not reply back
fsasaki: if it is a more severe change, important to get feedback
daveL: issue 88
... issue 90 (directionality)
<scribe> ACTION: felix on action 90 [recorded in http://www.w3.org/2013/04/03-mlw-lt-minutes.html#action01]
<trackbot> Created ACTION-473 - On action 90 [on Felix Sasaki - due 2013-04-10].
daveL: will go back to issue still open
<fsasaki> DaveL: safely closed: issue 79 82 84
fsasaki: Christian said fine to close this
should we close issue 68?
issue 68 closed
<tadej> I'm also fine with that - I seem to be muted
action fsasaki come to York's comments
<trackbot> Created ACTION-474 - Come to York's comments [on Felix Sasaki - due 2013-04-10].
<tadej> I'm muted
fsasaki: Tadej said everyone must fill in the form by tomorrow for Bled attendance
deadline for hotel researvation is tomorrow (April 4th)
fsasaki: any other qs on f2f?
goal is to close all open last call issues by Face2 Face
<fsasaki> "Caveat Related to XSLT-based Processing of ITS Selector Attributes: ..."
fsasaki: propose to remove above note note
<Yves_> +1 on removing that note
Jirka: example 11 should stay, just drop the note
fsasaki: anybody against closing removing the note?
action Jirka edit to issue 117
<trackbot> Created ACTION-475 - Edit to issue 117 [on Jirka Kosek - due 2013-04-10].
fsasaki: Dave, update on ontology before Bled Meeting?
daveL: send an email clarifying general usage issues (yes/no),
do stand-off notation like LQI require special class?
daveL: update Ontology before Bled meeting
fsasaki: Jirka summarized it.
any comments on issue 116?
issue 116 closed
fsasaki: many of these are connected to quality
<Yves_> Just one minor note: we use both "Web" and "web" across the document, should we be consistent?
<Yves_> I meant "Web" and "web"
<Yves_> in many places
<scribe> ACTION: fsasaki to ensure capitalization of Web is consistent in document [recorded in http://www.w3.org/2013/04/03-mlw-lt-minutes.html#action02]
<trackbot> Created ACTION-476 - Ensure capitalization of Web is consistent in document [on Felix Sasaki - due 2013-04-10].
fsasaki: safe to close the issues for now
<Yves_> we talked about encoding rather than linebreak
<Yves_> I think from Anne's input we can simply drop the NEL case in our list (because NEL is not converted to LF in XML)
Jirka: that is true
it is not interpreted as line break character
<Yves_> I can include that in the re-writing I have to do for encoding.
<Yves_> or Jirak's solution... fine with me too
<fsasaki> "The storage size is expressed in bytes and is provided along with the character set encoding and the line break type which will be used when the content is stored."
<fsasaki> this is mlw-lt issue-107
<trackbot> ISSUE-107 -- I18N-ISSUE-247: Clarify interpretation of line breaks when calculating storage size [ITS-20] -- open
action Jirka make edit on issue 107
<trackbot> Created ACTION-477 - Make edit on issue 107 [on Jirka Kosek - due 2013-04-10].
fsasaki: might need another call with i18n WG, let's see if they come back to us.
<fsasaki> Maybe we should add a sentence like: 'Note that the value of storage size will generally give no indication about the display length of the text and is therefore not adequate for expressing constraints relating to display length.' after: 'The storage size is expressed in bytes and is provided along with the character set encoding used to store the content.'
fsasaki: this is from Stefan'semail
does anyone disagree using byte as storage size?
email0001 and email0007
<Yves_> sure I can do that
action Yves make edit on issue 106
<trackbot> Created ACTION-478 - Make edit on issue 106 [on Yves Savourel - due 2013-04-10].
fsasaki: Yves submitted a list of translatable elements
fsasaki: question to everybody: do you agree with Yves' comments?
or have anything to add on the attributes
daveL: do we know how long it will take for them to get back
fsasaki: it depends on what dependency we create..
HTML spec is still in flux
fsasaki: in testsuite, all translate-related tests will need to be changed
fsasaki: latest version of what
WG spec WG
... there is mismatch
daveL: just checking through must and must not
normative or informative needs to be addressed
<fsasaki> "6 Using ITS Markup in HTML" and sec. 7: need "these section is normative"
<fsasaki> ACTION: felix to add "normative" statement to sec 6 and 7 [recorded in http://www.w3.org/2013/04/03-mlw-lt-minutes.html#action03]
<trackbot> Created ACTION-479 - Add "normative" statement to sec 6 and 7 [on Felix Sasaki - due 2013-04-10].