Efficient XML Interchange Working Group Teleconference

18 Oct 2016

See also: IRC log




Canonical EXI

<taki> DP: I can create a section describing substative changes since last call.

EXI Renaming

<taki> DP: It makes sense to me.

<taki> DP: Should we wait for more review?

<taki> TK

<taki> DP: I plan to announce JavaScript effort after the EXI renaming plan announcement.

<taki> TK: I can send the announcement out to public if there are no other comments by the end of Friday.

EXI for CSS - Slides

<taki> DP: I integrated comments from Liam and Don.

<taki> DP: Except for the parts about security.

<taki> DP: I will ask Carine and Liam if we can ask for a slot in CSS WG telecon around the beginning of November.

<taki> DP: for around 15 minutes time slot.

<taki> DP: Java8 has JavaScript API.

<taki> DP: Java9 makes that API public.

hi folks. telcon information advertised on member page isn't working for me...

Comment on renaming: capitalize as Efficient Extensible Interchange (EXI) , to match Extensible Markup Language (XML)

Reference: http://www.w3.org/XML

clearly we want the message and usage to be "it's the same as XML"

scribe: and certainly not "it's different than XML"

Extended String

<taki> DP: Xerces does not provide API to access foreign attributes.

<taki> DP: Do we have any preferred way to express prepopulated string?

<taki> DP: As an attribute value?

<taki> DP: Or as enumerations?

<taki> DP: We would like to group prepopulated values.

<taki> TK: Prepopulated values are associated with a simple type.

<taki> DP: I was more thinking that with prepopulated strings, we can prepopolate string table.

Just replied on mailing list with a perhaps-related example of annotations

Re: AW: AW: Annotation on Simple datatype definition; X3D schema annotation examples


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

corrected link for X3D Schema documentation http://www.web3d.org/specifications/X3dSchemaDocumentation3.3.html

by "decorate" am referring to Decorator pattern https://en.wikipedia.org/wiki/Decorator_pattern

another example http://www.web3d.org/specifications/X3dSchemaDocumentation3.3/x3d-3.3_ComposedCubeMapTexture.html#Link8F

in other words, we adapted annotation/appinfo and other schema constructs to express additional information in a schema-structured way.

avoiding namespace prefixes seems like a good practice so that native XML Schema tools can be used without strangeness emerging.

suggestion: try to use native XML Schema constructs, you can go quite far with them.

backtrack: LQ message asked "(5) did the exi experiment use a schema with all of the CSS property names?"

DP: answer is no, because that has to align with a given CSS encoding

this is an important point... your approach seems quite correct, in general case.

nevertheless we could create an EXI4CSS schema that included all of the HTML5 built-in CSS properties as enumerations...

scribe: which in turn would create a version-dependent string table, that might show significant compression and speedup advantages.

for the facebook use case (that we recently examined), this alternative approach might be quite preferable. it is also sharable/reusable for distributed benefit.

looking at CSS to see how they do versions: https://www.w3.org/Style/CSS/

so we might craft an XML scema for EXI something like EXI4CSS-HTML5-CSS2016Snapshot.xsd or somesuch

am presenting on "X3D Graphics and VR" at W3C Workshop on Web and VR this week in San Jose CA USA

please look at slideset pdf: http://www.web3d.org/presentations/2016-10/x3d-graphics-and-vr

then slide 11 for OWP including EXI

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/10/18 19:17:33 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/ad/and/
No ScribeNick specified.  Guessing ScribeNick: brutzman
Inferring Scribes: brutzman

WARNING: No "Present: ... " found!
Possibly Present: DP Reference TK backtrack exi https joined n8s suggestion taki trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

        <amy> Present+

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 18 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/18-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]