Efficient XML Interchange Working Group Teleconference

15 Dec 2015

See also: IRC log




<scribe> scribe: TK

<scribe> scribeNick: taki

Plans for telecons during holiday season

TK: Next telecon will be on Jan 12.

DP: Javier D. Fernández joined the WG.
... From University of Austria.
... He is interested in RDF representation.
... I did take a look at the format. (HDT? or both?) It is very much aligned with EXI strategy.
... One is a submission to W3C, I believe.


DP: I planned to update the document to prepare for review by the group for the first working draft.

CB: Thursday will the last day for publication this year.

DP: I will finish the draft this week. Don said he was going to take a look. Review by Jan 12 will be ok.

CB: Sounds good.

Canonical EXI

Re: Support for Canonical EXI interoperability test in TTFMS

DP: Header allows DTRM.

TK: User's EXI datatype that permits empty string also needs to be mentioned.

DP: The more you have to specify, the less good solution is. You have to process empty CH when the EXI datatype permits empty string.

TK: I will summarize the two proposals, asking the public which of the two is favorable.

Whitespace preservation mode

DP: Currently, we are using the rules defined by XBC working group.
... If you want that behaviour, you can put xml:space on the root element.
... We should try to limit the number of variations.
... Should we have a section about whitespace handling?

TK: Yes, I think we need to specify whitespace handling.

ACTION-732: Investigate whether ecma's json spec is more appropriate to make a reference to or not

CB: I suggest we use RFC.

<caribou> http://www.ecma-international.org/publications/standards/Ecma-404.htm

DP: Wikipedia says ECMA is minimal whereas RFC provides semantics and security aspects.

CB: We should use most recent and most recent one, which is the one from IETF.

TK: So, the group thinks we should use RFC for referencing JSON.

ISSUE-110: What to do with xml:space being preserved in strict mode

DP: If you have an element type-castable and nillable, in strict mode, you can't do both.

TK: I think best practice is to use default-schema mode when you deal with documents that use xml:space="preserve".

DP: Preservation of prefixes, for example. Qualified names are encoded as strings.
... In canonical EXI, we should mention it. But we should keep track of those issues, and have those mentioned somewhere.
... Appendix section of the spec. Or best practice document is another choice.

<dape> http://www.w3.org/TR/exi/#addingProductionsStrict

TK: Do we want to update the spec to mention that in the errata of the core spec.
... I am going to add it in the errata.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2015/12/15 16:40:59 $

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)

Found Scribe: TK
Found ScribeNick: taki

WARNING: No "Present: ... " found!
Possibly Present: CB DP TK caribou dape exi 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: 15 Dec 2015
Guessing minutes URL: http://www.w3.org/2015/12/15-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]