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

AW: Grammar String

From: Peintner, Daniel <daniel.peintner.ext@siemens.com>
Date: Wed, 21 Dec 2016 14:46:54 +0000
To: Takuki Kamiya <tkamiya@us.fujitsu.com>, "public-exi@w3.org" <public-exi@w3.org>
Message-ID: <D94F68A44EB1954A91DE4AE9659C5A980FF9F664@DEFTHW99EH1MSX.ww902.siemens.net>

I was practically exploring the concept of "grammar strings" and was asking myself why we limit the technique to strings. In my code experiment it felt easy to just use the existing EXI Enumeration codec which is type-aware already.

Having said that, I think it would be good to allows this kind of annotation also for other types to enumerate likely values.

This might not be anymore part of the extended string though.

Any thoughts on this?

Thanks and I wish you all a Merry Christmas and a Happy New Year,

-- Daniel

Von: Peintner, Daniel (ext) [daniel.peintner.ext@siemens.com]
Gesendet: Dienstag, 15. November 2016 17:08
An: Takuki Kamiya; public-exi@w3.org
Betreff: AW: Grammar String

Hi Taki, all,

the content looks good to me.

I was wondering whether we want to have some notion/flag to make clear that a certain annotation/appinfo is meant to create grammar strings.

e.g,  <xs:appinfo exi:prepopulateValues="true" xmlns:exi="http://www.w3.org/2009/exi" > ...

What do people think?


-- Daniel

P.S: I changed the style of the document to HTML5~

Von: Takuki Kamiya [tkamiya@us.fujitsu.com]
Gesendet: Samstag, 5. November 2016 01:41
An: public-exi@w3.org
Betreff: Grammar String


Per discussed during the last telecon, I added content in Grammar String section [1]
in Extended String document.

[1] http://www.w3.org/XML/EXI/docs/extendedString/exi-extString.html#grammarString

Takuki Kamiya
Fujitsu Laboratories of America
Received on Wednesday, 21 December 2016 14:47:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:47:21 UTC