18:55
<zcorpan>
http://simon.html5.org/tools/js/designmode-viewer/
18:58
<zcorpan>
Hixie: yt?
18:59
<Hixie>
yep
18:59
<Hixie>
wassup?
19:02
<zcorpan>
Hixie: what tool do i use to make a ToC and xrefs in the ARIA draft?
19:03
<Hixie>
i use the css postprocessor
19:03
<Hixie>
if that's what you're asking
19:03
<zcorpan>
yeah
19:03
<zcorpan>
pointer?
19:03
<Hixie>
http://www.w3.org/Style/Group/css3-src/bin/postprocess
19:04
<zcorpan>
thanks
19:04
<Hixie>
wow, this has to be the most tedious input device ever. http://www.youtube.com/watch?v=ENkjkIypXq4
19:04
<Hixie>
that's amazing.
19:07
<Hixie>
what's interesting about these videos is that they're disabilities adressed by input devices, and the alt/longdesc/summary/headers arguments don't even remotely affect them
19:09
<virtuelv>
amazing is the word
19:23
<zcorpan>
http://simon.html5.org/specs/aria-proposal now has a toc and xrefs :)
19:26
Hixie
shudders at "A role as defined in WAI-ARIA Roles or XHTML Role Attribute Module."
19:26
<Hixie>
please define the ua requirements for everything in this spec..
19:26
gsnedders
points at his watch as a conformant UA
19:27
<zcorpan>
Hixie: yeah, in due course
19:28
<Hixie>
btw when you have multiple class=notes next to each other, especially if they refer to each other, you might consider a div class=note with three paragraphs
19:28
<Hixie>
because the way the stylesheet works, the class=note introduces a Note: prefix which makes the paragraphs sound very unrelated
19:28
<Hixie>
wtf is a curie
19:28
<Hixie>
is it a qname?
19:29
<zcorpan>
not quite
19:29
<takkaria>
why did someone call it a curie, too? every time I see it, I think physics first off
19:29
<zcorpan>
didn't you ask that a few days ago also? :)
19:29
<Dashiva>
It's a c(razy) uri e(xpression)
19:30
<Hixie>
zcorpan: didn't make sense to me then, doesn't make sense to me now
19:31
<zcorpan>
Hixie: doesn't make sense to me, either
19:31
<Hixie>
2.2 doesn't seem to be updated to handle curies
19:31
<Hixie>
(ua reqs)
19:32
<Hixie>
are there _examples_ of these curie things?
19:32
<zcorpan>
it's not intended to handle curies
19:32
<Hixie>
ah ok
19:32
<Hixie>
then it needs to be made clearer
19:32
<Hixie>
cos right now it's unclear what a "supported custom role" is
19:32
<Hixie>
or whether "A role as defined in WAI-ARIA Roles or XHTML Role Attribute Module" can be a curie
19:33
<Hixie>
basically your spec right now is a little confused cos it sometimes gives descriptions at the level of syntactic details and sometimes just refers to other specs
19:33
<Hixie>
i recommend just doing everything at the syntax level and having notes that say "and this is a curie, see spec thisorthat"
19:33
<Hixie>
so that you don't have to read a bazillion specs to implement your spec
19:34
<zcorpan>
ok
19:34
<Hixie>
i'm really glad you're working on this spec though
19:35
<Hixie>
since it seems we're stuck with having role= in our life, i'm glad at least we'll have a well-defined spec
19:35
<Hixie>
are you sending last call comments on it?
19:35
<Hixie>
the role lc?
19:35
<zcorpan>
thanks for the feedback, i'll look into it later
19:35
<zcorpan>
i haven't
19:35
<zcorpan>
i guess i could
19:39
<Hixie>
please do
19:39
<Hixie>
i considered it but i had literally zero ua conformance criteria and i didn't know where to start
19:39
<Hixie>
you are far more knowledgable in this space
19:40
<zcorpan>
i guess :)
22:36
<jgraham>
Is it specified anywhere what to do if the <meta parsing algorithm returns UTF-16 but there is no BOM (or, I suppose, more generally if it detects any encoding that does not have enough codepoints in common with ascii for the algorithm to both work and return the real encoding?)