See also: IRC log
DB: I added an entry to EXI Deploypemt page.
https://www.w3.org/XML/EXI/wiki/EXIDeployment
DB: I also added some context,
too.
... We have code base in the main page.
DP: We do not have platforms or applications that use EXI on public page.
<brutzman> Implementations are listed on EXI working group page, the next section would be for applications that support EXI
DP: I am not sure what we should do for those.
<brutzman> interestingly we might expect that an application list might be short at first, then hopefully really long over time!
DB: Application list may get long over time.
<brutzman> DP people might not tell us about their applications
DP: People do not usually tell that their application uses EXI.
<brutzman> we might add links there to notify us, and (DP) to join the group
DB: We have one application of X3D-edit.
DP: I know at least one
database.
... Let's keep the list in EXI Deployment page, and have a link
from the public list.
<brutzman> added a link to X3D-Edit and the Working Group page there
<brutzman> suggestions for EXI working group page https://www.w3.org/XML/Group/EXI/
<brutzman> - put (EXI) in title
<brutzman> - put link to public page near top
<brutzman> oops, just didn't see it at first: http://www.w3.org/XML/EXI
<brutzman> hmmm, maybe use numbers instead of bullets to show adoption?
<brutzman> hi Taki, are you with us?
https://en.wikipedia.org/wiki/Efficient_XML_Interchange
<brutzman_> please see binary XML link https://en.wikipedia.org/wiki/Binary_XML
<brutzman_> see bullet "Efficient XML from AgileDelta, Inc., selected as the basis for the W3C Standard for Binary XML (EXI)"
<brutzman_> how about i flip that around to put EXI first, and ensure both are linked
<brutzman_> s/anyhoy/anyhow/
DP: OpenEXI results in an error.
I reported to TK.
... OpenEXI outputs an empty schemaId.
<dape> https://en.wikipedia.org/wiki/Comparison_of_data_serialization_formats
<dape> https://www.w3.org/TR/exi/#key-schemaIdOption
DP: Do we want to say anything about schemaId?
TK: We now allow both Header Options and schemaId absent.
DP: We need an additional configuration flag.
TK: I think so.
... I will send to the public list about the need for an
additional flag controlling schemaId.
DP: It looks like
omitOptionsDocument and header are conflicting.
... We can put a choice between omitOptionsDocument and header
in Canonical EXI Options Document schema.
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/W3D/X3D-edit/ Succeeded: s/aout/about/ FAILED: s/anyhoy/anyhow/ WARNING: No "Present: ... " found! You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy <amy> Present+ No ScribeNick specified. Guessing ScribeNick: taki Inferring Scribes: taki WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 21 Mar 2017 Guessing minutes URL: http://www.w3.org/2017/03/21-exi-minutes.html People with action items:[End of scribe.perl diagnostic output]