Efficient XML Interchange Working Group Teleconference

16 Aug 2016

See also: IRC log




<scribe> scribe: TK

<scribe> scribeNick: taki


RE: abbreviation for "EXI for JSON"?

DP: I am not sure if we should replace all occurrences of "EXI for JSON" with EXI4JSON.

DB: It has a benefit of becoming more searchable.

DP: In introduction, I can use EXI4JSON as an abbreviation.

<dape> Efficient XML Interchange (EXI) for JSON --> Efficient XML Interchange (EXI) for JSON (EXI4JSON)

TK: Can we also mention in the title as well?

<brutzman> Looks good. I think EXI4JSON should be used as often as possible because it aids in searchability.

<caribou> EXI for JSON (EXI4JSON) is a reasonable title

<brutzman> Searching to find "EXI for JSON" would likely find the initial entry as well

CB: I don't see need for replacing all occurrences of EXI for JSON.
... Especially, in text descriptions.

DP: We can define them as synonym in title. We can mix the usage whereever appropriate.

Comments on EXI4JSON

DP: We describe both processing steps.
... JSON to EXI, and EXI back to JSON.
... I would totally replace section 3.2.

DB: If section 3.1 describes the equivalences in representation, section 3.2 is not necessary?

<brutzman> Attempted summary: section 3.2 is no longer necessary if section 3.1 describes equivalences between representations?

DP: That is also now my understanding.

DB: Instead of "transform", you would use...

DP: "represent" or something

<brutzman> Example changes in 3.1: "transforms" becomes "value is equivalent to"

DP: and needs some text replacements, such as "transformed" with "represented".

DB: "equivalent representation for" is also good.

<brutzman> A similar expression might be "is an equivalent representation for" - but that might look too wordy. Whatever works.

DP: For the schema, I think we should keep the schema file.

<dape> https://www.w3.org/2001/XMLSchema.xsd

<brutzman> wondering, to avoid potential ambiguity, can we rename appendix "B Schema for JSON" to "B EXI Schema for JSON"

<taki1> CB: Schema for schema is not in TR space.

<taki1> CB: So you can still fix the schema.

<brutzman> Similarly we should rename schema to avoid ambiguity, exi-schema-for-json.xsd or somesuch

<brutzman> Motivation is search: if someone looks up "JSON Schema" they should realize this is different

<caribou> schema for EXI4JSON

<dape> https://www.w3.org/TR/exi/#optionsSchema --- Title is "C XML Schema for EXI Options Document"

<brutzman> exi4json.xsd perhaps

<taki1> DP: EXI spec says "XML schema for EXI options document"

<taki1> DB: For consistency, we should say "XML Schema for EXI4JSON"

<taki1> DP: The name of the file remains as it is.

<taki1> DP: The name should be schema-for-exi4json.xsd?

<taki1> TK: exi4json.xsd is also ok for me.

<taki1> DP: Where should we put it?

<taki1> CB: If you put it in TR space, it will be updated in place.

<taki1> CB: I would put it next to the specification in TR space for now.

<taki1> CB: It depends on how stable the schema the WG thinks.

<brutzman> just posted to member-exi, can we look at a wording suggestion? (i only have a few minutes left) https://lists.w3.org/Archives/Member/member-exi-wg/2016Aug/0024.html

<taki1> CB: We will have a new URI for the next publication.

<brutzman> i think the schema is stable and is unlikely to change functionally

<taki1> CB: Are we use a link to this document? Probably not, right?

<taki1> CB: We use it in appendix using relative URI. So this is ok.

<caribou> http://www.w3.org/TR/2016/WD-exi-for-json-20160128/

<taki1> CB: Schema will be still accessible.

<brutzman> hopefull the more precise wording in the 0024.html suggestion will prevent someone from thinking "oh they already have a schema-aware mapping customization from JSON schemas to customized XML schemas"

<brutzman> am supportive of publishing for comment, thanks for continuing diligence

<taki1> CB: I think we can remove the part that talks about general mapping from section 2. Concept.

<taki1> CB: Because the current first paragraph precisely describes what we do.

<taki1> TK: I agree.

<taki1> DP: For the acknowledgement section, we need the names of supporters.

RESOLUTION: The WG agrees that we publish EXI4JSON after reflecting the changes we discussed during this call.

Canonical EXI

<taki1> DP: For issue ISSUE-95, I tried to incorporate the changes.

<dape> https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#canonicalOptionsSchema

<taki1> DP: We want to import EXI options document schema.

<taki1> DP: However, the schema file is not available online.

<taki1> CB: We can add a schema.

<dape> https://www.w3.org/2009/exi/schema-name.xsd

<caribou> https://www.w3.org/2009/exi/options.xsd

Summary of Action Items

Summary of Resolutions

  1. The WG agrees that we publish EXI4JSON after reflecting the changes we discussed during this call.
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/08/16 15:31:38 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/initial entry/initial entry as well/
Found Scribe: TK
Found ScribeNick: taki
Present: TK DP DB CB

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

Found Date: 16 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/16-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]