See also: IRC log
<scribe> scribe: TK
<scribe> scribeNick: taki
DP: Decimal support is marked as
at risk.
... We will be able to remove it safely later.
... Appendix now talks about design decisions.
... I got comments from DB. I already implemented most of
them.
DP: JSON-LD supports certain
keywords. It is an additional item we started to discuss at
TPAC.
... It is also more general topic.
... Options we define in our documents. "strict" and
"schemaId".
... I would stick with current schema ID. In the next version,
we can add "-2" or something to indicate version.
... Steven Williams suggested us to use BSON as well.
... I am not BSON expert, but I know it is a binary
format.
... "strict" is required because unknown elements are not
convenient for EXI to JSON conversion.
... By requiring strict, implementation can be simpler.
JF: Appendix talks about
implementation.
... Appendix has schema.
DP: Appendix B is schema. section
3 discuss conversion rules.
... DP showing exificient implementation online...
JF: My first impression was this was about conversion.
TK: I think we can describe the reason why we require "strict" in design decision.
CB: We can publish as a Note, or
can publish it saying it will be revised.
... Note in general means final.
... Drafts invite comments much more than Notes.
DP: Liam suggested we first
publish draft or note. In the future, we can work on making it
REC.
... Currently, we have schema in the document. I want to make
the schema available separately.
CB: We can make a copy somewhere,
that's ok.
... Schema doesn't have to be normative since it is for
draft.
<caribou> once published https://www.w3.org/TR/exi-for-json
DP: I want to have the document and schema consistent.
<dape> https://www.w3.org/TR/exi-for-json/schema-for-json.xsd
<caribou> www.w3.org/2016/exi-for-json-schema.xsd
CB: We need to describe in the
draft that we have another place that manages latest
schema.
... The schema and document need to be modified at the same
time.
DP: Can Carine check and modify SOTD?
CB: Yes, I will do that.
DP: Latest draft mentions both
approaches.
... I am fine with going ahead with approach B.
TK: The group decided to choose approach B for how to represent empty elements.
DP: I will update the document accordingly.
DP: Section 4.2.5 describes whitespace handling rules.
TK: I will review that section.
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) Found Scribe: TK Found ScribeNick: taki Present: DP TK CB JavierF WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 12 Jan 2016 Guessing minutes URL: http://www.w3.org/2016/01/12-exi-minutes.html People with action items:[End of scribe.perl diagnostic output]