Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <1CE2FB42E90B614C98BC172FAB12D4C002D3FCFF8A@DEMCHP99E55MSX.ww902.siemens.net>
Date: Thu, 1 Mar 2012 15:45:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <52B10DF8-11D1-44FE-8A8B-184BB0AE12F2@sensinode.com>
References: <1CE2FB42E90B614C98BC172FAB12D4C002D3FCFF8A@DEMCHP99E55MSX.ww902.siemens.net>
To: "Kaebisch, Sebastian" <sebastian.kaebisch.ext@siemens.com>
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] SenML
Precedence: list

Hi Sebastian,

Your suggestions for optimizing the XSD for EXI use would be very =
welcome. Looking forward to it!=20

Thanks,
Zach=20

On Feb 29, 2012, at 6:26 PM, Kaebisch, Sebastian wrote:

>=20
> Hi all,=20
>=20
> I have some improvement suggestions concerning the XSD which is used =
for senML EXI coding. Right now, there are some types defined which are =
not optimal for small embedded devices. E.g., attribute "t", "ut", and =
"ver" are typed as "integer". I think, "int" will be enough in that =
context. Furthermore, I would like to suggest to make some changes in =
the XSD definitions (e.g., using enumerations) to make the EXI message =
instances more compact. I will prepare an XSD proposal for the next week =
for further discussions.
>=20
> Best regards
> Sebastian K=E4bisch
>=20
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

--=20
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297