ISSUE-1 |
CLOSED |
How do we handle outreach about Efficient XML? |
2006-01-05 |
All |
0 |
| ISSUE-2 |
CLOSED |
Test issue - please ignore |
2006-01-17 |
All |
0 |
| ISSUE-3 |
CLOSED |
XBC Characterizations document SVG chart displays poorly in Firefox 1.5 |
2006-01-31 |
XBC Errata |
0 |
| ISSUE-4 |
CLOSED |
Testing platform |
2006-03-03 |
All |
0 |
| ISSUE-5 |
CLOSED |
Existing XML parsers for test framework use, comparison |
2006-03-03 |
All |
0 |
| ISSUE-6 |
CLOSED |
Use of W3C Software License |
2006-03-15 |
All |
0 |
| ISSUE-7 |
CLOSED |
Organization of TTF directory |
2006-03-15 |
All |
0 |
| ISSUE-8 |
CLOSED |
Linking test data to associated schemas |
2006-03-15 |
All |
0 |
| ISSUE-9 |
CLOSED |
What is our definition of |
2006-03-22 |
All |
0 |
| ISSUE-10 |
CLOSED |
Do we have test coverage for DTDs, Entities, and Notations? |
2006-03-22 |
All |
0 |
| ISSUE-11 |
CLOSED |
Are we doing the right thing with the C infrastructure |
2006-03-30 |
All |
0 |
| ISSUE-12 |
CLOSED |
Need to determine if processing efficiency drivers are properly addressing caching issues |
2006-03-30 |
All |
0 |
| ISSUE-13 |
CLOSED |
Measurements Note issue: Confirm measurements points line up with format implementations. |
2006-04-12 |
All |
0 |
| ISSUE-14 |
CLOSED |
Measurements Note issue: Are we definitely going to create schema for all test files which don\'t have one? |
2006-04-12 |
All |
0 |
| ISSUE-15 |
CLOSED |
Measurements Note issue: Are we definitely going to measure encode and decode separately? |
2006-04-12 |
All |
0 |
| ISSUE-16 |
CLOSED |
Measurements Note issue: What should be the figures of merit for Compactness and Processing Efficiency? |
2006-04-12 |
All |
0 |
| ISSUE-17 |
CLOSED |
Measurements Note issue: will memory consumption be measured during processing? |
2006-04-12 |
All |
0 |
| ISSUE-18 |
CLOSED |
Measurements Note issue: How should results for native language implementations be treated? |
2006-04-12 |
All |
0 |
| ISSUE-19 |
CLOSED |
Spot-check the results for fidelity |
2006-06-01 |
All |
0 |
| ISSUE-20 |
CLOSED |
Increase the number runs per driver to collect statistical data |
2006-06-01 |
All |
0 |
| ISSUE-21 |
CLOSED |
SVG whitespace needs to be handled properly |
2006-06-29 |
All |
0 |
| ISSUE-22 |
CLOSED |
Floating point (and other heavyweight specialized encoding) differential support |
2006-10-06 |
All |
0 |
| ISSUE-23 |
CLOSED |
Interpretation of Distinguishing Bits |
2007-03-14 |
All |
0 |
ISSUE-24
TK |
CLOSED |
Answer http://lists.w3.org/Archives/Public/public-exi/2008Jul/0012.html |
2008-07-24 |
|
0 |
ISSUE-25
Encryption Metadata |
CLOSED |
Where do we specify the metadata used for encrypted EXI |
2008-12-17 |
|
0 |
| ISSUE-26 |
CLOSED |
The number of test cases should be mentioned in evaluation note |
2009-02-25 |
Evaluation Note |
0 |
| ISSUE-27 |
CLOSED |
Evaluation note needs to be clear that PE numbers are implementation-dependent |
2009-02-25 |
Evaluation Note |
0 |
| ISSUE-28 |
CLOSED |
Where should the next event after a self-contained element start? |
2009-03-31 |
EXI Spec |
0 |
ISSUE-29
Regex Complexity |
CLOSED |
Complexity of XML Regex to Restricted Character set feature |
2009-03-31 |
EXI Spec |
0 |
| ISSUE-30 |
CLOSED |
Value QName encoding |
2009-03-31 |
EXI Spec |
0 |
| ISSUE-31 |
CLOSED |
Union type and xsi:type when strict option is true |
2009-03-31 |
EXI Spec |
0 |
| ISSUE-32 |
CLOSED |
Interaction between xsi:type and attribute wildcard |
2009-03-31 |
EXI Spec |
0 |
ISSUE-33
Round-Robin |
CLOSED |
Decide what to do about or if we do round-robin re-use of string table entries |
2009-04-01 |
EXI Spec |
0 |
| ISSUE-34 |
CLOSED |
Implications of broadly applying xsi:type and xsi:nil semantics to all AT(*) event types |
2009-04-08 |
EXI Spec |
0 |
ISSUE-35
CDATA Section |
CLOSED |
Is there anything EXI is ought to do for enabling the preservation of CDATA section? |
2009-04-14 |
EXI Spec |
0 |
ISSUE-36
Content Coding |
CLOSED |
What to do with the appendix section "Content Coding" |
2009-04-28 |
EXI Spec |
0 |
| ISSUE-37 |
OPEN |
The graphs should be linked to raw data in Evaluation Note |
2009-04-30 |
Evaluation Note |
0 |
ISSUE-38
All Group |
CLOSED |
Simplifying xsd:all group behaviour |
2009-05-05 |
EXI Spec |
0 |
| ISSUE-39 |
CLOSED |
how ElementFragmentTypeEmpty can be invoked upon xsi:nil |
2009-05-05 |
EXI Spec |
0 |
| ISSUE-40 |
CLOSED |
strict option and xsi:schemaLocation |
2009-05-05 |
EXI Spec |
0 |
| ISSUE-41 |
CLOSED |
Should SE(*) in built-in grammar be aware of schema-informed grammar? |
2009-05-13 |
EXI Spec |
0 |
| ISSUE-42 |
CLOSED |
schema-informed AT(*) semantics needs to be clarified |
2009-05-27 |
EXI Spec |
0 |
| ISSUE-43 |
CLOSED |
What is the most effective way for non-member implementors to join discussion in order to resolve interoperability issues |
2009-06-03 |
Interoperability Test |
0 |
| ISSUE-44 |
CLOSED |
Implication of EXI strict mode and lexical value preservation |
2009-09-23 |
EXI Spec |
0 |
| ISSUE-45 |
CLOSED |
Support for the use of xsi:type on schemaID element in header options document |
2009-10-06 |
EXI Spec |
0 |
| ISSUE-46 |
CLOSED |
The smart integer encoding rule is supposed to apply to datatypes other than xsd:integer when datatype representation map is used |
2009-10-14 |
EXI Spec |
0 |
| ISSUE-47 |
CLOSED |
Determine the need for mentioning the way EXI treats IEEE float representation |
2009-10-28 |
EXI Spec |
0 |
| ISSUE-48 |
CLOSED |
Discuss and accomodate Don's editorial comment batch on BP |
2009-11-06 |
Best Practices |
0 |
| ISSUE-49 |
CLOSED |
Should the editorial notes be left in the final specification? |
2009-11-06 |
EXI Spec |
0 |
| ISSUE-50 |
CLOSED |
Lack of support for some datatypes in diff |
2010-04-15 |
Interoperability Test |
0 |
| ISSUE-51 |
CLOSED |
Dynamic typing support in EXI |
2010-04-16 |
EXI Spec |
0 |
| ISSUE-52 |
CLOSED |
xsi:nil feature simplification |
2010-04-16 |
EXI Spec |
0 |
| ISSUE-53 |
CLOSED |
Integer representation's sensitivity to min/max value facets of non-integral number dataypes (e.g. float) |
2010-04-28 |
EXI Spec |
0 |
| ISSUE-54 |
CLOSED |
Clarification as to when the sorting of pre-populated entries in local name partition occurs |
2010-06-02 |
EXI Spec |
0 |
| ISSUE-55 |
CLOSED |
Disposition of schema-informed grammar test cases that expect xsi:type and xsi:nil to match AT(*) |
2010-06-15 |
Interoperability Test |
0 |
| ISSUE-56 |
CLOSED |
Whether or not schema-informed AT(*) should be permitted to match xsi:nil and xsi:type attributes |
2010-06-15 |
EXI Spec |
0 |
| ISSUE-57 |
CLOSED |
Whether to or not to, and are there circumstances in which the order of xsi:type and xsi:nil attributes can be relaxed? |
2010-06-22 |
EXI Spec |
0 |
| ISSUE-58 |
CLOSED |
Whether to or not to add a testcase that would exhibit the interoperability of section "9.1 Blocks" that addresses the case in which the would-be last block is empty. |
2010-06-30 |
Interoperability Test |
0 |
| ISSUE-59 |
CLOSED |
Whether to require or not of processors a certain behaviour in lexical preservation mode when xsi:type occurs to indicate grammar switch |
2010-08-23 |
EXI Spec |
0 |
| ISSUE-60 |
CLOSED |
Review the proposed clarification including the judgement made to section 9.2.1 Structure Channel |
2010-09-30 |
EXI Spec |
0 |
| ISSUE-61 |
CLOSED |
RCS involving Unicode character categories were found to exhibit interoperability hitch |
2010-11-03 |
Interoperability Test |
0 |
| ISSUE-62 |
CLOSED |
How custom DTRM affects built-in DTRM, and what exactly the built-in DTRM represents |
2010-11-17 |
EXI Spec |
0 |
| ISSUE-63 |
CLOSED |
Element fragment grammar allows AT event occurrences after CH event |
2010-11-24 |
EXI Spec |
0 |
| ISSUE-64 |
OPEN |
EXI streams in non-strict mode always involve grammar growth to some varying extent upon undeclared element occurrences |
2010-12-08 |
V.Next |
0 |
| ISSUE-65 |
CLOSED |
Some portion of BP needs to be updated to synchronize with EXI 1.0 REC content |
2010-12-23 |
Best Practices |
0 |
| ISSUE-66 |
CLOSED |
Mapping between EXI options and EXI options document |
2011-01-05 |
|
0 |
| ISSUE-67 |
CLOSED |
Contents of Interoperability Test Notes Wiki are not up-to-date |
2011-01-31 |
Interoperability Test |
0 |
| ISSUE-68 |
CLOSED |
Determine the need to do something about prefix in profile, and the best mechanism among proposals |
2011-09-20 |
Profile |
0 |
| ISSUE-69 |
CLOSED |
Determine the need for doing something about value partition in profile, and the best mechanism for doing it |
2011-09-20 |
Profile |
0 |
| ISSUE-70 |
CLOSED |
Determine the best approach to providing a way to detect EXI Profile streams |
2011-09-20 |
Profile |
0 |
| ISSUE-71 |
CLOSED |
What needs to be said about the support for compression? |
2011-09-21 |
Profile |
0 |
| ISSUE-72 |
CLOSED |
Increase profile stream's amenability to decoders so that they are decodable even without knowing the exact numeric threshold values |
2011-09-28 |
Profile |
0 |
| ISSUE-73 |
CLOSED |
Increase profile stream's amenability to devices with abject resources by permitting paring as much footprint as possible |
2011-09-28 |
Profile |
0 |
| ISSUE-74 |
CLOSED |
What's the mechanism to distinguish Profile stream from vanilla EXI 1.0 stream? |
2011-10-26 |
Interoperability Test |
0 |
| ISSUE-75 |
CLOSED |
Whether the Profile specification can dictate a specific way to count the number of characters for names accrued at run time or not |
2011-10-26 |
Profile |
0 |
| ISSUE-76 |
CLOSED |
Did we forget to point to the newer version of Namespaces specification? |
2011-10-26 |
EXI Spec Errata |
0 |
| ISSUE-77 |
CLOSED |
How to best balance the need for limited built-in grammar growth in some and no need in others |
2011-10-31 |
Profile |
0 |
| ISSUE-78 |
CLOSED |
How can optimized implementations manifest the number of characters in profile? |
2011-10-31 |
Profile |
0 |
| ISSUE-79 |
CLOSED |
Independance of parameters in header |
2012-04-12 |
Profile |
0 |
| ISSUE-80 |
CLOSED |
Should be clear that Grammar Learning Parameters do not take into account xsi:type |
2012-04-19 |
Profile |
0 |
| ISSUE-81 |
CLOSED |
Interdependence of grammar parameters |
2012-06-13 |
Profile |
0 |
| ISSUE-82 |
CLOSED |
When to count xsi:type production in the number of learnt productions |
2012-06-13 |
Profile |
0 |
| ISSUE-83 |
CLOSED |
What is the best rule defining the encoding of <p> element? |
2012-10-10 |
Profile |
0 |
| ISSUE-84 |
CLOSED |
Profile spec needs a Conformance section |
2012-11-07 |
Profile |
0 |
| ISSUE-85 |
CLOSED |
The mention of "XML Parser" in appendix D Prefix Workarounds is confusing |
2012-11-28 |
Profile |
0 |
| ISSUE-86 |
CLOSED |
Reuse of productions with terminal AT(xsi:type) |
2012-11-28 |
Profile |
0 |
| ISSUE-87 |
CLOSED |
The way the use of out-of-band paramter values is indicated by <p> element |
2013-02-20 |
Profile |
0 |
| ISSUE-88 |
CLOSED |
Use Profile flexibility with caution |
2013-03-01 |
Profile |
0 |
| ISSUE-89 |
CLOSED |
How to handle NS events in Built-in Element Grammar |
2013-05-22 |
Profile |
0 |
| ISSUE-90 |
CLOSED |
How to handle CM events in Built-in Element Grammar |
2013-05-22 |
Profile |
0 |
| ISSUE-91 |
CLOSED |
Use of terms derivation by restriction, list and unions needs to be clarified throughout the document |
2013-05-29 |
EXI Spec Errata |
0 |
| ISSUE-92 |
CLOSED |
The spec tends to mislead some implementors into believing decimal codec can reuse code from integer codec |
2013-07-10 |
EXI Spec Errata |
0 |
| ISSUE-93 |
CLOSED |
Is there a problem in removing the "at risk" admonition associated with the empty exi:p element |
2013-07-17 |
Profile |
0 |
| ISSUE-94 |
CLOSED |
Wordsmithing |
2013-09-12 |
Canonical EXI |
0 |
| ISSUE-95 |
CLOSED |
Some points for future improvements after FPWD |
2013-09-12 |
Canonical EXI |
0 |
| ISSUE-96 |
OPEN |
Fix a typo "respectfully" in Introduction section |
2013-10-23 |
EXI Spec Errata |
0 |
| ISSUE-97 |
CLOSED |
Clarify what canonical EXI means to text XML |
2013-10-23 |
Canonical EXI |
0 |
| ISSUE-98 |
CLOSED |
Describe how EXI Options and schema options are communicated |
2013-10-23 |
Canonical EXI |
0 |
| ISSUE-99 |
CLOSED |
How does canoncal EXI deal with enveloped signature? |
2013-10-23 |
Canonical EXI |
0 |
| ISSUE-100 |
CLOSED |
Invalid typed attributes/elements in strict mode - wildcard available |
2014-01-13 |
Canonical EXI |
0 |
| ISSUE-101 |
CLOSED |
EXI signature optimization |
2014-02-05 |
Canonical EXI |
0 |
ISSUE-102
brutzman |
RAISED |
Example documentation generator for EXI encoding/decoding |
2014-02-18 |
Primer |
0 |
| ISSUE-103 |
OPEN |
Use of the word "options" to describe EXI Options are confusing |
2014-05-14 |
EXI Spec Errata |
0 |
| ISSUE-104 |
CLOSED |
What is expected of a processor when EXI Options document was omitted |
2014-06-10 |
EXI Spec Errata |
0 |
| ISSUE-105 |
CLOSED |
Signature in Processing Steps |
2015-04-29 |
Canonical EXI |
0 |
| ISSUE-106 |
CLOSED |
Schema(Id) and Canonical EXI consequences |
2015-04-29 |
Canonical EXI |
0 |
| ISSUE-107 |
CLOSED |
Merge multiple CH events |
2015-07-08 |
Canonical EXI |
0 |
| ISSUE-108 |
CLOSED |
Consider the need for permitting to preserve timezone in datetime value canonicalization |
2015-10-14 |
Canonical EXI |
0 |
| ISSUE-109 |
CLOSED |
Consider the need for permitting Canonical EXI without header options |
2015-10-14 |
Canonical EXI |
0 |
| ISSUE-110 |
CLOSED |
What to do with xml:space being preserved in strict mode. |
2015-11-17 |
Canonical EXI |
0 |
| ISSUE-111 |
OPEN |
BSON support |
2016-01-15 |
EXI4JSON |
0 |
| ISSUE-112 |
CLOSED |
Representation of empty elements |
2016-02-22 |
Canonical EXI |
0 |
| ISSUE-113 |
OPEN |
What is the best way to let users specify value strings in schema for pre-population? |
2016-04-02 |
Extended String |
0 |
| ISSUE-114 |
CLOSED |
How to name each of four possible EXI Canonicalization variety |
2016-05-16 |
Canonical EXI |
0 |
| ISSUE-115 |
CLOSED |
XML structure for EXI4JSON |
2016-05-16 |
EXI4JSON |
0 |
| ISSUE-116 |
OPEN |
JSON keys invalid as XML Names |
2016-06-20 |
EXI4JSON |
0 |
| ISSUE-117 |
OPEN |
Name Clash between JSON key names and names used by EXI4JSON |
2016-06-20 |
EXI4JSON |
0 |
| ISSUE-118 |
OPEN |
Do we need flags that indicate keynames must be un-escaped by decoders |
2016-08-03 |
EXI4JSON |
0 |
| ISSUE-119 |
RAISED |
Publicizing EXI capabilities and opportunities |
2016-09-13 |
|
0 |
| ISSUE-120 |
CLOSED |
Canonical EXI should use XSD 1.1 date and time types intead of those of XSD 1.0 |
2018-04-16 |
Canonical EXI |
0 |
| ISSUE-121 |
CLOSED |
Canonical EXI needs clarification on how to canonicalize dateTime values |
2018-04-16 |
Canonical EXI |
0 |
| ISSUE-122 |
CLOSED |
DateTime Canonicalization should preserve seconds field |
2018-04-16 |
Canonical EXI |
0 |