Efficient XML Interchange Working Group Teleconference

22 Mar 2016

See also: IRC log




<scribe> scribe: TK

<scribe> scribeNick: taki

Extended String

DP: In some use cases, there are lots of enumerated values.
... Even enumerated values are represented as strings when lexical preservation is true.

TK: Original string codec doesn't pick up extended string codec.

DP: Enumerated values are something we already have.
... If you can use values in schema, use those values. Otherwise, use shared strings.

TK: We can reserve names that are meant for enumerated string values. Another way is use annotation.

DP: One possibility is to group the strings into chunks.

TK: I wondered whether we want to use separate tables for schema strings and shared strings.
... I will experiment with schema annotation approach.

Canonical EXI

DP: It doesn't fail simply because it can't represent structural whitespaces now.

TK: I will review the paragraphs in details.

EXI for CSS - first try

DP: I played a bit with CSS.
... In Java, (also in W3C), there is a way to map CSS to DOM.
... I used this DOM to create schema, then used this schema with EXI.
... I tried a bit with it.
... Depending on the CSS and the constructs you use in CSS, the result is different.
... I compared with minified CSS.
... If you have very simple CSS consisting of a few strings, there is no difference.
... If it is more complex, EXI shows good result.
... Maybe there is css test suite.

<brutzman> Curiously the HTML5 specification lists 13 separate CSS references, primarily CSS2 https://www.w3.org/TR/html5/references.html#references

CB: It is better to use real ones.
... Also, try CSS3. It has richer constructs.

<brutzman> https://www.w3.org/TR/CSS points to CSS Snapshot 2015 (Working Group Note) http://www.w3.org/TR/2015/NOTE-css-2015-20151013

<brutzman> HTML5 points to Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification, which is superceded by CSS Level 2 Revision 2.2 http://www.w3.org/TR/2015/ED-CSS22-20150904

<brutzman> ... which is W3C Editors' Draft 04 September 2015

DP: The library I used say it supports CSS3.

<caribou> https://drafts.csswg.org/css2/

<brutzman> the link was found at CSS2, which itself redirected off of W3C site https://drafts.csswg.org/css2/ but claims to be W3C Editor's Draft

<brutzman> ... specifically W3C Editors' Draft 04 September 2015, new editor Bert Bos

DP: I will try to use CSS3. The library cialms to support CSS3.

<caribou> CSS Selectors is even CSS4: https://drafts.csswg.org/selectors/

DP: I read something about CSS4.

<caribou> https://drafts.csswg.org

<brutzman> CSS Snapshot 2015 says "This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2015. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate."

<brutzman> CSS2 R2 Appendix D. Default style sheet for HTML 4 (seems over-simple) https://drafts.csswg.org/css2/sample.html

<brutzman> perhaps better: Appendix G. Grammar of CSS 2.2 https://drafts.csswg.org/css2/grammar.html

<brutzman> so that is very helpful. to pursue such a capability, we have to track both implementation software also the apparently evolving standards landscape

<brutzman> not clear if the grammar has been updated somewhere for CSS3 or HTML5

<brutzman> am hoping that central CSS data structures are well defined, and the variations are primarily property names.

<brutzman> if that is the case, an XML schema for CSS that is oriented around the data structures would be relatively stable

<brutzman> so it appears that we need to keep studying CSS2 and CSS3 design

<brutzman> Possibly useful: CSS Syntax Module Level 3 https://drafts.csswg.org/css-syntax

DP: I think we should not focus on schema too much. We should think about ways to make it work even without schemas.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/03/22 15:38:18 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/ert/Bert/
Found Scribe: TK
Found ScribeNick: taki

WARNING: No "Present: ... " found!
Possibly Present: CB DP TK brutzman caribou dape exi https joined scribeNick trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 22 Mar 2016
Guessing minutes URL: http://www.w3.org/2016/03/22-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]