15:01:48 RRSAgent has joined #exi 15:01:48 logging to http://www.w3.org/2016/02/02-exi-irc 15:01:50 RRSAgent, make logs public 15:01:50 Zakim has joined #exi 15:01:52 Zakim, this will be EXIWG 15:01:52 I do not see a conference matching that name scheduled within the next hour, trackbot 15:01:53 Meeting: Efficient XML Interchange Working Group Teleconference 15:01:53 Date: 02 February 2016 15:03:53 dape has joined #exi 15:09:04 scribe: TK 15:09:12 scribeNick: taki 15:10:49 CB: We have published EXI for JSON draft on Thursday. 15:11:35 CB: XML spec currently used is outdated. 15:11:52 DP: I noticed HTML looked different. 15:12:07 DP: The one I generated was different. 15:12:43 CB: I directly fixed. Processed version was missing. 15:12:54 www.w3.org/2007/10/htmldiff?doc1=http://www.w3.org/TR/exi-for-json/&doc2=https://www.w3.org/XML/EXI/docs/json/exi-for-json.html 15:13:48 CB: If you update xmlspec, it would be a better solution. 15:16:17 CB: I did not change XSL. 15:17:09 DP: xmlns in the example somehow uses "https". 15:17:28 https://www.w3.org/2015/EXI/json 15:17:59 DP: Validator failed because it was expecting "http". 15:18:34 https://www.w3.org/TR/2016/WD-exi-for-json-20160128/schema-for-json.xsd 15:19:38 CB: We have inconsistency. 15:20:27 brutzman has joined #exi 15:22:57 xmlns:xs="https://www.w3.org/2001/XMLSchema" 15:23:03 targetNamespace="https://www.w3.org/2015/EXI/json" 15:28:45 ACTION: DP to modify XML Schema contained in appendix B to use "http" instead of "https". 15:28:46 Created ACTION-734 - Modify xml schema contained in appendix b to use "http" instead of "https". [on Daniel Peintner - due 2016-02-09]. 15:29:23 DB: target namespace is URL. it is ok to use "http". 15:29:58 DP: For processors the two are different, and it failed. 15:31:35 DB: "http" is directed to "https" when I typed in the browser. 15:31:43 CB: Server does that. 15:32:15 DB: If you use browser that doesn't support https, it would use http. 15:33:12 DB: Dumb client would use http, then? 15:33:18 CB: Correct. 15:33:36 thank you for explaining that dumb clients will not get negotiated and not be redirected 15:34:27 DP: It is safer to use plain. 15:34:40 s/plain/plain http/ 15:37:26 TOPIC: EXI for JSON structure 15:39:26 TK: experimented with EXI for JSON 15:39:46 ... idea was to play with XML schema support 15:40:12 ... Don also found issue with JSON syntax. Thanks! 15:40:39 ... found difficulties to create XSD for EXI for JSON content 15:41:34 ... e.g., link is a map with two optional key/value pairs 15:42:05 ... XML structure uses "key" attribute for JSON key 15:42:52 ... EXI grammar generation has issue resolving that (see proto grammar) 15:43:20 ... propose to use different way to specificy name 15:43:56 ... proposal is that name becomes attribute name itself.. with empty string 15:44:18 .. Boss becomes Boss 15:46:01 ... schema has ambiguity ... two times "string" element 15:46:24 DP: "old" cos-ambiguity issue with XSD? 15:46:55 TK: Correct. issue for XSD processors, .. however no issue for EXI grammar generation rules 15:47:26 Link to email on this topic: EXI for JSON structure, https://lists.w3.org/Archives/Public/public-exi/2016Feb/0000.html 15:48:11 DP: I didn't have time to look closely at this. I will take a look. 15:48:18 Request: for comparison, might someone post the expected conversion of that JSON snippet to EXI XML on the mail list? 15:49:11 DP: On the other hand, it will be a different approach from others are taking, such as XQuery and others. 15:52:43 DP showing the differences..... 15:55:47 DB: The new structure may cause some issues in making XPath query. 15:59:28 DP: We need to solve an issue of creating a dedicated schema. 15:59:42 A merit of the current schema is that all of the JSON keys and JSON key values can be directly referenced in XPath expressions. An XSLT program (or other XPath query) can iterate over all of the key="someUniqueFieldName" attributes. 15:59:54 DP: I also have an alternative idea, and will try if it would work or not. 16:03:02 A significant problem in the suggested alternative is that no key attribute can be directly accessed or iterated over. Each key attribute name has to be discovered before the corresponding value can be accessed. This greatly complicates document parsing. 16:04:44 Please explain "issue of creating a dedicated schema" ? The working-draft EXI for JSON schema would seem to be able represent any JSON document. 16:05:36 DP: Don, if you are aware of another way to help solving this issue, that would also help. 16:06:47 Restatement: am not sure what problem we are trying to fix. If we can represent any JSON structure in the provided XML encoding, then EXI can compress it, correct? 16:07:34 DP: EXI for JSON currently uses generic schema. It currently does not provide a way to use specific schemas. 16:08:43 DP: There is nothing wrong in the current spec. 16:09:02 If the motivation is to confirm the validity of a JSON object, then jslint and jshint can be used. If the motivation is to confirm the content-validity of a JSON structure, then a JSON Schema might be used. 16:09:29 DP: We did discuss in the past that we should provide a way to describe specific structure. 16:10:00 DB: jslint validates JSON syntax. 16:10:16 These two approaches are analagous to well-formed XML, and to schema-valid XML, respectively. 16:10:30 s/These/Yes, these/ 16:12:08 Further information about JSON Schema can be found at http://json-schema.org 16:13:56 Latest JSON Schema is RFC draft https://tools.ietf.org/html/draft-zyp-json-schema-04, expired 4 August 2013. 16:15:30 Incidentally, I haven't found information about whether JSON Schema work remains active or will resume... disappointing that status isn't clear on the website. 16:17:11 The motivation is clearer - thanks for the explanation. Not sure if I see a problem. If the goal is deeper validation, then "let JSON be JSON" and use JSON tools to validate a given structure. 16:17:35 DP: Generic schema is very generic. 16:18:06 DP: Currently, we do not provide as good compaction as EXI does not XML. 16:18:16 s/not/for/ 16:18:47 Curious side effect: since JSON Schemas are themselves written in JSON, those can also be expressed as EXI XML. That is sort of like second-order abstractions however, probably not very practical or useful. 16:19:41 DB: It is a merit to use generic schema for EXI for JSON. 16:20:31 DP: However, it does not know about specifics, for example "family" in this specific case. 16:20:48 The general nature of XML Schema for EXI JSON seems to be a significant merit. It is able to express any arbitrary JSON structure, and then take advantage of a primary strength of EXI: type-aware data compression. 16:21:55 Conceivably the motivators we are discussing are building the case for establishing a more comprehensive mapping between JSON structures and content-specific XML Schemas. 16:25:03 Some months ago we discussed possible general mapping of structured JSON content to a correspondingly structured XML Schema. 16:25:14 DP: I think we need to be careful because the old way allowed more compact implementation because it only needs to be aware of "key" attribute. 16:25:48 We have had to work through a number of issues in the X3D Encoding for JSON. http://www.web3d.org/x3d/stylesheets/X3dToJson.html 16:27:04 There are some fundamental gaps in data models: a strict object-oriented JSON approach is different than a more flexible XML document approach, even when PSVI limits are accepted. 16:28:14 I think we made the right choice with EXI for JSON, your approach looks great. Let's keep testing... a more general approach is conceivable but it is definitely future work and would need much more effort. 16:30:28 In the case of X3D JSON, we found a number of data-modeling issues where well-defined and valid .x3d XML documents were not directly expressible as JSON. Thus we made some adaptations and tradeoffs, 100% round-trip conversions remained out of reach. 16:31:40 We have probably gotten to ~95% bidirectional mappings between the XML data model and the JSON object model. Other XML schemas may have further issues that we didn't have to address. 16:32:13 http://www.web3d.org/x3d/stylesheets/X3dToJson.html#Issues 17:12:21 rrsagent, create minutes 17:12:21 I have made the request to generate http://www.w3.org/2016/02/02-exi-minutes.html taki 17:19:34 Zakim has left #exi