RE: [ACTION 189] Split special requirements into several data categories

Hi Micha,

> I hope, that my interpretation of displaySize was correct?
> ...
> I’m looking forward to your comments.


For displaySize and storageSize:

Both data categories look the same. Is that on purpose? It seems to me that storageSize is generally ok. But displaySize would require additional information such as font information or units, etc. My guess is that we should probably drop it if it's too complicated to define in the time we have.

More notes on storageSize:

- the definition of storageSize says: "...the number of allowed characters". I'm guessing it should be "...the number of allowed bytes". And we could be more specific with "...the maximum number of byte allowed".

- I wonder if we should specify UTF-8 as the default for storage. Having a default value will allow not to specify the attribute and I'm guessing this may lead to mistakes as many assume classic extended characters such as 'ä' are simply a single byte, while they are not. Maybe storageEncoding should have no default and should be always specified?

- Like for forrbiddenCharacters this data category only talks about the translation. My impression is that it should apply to the content, source or target.

Cheers,
-ys

Received on Monday, 13 August 2012 12:56:46 UTC