Re: forbiddenCharacters data category - related to [ACTIOn-189]

Hi Yves, all,

thanks for the update, Yves. Just two comments.

About the regex: the example is not compatible with XML Schema regex:

- the escaping mechanism with \uHHHH would need to be converted to numeric
character references &#xHHHH;
- <> need to be converted to &lt;&gt;
- Both \u0000 and \u001F are forbidden characters in XML.

We should either drop the regex at all, use XML Schema regex (I say your
counter arguments, so this is probably no option) or define a clear
specification about what to do when one uses XML Schema regex, e.g. have a
pointer to characters that are disallowed in XML and XML Schema regex
anyway.

Aslo, about
"The information applies to the textual content of the element,
*including* child
elements.": should this include also attributes?

Best,

Felix

Am Freitag, 24. August 2012 schrieb Yves Savourel :

Hi everyone,
>
> Please find attached a new proposal for the Forbidden Characters data
> category.
>
> Most of it is the same as Michael's initial text, I've just:
>
> - re-worded a part that implied the data category was applying to
> translated content only.
>
> - defined the regex syntax for the forbiddenCharacters value (it would be
> nice if we could have a pattern for it in the XML schema).
>
> Cheers,
> -yves
>
>