Call for consensus - storageSize and displaySize

Hi all,

can we find an agreement on what storageSize and displaySize should actually be?

In yesterday's call I understood, that storageSize should simply depict the maximum byte size of a particular content (not only the translated one but also the original one). If this is so, I do not quite understand why we should need the attribute storageEncoding in this data category? Could somebody please explain this to me? If not, can we simply drop the storageEncoding attribute?

Secondly, we have been discussing about the displaySize attribute. I'm not 100% sure what the purpose of this data category is. Could somebody please explain what it means, what are typical use cases and whether it should be based on character or byte counts?

I would ask everyone to find an agreement on these two topics by next Thursday.

Thank you very much



Dr. Michael Kruppa, Senior IT-Consultant
Tel.: +49 69 972 69 189 Fax: +49 69 972 69 204; E-Mail:<>
Cocomore AG, Gutleutstraße 30, D-60329 Frankfurt
Internet:<> Facebook: Google+:<>
Cocomore ist aktives Mitglied im World Wide Web Consortium (W3C) und im Bundesverband Digitale Wirtschaft (BVDW)
Cocomore is active member of the World Wide Web Consortium (W3C)
Vorstand: Dr. Hans-Ulrich von Freyberg (Vors.), Dr. Jens Fricke, Marc Kutschera, Vors. des Aufsichtsrates: Martin Velasco, Sitz: Frankfurt/Main, Amtsgericht Frankfurt am Main, HRB 51114

dmexco 2012 in Köln: Besuchen Sie unseren Messestand auf der internationalen Leitmesse für die Digitale Wirtschaft am 12. und 13. September 2012. Sie finden uns in Halle 7, Stand E057.
dmexco 2012 in Cologne: Come to see us on September 12 and 13 at the Digital Marketing Exposition and Conference (hall 7, stand E057).

Received on Friday, 24 August 2012 14:09:31 UTC