15:01:14 <RRSAgent> RRSAgent has joined #exi
15:01:14 <RRSAgent> logging to http://www.w3.org/2015/11/17-exi-irc
15:01:16 <trackbot> RRSAgent, make logs public
15:01:16 <Zakim> Zakim has joined #exi
15:01:18 <trackbot> Zakim, this will be EXIWG
15:01:18 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
15:01:19 <trackbot> Meeting: Efficient XML Interchange Working Group Teleconference
15:01:19 <trackbot> Date: 17 November 2015
15:01:34 <dape> dape has joined #exi
15:04:52 <taki> Scribe: TK
15:04:55 <taki> ScribeNick: taki
15:04:57 <taki> TOPIC: W3C Notes in public?
15:05:32 <taki> DP: I think there are multiple possibilities.
15:05:54 <taki> DP: Just create a public folder, e.g. docs, where we put public specs.
15:06:21 <taki> DP: To move the entire folder to public space, this is another idea.
15:06:35 <taki> DP: Now we are supposed to be public.
15:07:45 <taki> CB: We can create docs directory in public.
15:08:24 <taki> DP: For new documents, OK. What about existing docs, such as canonical EXI? We copy it to public space?
15:08:30 <taki> CB: Yes.
15:09:21 <taki> CB: We can also put link to editor's draft in published spec next time we publish.
15:09:35 <taki> DP: How do we do that?
15:10:29 <taki> CB: Under TR directory, there are many links to github.
15:11:14 <taki> CB: Since we use tracker, transition to github may be an overkill.
15:11:39 <taki> DP: OK. Then I can create docs directory, and move documents, right?
15:11:42 <taki> CB: Yes
15:12:53 <taki> ACTION: DP to move three documents (Canonical EXI, extended String, JSON support) to public space.
15:12:54 <trackbot> Created ACTION-731 - Move three documents (canonical exi, extended string, json support) to public space. [on Daniel Peintner - due 2015-11-24].
15:14:28 <taki> CB: New groups are using "re-spec".
15:14:50 <taki> CB: and using github issues instread of tracker.
15:15:29 <taki> DP: Do you suggest to use it?
15:15:58 <taki> CB: Since we are used to XML-based spec, we should continue to use it.
15:16:07 <taki> CB: CVS won't go away for now.
15:16:34 <taki> CB: It is quite well maintained.
15:17:45 <taki> CB: Stylesheet in "format" directory may be outdated.
15:19:29 <taki> TOPIC: JSON support
15:19:54 <taki> DP: We started to modify the schema. We took it over from XQuery/XSLT WG in a sense.
15:20:06 <dape> https://www.w3.org/XML/Group/EXI/docs/json/exi-for-json.html#schema-for-json
15:20:09 <taki> DP: I removed constructs that we do not need.
15:20:48 <taki> DP: I added datatypes.
15:21:03 <brutzman> brutzman has joined #exi
15:22:36 <taki> DP: I will move this document to public space.
15:27:07 <brutzman> curious regarding the JSON reference, isn't ECMA version authoritative?
15:27:26 <brutzman> JSON Data Interchange Format, ECMA Standard ECMA-404, first edition, October 2013. http://www.ecma-international.org/publications/standards/Ecma-404.htm
15:27:34 <taki> DP: Array, Object, Value, Null, are now all global.
15:28:35 <taki> DP: We currently reference RFC. There is also ECMA standard.
15:29:45 <taki> DB: It is interesting in that RFC is more recent. I will try to investigate which one should be more appropriate to reference to.
15:30:04 <taki> DB: Wikipedia refers to both RFC and ECMA.
15:30:16 <taki> s/DB/DP/
15:31:51 <dape> https://en.wikipedia.org/wiki/JSON
15:31:51 <taki> DP: From the point of view of syntax, it should be the same.
15:32:27 <caribou> RFC 7159
15:32:28 <caribou> IETF. The JavaScript Object Notation (JSON) Data Interchange Format. March 2014. See http://www.ietf.org/rfc/rfc7159.txt
15:32:44 <caribou> we usually use the IETF one
15:33:11 <taki> CB: The link to RFC is the one used in XSLT.
15:33:47 <caribou> it's more recent than the ECMA 404
15:34:56 <taki> ACTION: DB to investigate whether ECMA's JSON spec is more appropriate to make a reference to or not.
15:34:56 <trackbot> Created ACTION-732 - Investigate whether ecma's json spec is more appropriate to make a reference to or not. [on Don Brutzman - due 2015-11-24].
15:35:57 <caribou> <<1.2.  Specifications of JSON
15:35:57 <caribou>    This document updates [RFC4627], which describes JSON and registers
15:35:57 <caribou>    the media type "application/json".
15:35:57 <caribou>    A description of JSON in ECMAScript terms appears in Version 5.1 of
15:35:58 <caribou>    the ECMAScript specification [ECMA-262], Section 15.12.  JSON is also
15:35:58 <caribou>    described in [ECMA-404].
15:35:58 <caribou>    All of the specifications of JSON syntax agree on the syntactic
15:35:59 <caribou>    elements of the language.>>
15:36:11 <caribou> (quote from the IETF RFC 7159)
15:36:27 <taki> DP: I just created the document. I can do some work. I wonder whether there are other people who can support the work.
15:36:56 <taki> DB: I can certainly help on that.
15:40:26 <taki> DB: RFC on JSON security is still developing.
15:41:11 <brutzman> Curious/recent pain point with JSON encoding: apparently inclusion of newline and tab characters in a JSON string is not allowed, they must be escaped as \n and \t.
15:44:42 <brutzman> Recent discussion by X3D working group: http://web3d.org/pipermail/x3d-public_web3d.org/2015-November/003803.html
15:47:22 <taki> DP: If someone wants to link to our document, we may want to have real publication once our document becomes more stable.
15:49:02 <taki> TOPIC: Canonical EXI
15:50:29 <taki> TOPIC: Support for Canonical EXI interoperability test in TTFMS
15:52:59 <taki> DP: For datatypes, enumeration with "" is also good.
15:55:29 <brutzman> ... regarding JSON references, they are now included in Action 732
15:55:31 <brutzman> https://www.w3.org/2005/06/tracker/exi/actions/732
16:01:52 <caribou> bye
16:03:15 <brutzman> bye, thanks
16:13:36 <taki> DP: I will try to write both intention and the detailed rule in the document.
16:14:02 <taki> TOPIC: Whitespace handling in TTFMS
16:14:58 <taki> DP: I have some debugging tool, and found whitespace preservation, namespace declarations.
16:18:48 <taki> DP: xml:space is preserve, all whitespaces need to be preserved, right?
16:20:23 <taki> ISSUE: What to do with xml:space being preserved in strict mode.
16:20:23 <trackbot> Created ISSUE-110 - What to do with xml:space being preserved in strict mode..  Please complete additional details at <https://www.w3.org/2005/06/tracker/exi/issues/110/edit>.
16:21:32 <dape> https://www.w3.org/2005/06/tracker/exi/issues/107
16:23:52 <taki> DP: Issue 107 is related. Since infoset can have multiple CH one after another.
16:40:58 <taki> rrsagent, create minutes
16:40:58 <RRSAgent> I have made the request to generate http://www.w3.org/2015/11/17-exi-minutes.html taki
16:48:12 <taki> taki has left #exi
17:29:02 <Zakim> Zakim has left #exi
19:45:18 <liam> liam has joined #exi
19:54:01 <liam> liam has joined #exi