EXI telecon time poll

TK: CB says Monday and Thursday work.

DP: Both work for me as well.

TK: Next week, we don't have EXI telecon.

Canonical EXI

DP: The test cases, in general are complete.

TK: We can start running test cases.

DP: I already noticed differences.
... Time canonicalization, and one issue in float encoding.
... I will run the entire test cases again.

CB: The charter ends at the end of August.
... We have to show progress before that.

TK: Should we notify the public about complete test cases?

CB: If we can get third implementation, it will be better.
... We can claim now test cases are ready.

<scribe> ACTION: DP to Notify public that the Canonical EXI test cases are ready for use. [recorded in http://www.w3.org/2017/07/04-exi-minutes.html#action01]

<trackbot> Created ACTION-746 - Notify public that the canonical exi test cases are ready for use. [on Daniel Peintner - due 2017-07-11].

EXI4JSON

JSON schema mapping best practices

DP: XSD all capability is limited.
... Therefore, TK suggested to use "choice".
... It causes again UPA issue.
... Can we use XSD 1.1 feature?
... Xerces does not complain, either.
... One solution is to properly add "any" for each object if it allows for additional properties.
... We can soften the requirement about strict being "true".
... From EXI's point of view, it does not cause issue.

TK: I am also in favor of option 1.

DP: Do we also mention that XML Schema 1.0 processor may report an error, but for the purposes of generating EXI grammar, it is OK. And also XML schema 1.1 fixed this issue.

CB: XSD 1.1 is implemented in products. Xerces and Saxon, for example.
... Existing schemas are still using XSD 1.0.

<dape> http://xerces.apache.org/mirrors.cgi

DP: We can say, unknown datatypes are mapped to string codec.

CB: If you want to use XSD 1.1 with EXI 1.0, you can say that.
... It would be easier to provide FAQ about this.

<dape> https://www.w3.org/TR/xmlschema11-2/#built-in-datatypes

<dape> https://www.ibm.com/developerworks/library/x-xml11pt1/

<dape> https://www.w3.org/TR/xsd-precisionDecimal/

<scribe> ACTION: TK to experiment with the use of XSD 1.1 new datatypes. [recorded in http://www.w3.org/2017/07/04-exi-minutes.html#action02]

<trackbot> Created ACTION-747 - Experiment with the use of xsd 1.1 new datatypes. [on Takuki Kamiya - due 2017-07-11].

Schema-informed JSON support experiment

DP: It relates to the mapping for JSON schema.
... JSON schema is not deterministic in the sense that it first needs to explore further.
... I was trying to write JSON-schema to XML schema converter.

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: 04 Jul 2017
Guessing minutes URL: http://www.w3.org/2017/07/04-exi-minutes.html
People with action items: dp tk