Meeting minutes
addison: we don't have a super deep agenda for today
… meeting with Web Payments
… i have a couple of agenda+
… IFT, EPUB
… we could do today or Thursday
r12a: let's do today
… i think we need to also talk about what we want to talk about with css tomorrow
addison: SPC
addison: they want to resolve the FO
… I think they think they have a resolution at hand
Action Items
<addison> https://
addison: 1017 is getting stale
addison: did 1034, need some time to review that
… did 1063 a while ago
r12a: did 1066
… renamed the label
… to match the document name
<r12a> https://
atsushi: did 1073
addison: think we did 1078
… did 1084 last Friday
… effectively the outcome is that we're going to prepare an I-D
… the three of us each have pieces in there
… URL references to language tags
… which can be used in semantic web
r12a: did 1087
r12a: did 1088
r12a: did 1089
<Najib> I can hear you
<Najib> no matter live transcript
[Discuss Live Transcript issue]
On Saving Automated Meeting Transcripts
<r12a> https://
Info Share
Review Radar
<addison> https://
addison: no new requests
<addison> https://
r12a: "JSON LD WG self review" is with a "close?" label
… let's close it
r12a: https://
addison: done
addison: we're going to meet with coga folks on Thursday
… we can look at coga issues
… could add it to the agenda
… move it to Completed on Thursday if we can
EPUB Review
https://
r12a: +1 to close 1382
<xfq> https://
xfq: added a reference to charmod-norm to say that filenames must be unicode canonical norm and full case folding
richard: agree it should be closed
addison: +1
<xfq> https://
xfq: saw two new comments today, one from richard and one from matt
… about character restrictions
<xfq> https://
xfq: they changed to text to include all non- characters
addison: never is a long time: don't think they should limit valid characters
richard: no actual restrictions except for 32 characters
<r12a> https://
addison: think disallowing tag characters is a problem
… if characters are not a problem in file systems either is a barrier to users or ends up with reqs being ignored
close 1380, open new issues
<xfq> https://
xfq: they have name attribute, IDL. they said it's only used as identifier
<xfq> https://
addison: is it true?
… could be okay with it
<xfq> https://
close 1355
xfq: length of path and file names
… propose close, they added text
addison: lgtm
<xfq> https://
xfq: encoding of css files
… why UTF-16 was mentioned?
… was historical stuff
… new text: UTF-8 is recommended, can choose either UTF
Web Payments
<r12a> https://
addison: three pending and one tracker
<addison> https://
r12a: i suspect this is the sort of thing that they all want to discuss
<addison> https://
r12a: maybe we can discuss this in the joint meeting to get more informed feedback
addison: 1412
… it has natural language text string but with no language and direction metadata
<addison> https://
r12a: most of the strings are USVStrings, but this one is DOMString
… don't know why they treat them differently
dictionary PaymentCredentialInstrument {
required DOMString displayName;
required USVString icon;
};
r12a: they can get the language and direction from the html page they're embedded?
addison: it's an externally supplied piece of information
<r12a> https://
addison: the heart of all this is do we think natural language text need language and direction metadata all the time
… introducing new structure could break things, i understand that
… but for new things should we add metadata or not?
r12a: i think we should add metadata
CSS
<r12a> https://
https://
<r12a> https://
<r12a> https://
r12a: Order of discussion
addison: font fingerprinting issue is important
… and generic font family issue
r12a: fallback @@
… different generic styles for different scripts
… there's the question of , how do you make that work
r12a: i think that also addresses the issue "What does fangsong map to for non chinese"
… and "Specify what generic font family maps to nastaliq"
… for flow-relative syntax for margin-like shorthands, we're very closed to the solution
r12a: about #6319, the color one, it's only marginally involved in i18n
… i don't think we should spend too much time on it unless we have loads of time left over
r12a: i'm generally kind of wary of talking about ruby because it is a huge sinkhole
Discuss outcome of WP meeting
addison: i think that was the right outcome
… if we solve it in TC 39, it will be a long conversation
r12a: could we change it to something like internationalized string?
… People might misunderstand the name localizable
addison: people will type it in definitions
[Discuss the naming]
addison: we don't mean localization, we mean adding metadata to strings we already have
r12a: i think you're right
<r12a> ... that we need to push on for a solution of the lang/dir string thing
addison: do we need to do other things, like do an explainer?
addison: meet with CSS tomorrow
r12a: we need to read these threads again
addison: will send an email to Murata-san