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

Hi Yves,

thanks for your feedback.

The attribute name was simply a cut&paste mistake. You're right, it should be forbiddenCharacters.

About the text saying that the attribute only relates to the translated content:

Why should this also apply to the original text? Is not the content provider of the original text the one who also states the ITS attributes?

Thanks for the Regex suggestion. To me this sounds quite reasonable.

Cheers

Michael

________________________________________
Dr. Michael Kruppa, Senior IT-Consultant 
Tel.: +49 69 972 69 189 Fax: +49 69 972 69 204; E-Mail: michael.kruppa@cocomore.com 
Cocomore AG, Gutleutstraße 30, D-60329 Frankfurt
Internet: http://www.cocomore.de Facebook: http://www.facebook.com/cocomore Google+: http://plus.cocomore.de

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).



-----Ursprüngliche Nachricht-----
Von: Yves Savourel [mailto:ysavourel@enlaso.com] 
Gesendet: Montag, 13. August 2012 14:38
An: public-multilingualweb-lt@w3.org
Betreff: RE: [ACTION 189] Split special requirements into several data categories 

Hi Micha,

On ForbbidenChars:

- The attribute is called specialRequirementsForbiddenChars but the examples use forbiddenCharacters. The name in the list of attribute probably should be forbiddenCharacters.

- The text is several places states that this data category is to specify forbidden characters in the translation. I'm not saying it's wrong, but I wonder if its shouldn't be less specific and apply to the content in general (source and translation).

- For the value of forbiddenCharacters: Here is a first stab at a description:

A forbiddenCharacters attribute that contains a regular expression matching the characters which are not allowed. The regular expression syntax is restricted to a basic character class pattern: the enumeration of the characters between square brackets ('[', and ']'). One or more operators '-' may be used to indicate ranges. The prefix '^' may be used to invert the selection. The characters '\', '-', ']', '[' and '^' must be prefixed with '\' when used as literal. Any literal character may be expressed using the \uHHHH notation, where HHHH is the Unicode code point of the character.
Examples:
- [abc] disallows the characters 'a', 'b' and 'c'. 
- [a-c] disallows the characters 'a', 'b' and 'c'.
- [a-cA-C] disallows the characters 'a', 'b', 'c', 'A', 'B', and 'C'.
- [^abc] disallows any characters except 'a', 'b', and 'c'.
- [^a-c] disallows any characters except 'a', 'b', and 'c'.
- [\u0061-c] disallows any characters except 'a', 'b', and 'c'.
- [\-\[\]] disallows the characters '-', '[' and ']'.

Arle may be able to express this in better English.

Cheers,
-ys

Received on Monday, 13 August 2012 13:11:37 UTC