W3C

- DRAFT -

Efficient Extensible Interchange Working Group Teleconference

31 Jul 2017

See also: IRC log

Attendees

Present
Regrets
Chair
SV_MEETING_CHAIR
Scribe
taki

Contents


TPAC2017 for EXI?

DP: We can still use some other space even if we could not use ad-hoc meeting space.

Canonical EXI

TK: Thank you Daniel for the interoperability test results.
... It looks all problems are on OpenEXI side.

DP: If you observation is different, please let me know.

TK: I will give an update next week.

https://www.w3.org/wiki/TPAC/2017/ad-hoc-meetings

<brutzman> TPAC 2017 agenda http://www.w3.org/2017/11/TPAC/Overview.html

TPAC2017 for EXI

DB: Thursday afternoon, there is AC meeting.

DP: Alternative is, to have ad-hoc meeting on Friday.
... I am not sure if I can join TPAC at this point, but if I can go, I will try to stay one day longer.

<brutzman> W3C Publishing Summit https://www.w3.org/publishing/events/summit2017.html

<brutzman> here is another area of work that might benefit from EXI: https://www.w3.org/blog/2016/10/w3c-and-big-data

<brutzman> am simply thinking that we might conceptualize a broader strategy for EXI, how does it help other areas of W3C work and the Open Web Platform.

<brutzman> ... then we might use TPAC week as a goal for upcoming communications, and an opportunity to interact with other groups and consider joint endeavors.

EXI4JSON

<brutzman> TK: moved EXI Ad Hoc meeting to Friday 10 NOV 1500-1800. https://www.w3.org/wiki/TPAC/2017/ad-hoc-meetings#EXI_ad-hoc_meeting

DP: I tried to share feedback from my experiences with WoT.
... Thing Description is written in JSON.
... We are looking at EXI4JSON, CBOR, etc.
... I noticed several things.
... I categorized into three.
... General EXI4JSON issue.
... For small documents, character escaping makes names with "@" sign bigger.
... One character becomes 4 characters for those for the first occurrence.
... Second category is EXI4JSON with dedicated schema.
... UPA issue.
... Valid in XSD 1.1, but not in XSD 1.0.
... Media-types. We want to use enumerated values.
... With strict mode, we cannot deviate.
... URI strings are very similar, with only the last part of strings are different.
... I am not sure if we need to stick with "strict" mode.
... Last category is how to standardize EXI4JSON.
... People were against using non-standard specification.
... EXI is a standard. How can we make EXI4JSON a standard?

<brutzman> question: A1. keyname escaping, is the basic issue that @ symbol is not allowed as a key?

<dape> Don you are right @ is not a valid character in XML... and since we wanted to keep compatibility with XML we decided to escape @ and similar characters

<brutzman> thanks, next question

<brutzman> # B Issues with dedicated schemas in EXI4JSON: it would seem we most want compatibility with XSD 1.1 version...

<brutzman> ... alternatives might be to either only support 1.1, or else list deviations such as this that might be known limitations of some sort.

<brutzman> B2. Pre-populated strings based on enumerated values: it is also possible to define enumeration values and use them as attribute values, even if they are optional/extendible (meaning not strict but allowed)...

<dape> no mentioning of 1.1 is made

<brutzman> ... wondering if we can handle this case. (in X3D schema we have been informally documenting such relationships as appinfo)

<brutzman> B2. Pre-populated strings based on enumerated values: seems very valuable, hope we can do it.

<dape> EXI refers to xml schema 1.0 in the spec

TK: I suggest to continue discussion on EXI4JSON next week.

<brutzman> Daniel maybe next time we could talk about JSON schema efforts, looks like you posted over on that list.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/07/31 16:06:08 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)


WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: taki
Inferring Scribes: taki

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

Found Date: 31 Jul 2017
Guessing minutes URL: http://www.w3.org/2017/07/31-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]