14:04:49 RRSAgent has joined #exi 14:04:49 logging to http://www.w3.org/2015/10/13-exi-irc 14:04:51 RRSAgent, make logs public 14:04:51 Zakim has joined #exi 14:04:53 Zakim, this will be EXIWG 14:04:53 I do not see a conference matching that name scheduled within the next hour, trackbot 14:04:54 Meeting: Efficient XML Interchange Working Group Teleconference 14:04:55 Date: 13 October 2015 14:12:20 TOPIC: Comments on JSON Schema of XSLT working group 14:13:17 DP: I investigated whether it is possible to use the updated schema to decode documents encoded with the original schema. 14:13:50 DP: I found you will run into issues. I don't think it is possible. 14:15:15 DP: As it turns out, it is difficult to extend the schema currently without causing incompatibilities. 14:15:28 DP: We should convince XQuery/XSLT WG. 14:15:44 CB: They are working together on XPath2. 14:16:10 CB: They need one more time to take a look at it. They will have the next telecon next Tuesday. 14:17:21 CB: The call overlaps with ours. 14:17:53 DP: So, we can't discuss next week in our telecon. That's something to discuss at TPAC. 14:19:16 DP: Do they expect us to show them the benefit? 14:19:32 CB: They are more interested in knowing the impact for them. 14:20:26 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. 14:20:54 DP: That way, both can use the same schema without penalty. 14:21:29 CB: We could use different schemas. 14:21:55 CB: If we can't find a good solution, it would also be fine to use separate ones. 14:22:56 CB: If you feel like you would like to add some more information before they can discuss, then we can do so too. 14:26:57 DP: If they use the schema as we described, it would be difficult for them to handle it, probably. 14:30:01 DP: Do they use JSON or XML? 14:30:07 CB: They read JSON. 14:30:25 CB: Converts JSON to XML tree. 14:32:03 DP: What if they read EXI-encoded JSON? 14:34:18 DP: If they go through plain text JSON, then they will never encounter that. 14:37:35 DP: Let's first focus on their current use case because new use cases have potential but maybe confusing for them. 14:38:39 TOPIC: Comments: Canonical EXI -- Last Call Working Draft 14:44:18 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. 14:46:32 DP: We need to provide some kind of identifier for general use cases. 14:51:55 https://www.w3.org/XML/Group/EXI/docs/canonical/canonical-exi.html#N67698 14:53:12 DP: We don't say it must be done that way right now. 14:53:40 DP: We ought to define it properly now. 14:54:36 DP: With/without options, header options, schemaId and datetime normalization. 14:57:46 DP: It is good to specify it in our spec. 14:59:32 DP: I would state that the safest is to use datetime normalization and use of header options as default. 15:01:23 DP: I can propose it to the mailing list. 15:02:05 TK: I think it is good that way. 15:03:08 ACTION: DP to propose how to differentiate canonicalization variations and which variation is the default 15:03:08 Created ACTION-726 - Propose how to differentiate canonicalization variations and which variation is the default [on Daniel Peintner - due 2015-10-20]. 15:03:19 1. http://www.w3.org/TR/exi-c14n (default with EXI Option, with schemaId, with dateTime normalization) 15:03:25 2. http://www.w3.org/TR/exi-c14n#WithoutEXIOptions 15:03:31 3. http://www.w3.org/TR/exi-c14n#WithoutSchemaId 15:03:38 4. http://www.w3.org/TR/exi-c14n#WithoutEXIOptionsWithoutDatetimeNormalization 15:03:44 5. http://www.w3.org/TR/exi-c14n#WithoutSchemaIdWithoutDatetimeNormalization 15:05:31 6. http://www.w3.org/TR/exi-c14n#WithoutDatetimeNormalization 15:08:34 TOPIC: Support for Canonical EXI interoperability test in TTFMS 15:09:39 DP: Preservation of whitespaces. 15:10:04 DP: Respect whitespaces or not. 15:10:26 DP: xs:anySimpleType, we need to define how to encode data. 15:10:39 DP: Same applies to schema-less case. 15:16:58 DP: Before, I was trimming whitespaces. 15:19:34 DP: We need to define how to remove or preserve whitespaces. 15:36:00 http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace 15:36:50 "preserve No normalization is done, the value is not changed (this is the behavior required by [XML 1.0 (Second Edition)] for element content) " 15:42:28 ACTION: TK to share the whitespace removal rule used in compaction measurement 15:42:29 Created ACTION-727 - Share the whitespace removal rule used in compaction measurement [on Takuki Kamiya - due 2015-10-20]. 16:07:44 rrsagent, create minutes 16:07:44 I have made the request to generate http://www.w3.org/2015/10/13-exi-minutes.html taki 16:33:23 Zakim has left #exi 16:41:02 taki has left #exi