<trackbot> Date: 13 October 2015

Comments on JSON Schema of XSLT working group

DP: I investigated whether it is possible to use the updated schema to decode documents encoded with the original schema.
... I found you will run into issues. I don't think it is possible.
... As it turns out, it is difficult to extend the schema currently without causing incompatibilities.
... We should convince XQuery/XSLT WG.

CB: They are working together on XPath2.
... They need one more time to take a look at it. They will have the next telecon next Tuesday.
... The call overlaps with ours.

DP: So, we can't discuss next week in our telecon. That's something to discuss at TPAC.
... Do they expect us to show them the benefit?

CB: They are more interested in knowing the impact for them.

DP: We would say certain document path is not needed for us such as "escape", likewise, certain constructs will not be used for their uses.
... That way, both can use the same schema without penalty.

CB: We could use different schemas.
... If we can't find a good solution, it would also be fine to use separate ones.
... If you feel like you would like to add some more information before they can discuss, then we can do so too.

DP: If they use the schema as we described, it would be difficult for them to handle it, probably.
... Do they use JSON or XML?

CB: They read JSON.
... Converts JSON to XML tree.

DP: What if they read EXI-encoded JSON?
... If they go through plain text JSON, then they will never encounter that.
... Let's first focus on their current use case because new use cases have potential but maybe confusing for them.

Comments: Canonical EXI -- Last Call Working Draft

DP: The only way I think can support this, three combinatioins, similar to canonical EXI with comments, we could define canonical EXI with/without header options, schema Id, etc.
... We need to provide some kind of identifier for general use cases.

https://www.w3.org/XML/Group/EXI/docs/canonical/canonical-exi.html#N67698

DP: We don't say it must be done that way right now.
... We ought to define it properly now.
... With/without options, header options, schemaId and datetime normalization.
... It is good to specify it in our spec.
... I would state that the safest is to use datetime normalization and use of header options as default.
... I can propose it to the mailing list.

TK: I think it is good that way.

<scribe> ACTION: DP to propose how to differentiate canonicalization variations and which variation is the default [recorded in http://www.w3.org/2015/10/13-exi-minutes.html#action01]

<trackbot> Created ACTION-726 - Propose how to differentiate canonicalization variations and which variation is the default [on Daniel Peintner - due 2015-10-20].

<dape> 1. http://www.w3.org/TR/exi-c14n (default with EXI Option, with schemaId, with dateTime normalization)

<dape> 2. http://www.w3.org/TR/exi-c14n#WithoutEXIOptions

<dape> 3. http://www.w3.org/TR/exi-c14n#WithoutSchemaId

<dape> 4. http://www.w3.org/TR/exi-c14n#WithoutEXIOptionsWithoutDatetimeNormalization

<dape> 5. http://www.w3.org/TR/exi-c14n#WithoutSchemaIdWithoutDatetimeNormalization

<dape> 6. http://www.w3.org/TR/exi-c14n#WithoutDatetimeNormalization

Support for Canonical EXI interoperability test in TTFMS

DP: Preservation of whitespaces.
... Respect whitespaces or not.
... xs:anySimpleType, we need to define how to encode data.
... Same applies to schema-less case.
... Before, I was trimming whitespaces.
... We need to define how to remove or preserve whitespaces.

<dape> http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace

<dape> "preserve No normalization is done, the value is not changed (this is the behavior required by [XML 1.0 (Second Edition)] for element content) "

<scribe> ACTION: TK to share the whitespace removal rule used in compaction measurement [recorded in http://www.w3.org/2015/10/13-exi-minutes.html#action02]

<trackbot> Created ACTION-727 - Share the whitespace removal rule used in compaction measurement [on Takuki Kamiya - due 2015-10-20].

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

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

WARNING: No "Present: ... " found!
Possibly Present: CB DP TK dape exi https joined 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: 13 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/13-exi-minutes.html
People with action items: dp tk