- From: Yuri Delendik <yury_exi@yahoo.com>
- Date: Wed, 17 Sep 2008 21:49:45 -0700 (PDT)
- To: public-exi@w3.org, john.schneider@agiledelta.com
Hi John, That helps, but raises another question: The 4th Draft does not have explain that "enumerations are represented according the restricted character set associated with their base type". Closest thing in the text is that an enumeration will be presented by their base type only when "... for schema types derived from others by union and their subtypes, QName or Notation and types derived therefrom by restriction". Will the next draft have different representation of enumerations? Thanks -----Original Message----- From: public-exi-request@w3.org [mailto:public-exi-request@w3.org] On Behalf Of John Schneider Sent: Wednesday, September 17, 2008 12:42 PM To: 'Yuri Delendik'; public-exi@w3.org Subject: RE: [EXI] Restricted charset for enum Hi Yuri, Where preserve.lexicalValues = true, enumerations are represented according the restricted character set associated with their base type (see table 7-2). E.g., an enumeration of integers would end up using the restricted character set {#x9, #xA, #xD, #x20, +, =, [0-9]}. EXI does not require the encoder/decoder to build and track a different restricted character set for each enumeration. Hope this helps!, John > -----Original Message----- > From: public-exi-request@w3.org > [mailto:public-exi-request@w3.org] On Behalf Of Yuri Delendik > Sent: Tuesday, September 16, 2008 9:46 PM > To: public-exi@w3.org > Subject: [EXI] Restricted charset for enum > > > (Section 7. Representing Event Content) > When preserve.lexicalValues = true, is enumeration presented > as a String with restricted characters set? It make sence to > define it as a set of characters that can be found in values > (? plus whitespaces). > > Thanks. > >
Received on Thursday, 18 September 2008 04:50:26 UTC