W3C home > Mailing lists > Public > public-exi@w3.org > March 2016

AW: ACTION-736: Check issue 100 to see canonical exi section 4.2.2 properly handles it

From: Peintner, Daniel (ext) <daniel.peintner.ext@siemens.com>
Date: Wed, 16 Mar 2016 14:52:51 +0000
To: Efficient XML Interchange Working Group <public-exi@w3.org>
Message-ID: <D94F68A44EB1954A91DE4AE9659C5A980FE73BFA@DEFTHW99EH1MSX.ww902.siemens.net>
All,

I had the Action to look into issue 100 [1].

I think the Canonical EXI draft version [2] should be ok w.r.t. issue 100.

In step #1 productions which are not usable (e.g., EXI Profile) are removed.

In the second step the event is selected that matches most precisely.

While cross-checking I detected another issue.
I think we better change the order of attribute selection in this section [3].

The current order for attribute events is as follows:
    a. AT ( qname ) [schema-typed value]
    b. AT ( uri : * ) [schema-typed value]
    c. AT ( * ) [schema-typed value]
    d. AT ( qname ) [untyped value]
    e. AT ( * ) [untyped value]

Form the point of view of an implementation I think it is more straight-forward to move "AT ( qname ) [untyped value]" up.
The reason is that an implementation is likely to first check the qname and if the qname exists and it checks the value.
Hence my proposal would be to change the order as follows.

    a. AT ( qname ) [schema-typed value]
    b. AT ( qname ) [untyped value]
    c. AT ( uri : * ) [schema-typed value]
    d. AT ( * ) [schema-typed value]
    e. AT ( * ) [untyped value]

I am a bit unsure whether b or c should come first.

Any thoughts?

Thanks,

-- Daniel

[1] https://www.w3.org/2005/06/tracker/exi/issues/100
[2] https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#exiEvents
[3] https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#N66353





________________________________
Von: Efficient XML Interchange Working Group Issue Tracker [sysbot+tracker@w3.org]
Gesendet: Dienstag, 8. März 2016 17:09
An: public-exi@w3.org
Betreff: ACTION-736: Check issue 100 to see canonical exi section 4.2.2 properly handles it

ACTION-736: Check issue 100 to see canonical exi section 4.2.2 properly handles it

https://www.w3.org/2005/06/tracker/exi/actions/736<&smime=14.3.123.2https://www.w3.org/2005/06/tracker/exi/actions/736>

Assigned to: Daniel Peintner
Received on Wednesday, 16 March 2016 14:53:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 16 March 2016 14:53:19 UTC