DP: I caught up with TK's email.
... Canonical EXI 4.3.1 and 4.3.2.
... I propose two sections together.
... I added an example.

<dape> https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#excludeExtraneousEvents

DP: The example is about simple type and strict is on.
... I will update section 4.3.1 to make the second paragraph more generic.

<dape> Section, 4.2.2 issue: https://lists.w3.org/Archives/Public/public-exi-comments/2017Mar/0003.html

DP: Section 4.2. I added a list of two steps.

<dape> Section, 4.2.2 issue: https://lists.w3.org/Archives/Public/public-exi-comments/2017Mar/0002.html

DP: There are situations that Canonical EXI processor behaves differently from XML-schema validator.
... We might want to avoid using the term "canonical exi" processor.

TK: I suggest we use "should not", instead of "must not".

DP: schemaId issue.

https://lists.w3.org/Archives/Public/public-exi-comments/2017Mar/0000.html

DP: I used "MAY" because it is optional.
... JS is in favor of removing it.
... I think the warning in constraint item 4 in section is important.
... Do we want to remove item 4 constraint, and move the warning to after the constraints list?

integer in EXI4JSON

DP: We have various types.
... It may increase event code size.
... There are some other types in "otherType"/

s/\// /

DP: I also confirmed most JSON library differentiates floats from integers.
... I will check what would be the impact.

CB: A draft about "+exi" was re-submitted in IETF.
... In my opinion, they should work-around it because the situation is the same.
... One person pushed back.
... Without knowing the schame, you cannot process the document.
... Some people started to use "+exi" already.

DP: My recollection is that seml walked away from EXI. I think they now use JSON.
... For senml, they did not allow "senml+exi".

CB: I think there is "senml-exi".
... I wonder who are using "+exi".

DB: In addition to XML, there are JSON, etc.
... EXI is somewhat special.

CB: With "+exi", you can use various schemas.
... I will keep watching.

<brutzman> thanks Carine for all of the information about media type efforts.

<brutzman> Not finding anything on our public or private working group pages regarding media type efforts.

<brutzman> EXI has many similarities to gzip in that there can be both application/gzip [RFC6713] https://tools.ietf.org/html/rfc6713 and http content encoding

<brutzman> EXI also has similarities to XML for media types, where it is possible to consider something+XML as well as something+exi encodings.

<brutzman> EXI is now going beyond the functionality of each with the emergence of extensible encodings for JSON, CSS, JavaScript etc.

<brutzman> So a comprehensive strategy will need to be pursued, this is very important.

<brutzman> The X3D media types will want to exercise each of these options.

<brutzman> we should likely expect additional future work to emerge as we achieve Canonical EXI and begin to align it with XML Encryption and XML Authentication.

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)

FAILED: s/\// /
Succeeded: s/DP/CB/
Present: DP TK CB DB
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: 07 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/07-exi-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.