15:53:23 RRSAgent has joined #cssns 15:53:23 logging to http://www.w3.org/2011/06/17-cssns-irc 15:53:51 zakim, this will be conf1 15:53:51 ok, plinss; I see Team_(cssns)16:00Z scheduled to start in 7 minutes 15:55:36 plh has joined #cssns 15:56:26 ChrisL has joined #cssns 15:57:38 rrsagent, here 15:57:38 See http://www.w3.org/2011/06/17-cssns-irc#T15-57-38 15:57:50 zakim, code? 15:57:50 the conference code is 26631 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), plinss 15:57:54 rrsagent, make logs public 15:58:18 Team_(cssns)16:00Z has now started 15:58:25 +plinss 15:58:41 +Plh 15:58:49 r12a has joined #cssns 15:59:11 +ChrisL 15:59:19 scribenick: ChrisL 15:59:58 zakim, dial richard please 15:59:58 ok, r12a; the call is being made 15:59:59 +Richard 16:01:07 chair: plh 16:01:41 Meeting: Normalisation and W3C with particular reference to CSS 16:02:36 plh: Primary goal is to move css selwsctors forward 16:02:39 http://www.w3.org/wiki/I18N/CanonicalNormalization 16:02:47 http://lists.w3.org/Archives/Public/www-style/2009Feb/0231.html 16:02:59 http://www.w3.org/International/docs/charmod-norm/ 16:03:42 peter, is dbaron's preserence for normalise-at-parse expressed somewhere other than his 2009 summary linked above? 16:05:32 http://lists.w3.org/Archives/Public/www-style/2009Feb/0231.html was wikified (link above) 16:05:54 http://www.w3.org/wiki/I18N/CanonicalNormalization 16:06:55 http://test.csswg.org/harness/results/CSS21_DEV/ 16:07:34 http://test.csswg.org/harness/results/CSS21_RC6/ 16:10:14 http://www.w3.org/Style/CSS/Test/ 16:14:31 + +1.408.790.aaaa 16:15:07 zakim, aaaa is addisson 16:15:07 +addisson; got it 16:15:31 plh: css ns blocked on normalisation issue, which also blocks css selectors 16:15:48 http://www.w3.org/TR/2008/CR-css3-namespace-20080523/ 16:16:18 aphillip has joined #cssns 16:16:21 http://dev.w3.org/CSS/css3-namespace-test-suite/ 16:16:54 plh: norm is not done on the identifier. implementors not willing to do so 16:17:08 plinss: yes 16:17:44 adisson: we dont require full normalisation of docs or stylesheets but we want normalised compare especially for identifiers and namespaces 16:18:09 ... same ns or not should nor depend on source encoding or order of combining marks 16:18:27 plinss: so you said you dont want to normalise selectors? 16:18:45 ad: not require stylesheets to be in a particular form 16:18:56 ... comparisons should be normalised 16:19:05 ... but not random text selection 16:20:33 ChrisL: 'early' norm can men by content autors or at parse time; which do you mean 16:20:53 ad: content is not normalised all the time. so user agents are responsible. 16:21:29 ... should they normalise at parse or compare 16:21:56 r12a:may be a reason to have denormalised text in content. but different for class selectors, id s etc which are compared 16:22:07 ... may make sense to normalise just those 16:22:18 ad: interactions with dom and exmascript 16:22:50 ... wg position is to focus on comparison being normalised. dont care how its done. normalising identifiers at parse time is one way 16:23:11 plinss: so you see that as just an implementation detail? 16:23:21 ad: there can be side effects from that choice 16:23:49 ... harder to normalise individual tokens, but possible. then question is which tokens 16:24:03 plinss: and what does the dom see and what does script assume 16:24:26 ad: so yu can't make certain queries anymore 16:24:39 plinss: not sure how this is particular to nnamespaces 16:25:09 ad: ns is a token plus an IRI. want them to compare in a normlised fashion 16:25:25 ... so can tell what ns is in use regardless of document encoding 16:25:37 r12a: mac vs pc normalisation ... 16:25:45 ad: mainly filenames there 16:26:20 ... also vietnamese keyboard different on mac and pc wrt normalisation so you get two different strings that look the same 16:26:50 plinss: no namespaces in css are like xml - you take a uri and give it a prefix to use. you want to notmalise the prefix or the uri? 16:27:28 ad: uri has no non-ascii. iri has the rues in it (or will have) for how that works. so main concern is the prefix that has to be unique 16:28:02 plinss: prefix in css is an ident. so we would have to normalise all idents. but we have author deined idents - why pick on ns in particular 16:28:25 ad: coparisons should be normalising for identifiers 16:29:04 plh: so we just published css as a rec, and it defines an ident. so why does this apply to css ns and not css 2.1 16:29:12 ad: it does apply to css 2.1 16:29:54 ad: the horse has escaped. so i18n wg is in catch up. not been succesful so far. 16:30:22 ... last vestige of attempt to normalise is to getidentifiers normalised. if we cant do that then we are done 16:30:46 ... valid for us t question whether we are doing the right thing to put the onus on content authors to sort it out 16:31:03 plh; for styling, if the class or id does not match you will see right away 16:31:31 ad: stylesheet may be dynamically generated and separae from the doc. author can't see why it doesnt work 16:32:03 plinss: yes, but that does not apply here as ns prefixes are local to the scope of a single stylesheet. only the uri is matched internallt 16:32:33 ... so there is a consistent normalisation. unrelated to any prefixes used in the document 16:32:48 ... any unicode in an author defined ident is in the one document 16:32:59 ad: or if you use escapes 16:33:13 plinss: esapes should not be normalised anyway 16:33:20 ad: ok, thats not so .... 16:33:42 plinss: css ident is asci wit unicode escapes, we dont apllow random unicode in there 16:33:54 ad: think you allow a reasonable range 16:34:02 plinss: a small range 16:34:31 ... i see classes as an issue certainly, but also attribute selectors. but none of that applies to namedspaces 16:34:34 ident [-]?{nmstart}{nmchar}* 16:34:34 name {nmchar}+ 16:34:34 nmstart [_a-z]|{nonascii}|{escape} 16:34:34 nonascii [^\0-\237] 16:34:41 ... and frankly that applies right back to css1 16:35:34 plinss: if we want norm we should require it all the places tat it matters. every place the author can type an ident. or nothing 16:35:47 ... happy to support that but this is ot the place to make the stand 16:36:24 ad: our comments actually went to selectors first. its kind of a test case as someone has to do something to decisde which directionw e go 16:36:49 ... are we going to normalise some important thins or not. if not then the guidelines need to be changed so people know what to avoid 16:37:01 .. didnt go to ns til the end. started with selectors 16:37:21 ... this is a relaxation f out position 5 yerars ago which was noralise everything 16:37:30 .. realise this is problematic 16:37:42 r12a: and we need to get html to norm at the same time 16:37:57 plinss: lots of things do selection 16:38:49 ad: out position is that we recomend css wg , and we wont object to publishing css ns without it 16:38:57 r12a: yes 16:39:08 ... but wanted to be sure we asked the question 16:39:37 ad: concerned about selectos. concern is we have a web tha is not normalised and not normalising 16:39:44 plh: bring it to the tag? 16:39:53 ad: yes (again) 16:40:18 ad: dont want to make recommendatins that are destructive and pointless 16:40:34 ... started work towards fixing charmod to say the right thing 16:40:47 ... only question mark is whether comparisons are normalised 16:40:58 plinss: csswg see this way outside scope of css 16:41:22 ... normalising idents needs to have a norm story for comparing outside the stylesheet, so affects html 16:41:36 ad: and you shouldnt assume the docs are normalised 16:41:51 plinss: has implications on html 16:42:10 ... if css normalises a class name but javascript doesnt then there is an issue 16:42:20 ... needs to go tot tag and be consisten on all specs 16:42:43 ... tag finding would be very useful. dont want to see a mismatch on identifier handling 16:43:00 plh: also orm on fragment identifiers 16:43:07 ad: potentially 16:43:18 ... iri may require that but not currently 16:43:44 ad: speaking not as the chair,the horse is out so i suspect we wont do any of this 16:43:51 ... too many leaks to fix 16:44:03 ... want to avoid inconsistency 16:44:17 ... wg thinks we should at least make an effort 16:44:24 ... tag finding is best way 16:44:40 plh: css1 css 2.1 - its too late to change tat 16:44:48 cnt change selectors in css2 16:45:05 r12a: can start wt next version 16:45:08 plh: no 16:45:41 plh: css3 selectors have to be backward comat with css 2.1 as there is no versioning in css 16:46:06 r12a: in practical terms it would be backwards compar as only a handful of people would rely on this 16:46:29 ad: this isnt a hugely breaking change its a subtle change for almost everyone 16:46:39 plh: makes it even harder to sell 16:47:09 ChrisL: everyone will notice if all comparisons are slower 16:47:21 ad: only if its a major slowdown 16:47:41 plinss: this is why implementors prefer nortm at parse time. but that is a sepatrate detail 16:47:50 ... main focus is what to do with namespaces 16:48:07 ... takin it to tag is the right way to go. needs a champion on the tag 16:48:42 ... once we have a stor thatgoes across html and dom and css then we can change thngs 16:49:00 plh: so .... what do we do 16:49:15 ... brig it to tag with peter 16:49:32 ... and css wg decides then moves to pr with css ns 16:49:41 ... these could be done together 16:49:56 ... its blocked since 2009 and is not productive 16:50:05 ad: formal objection is not productive 16:50:56 plh: want the issue t be looked into if css wg moves forward 16:51:44 ad: specially concerned abot nt impacting html5 more than needed 16:52:18 -ChrisL 16:52:32 action: r12a to bring normalisation of idents to tag 16:52:59 +ChrisL 16:53:24 plh; hw ln for a ransitin rewuest 16:53:30 plin: less than a week 16:53:33 addison: i18n will not formally object to NS, but we very well could do so for Selectors 16:53:53 s/ad/aphillip/g 16:54:22 plinss: tag currently focussed on microdata vs rdfa. so at least a few weeks 16:54:44 r12a: i18n will require a lot longer than that 16:55:01 ... and aftyer a tag ruig would require a lot more time than that 16:55:14 ... so is it worth holding up css ns and selectors? 16:55:32 aphillip; if selectors is published without norm then its the end of the road 16:56:04 r12a: we have done ok without it so far. there wil be new versionsin the future 16:56:17 plinss: selectors level 4 is already being worked on 16:56:32 aphillip: more time that passes the harder it is to effect change here 16:56:43 ... its selectos, ecmascript, dom etc 16:56:54 plh: this is already implemented in older browsers 16:57:53 plinss: selectos 3 added mainly pseudoclases it does not change the comparisons much 16:58:31 ad: we last published charmod-norm 6 years ago. the we got browbeaten into not requirin early normalisation 16:59:00 ... its untenable then and we have worked on it for 1 years. so 16 years on we are no closer to accomplishig it 16:59:37 plinss: because css is modular, norm affect much more than jus selectors 16:59:54 ... so we would want a normalisation update to 2.1 that covers all idents 17:00:14 ad: dont want the i18n wg focused on this corner case for all eternity 17:00:33 ... not being helpful by hitting norm every couple of years 17:01:00 ad: we can ask for the tags attention and it may be thre weeks or so before we get even a reply 17:01:14 ... will take us that long to get a discussion document 17:01:27 plh: counting on peter to advocate for this being on thw agenda 17:01:33 plinss: happy to do so 17:01:58 plh: ok so for ns, my sentiment is that we are better off letting css ns and selectors progress 17:02:13 ... because a lot of chang eis needed and its not limited to just those two 17:02:34 .. so css wg shoudlrequest PR on both noting te issue is not closed byut asking to move forward 17:03:10 action: plinss request PR transition for css namespaces and css selectors, once tag is alerted 17:03:40 rrsagent, make minutes 17:03:40 I have made the request to generate http://www.w3.org/2011/06/17-cssns-minutes.html ChrisL 17:04:14 plh: come back to this in a few weeks with the request i hand 17:04:17 adjourned 17:04:22 rrsagent, make minutes 17:04:22 I have made the request to generate http://www.w3.org/2011/06/17-cssns-minutes.html ChrisL 17:04:41 -ChrisL 17:04:43 -Plh 17:04:46 -addisson 17:04:48 -Richard 17:04:49 -plinss 17:04:49 Team_(cssns)16:00Z has ended 17:04:50 Attendees were plinss, Plh, ChrisL, Richard, +1.408.790.aaaa, addisson 17:05:07 rrsagent, make minutes 17:05:07 I have made the request to generate http://www.w3.org/2011/06/17-cssns-minutes.html ChrisL 19:26:52 Zakim has left #cssns 21:36:53 r12a has left #cssns