17:41:09 <RRSAgent> RRSAgent has joined #exi
17:41:09 <RRSAgent> logging to http://www.w3.org/2016/10/18-exi-irc
17:41:11 <trackbot> RRSAgent, make logs public
17:41:11 <Zakim> Zakim has joined #exi
17:41:13 <trackbot> Zakim, this will be EXIWG
17:41:13 <Zakim> ok, trackbot
17:41:14 <trackbot> Meeting: Efficient XML Interchange Working Group Teleconference
17:41:14 <trackbot> Date: 18 October 2016
17:41:16 <taki> zakim, this is exi
17:41:16 <Zakim> got it, taki
17:41:36 <taki> TOPIC: Canonical EXI
17:42:04 <taki> DP: I can create a section describing substative changes since last call.
17:44:40 <taki> TOPIC: EXI Renaming
17:44:54 <taki> DP: It makes sense to me.
17:45:07 <taki> DP: Should we wait for more review?
17:45:35 <taki> TK
17:47:17 <taki> DP: I plan to announce JavaScript effort after the EXI renaming plan announcement.
17:48:24 <taki> TK: I can send the announcement out to public if there are no other comments by the end of Friday.
17:50:03 <taki> TOPIC: EXI for CSS - Slides
17:50:18 <taki> DP: I integrated comments from Liam and Don.
17:50:51 <taki> DP: Except for the parts about security.
17:56:10 <taki> DP: I will ask Carine and Liam if we can ask for a slot in CSS WG telecon around the beginning of November.
17:56:37 <taki> DP: for around 15 minutes time slot.
18:02:50 <taki> DP: Java8 has JavaScript API.
18:02:59 <taki> DP: Java9 makes that API public.
18:04:24 <brutzman> brutzman has joined #exi
18:04:54 <brutzman> hi folks.  telcon information advertised on member page isn't working for me...
18:13:54 <brutzman> Comment on renaming: capitalize as Efficient Extensible Interchange (EXI) , to match Extensible Markup Language (XML)
18:15:11 <brutzman> Reference: http://www.w3.org/XML
18:16:36 <brutzman> clearly we want the message ad usage to be "it's the same as XML"
18:16:57 <brutzman> ... and certainly not "it's different than XML"
18:17:10 <brutzman> s/ad/and/
18:21:31 <taki> TOPIC: Extended String
18:22:46 <taki> DP: Xerces does not provide API to access foreign attributes.
18:23:17 <taki> DP: Do we have any preferred way to express prepopulated string?
18:23:37 <taki> DP: As an attribute value?
18:23:45 <taki> DP: Or as enumerations?
18:33:14 <n8s> n8s has joined #exi
18:38:12 <taki> DP: We would like to group prepopulated values.
18:39:42 <taki> TK: Prepopulated values are associated with a simple type.
18:44:21 <taki> DP: I was more thinking that with prepopulated strings, we can prepopolate string table.
18:49:13 <brutzman> Just replied on mailing list with a perhaps-related example of annotations
18:49:36 <brutzman> Re: AW: AW: Annotation on Simple datatype definition; X3D schema annotation examples
18:49:54 <brutzman> https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0029.html
18:51:16 <brutzman> in essence we decorated the XML schema to have the functionality of Interface Definition Language (IDL) for documenting eventIn and eventOut (transient) interfaces that are not present in the XML document itself
18:52:06 <brutzman> corrected link for X3D Schema documentation http://www.web3d.org/specifications/X3dSchemaDocumentation3.3.html
18:55:12 <brutzman> by "decorate" am referring to Decorator pattern https://en.wikipedia.org/wiki/Decorator_pattern
18:57:33 <brutzman> another example http://www.web3d.org/specifications/X3dSchemaDocumentation3.3/x3d-3.3_ComposedCubeMapTexture.html#Link8F
19:00:33 <brutzman> in other words, we adapted annotation/appinfo and other schema constructs to express additional information in a schema-structured way.
19:01:13 <brutzman> avoiding namespace prefixes seems like a good practice so that native XML Schema tools can be used without strangeness emerging.
19:01:47 <brutzman> suggestion: try to use native XML Schema constructs, you can go quite far with them.
19:04:03 <brutzman> backtrack: LQ message asked "(5) did the exi experiment use a schema with all of the CSS property names?"
19:04:46 <brutzman> DP: answer is no, because that has to align with a given CSS encoding
19:05:24 <brutzman> this is an important point... your approach seems quite correct, in general case.
19:06:02 <brutzman> nevertheless we could create an EXI4CSS schema that included all of the HTML5 built-in CSS properties as enumerations...
19:06:52 <brutzman> ... which in turn would create a version-dependent string table, that might show significant compression and speedup advantages.
19:07:49 <brutzman> for the facebook use case (that we recently examined), this alternative approach might be quite preferable.  it is also sharable/reusable for distributed benefit.
19:09:35 <brutzman> looking at CSS to see how they do versions: https://www.w3.org/Style/CSS/
19:11:15 <brutzman> so we might craft an XML scema for EXI something like EXI4CSS-HTML5-CSS2016Snapshot.xsd or somesuch
19:13:54 <brutzman> am presenting on "X3D Graphics and VR" at W3C Workshop on Web and VR this week in San Jose CA USA
19:14:19 <brutzman> please look at slideset pdf: http://www.web3d.org/presentations/2016-10/x3d-graphics-and-vr
19:14:54 <brutzman> then slide 11 for OWP including EXI
19:17:28 <taki> rrsagent, create minutes
19:17:28 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/18-exi-minutes.html taki
19:18:53 <brutzman> NY Times: Stepping Up Security for an Internet-of-Things World, by Steve Lohr, 16 OCT 2016
19:19:14 <brutzman> http://www.nytimes.com/2016/10/17/technology/security-internet.html
19:21:05 <n8s> n8s has joined #exi
20:02:47 <Zakim> Zakim has left #exi
20:33:28 <n8s> n8s has joined #exi
22:48:30 <n8s> n8s has joined #exi
23:52:32 <n8s> n8s has joined #exi
23:54:59 <n8s_> n8s_ has joined #exi