[ACTION-160] (related to [ACTION-135] too) Summarize specialRequirements

Hi all,

I had the action item to summarize yesterday's call discussion on specialRequirements:

Based on the email discussion (ACTION-135):

- There was a consensus that the three aspects of the potential data category ("storage size", "display length" and "forbidden characters") were somehow related but distinct facets.

- It was pointed out that Schematron or XSD constraints mechanism could possibly implement at least part of the requirements. Felix was tasked to provide examples.

- It was pointed out that similar work (for either "storage size" and "display length" or both) was being done on the XLIFF side, and a work document would be available soon (within weeks). DavidF was tasked with making sure the document would be posted on this list as soon as possible.

[I'm also CCing Fredrik Estreen (who is looking at this issue in XLIFF) just so he is in this loop].

- The conclusion was that, only the "storage size" property was seemingly stable and that the two other aspects ("display length" and "forbidden characters") were more difficult to define, and that it would be good to see what mechanism would be suggested in Fredrik's document.

To add to this summary, here I a possible way to represent "storage size" as a separate data category:

<its:maxStorageSizeRule selector="//title"
 maxStorageSize="100" storageEncoding="UTF-16"/>

where maxStorageSize is mandatory and expressed in bytes and storageEncoding is optional and defaults to UTF-8 (?)

I suppose there is no reason not to have local support as well:

 <title ist:maxStorageSize="100" its:storageEncoding="UTF-16">text</title>


Received on Friday, 6 July 2012 04:21:58 UTC