W3C home > Mailing lists > Public > public-exi@w3.org > October 2008

RE: [EXI] NS event encoding for default namespace

From: Taki Kamiya <tkamiya@us.fujitsu.com>
Date: Tue, 7 Oct 2008 14:44:49 -0700
To: <santhana@huawei.com>
Cc: <public-exi@w3.org>
Message-ID: <A345700B79064669847616B4798ED5F9@catarojp>

Hi Santhanakrishnan,

Sorry for the belated response.

When you turn on preserve.prefix option, the event sequence you described
is what you would expect from EXI processor. The NS event is necessary to
bind an URI to a prefix, which in this case is an empty prefix.

Implicit determination of prefix indicated by absence of such binding may work,
but will complicate the way EXI processors have to follow, which we wanted to
avoid as much as possible. There have been proposed various ways to change
NS encoding mechanism within the WG, but we agreed the current way is the
best given its simplicity and little file size over head in general.

Hope it helps,

-taki


________________________________

From: public-exi-request@w3.org [mailto:public-exi-request@w3.org] On Behalf Of santhanakrishnan
Sent: Friday, August 29, 2008 7:00 AM
To: public-exi@w3.org
Subject: [EXI] NS event encoding for default namespace


Hi EXI WG
        Should the NS event be encoded for default namespace also.

Assume the below XML document

<root xmlns="www.urn.foo">
</root>

Is the following sequence correct ?

SD
SE(root)
NS uri="www.urn.foo" prefix=""
EE
ED

I dont feel any use of the NS event here as it is a default namespace case. Please clarify.


regards
Santhanakrishnan
Received on Tuesday, 7 October 2008 21:45:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:52:43 UTC