- From: Taki Kamiya <tkamiya@us.fujitsu.com>
- Date: Tue, 14 Oct 2008 16:49:06 -0700
- To: "'Ed Day'" <edday2006@gmail.com>, <santhana@huawei.com>
- Cc: <public-exi@w3.org>
Hi Santhanakrishnan and Ed, When schemaID [1] value is set to be empty in header options, the EXI stream is schema-informed with XML Schema built-in type definitions, but with no user-defined types. In such an EXI stream, if xsi:type="xsd:integer" is used in the context of a built-in element grammar [2], the grammar for xsd:integer is used for encoding the element content. Hope it helps, [1] http://www.w3.org/XML/Group/EXI/docs/format/exi.html#key-schemaIDOption [2] http://www.w3.org/XML/Group/EXI/docs/format/exi.html#builtinElemGrammars -taki -----Original Message----- From: public-exi-request@w3.org [mailto:public-exi-request@w3.org] On Behalf Of Ed Day Sent: Tuesday, October 14, 2008 7:07 AM To: santhana@huawei.com Cc: public-exi@w3.org Subject: Re: [EXI] Handling of xsi:type and xsi:nil attributes in Built-in encoding Hi Santhanakrishnan, On Tue, Oct 14, 2008 at 4:32 AM, santhanakrishnan <santhana@huawei.com> wrote: > Hi WG > When xsi:type and xsi:nil attributes occur in an xml instance how to > handle them for pure Built-in EXI encoding. > > Consider the following case > <product xsi:type="xsd:integer">123</product> > > How the character content 123 will be encoded in the pure built-in EXI > encoding. As a string or as integer ? As a string. There was a proposal at one time to use xsi:type information as a means of doing typed encoding without a schema, but it was not implemented. > > regards > Santhanakrishnan Ed Day Objective Systems, Inc. http://www.obj-sys.com
Received on Tuesday, 14 October 2008 23:49:55 UTC